When does a changing role become a “bait-and-switch”?

“That’s beyond my job description.”

It is a familiar refrain in workplaces where a title stays fixed while the work inside it expands. Businesses restructure, priorities shift, and AI can change a job before HR changes its description. But when does normal evolution become an employer asking someone to do a materially different job without resetting what success, support, or progression should look like?

Experts say the answer isn’t simply whether the job looks different from the one someone accepted. It is what happens to the employee’s expectations, support and career prospects as that role evolves.

“Everyone should expect their job to change,” says Andreas Hassellöf, CEO of Ombori. “With AI, most roles will look quite different within a year or two, and in many cases managers do not see it coming either.”

That does not mean every evolving role is a bait-and-switch. “It becomes one when the change is clear and nobody acts on it: the responsibilities grow while the expectations, support and opportunities stay where they were,” Hassellöf says.

According to Paras Rishi, Head of Marketing at Cleartrip Arabia & Flyin.com, change has always been the name of the game. “Roles naturally change as businesses grow and priorities shift,” he says. “The red flag is when a job changes without a clear business reason, transparent communication or a credible path forward.”

According to Dr. Lucy Bolton, Associate Professor at Heriot-Watt University Dubai, the issue is also about the expectations employees bring into a new role.

“From a work psychology perspective, the key issue is not simply that a role has changed. Most people expect some evolution in their work,” Bolton says. “The difficulty arises when change happens without an honest conversation, leaving the employee feeling that the psychological contract they entered into has been broken.”

The distinction matters as workplaces become more fluid. In an August 2026 ResumeBuilder.com survey of 1,023 U.S. employees, 18% said their role had changed significantly or was completely different from what they were hired to do. Thirty percent felt undervalued or overlooked, while 74% said career conversations were inconsistent, delayed or only happened after a problem arose.

So, how much change is normal? And when does it start working against the person whose role is changing?

AI AS AN ACCELERATOR OF JOBS

AI is making the question harder to answer because it can alter the substance of a role without necessarily changing its title.

For Hassellöf, the technology itself is not the problem. The bigger question is what an organization does with the capacity AI creates.

“AI speeds this up. When it lets one person do the work of several, how that extra capacity is used is a leadership choice,” he says. “A clear warning sign is someone effectively doing two jobs on the same title and the same expectations as before.”

That can happen gradually. A tool automates part of a job, freeing up time. Instead of redefining the role, an organization may simply add more responsibilities to the employee’s plate.

The healthier version looks different. If AI takes over routine execution, employees can potentially spend more time making decisions, developing expertise and tackling more complex problems.

“AI moves work away from execution and towards judgment: defining the problem, checking the output and deciding what is good enough,” Hassellöf says. “That is real growth when the person is trusted with those decisions.”

The problem comes when increased productivity simply becomes an excuse to increase workload.

“But if someone is simply expected to produce more because AI made tasks faster, with no new skills, authority or route to progress, the benefit flows to the organization,” he says.

Rishi agrees that the distinction is between capability and volume.

“Ask whether the added responsibility builds capability or simply adds workload,” he says. “Growth means developing relevant skills, gaining ownership and delivering meaningful business outcomes.”

For Rishi, AI should change the quality of work, not simply increase the amount of it. “AI should help people solve better problems, make stronger decisions and serve customers more effectively, not merely do more with less,” Rishi adds.

MORE DOESN’T ALWAYS MEAN GROWTH

From the outside, taking on more work can look like career progression. But responsibility and development are not necessarily the same thing.

Bolton suggests employees should look at what the additional responsibilities are actually doing for their careers.

“A useful question is: are these new responsibilities expanding my skills and future opportunities, or am I repeatedly compensating for wider organizational gaps?” she says.

Such a distinction matters for employees who become known as the person who can always take on more.

“Growth should involve support, learning, recognition and some degree of employee voice,” Bolton says. “Simply being capable of taking on more does not mean that everything added to a role is developmental.”

Hassellöf describes a similar risk in terms of “career capital.” An employee can become increasingly valuable to their current employer while simultaneously moving further away from the expertise they wanted to build.

“A major career risk is becoming indispensable in a role that is taking you away from the expertise you set out to build,” he says. “You can solve problems for your employer every day and still find it harder to position for the next role you want.”

That makes the nature of the new work more important than the sheer amount of it.

“As AI changes roles, separate work that expands your judgment from work that simply makes you responsible for keeping more things running,” Hassellöf says. “Only the first builds career capital.”

Employees can also make the assessment themselves. Hassellöf suggests asking three questions: “What am I learning? What decisions am I now trusted to make? How will this experience advance my career?”

Rishi takes a similar view, arguing that employees should connect changing responsibilities to tangible outcomes.

“Progress is measured by capability and impact, not hours or task volume,” he says.

WHEN YOUR JOB NO LONGER REFLECTS WHAT YOU ACCEPTED

The first step is not necessarily to start looking for another job. It is to establish how much the role has actually changed.

Hassellöf recommends making that change visible rather than assuming a manager will notice it.

“The first step is to make the change visible and specific,” he says. “Document how the role has evolved, which responsibilities have been added or removed, and what this means for the objectives you originally agreed.”

That gives employees something more useful than a general feeling that their workload has increased. It creates a basis for a conversation about what the role is now supposed to be.

“Assume good faith at the start,” Hassellöf says. “Your manager may not have noticed how far the role has moved, because nobody planned it. Raising it early is usually the quickest way to fix it.”

That conversation should clarify what the employee is actually accountable for, which responsibilities matter most and what support comes with the change.

“If AI has automated part of the original job, ask which higher-value work and which decisions you now own in its place,” Hassellöf says.

Bolton similarly recommends starting with clarity rather than confrontation.

“I would encourage employees to ask for a conversation about what has changed, what can realistically be prioritized, and how the revised role supports their progression,” she says.

If the role has changed substantially, that does not automatically mean the employee should reject it. A new combination of responsibilities can sometimes create opportunities that were not part of the original job.

Rishi suggests looking for those opportunities inside the organization.

“Start by identifying where your skills can create value within the organization’s new priorities,” he says. “Cross-functional projects can create visibility and open new paths.”

But if the conversation produces no clarity and expectations keep expanding without support or recognition, the problem becomes harder to dismiss as normal job evolution.

LOOK FOR THE WARNING SIGNS

The easiest time to spot a potential bait-and-switch may be before you accept the offer.

A job description is only a snapshot, especially in companies where priorities move quickly. Candidates can get a better sense of the reality of the job by asking what happens after the hiring process ends.

“Look past the job description and ask for evidence of what the role involves in practice,” Hassellöf says. “Titles can be broad, and descriptions often reflect what an organization hopes the role will become.”

He recommends asking what success would look like in the first 90 days, how a typical week would be divided among responsibilities and why the position is open.

Candidates should also ask how AI is expected to change the role over the next year.

“Notice whether different interviewers describe the role consistently,” Hassellöf says. “Vague answers, shifting expectations or pressure to accept quickly can all signal that the role has not been clearly defined.”

Rishi recommends a similarly simple test: “What does success look like in this role after 12 months?”

The answer can reveal more than a list of responsibilities because it forces the employer to explain what the role is ultimately expected to accomplish.

“Candidates should understand not only what they will do, but why the role matters,” Rishi says.

Bolton suggests going further back into the role’s history.

“Candidates can also ask who previously held the role, what occupies most of a typical week, and what has changed in the team recently,” she says.

The goal is not to find a job that will never change. Few such jobs exist anymore. It is to establish whether the employer clearly understands what it is hiring someone to do, and whether the role can evolve without losing its original purpose.

JOB EVOLUTION ISN’T ALWAYS BAD

There is a temptation to treat any departure from a job description as evidence that something has gone wrong. But that likely doesn’t reflect the reality of modern work.

The more useful question is what the change is doing for the employee.

“Everyone should expect their job to change,” Hassellöf says. But he also recommends checking regularly whether that evolution is still building the expertise an employee wants.

“Treat change as the default, and check every few months whether your role is still building the expertise you want,” he says.

If it is, a changing role may signal growth rather than a bait-and-switch. If it is not, the employee needs to recognize the gap before it becomes difficult to explain where their career is heading.

For Bolton, that means keeping sight of the bigger career picture.

“Most importantly, professionals should keep sight of the career they are trying to build,” she says. “Being helpful is valuable, but not when someone gradually becomes disconnected from the skills, identity and direction they originally joined to develop.”

Ultimately, the dividing line is not whether the job changed. It is whether the change leaves an employee with more skill, judgment and agency, or simply more work.

As Rishi puts it: “The strongest careers are built by solving important problems and proving impact. As roles change, professionals who connect their work to business outcomes will remain the most adaptable, and the most valuable.”