How to get Harbinger jobs after its $240M raise

What did Harbinger announce, and which jobs will it create?

Harbinger announced a $240M Series D on November 5, 2026. The money pays for a push beyond electric delivery trucks into defense, autonomy software and battery energy storage, so the company will be hiring for two very different kinds of work at once. The Southern California startup has now raised more than $650 million since it was founded in 2021. Tiger Global, Capricorn's Technology Impact Fund and Ridgeline co-led the round, and existing backers including FedEx put in money too. FedEx's involvement makes sense. In September it ordered 2,000 electric delivery vans from Harbinger in a deal worth more than $300 million, with delivery due by the end of 2027. The truck business needs people who can ship at volume. The newer businesses need people who can build things Harbinger has never built.

The defense work is already under way. In May, Harbinger partnered with American Rheinmetall to develop uncrewed ground vehicles for the US military, and in June it set up a defense unit called Harbinger Praesidia. American Rheinmetall then won an 18-month Army contract for Project Sustainment, an effort to build autonomous supply vehicles, and Harbinger is supplying the hybrid platform. The vehicle has no cab, uses a gas engine as a generator for an all-electric drivetrain, and carries up to 18,000 pounds. Harbinger also bought the autonomous-driving company Phantom AI. Put that together and you can predict the openings: vehicle integration, autonomy software, high-voltage systems, test and validation, and program roles for people comfortable with both government customers and startup pace.

You can see what Harbinger already hires for in recent job-board listings. They include power electronics, firmware for motor control on bare-metal and RTOS systems, electrical systems engineering, battery manufacturing process, design release for the frame, and end-of-line test equipment. Most roles are in Garden Grove, California, and some manufacturing roles are in Sturgis, Michigan. Job boards put the open-role count anywhere from about 40 to 75, and that number will change quickly after a raise this size. My advice: don't wait for a posting with "defense" in the title. The military platform is derived from the commercial chassis, so the engineers who build the trucks will also build the military version. A strong EV CV gets you most of the way.

Which keywords should an EV engineer mirror for Harbinger's defense roles?

Start by copying the exact technical terms from the posting. Add defense vocabulary only where your experience actually backs it up. ATS filters and recruiters both match on the words the hiring manager wrote. If a Harbinger listing says "high-voltage systems integration," "RTOS," "motor control" or "end-of-line test," use those phrases word for word, ideally in your skills section and again in a bullet that proves them. Electric truck engineering jobs share a familiar core vocabulary: HV architecture, battery pack and BMS, inverter and DC-DC, CAN and J1939, DFMEA and PFMEA, DVP&R, PPAP and APQP. Don't soften these into vaguer wording. "Worked on battery systems" won't match any filter a recruiter sets up.

Defense programs have their own vocabulary, and much of it maps onto commercial work. Ruggedization and environmental qualification are close to the automotive validation you've probably done. If you've run vibration, thermal cycling or ingress-protection tests, say so and name the standards you tested to. Requirements traceability, verification and validation, and configuration control are everyday terms in defense, and most automotive engineers already do this work under ISO 26262 or ASPICE. Autonomy roles will look for perception, sensor fusion, ROS, drive-by-wire and teleoperation. The rule is simple: only use a defense term you could defend in an interview. A recruiter at a defense-adjacent startup will quickly spot "MIL-STD-810" on a CV that has no test work behind it.

This may sound backwards, but your commercial experience is the selling point, not something to hide. Harbinger's pitch to the Army is a platform derived from its commercial trucks, which is cheaper and faster to field than a vehicle designed from scratch for the military. So the company wants people who understand production cost, supplier quality and volume manufacturing. Keep phrases like "production launch," "cost-down," "start of production" and "supplier PPAP" prominent. If you come from a legacy OEM or a tier-one supplier, name the vehicle programs you supported and their volumes. Other hardware startups that just raised money need the same thing. Our guide to how engineers reposition for a space company after a big funding round covers a similar move from telecom and defense into space.

Should you mention security clearance eligibility on your CV?

Only mention a clearance if you hold one or the posting asks about it. Otherwise, state your work-authorization status plainly and leave it there. An active clearance is a real asset, so if you have one, put the level and status on a single line near the top of your CV. If you don't have one, skip "clearance eligible." You can't grant yourself eligibility, and recruiters know that. Harbinger's Army work is currently a prototype effort run through a prime contractor, and nothing public says its engineering roles need a clearance today. Don't guess. Read each posting carefully. If it says nothing about clearance, the question isn't part of the screening yet, and any space you spend on it is space taken from your engineering proof.

Export control is more likely to matter than clearance. Defense hardware and its technical data often fall under ITAR. Under those rules, a "U.S. person" is a citizen, national, green-card holder, asylee or refugee. That's a separate question from clearance: ITAR status decides whether you can see controlled technical data without an export license, while a clearance decides whether you can see classified information. Employers hiring for ITAR-controlled work usually say so in the posting. If a Harbinger listing includes that language, add a short line such as "U.S. citizen" or "U.S. permanent resident" under your contact details. That saves the recruiter a screening call and stops you from being filtered out on a question you'd pass.

If you're on an H-1B, OPT or another visa, don't let the defense headlines put you off. The commercial trucks, the energy storage business and much of the software work may never involve controlled data, and the FedEx van order alone means a lot of manufacturing work through 2027. Apply to those roles with confidence. Some privacy rules apply to everyone: never put your Social Security number, date of birth or clearance investigation details on a CV, because it gets copied into several systems you don't control. Veterans have an advantage here and should use it. A line like "U.S. Army, 2014–2020, motor transport operator" tells a team building uncrewed supply vehicles that you understand the people who'll use them.

How do you show hardware impact with numbers on an EV engineer resume?

Put a measurable unit in every bullet: cost per unit, cycle time, yield, test hours, failure rate, weight, range or build volume. Hardware engineers often describe what they were responsible for ("responsible for inverter thermal design") when hiring managers want the result ("cut inverter junction temperature at peak load, which let the team drop a heatsink and lower unit cost"). Add your real figures to that structure, and only use numbers you can explain to someone who knows the system well. A startup that just took $240 million from investors expecting a production ramp cares most about three things: did your work ship, did it get cheaper, and did it pass testing. Write each bullet as action, system, metric and scale, in that order.

Each role has its own natural metrics. Battery manufacturing engineers should lead with yield, takt time, scrap rate and line uptime. Power electronics and HV systems engineers can cite efficiency, power density, thermal margin and the number of validation hours or test cycles passed. Firmware engineers can point to control-loop timing, boot time, memory footprint or how many fielded units run their code. Systems engineers should count the requirements they managed, the interfaces they owned and the issues closed before launch. Test engineers can count stations built, coverage gained and defects caught before customer delivery. If a number is confidential, use a percentage or a rough size instead. "Reduced warranty claims by roughly a third" is honest, safe under most NDAs, and still makes the point.

For defense-leaning roles, add a second kind of proof: reliability in harsh conditions and experience with demanding customers. Harbinger's uncrewed platform is built to run silently on battery, cover long distances in hybrid mode and supply power to equipment in the field. Any work you've done on durability, thermal management in extreme climates or power export applies directly. Fleet experience counts too. If you supported vehicles for a large commercial fleet, give the fleet size and uptime targets. A logistics customer and an Army sustainment unit want very similar things from a truck. Keep your CV to one page if you have under ten years of experience and two pages at most beyond that. Cut any bullet without a number unless it explains the scope of your work.

How do you check your CV against a real Harbinger posting?

The fastest way to check fit is to put a live Harbinger job description next to your CV and look for missing skills, keywords and seniority signals before you apply. Take two real examples. A recent Harbinger listing for a Software Engineer, Firmware describes bare-metal and RTOS firmware driving advanced motor control systems. Another, for a Systems Engineer, Electrical, asks for 5+ years of systems engineering in automotive or a similar field. If your CV says "embedded developer" and lists C but never mentions RTOS, motor control or your microcontroller family, you're asking the recruiter to guess, and most won't. Use the posting's terms, prove each one with a quantified bullet, and state the years of experience they asked for in your summary.

HRLens does that side-by-side check for you. Upload your CV to the free HRLens CV analysis and paste in the full text of the Harbinger posting. Copy the text rather than a LinkedIn or Indeed link, because those sites block automated fetching. The analysis lists the skills the job asks for that your CV doesn't show. The free result also gives you a score out of 100 and category scores for experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility. That tells you whether the problem is missing keywords or a layout the ATS can't read. If you'd like to see the process first, this walkthrough on checking whether your CV matches a job description covers it step by step.

Don't mass-apply. Pick two or three Harbinger roles that genuinely fit, tailor a version for each, and keep track of which version you sent where. A commercial HV systems role and a Praesidia autonomy role need different top thirds of the CV, and one generic document sent to both will be a weak fit for each. Every HRLens analysis also creates ATS-friendly rewritten CVs in six templates that use the job's keywords. If your current CV is an old Word file built for a different industry, it's often quicker to start fresh in the HRLens CV builder: paste in your old CV, say you're targeting an EV-to-defense role, refine it by chat, and run the analysis again. Two tailored applications with a referral usually beat twenty generic ones.

Frequently asked questions