The Remote Job Bait-and-Switch: Give Postings an Audit Trail

A job-posting bait-and-switch is when a role is advertised one way, as remote, at a certain salary, in a certain location, and then quietly becomes something else by the time the offer arrives. The listing was accurate when the candidate applied and dishonest by the time they accepted, with no record that anything changed. It is a distinct failure from a ghost job, which was never real to begin with. This one was real. It just did not stay that way.

Most coverage treats this as an ethics problem: companies lie, here is how it feels, here is the trust cost. That framing is not wrong, but it is not actionable for the founder who never meant to lie. The more useful frame is that a job posting is a set of structured claims, and your hiring stack lets you overwrite those claims silently, with no version history and no obligation to tell the people already in your pipeline. Fix the data model and the honesty mostly takes care of itself.

A joke about lying went viral because it wasn’t unbelievable

In early 2026 a LinkedIn post made the rounds: “I tell candidates the job is remote. They accept. Then I tell them it’s in-office. They still show up.” Reddit lit up. The post was explicit satire, written by Drew Szurko, who labeled it as such and later called it “lighthearted satire” poking at the chaotic hiring he had watched since 2020. The reason it went viral is the uncomfortable part. Thousands of people read a joke about a recruiter bragging about deceit and could not tell it was a joke, because it described something they had lived.

The genuine version is not hard to find. A supplement company, Inno Supps, posted a “remote” senior copywriter role on LinkedIn whose description read: “While this role is listed as ‘remote’ for visibility, it is an on-site position and requires in-office presence,” alongside “Please apply only if you are willing to eventually work on-site in Henderson, Nevada.” A screenshot drew roughly 2.3 million views on X (reported by Fast Company), users found a similarly-labeled CEO listing, and the posting stopped taking applications. This is an employer stating, in writing, that “remote” was a visibility tactic. The satire did not exaggerate the practice. It just said the quiet part out loud.

The lesson is not that recruiters are cartoon villains. It is that the practice is common enough that a joke about it reads as a confession.

Bait-and-switch, by the numbers

Bait-and-switch is not an edge case. In Greenhouse’s 2024 Candidate Experience Report, a survey of about 2,900 candidates across six countries, more than half of US workers reported hitting a version of it once they started a job.

Read those two middle rows together and you have the everyday shape of the problem. It is rarely the Inno Supps screenshot. It is the salary band that slid a little between the posting and the offer, across four rounds nobody kept notes on. The Greenhouse data also found the burden is not evenly distributed: Black candidates were about 12 percentage points more likely than white candidates to experience the responsibilities mismatch.

Why does remote status, specifically, get gamed? Because it is the single term candidates will quit over. FTI Consulting’s 2024 survey found 70% of remote and hybrid workers would seek other employment if forced back to the office full-time at their current salary. Remote is the highest-leverage word in your posting, which is exactly why it is the most tempting one to stretch. Forbes went as far as calling remote listings “the new ghost jobs” in April 2026.

Keep the two failures separate, though. Ghost jobs are postings that were never real; roughly 1 in 7 listings by one 2026 study. Bait-and-switch is a posting that was real and became false. Same family, opposite mechanism, and the fix is different: ghost jobs need intent-to-hire disclosure, while bait-and-switch needs change disclosure.

Can a company change a remote job to in-office after you accept?

Yes, employers can generally change a role, but a material misrepresentation the candidate relied on can cross into fraudulent inducement of employment. The elements are straightforward: the employer misrepresented a material fact, the candidate reasonably relied on it, and the candidate suffered harm as a result. A remote promise that flips to onsite after acceptance is a textbook material fact.

The exposure gets sharper when the worker relocated. In California, Labor Code section 970 bars inducing someone to move for work through false representations about the kind, character, existence, or location of the work. Section 972 allows double damages, with related misdemeanor exposure. So “we changed it after they accepted, and they had already moved for it” is close to the fact pattern these statutes were written for. This is a California statute; elsewhere candidates rely on general fraudulent-inducement common law, so do not read this as a nationwide double-damages rule. But the direction of travel is clear enough that “we don’t keep records of what the posting said” is a bad place to be standing.

Here is the practical trap. If a candidate later claims the role was misrepresented, the argument is won or lost on evidence. What did the posting say on the day they applied? What changed, and when? Was the change disclosed? If your answer is a shrug because the field was overwritten in place, you have no defense and no memory. The honest employer and the litigation-exposed employer are often the same person; the difference is whether the record exists.

Why “just don’t lie” doesn’t fix it

“Don’t lie to candidates” is good advice and a bad control. It assumes bait-and-switch is a character flaw, when most of it is drift. Budgets move. An RTO policy lands mid-quarter. A “remote” role quietly becomes “remote, but we’d prefer you near HQ,” then hybrid. No one decided to deceive anyone. The role changed, and the posting was a mutable record with no memory.

That is the actual defect. When you can set remote: true and later overwrite it to false with no trace, three bad things are true at once. The change is invisible, so nobody notices the posting and the pipeline have diverged. The candidates who applied under the old terms are never told. And there is no record to reconstruct later, for a candidate dispute or for your own sanity. A posting that is true on Monday and false by the offer letter is not a moral failure. It is an unversioned mutable field.

This is why exhortation does not scale. You cannot remember to be honest about a change you did not notice you made. The fix has to live in the system, not in the recruiter’s conscience. The same logic underpins why employer ghosting needs communication SLAs rather than a reminder to “be responsive,” and why pay transparency works better as versioned salary claims than as a promise to be fair.

A job posting is structured data, so version it

Once you see the posting as data, the fix is obvious: make the load-bearing fields append-only. Treat remote status, location, and the salary band as versioned records instead of overwritable cells. Then four things follow more or less for free.

1. An audit trail. Overwriting remote: true to false writes a new version instead of erasing the old one. You preserve what the posting claimed at every point, including what it claimed on the exact date any given candidate applied.
2. Automatic re-disclosure. When a material field changes on a posting that has candidates in-pipeline, the system sends them an on-the-record notice: “this role’s location changed from Remote to Hybrid on this date.” A silent overwrite becomes a documented disclosure.
3. A diff at the offer. At the offer stage, surface the gap between what the candidate saw at apply time and what the offer delivers, so a remote-to-onsite flip or a comp change is explicit and acknowledged rather than sprung.
4. A public track record. Aggregate change history into a careers-page signal, the reputational counterweight to the screenshot. “This employer’s postings match their offers” is a claim a candidate can check.

Notice that the audit trail is not only a candidate-trust feature. It is also your legal shield. The fraudulent-inducement defense is exactly this record: here is what the posting said when they applied, here is the change, here is the timestamped re-disclosure they acknowledged.

Regulators are already pushing employers toward keeping the records, even if none yet mandate this precise re-disclosure. Ontario’s Working for Workers Act, in force January 1, 2026 for employers with 25 or more staff, requires disclosing whether a posting is a real vacancy, notifying interviewees within 45 days, and retaining hiring records for three years, with fines up to CAD 100,000. On pay, 17 US states now require salary ranges in postings (Paycor, early 2026), and the guidance is that a posted range must reflect what the employer reasonably expects to pay at time of hire. That is a versioned claim in all but name. The compliance chore and the trust feature are the same artifact.

What an honest, auditable posting looks like in Kit

Kit is an applicant tracking system built so that a posting is structured data from the start, which is the precondition for keeping it honest. You cannot version what you never modeled as a field.

What Kit ships today, verifiable in the product:

• The claims are first-class fields, not prose. Every job posting stores remote as a boolean, a real location, and a structured comp band (salary_min, salary_max, currency, and period), instead of burying them in a paragraph a candidate has to interpret.
• Postings have provenance and a real lifecycle. Each posting records who published it and when (published_by, published_at) and moves through genuine states, from draft to published to paused to closed, rather than a cosmetic refresh.
• The offer is its own object. Kit models the offer and the candidate’s response as first-class records, and gives candidates a magic-link portal to track their stage. The two endpoints a bait-and-switch happens between, apply and offer, are both things Kit represents.

Now the honest part, because this piece is about integrity. Kit does not yet version those fields or auto-re-disclose changes; the structured claims are still editable in place, like everywhere else. The versioning, the diff-at-offer, and the public track record described above are the direction this should go, not a checkbox you can tick today. Presenting a proposal as a shipped feature would be its own small bait-and-switch, and it would undercut the whole argument.

What is real and usable right now is the foundation: postings modeled as structured, provenanced data, a modeled offer stage, and a candidate portal, so that when the fields do become versioned, the record already knows who saw what and when. If you want the same integrity-by-default thinking applied to the page itself, owning your careers page is the companion move.

The 5-minute posting-integrity checklist

You do not need versioned fields to stop most bait-and-switch this week. You need a few habits and a paper trail.

• Decide the office policy before you post. Most remote-to-onsite flips are unresolved expectations, not deceit. Settle remote, hybrid, or onsite before the listing goes live, not during the final round. If some in-person time is genuinely required, say so up front; a disclosed in-person final round is honest, a sprung one is not.
• Model the claims as fields, not sentences. Put remote status, location, and the salary band in structured fields so a change is a discrete, trackable event instead of an edit buried in a wall of text.
• Re-disclose every material change in writing. If remote becomes hybrid, or the band moves, tell every candidate already in the pipeline, in writing, with a date. This is the single highest-leverage habit, and it maps directly to your offer-acceptance rate.
• Keep the record. Save what the posting said when each candidate applied. Ontario already requires three-year retention; you want that record whether or not the law reaches you.
• Scope your remote promise honestly. “Remote” should mean remote. If you mean “remote across these time zones,” write that. Hiring a distributed team is a legitimate constraint, and stating it is not a downgrade.

Bait-and-switch broke candidate trust one silent overwrite at a time. The way back is not a promise to be honest; it is a posting that remembers what it claimed. Model the role as data, disclose the changes, and keep the record. If you want to build a hiring process on that foundation, start a free trial and post one role the honest way, or browse the role templates to set up a pipeline in minutes.