Bait and switch staffing is the oldest fraud in contract engineering: the vendor puts its best engineer in front of you for the interview, and a different, cheaper person does the work. Sometimes the name changes on day one. Sometimes the name stays and the person behind it changes. Either way, you interviewed someone you never got.
A data platform consultant described it in a 2013 post that still reads like it was written this year: a vendor presents a strong consultant, and someone else turns up, and "the hope is the client remains unaware it is a different person." What's new in 2026 is that remote work and AI make the switch easier to pull off and harder to notice.
Key Takeaways
- Bait and switch comes in three forms: a named substitution after signing, a proxy who interviews for the real worker, and an engineer who quietly subcontracts the work.
- Federal contracts have handled the contract side for years with "key personnel" clauses. You can borrow the idea in any staffing agreement.
- The practical defense is identity continuity: the person you interviewed is the person on every call, commit and invoice.
- Ask every staffing vendor four fraud questions before you sign, and get the answers in the contract.
The three versions of bait and switch
The named substitution. You interview and approve Ana. The vendor emails a week before the start date: Ana took another project, but Luis is "equally strong." You never interviewed Luis. Some vendors do this honestly when an engineer really does leave. Some do it by design, using a few strong interviewers to win deals for a bench of weaker people.
The proxy interview. The name never changes. A stronger engineer sits the interview under the worker's name. SHRM, citing Computerworld, described a Kubernetes engineer who passed three rounds, and then at his first real meeting "it wasn't the same guy." Our guide on how to identify a proxy interview covers the tells.
The silent subcontract. The engineer you hired is real and does show up to standups, but passes the actual work to someone cheaper. You see it as a drop in quality, code that doesn't match how they talk about it, and commits at odd hours. The 2022 State, Treasury and FBI guidance on North Korean IT workers lists "multiple logins into one account from various IP addresses" as a red flag for the extreme version of this.
Borrow the government's key personnel clause
Federal contracts deal with substitution explicitly. HHS's key personnel clause, HHSAR 352.237-75, says the contractor "shall not divert, replace, or announce any such change" to named key personnel without the contracting officer's written consent, and requires advance notice with the replacement's qualifications.
You don't need a contracting officer to use the same idea. Put these in your staffing agreement:
- The engineers are named. Any replacement needs your written approval, after you've interviewed the replacement.
- The vendor gives notice before any change, with a reason.
- The named engineer does the work personally. Subcontracting needs your written consent.
- Identity is confirmed at onboarding, and the same person attends a video call before access is granted.
This is general information, not legal advice; have your lawyer adapt the wording.
Four fraud questions to ask any staffing vendor
| Question | A good answer | A red flag |
|---|---|---|
| How do you confirm the engineer who interviews is the one who works? | Specific steps at interview, onboarding and early weeks | "We trust our people" |
| Can you replace a named engineer without my approval? | No, written in the contract | Vague, or "only if needed" |
| Do your engineers subcontract? | Not allowed, in the contract | Silence |
| What happens if the engineer underperforms? | A defined replacement process with a clock and a cure period | "Contact your account manager" |
More general questions are in our post on questions to ask a staffing agency.
How we handle it at Ruzora
Every engineer on our bench has passed a graded coding challenge and an AI interview answered on camera, two separate evaluations. You see blind profiles, pick who you want to meet, sign the service agreement, and then interview the named engineers yourself, with full identity, before anyone starts. If an engineer has documented technical performance problems in their first 60 days, counted from their first working day, we replace them, and you pick the replacement from a new shortlist after interviewing them yourself.
A Concrete Version
A 50-person proptech company contracts two senior React engineers through a low-cost vendor at a rate well below other quotes.
- Week 0: interviews go great. Both engineers are articulate and fast.
- Week 1: one engineer's camera is "broken" for standups. The other's voice sounds different from the interview, which the tech lead puts down to a bad mic.
- Week 3: PR reviews show code style that changes day to day, commits at 3 a.m. local time, and a pull request description that doesn't match how the engineer explains the change on a call.
- Week 4: the tech lead asks for a camera-on pairing session. The engineer can't explain a function from their own PR.
The contract had no key personnel or no-subcontracting clause. The company ends the engagement and loses four weeks plus onboarding time. With the clauses above, week one's "broken camera" would have triggered a contractual identity check, not a hunch.
The Honest Counterpoint
Not every substitution is a scam. Engineers do get sick, quit or take another offer between the interview and the start date. A vendor that can never replace anyone is a vendor that can't help you when something goes wrong. The point is consent: replacements happen with your approval and your interview, not by email.
And contract clauses only help if you check. A key personnel clause in a PDF does nothing if nobody turns their camera on after week one. The clause gives you the right; the habit of checking catches the switch.
Frequently Asked Questions
What is bait and switch staffing?
A staffing vendor presents one engineer during interviews and supplies a different person to do the work, either by swapping the name after signing, using a proxy in the interview, or letting the engineer quietly subcontract.
How do I prevent bait and switch in a staffing contract?
Name the engineers, require your written approval and your own interview for any replacement, ban subcontracting without consent, and confirm identity on video at onboarding before granting access. This is general information, not legal advice.
Is bait and switch common with offshore vendors?
There's no reliable public data on how common it is. It's more likely when rates are far below market and the vendor's model depends on volume. Check the contract and the person, whatever the geography.
The Bottom Line
Bait and switch staffing is stopped by two things: a contract that names the engineer and requires your consent for changes, and the habit of checking that the same person shows up. If you want to interview the named engineer yourself before they start, see our bench or read our pricing.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
