The EV sector has attracted more engineering talent in the past five years than almost any other industry. It has also produced more hiring mistakes.
The combination of extreme urgency, a shallow talent pool, and a set of technical requirements that don’t map neatly onto any single prior sector has created conditions where even well-resourced companies get their briefs wrong, their timelines wrong, and their candidate assessments wrong with notable regularity.
This guide is for Heads of Talent, VPs of Engineering, and founders at EV companies who want to hire better. It covers the most common mistakes in EV talent acquisition and what to do instead.
Mistake 1: Writing Briefs That Don’t Reflect the Actual Role
The most common source of bad EV hires is a brief that describes an idealised candidate rather than the person who will actually succeed in the role. This takes a few consistent forms.
Overstacking requirements is widespread. EV companies routinely write job specifications that require ten or more years of EV-specific experience, deep expertise in both hardware and software, and familiarity with automotive SPICE, ISO 26262, and AUTOSAR simultaneously. The number of candidates who genuinely meet all of those requirements is very small. The result is either a long vacancy or a hire who looks good on paper but was oversold at interview.
Confusing automotive experience with EV experience is also common. A mechanical engineer with fifteen years at a traditional OEM brings real value to an EV programme, but their experience with combustion powertrain architecture, fuel systems, and exhaust engineering may be largely irrelevant. The more useful question is which elements of their experience transfer directly to the EV context and which need to be learned. Briefs that don’t make this distinction produce shortlists that are hard to evaluate.
Mistake 2: Underestimating the Hardware/Software Hybrid Requirement
Modern EV development is a deeply integrated hardware-software engineering challenge. Battery management systems, motor controllers, thermal management systems, and chassis dynamics are all increasingly software-defined. The engineering teams that build them need people who can work fluidly across the hardware-software boundary, not specialists who sit firmly on one side of it.
The mistake most EV companies make is hiring for hardware and software separately and assuming the integration will happen naturally. It doesn’t. The roles that create the most value in EV development are the ones that sit at the boundary: embedded software engineers who understand power electronics, systems engineers who can own the full signal chain from sensor to actuator, and integration engineers who can diagnose failures that span the hardware-software interface.
These profiles are hard to find and easy to lose to the large OEMs who can offer stronger compensation packages. Identifying them requires looking beyond conventional job title searches and understanding what specific technical experiences in a candidate’s background indicate genuine cross-domain capability.
Mistake 3: Failing to Compete on Compensation
EV talent at senior level is being recruited by Tesla, Rivian, Lucid, BMW, and Volkswagen Group simultaneously. Startups and scale-ups that benchmark their compensation against their own funding stage rather than against the market they are actually competing in will consistently lose their top candidates.
The specific areas where compensation mismatches are most damaging are base salary for senior engineers (where OEM packages are often significantly higher than growth-stage EV companies budget for), equity structures that don’t reflect the actual risk-reward profile of joining an earlier-stage company, and relocation support for candidates who need to move to access the role.
Being honest about where your compensation sits relative to the market, and structuring offers that compete on the dimensions where you can win (equity upside, technical challenge, pace of development, mission) rather than trying to match OEM base salaries you can’t afford, produces better outcomes than pretending the gap doesn’t exist.
Mistake 4: Ignoring the Functional Safety Requirement Until It’s Too Late
ISO 26262 functional safety expertise is not a nice-to-have in EV development. It is a regulatory and commercial requirement for any company selling into automotive OEM supply chains or producing vehicles for road use. The mistake many EV companies make is treating it as a late-stage hire, bringing in functional safety engineers once the architecture is already set.
At that point, retrofitting functional safety into a system design that wasn’t built with it in mind is expensive, time-consuming, and sometimes impossible without fundamental redesign. Hiring functional safety expertise early, even at a senior individual contributor level rather than a full team, and ensuring that ASIL decomposition and safety case development are embedded in the engineering process from the start, is significantly cheaper than the alternative.
How Storm4 Supports EV Hiring
Storm4’s Electric Vehicle recruitment team works with EV companies across the full hardware-software spectrum, from powertrain and battery system engineers through to embedded software, functional safety, and systems integration.
Our connections into Autonomous Vehicle software recruitment and Future Mobility recruitment give us reach into the cross-domain engineering talent that EV programmes increasingly need, and our Energy Storage recruitment network means we can support the full vehicle and storage system hiring picture.
Submit your vacancy and our team will be in touch.
