How Mobility Companies Win Engineers Against Big Tech Comp

An ADAS software engineer has two offers on the table. Yours is $40,000 lower on base. The competing offer is from a company you have heard of, with RSUs that vest in four years and a brand that reads well on a resume.

You can close this hire. I have done it. But not by matching base, and not by hoping the engineer chooses mission over money. You close it by changing the conversation before the offers are on the table.

Here is what actually works.

The real comp gap

Big Tech numbers are real. Senior ADAS engineers, ML engineers who work on perception and prediction systems, embedded systems architects: these people see total compensation packages from Google, Meta, and AI labs that range well above $300,000 annually when RSUs are included at grant-date value. Seed and Series A mobility startups cannot match those numbers outright.

But the Series B and later companies can get close, and closer than most hiring managers realize. The mistake is anchoring the conversation to base salary alone. When you lead with base, you let the candidate do their own math against Big Tech's total package. You will lose that comparison almost every time.

The frame that wins is total expected value, not base.

How to frame total comp in mobility

Big Tech RSUs at public companies vest into known quantities. $200,000 in Google RSUs vests into $200,000, give or take. The engineer knows what they are getting.

Your equity at a Series B or Series C company does not work that way. The number that matters is not grant value, it is the outcome range. A $150,000 equity grant at a company that goes from Series B to IPO or acquisition at a 5x to 10x increase in valuation produces a materially different outcome than the face value suggests. Most hiring managers never put that math in front of the candidate.

The conversation I have before presenting an offer sounds like this: "I want to walk through the equity picture with you before we get to the formal offer. Here is the current valuation, here is the strike price on your options, and here is what historical outcomes have looked like for Series B companies in this sector." You are not promising anything. You are giving the engineer the information they need to do their own math, instead of defaulting to the only number they have: Google's base.

The 98% offer acceptance rate I built at Sony Honda Mobility's AFEELA U.S. launch was not an accident of candidate quality. The pipeline was competitive. We were hiring engineers who had options. The difference was a deliberate offer process, not a compensation structure that outspent everyone in the room.

The pre-offer conversation that changes the outcome

Most hiring managers learn about a competing offer after the candidate declines or starts negotiating. At that point, you are in a reaction position. The pre-offer call fixes this.

I schedule a 15-minute call with the finalist the morning before or the day of the formal offer presentation. The agenda is not to sell harder. It is to surface information. Three questions I ask on that call:

• What does your current situation look like? Are they still interviewing elsewhere? Do they have other offers in flight?
• What would make this an obvious yes? Not a negotiation opener. A direct question that tells you whether comp is actually the issue or whether something else (title, scope, remote flexibility, team structure) is the real variable.
• Is there anything about the role or the company that you want more clarity on before we present the offer? Unresolved doubts kill acceptances. Surface them here, not after the candidate has 48 hours to sit with them.

This call does two things. It tells you whether you are actually competing on comp, or whether something else is driving the hesitation. And it signals to the candidate that this is a process run by someone who takes hiring seriously, not a company that fires off an offer PDF and hopes for the best.

Where mobility companies genuinely win

There are three areas where a well-run mobility company consistently outcompetes Big Tech for engineering talent.

Scope and ownership. An ADAS engineer at a large tech company works on a defined subsystem with a clear boundary. An ADAS engineer at a Series C mobility startup may own the full perception stack, interface directly with manufacturing, and be in the room when the system design decisions happen. For engineers who want to build things, not just optimize them, the scope argument is real and it closes offers.

Timeline to production. Big Tech AI products have unclear timelines to real-world deployment. Mobility startups with vehicles in production or active certification programs offer a different answer to "when will I see this in the world." Engineers who want to see their work physically deployed are not going to get that answer from an AI lab. They will get it from a company building something that moves.

Equity inflection timing. The equity argument above only works when you present it honestly and specifically. Vague claims about upside do not close engineers who have seen companies not IPO. Specific, honest conversations about current valuation, funding history, and realistic outcome scenarios do work, especially with candidates who understand how to read a cap table.

What actually makes candidates choose Big Tech

I want to be direct about this, because it matters for your process. Engineers choose Big Tech for four reasons that have nothing to do with compensation:

• The mobility company moved slowly. Three rounds of interviews stretched across six weeks, and Google called back in two.
• No one on the hiring side could answer questions about the company's engineering culture or team structure. The candidate filled in the blanks negatively.
• The equity conversation never happened, so the candidate defaulted to comparing base salaries.
• The offer came in below what the recruiter screen suggested was the range, and the candidate felt misled.

None of these are compensation problems. They are process problems. A 42-day average time to fill, which is what I ran at AFEELA against a 60-to-75-day industry average, is not primarily a result of moving fast for speed's sake. It is a result of a process where candidates are not left waiting, equity is discussed early, and the pre-offer call happens before the final presentation every time.

The one thing that matters most

If I could give hiring managers at mobility companies one change to make to how they run offers, it is this: stop treating the formal offer as the place where you make your case. By the time the offer document lands, the candidate should already know the equity picture, already have answered their own hesitations, and already have a reason to say yes that goes beyond the base number.

The offer is a formality. The sales conversation happens before it.

Mobility is genuinely competing for the same people that Google and OpenAI want. The companies that win those hires do not do it by outspending. They do it by running a process that treats the offer conversation as something that deserves the same rigor as the technical interview loop.

The engineers who build the things that matter want to work on problems that matter. The mobility stack is one of the most technically complex and consequential engineering domains in the world right now. That is not a consolation prize. Lead with it.

The Mobility Jobs board tracks open engineering roles across EV, AV, eVTOL, electric marine, and autonomous delivery companies. If you are hiring in this space, the board gives you a live picture of who else is competing for the same candidates you are.