From OEM to EV/AV Startup: What Actually Transfers

I have recruited across both worlds: Fortune 500 automotive and pre-revenue startups scaling to thousands of employees. The engineers who land well at startups and the ones who wash out inside six months are not separated by technical skill. They are separated by one thing: how they understood what the move actually required before they took it.

This is a practitioner's guide to that gap. What OEM experience genuinely prepares you for. What creates friction. And how to position yourself for the companies that are actively looking for exactly what you have.

The Assumption That Gets OEM Candidates Rejected

The most common mistake I see from OEM candidates interviewing at startups is leading with institutional credibility. Ford. GM. Stellantis. Tier 1 suppliers. These are powerful signals in the incumbent world. At a Series B EV company, they can read as liability.

Startup hiring managers worry about one thing above all others: will this person move fast enough? Not because startups are chaotic for sport, but because their runway is finite and their milestones are not negotiable. When an OEM candidate spends an interview explaining the scale of their organization, the breadth of their team, and the sophistication of their process, the startup interviewer hears: "I am used to doing things slowly, with a lot of support, and I have never had to build from zero."

That perception, fair or not, kills more OEM-to-startup transitions than any skills gap. Addressing it proactively is the whole game.

What Genuinely Transfers

Systems-level thinking under constraint

If you have spent years working on a program with 50 interdependencies, managing handoffs between powertrain, chassis, body, software, and supplier, you understand systems thinking in a way that a pure software engineer rarely does. Hardware integration is real. Tolerances are real. Late supplier deliveries are real. Startups building physical vehicles need people who have lived through a launch program and know what actually breaks.

This transfers directly. The key is framing it as velocity experience, not process experience. "I have launched a program under a compressed timeline with constrained resources" lands better than "I managed cross-functional alignment at scale."

Supplier relationships and supply chain judgment

Startups typically lack the purchasing leverage that OEMs spend decades building. An engineer who has navigated Tier 1 supplier relationships, who knows what a good SOW looks like, who can tell a vendor relationship that will hold from one that will collapse under pressure: that is genuinely rare and genuinely useful.

If you have negotiated tooling agreements, managed PPAP timelines, or been the person who talked a supplier out of a critical path delay, say so directly. Startups are buying that judgment, not just your years of experience.

Quality and safety rigor

FMEA, DFMEA, DVP&R, functional safety. The OEM world does not move fast, but it is not wrong about everything. The discipline around safety-critical systems that large programs require is exactly what eVTOL and autonomous vehicle companies need as they approach certification. Joby Aviation has 242 open roles on my board. Archer has 155. Both are navigating FAA certification timelines that require exactly the kind of structured quality thinking that OEM programs beat into their engineers.

The translation: your OEM rigor is not a liability. It is a feature, if the company is past the prototype stage and approaching production or certification. Know where your target company sits on that arc before you interview.

Cross-functional muscle memory

OEM programs require you to speak manufacturing, speak software, speak legal, speak procurement, all in the same week. Startups desperately need generalists who can hold context across disciplines. The engineer who has only ever talked to other engineers in a startup environment often struggles when the company hits 150 people and suddenly needs someone who can run a meeting with finance, legal, and an external partner all in the room.

Your cross-functional experience from OEM programs is a real advantage. Name it specifically: "I have been the technical point of contact for external partners, legal review, and manufacturing sign-off simultaneously." That is startup-ready language.

What Gets You in Trouble

Approval cycle dependency

In a large OEM, getting sign-off requires building consensus across multiple stakeholders, presenting to review boards, and waiting. That is appropriate at the scale those organizations operate. At a startup, waiting for approval reads as inability to move. The engineers who struggle most are the ones who have unconsciously learned to defer decisions upward, even small ones.

Before you interview, audit your own behavior. When was the last time you made a significant technical decision without getting sign-off? If you struggle to answer that, practice it. Startups will ask you directly: "Give me an example of a decision you made without asking anyone." Have a real answer.

Scope protection as identity

OEM roles are defined. You own a specific subsystem, a specific set of deliverables, a specific team. That clarity is functional in a large organization. At a startup with 80 people, the person who says "that is not my lane" is a problem. The person who says "I will pick it up, it needs doing" builds trust and gets promoted.

Startups look for people who instinctively expand their scope when there is a gap, not people who guard their defined territory. If your OEM experience has conditioned you toward the latter, be honest with yourself about it before taking the leap.

Tool and process expectations

Mature OEM environments have enterprise systems, dedicated IT, legal support, established vendor relationships. Startups often have a Slack channel, a Google Drive, a half-built ERP they switched to last quarter, and one overworked paralegal. The adjustment is real. Engineers who thrive are the ones who can solve problems without infrastructure. The ones who struggle spend the first three months waiting for tools that will not arrive.

What Startup Interviewers Are Actually Screening For

After hiring across both environments, I have found that startup interviews for OEM candidates are really asking three questions, even when they are phrased differently.

First: can you operate without a structure that does not exist yet? Every behavioral question about ambiguity, first principles, and building from zero is asking this. Answer with stories where you created the structure, not stories where you navigated one.

Second: will you stick around long enough to matter? Startups invest heavily in onboarding people who know how to operate in large organizations and then need time to recalibrate. They want confidence that you are not going back to an OEM in 18 months because the pace was uncomfortable. Be honest about what drew you to the startup environment and what you are willing to trade off.

Third: can you tell us what you actually built? Not what program you supported. Not what team you were on. What did you personally build, decide, or change? OEM candidates often struggle here because their contributions are genuinely hard to isolate from a large program. Do that work before the interview. Trace a clear line from your individual decisions to a measurable outcome.

How to Position the Move on a Resume and in Interviews

Lead with output, not organization. "Delivered propulsion system integration for a 150,000-unit annual volume platform, on schedule, under revised budget" is startup-ready. "Supported the propulsion team on the F-150 Lightning program" is not.

Compress your OEM timeline. If you have 12 years at GM, you do not need 12 years of bullet points. Two or three entries that show increasing scope and specific outcomes are more credible than a comprehensive account of everything you touched.

Explicitly name your non-OEM adjacent work. Any contractor or startup-adjacent project, any side build, any time you have operated without institutional support, surfaces it prominently. It is the counterweight to the OEM brand weight.

And know which startups to target. The companies that most want OEM talent are the ones approaching production, certification, or high-volume scale: exactly the stage where startup-native engineers often lack experience. Right now, the Mobility Jobs board at larrysherwoodjr.com/jobs/ tracks over 800 open EV roles and more than 400 each in eVTOL and AV, pulled nightly from company career systems. Filter by function to find where your OEM discipline maps best.

The Companies That Want Exactly What You Have

Not all startups are at the same stage. A Series A company building its first prototype does not want OEM rigor, it wants speed and scrappiness. A Series C company approaching SOP or certification absolutely does. Targeting the right stage matters as much as targeting the right vertical.

Companies at the production-approach stage, the ones scaling from prototype to certified or high-volume product, are where OEM experience converts most cleanly. Rivian, Lucid, Slate Auto in EV. Joby, Archer, Wisk in eVTOL. Waymo, Applied Intuition, Aurora in AV. These are organizations that have moved past the scrappy phase and need people who know what rigor looks like. Your OEM experience is competitive there, not a liability.