After three months of searching, an embodied AI startup meets a candidate who fits the technical direction and communicates well. The founder conducts the final interview, discussing the product, technology and team. The candidate asks for a week to decide.
When HR follows up, the candidate has accepted another offer. The conversation had felt promising. What changed?
The problem may lie in what happened after the conversation, rather than during it.
A strong interview does not remove the competition
Liepin figures put Robotics vacancy growth at 75.26% and average advertised annual pay at RMB 328,000. For humanoid robotics, the figures are 215.80% growth and RMB 406,100. Maimai's January–April 2026 data is cited as showing 15-fold growth in embodied AI vacancies and average monthly pay of about RMB 62,000.
Ministry of Human Resources and Social Security monitoring puts the ratio at 5.2 technical vacancies for each available robotics candidate. Such candidates have alternatives. They are assessing where to spend the next several years, not simply whether the interview went well.
Silence after the interview
A 2026 Zhaopin candidate-experience report cited through Moka HR says 72% of candidates had withdrawn after more than five days without an update, compared with 61% in 2024. That is an increase of approximately five percentage points a year.
Another cited finding is that 89% valued being told which stage they had reached more than speeding up recruitment itself. Waiting is easier to understand when there is a reason, an owner and a next date.
Moka HR describes a case involving a 500-person technology company. The average gap between the final interview and formal offer was 8.3 days. Of 11 candidates in the case, three senior backend engineers were lost to competitors, with acceptance elsewhere recurring in the recorded reasons.
A vague “we are still evaluating” response does little to protect the employer's position during that gap.
Compensation that remains unclear
Zhaopin's spring 2026 survey is cited as finding that 71.3% of candidates regarded vague, unconvincing pay discussions as among the least acceptable recruitment behaviours. Conditions promised but not delivered after joining followed at 51.1%.
Some startups postpone the pay discussion until the end. Others give a headline amount without explaining monthly cash, performance calculations, equity, options or exercise conditions.
A senior candidate reads this as evidence about management. If the company cannot explain an important commitment clearly before joining, uncertainty about other commitments follows.
Too many interviews without a shared standard
The same Zhaopin material puts prolonged, inefficient interviews and repeated delays among unacceptable behaviours for 49.6% of respondents.
Four or five rounds may expose a candidate to incompatible expectations: algorithm depth from a technical lead, engineering experience from the founder, stability from HR and cost control from the COO. Different interviewers can contribute different evidence, but they need to assess the same role.
The Moka HR example describes an offer process involving five approval points and three departments before improvement. A delay at any point became the candidate's waiting time. Fragmented founder availability and repeated pay approvals make the problem worse.
The resulting signal is that the company has not agreed what it wants.
The working environment does not match the promise
A candidate from a mature research team may be used to data infrastructure, compute resources, established tools and engineering support. A startup may still be building all of them.
That difference is not inherently disqualifying. Concealing it is. A company that describes a mature R&D platform but offers an unfinished laboratory risks making the candidate feel that the real vacancy is for an entire infrastructure team.
Even after acceptance, a large gap between the interview account and the actual environment can produce an early departure. Some candidates return to the market within three months when expectations are badly misaligned.
Technical authority is left unresolved
An expert founder may want a leader to run the team while retaining every significant technical judgement. Candidates can usually detect that arrangement after a few discussions.
They will ask who chooses the roadmap, controls budgets and approves recruitment and pay. If all decisions remain with the founder, the appointment is closer to senior execution than technical leadership. A person seeking genuine responsibility may decline even after an engaging technical conversation.
Review the losses before increasing interview volume
Look at the past three months of candidates who completed discussions but did not join. Separate withdrawals after more than five days without feedback, unclear compensation, slow decisions, mismatched expectations and uncertainty about authority.
This is an examination of why suitable people chose not to join. Treating every unsuccessful process as evidence of candidate weakness misses the opportunity to improve it.
UB hunter reviews the sequence from interview to offer to identify where confidence falls away. The remedy may be clearer communication, a transparent package, a shorter decision path or a more accurate account of the work. More interviews help only after the cause of the losses is understood.