I think employers have talked themselves into believing that a job description is a rough draft they get to keep revising after someone accepts it, and that the person who accepted it should just adapt. New survey data says workers disagree, and I think workers are right to.
The gap between the pitch and the job
ResumeBuilder.com’s Bait-and-Switch Hiring Report, based on a nationally representative survey of 1,023 U.S. employees conducted through Pollfish on August 11, 2026, found that 18% of workers say their current role has changed significantly or is completely different from what they were hired to do. Another 56% say their role mostly or somewhat matches what was promised, with a few changes over time. Only 26% say the job matches exactly what they expected walking in.
The same survey found 20% of workers say their day-to-day expectations are often unclear or completely unpredictable, and 74% say conversations about career growth are inconsistent, delayed, or only happen after something has already gone wrong. Just 26% say those conversations happen proactively.
The counter-argument, and why it does not hold
The obvious defense is that business needs change, so of course roles change with them, and an employer that insists on freezing a job description in amber is choosing rigidity over agility. I take that argument seriously. Nobody benefits from a company that cannot reassign work when priorities shift, and plenty of role evolution is healthy, even necessary.
But that defense answers a question nobody is asking. The problem the data describes is not that roles evolve. It is that they evolve without the conversation, the renegotiation, or the acknowledgment that should come with it. Stacie Haller, ResumeBuilder.com’s Chief Career Advisor, put the mechanism plainly in the report: “When the role changes after the hire, workers question whether their current position still aligns with the career path they originally chose.” That is not a complaint about change. It is a description of what happens when change arrives with no explanation attached. An employer that reassigns work and has the conversation about it is agile. An employer that reassigns work and lets the employee discover it unannounced is just quietly renegotiating the deal in its own favor.
Why this is a talent management failure, not an HR footnote
I would argue this belongs at the center of talent strategy, not on the list of minor engagement gripes, because of where it compounds. The same survey found 30% of workers feel undervalued or completely overlooked based on their workplace contributions, and career-growth conversations are the most common thing organizations let slide. Put a mismatched job on top of an inconsistent growth conversation and a worker who already feels overlooked, and the result is not a workforce quietly tolerating change. It is a workforce quietly disengaging, then leaving, then telling the next candidate exactly why.
HR teams that are already fighting to keep compensation conversations honest, a fight this publication has made the case for in Stop Apologizing for the 3% Raise, cannot afford to let job scope drift the same way pay has. Both are versions of the same failure: promising one thing at the offer stage and delivering another without saying so out loud.
What it means for the HR leader
If a role changes meaningfully within the first year, that should trigger the same kind of formal check-in a promotion would: a conversation about scope, expectations, and whether compensation still fits the work actually being done, not just the work in the offer letter. Managers should be trained to flag scope drift the moment they notice it, not wait for an exit interview to surface it. And career-growth conversations cannot stay the thing that happens “when there’s an issue,” because by then the employee has usually already decided the issue is the company, not the role. The skills and credentials conversation runs into the same trap, as this publication argued in A Credential Won’t Fix What SHRM Says Is Broken: a fix that arrives after trust has already broken down does not land the same way one offered proactively would.
None of this requires freezing job descriptions. It requires treating a materially changed job the way employers already expect employees to treat a materially changed workload: worth a conversation, not a surprise. Employers who skip that conversation should stop being surprised when the workers on the other end of it start looking for the exit.
Source: ResumeBuilder.com
