The engineer you interview should be the engineer who joins
A senior engineer runs the interview. A junior one shows up on day one. This swap has a name, and a contract can stop it before you sign.
The short version
5 things that decide this
- 01Senior-in-the-interview, junior-on-the-invoice is common enough in staffing that buyers search for it by name after it happens to them.
- 02The mechanism is bench economics: a vendor's best engineers stay booked on existing accounts, so new deals get staffed from whoever is free.
- 03A rate card alone does not stop this. The interviewed engineer and the assigned engineer are two different line items unless the contract ties them together.
- 04Three clauses close the gap: named-resource assignment, a replacement notice window, and a right to interview any substitute before they start.
- 05Ask any staffing partner who actually gets assigned when their top engineers are already billed elsewhere. The honest answer tells you their bench depth.
Why the swap happens
A staffing vendor sells hours, not outcomes. Its profit comes from keeping every engineer billed against a client, all the time. That structure rewards a specific move. Put a senior engineer in front of a prospect to close the deal. Then staff the actual work with whoever is sitting on the bench.
This is not usually a lie told on purpose. It is what the incentives produce. The interviewer's job is to win the account. A staffing coordinator's job, a week later, is to fill a seat from whoever is available. Nobody in that chain is measured on whether the two people match.
The buyer finds out at the worst possible time: after the contract is signed and the first sprint is already behind. Onboarding friction discourages pushing back once the wrong engineer has already started, and switching vendors costs more than living with the mismatch. That is exactly why the pattern survives.
- 01A vendor's most senior engineers are usually the ones already billed on long-running accounts, not the ones free to staff a new deal.
- 02A generic rate card ("senior engineer, $X/hour") describes a role, not a person, so it does not commit the vendor to anyone specific.
The clauses that prevent it
None of this needs trust. It needs paper. Three clauses, all standard in a well-written staffing agreement, remove the vendor's room to swap.
Named-resource assignment states the engineer's name in the statement of work, alongside their title. "A senior backend engineer" is a role. "Maria Chen, senior backend engineer" is a commitment. If the vendor cannot name who will do the work before you sign, they have not decided yet. The decision they make later will follow their bench, not your project.
A replacement notice window requires advance written notice, ideally two weeks, before any named engineer is swapped, with a stated reason. This does not ban replacement. People leave, get sick, or move roles. It bans silent replacement, where the first sign of a swap is a new name in the standup invite.
A right to interview any substitute puts the buyer back in the seat they had during the original hiring process. If the vendor proposes a replacement, you meet them first. You approve them before they start billing, on the same terms as the person they are replacing.
What we commit to in writing
Our staff augmentation agreements name the engineer, not the role. If a named engineer has to leave an engagement, you get notice before the change and you interview whoever we propose next. Nobody joins your team on our say-so alone.
This is a structural choice, not a favor. A vendor who will not put a name in the statement of work is telling you something. The person you interviewed is not the commitment. Ask for the name. If the answer is a role instead, that is the whole conversation.
Questions this raises
01How do I know if a staffing vendor is likely to bait and switch?
Ask them to name the engineer in the contract, alongside the title and rate. A vendor confident in their bench will do this without hesitation. One who hedges, offering only a role description, is keeping the assignment open until after you sign.
02What should a replacement clause actually say?
It should require written notice before any named engineer is swapped, with a stated reason. It should also give you the right to interview and approve the replacement before they start billing. A surprise name in a standup invite is the failure mode it exists to stop.
03Is staff augmentation worse than outsourcing for this reason?
Not inherently. The two models fail differently: staff augmentation risk is bench-economics substitution, outsourcing risk is losing visibility into who touches the code at all. Both are contract problems, not category problems, and both are solvable with the right clauses.
