How Long a Hiring Process Should Actually Take in Mobility

On day thirty-eight, a battery validation engineer opened an email asking for availability for one more conversation. It would be the sixth. There had been a recruiter screen, a hiring manager call, a technical phone screen, a take-home test plan that ate most of a weekend, and a four-hour onsite panel. The new request was a thirty-minute chat with a vice president who had been traveling during the onsite. The engineer read it twice, looked at the calendar, and counted back to the day the application went in. Five and a half weeks.

On the other side of the same email, the hiring manager believed the process was moving well. Every stage had been scheduled within a few days of the one before. Nobody had dropped the ball. The vice president wanted to meet every senior hire in the group, which is a reasonable thing for a vice president to want. From where the manager sat, one more thirty-minute call was a small ask at the end of a clean process.

Both of them were right about the facts. They disagreed completely about what those facts added up to, and that disagreement is the real subject of this guide: how long a mobility hiring process should take, and why the two people inside it almost never agree on how long it is taking.

From the candidate's chair

A candidate experiences a hiring process as one continuous stretch of calendar. The clock starts the day they apply or the day a recruiter reaches out, and it does not pause for anything. Every week inside that stretch is a week spent half committed: preparing for interviews, holding back on other opportunities, rehearsing a resignation conversation that may never happen.

What candidates usually get wrong is assuming that length signals interest. A long process feels like a thorough one, and a thorough one feels like a company taking them seriously. Sometimes that is true. More often, in my experience across 1,000+ hires, a long process signals a team that has not agreed on what it is hiring for. Each added round is someone trying to resolve a doubt that should have been resolved before the job description was posted.

The second mistake is not asking for the map. Most candidates accept each next step as it arrives, without ever asking how many steps there are. What they cannot see is that the hiring team may not know either. What looks from outside like a defined process is frequently a sequence of decisions made one stage at a time, by whoever happens to be available that week.

From the hiring team's chair

A hiring team experiences the same process as a series of stages, and it measures each stage separately. Was the screen scheduled within three days? Did the panel happen within a week of the manager call? Did feedback come in on time? Judged stage by stage, most processes look efficient to the people running them.

The constraints are real. Hardware mobility roles often need a panel that crosses disciplines: a controls engineer gets interviewed by software, by systems, and by someone from test or manufacturing. Those people are running launches, supplier audits and design reviews. Getting four of them into one afternoon can take a week on its own. Roles in defense and aerospace can add export control checks or security clearance steps that no recruiter can accelerate.

What hiring teams usually get wrong is never adding the stages up. Nobody owns the total. The recruiter owns scheduling, the manager owns the decision, the interviewers own their own slots, and the elapsed time from application to offer belongs to no one. The second mistake is treating an extra round as free. Every added conversation looks small from the inside. From the outside, it is another week.

What the hiring team cannot see is the candidate's other calendar: the competing process that started two weeks later and is now one step from an offer, because that company runs four stages instead of six.

Where it breaks

The break is arithmetic. Six reasonable stages, each separated by a reasonable gap of four to six days, add up to five or six weeks before anyone has written an offer. Nobody made a mistake at any single step, and the total is still too long.

Here is the benchmark I have used across EV, autonomy and aerospace hiring. For most individual contributor roles, including senior engineers, three to four weeks from first conversation to written offer is achievable and should be the plan. Four stages are usually enough: a recruiter screen, a hiring manager conversation, one technical assessment, and one panel that includes everyone with veto power. Director level and above can reasonably run five to six weeks, because more stakeholders genuinely need a voice. Roles that require a security clearance or an export control review run on a separate clock, and the honest move is to say so on day one rather than let it surface in week five.

Anything past six weeks for a non-executive role is not thoroughness. It is a process that has lost its owner.

The market makes the arithmetic worse. The board I run carries 27,300+ open roles across 166 mobility companies, and 13,100+ of them are engineering roles. A strong candidate is almost never in only one process. The same data shows the other side of the problem: more than half of the open autonomous vehicle and eVTOL roles on the board were first posted more than a month ago. Some of those are evergreen requisitions. Many are roles where the company interviewed people and could not close, and a slow process is one of the most common reasons I see for that. Browse the board and check the posting dates for any company you are talking to. The requisitions that have been open since summer are not hard to find.

Slow processes do not produce better hires. They produce hires from the pool of people who were still available at the end, which is a different and usually thinner pool than the one that started.

What to do differently

If you are the candidate

• Ask for the whole map in the first conversation. How many stages, who is in each one, and when does the team expect to decide? Write the answer down. You will want to refer back to it.
• Treat an unplanned extra round as a question, not a formality. Ask politely what the new conversation needs to resolve. The answer tells you whether there is a real doubt you can address directly, or only a calendar gap.
• Share your timeline early and honestly. If you are in other processes, say so at the recruiter screen, not at the final round. A hiring team can compress a schedule it knows about. It cannot compress one it learns about on the last day.
• Keep your other searches moving until you have a written offer. Pausing at week three because one process feels promising is how a six-week process turns into a ten-week search.

If you are the hiring team

• Set a target for total elapsed time, and name one person who owns it. Three to four weeks for most roles. The recruiter is usually the right owner, with the authority to push interviewers for slots.
• Design the full loop before the requisition opens. Decide every stage and every interviewer up front, including the executive who wants to meet senior hires. Put that executive inside the panel, not after it.
• Hold panel time on the calendar in advance. A standing weekly interview block for each active requisition removes most of the scheduling delay that stretches hardware loops.
• Require written feedback within one business day of every stage. The gap between stages is rarely the interview itself. It is waiting for opinions.
• Tell the candidate the timeline, then report against it. If a clearance step or a travel week will add time, say so at the start. A known delay is tolerated. A surprise delay reads as indifference.

The battery validation engineer took the vice president call on day forty-one. It went well. The offer arrived on day forty-seven. Four days earlier, another company, one with a four-stage process that had started three weeks later, had sent an offer with a Friday deadline, and the engineer had already signed it. The hiring manager called it bad luck. It was not luck. It was six reasonable stages that nobody had ever added up.