What to Do When the Job Isn't What They Promised in the Interview

You accepted the job based on a specific picture: the hours, the flexibility, the scope you discussed in the interview and saw in the offer. Then, a few weeks or months in, a requirement surfaces that nobody mentioned. A mandatory late day every week. A weekend on-call rotation. In-office days quietly added to a schedule that was sold as flexible. And it rarely arrives as a proposal — it arrives as a message informing you that it's already decided.

Two questions come up immediately: can they do this, and can I refuse? The short answers are probably yes, and yes — with consequences. The longer answer is worth walking through, because how you handle the next two weeks determines whether this becomes a negotiation or a resignation.

What the law actually says (mostly nothing helpful)

In the US, most employment is at-will. That means your employer can change the terms of the job going forward — schedule, duties, location — and can end your employment if you don't accept the new terms. The fact that a requirement wasn't disclosed during hiring is morally significant and legally, in most cases, irrelevant. What was said in an interview almost never creates an enforceable promise about your hours.

There are exceptions. A written employment contract that actually specifies your hours. A union collective bargaining agreement. A schedule change that targets you because of a protected characteristic, or that arrives as retaliation for something you reported. A few states recognize implied contracts in narrow circumstances. But read your offer letter before assuming it protects you: the standard one covers salary, title, start date, and an at-will disclaimer, and says nothing binding about your schedule. And a note of caution — this isn't legal advice, labor law varies by state and country, and if your contract does specify hours, or the new requirement pushes a non-exempt role past overtime thresholds without pay, a conversation with an employment attorney or your state labor department is worth the time. Most people in this situation, though, don't have a legal problem. They have a negotiation problem.

Treat it as a negotiation, not a verdict

The message that says you're now required to pick a late day reads like a ruling. It's usually an opening position. Workplace customs — the all-staff long day, the unofficial Saturday check-in — tend to be enforced unevenly, and the person relaying the requirement often has more discretion than the wording suggests. Your first move isn't to comply or refuse. It's to find out what problem the requirement solves. Coverage for a specific time window? Client calls in another time zone? Or just optics, because everyone else does it?

Then bring a constraint and an alternative, not a flat refusal. "I can't be in the building fourteen hours because of my commute, but I can take the late coverage remotely." "I can't do late days, but I can open early twice a week." The difference matters because of how approval works above your manager's head: a manager can defend an alternative that still solves the problem, but can't defend an exemption granted for no stated reason. A flat no forces an authority contest you will usually lose. A workable alternative gives everyone a way to say yes.

If the answer comes back as a hard no with zero flexibility, that's real information — about the employer, not just the schedule. You can decide what to do with it. But at least you'll be deciding with facts instead of a Slack message.

Put the outcome in writing — whatever it is

Whatever gets decided — an accommodation, an alternative arrangement, or the requirement standing as-is — recap it in an email the same day. "Confirming what we discussed: I'll cover the late shift remotely on Wednesdays, leaving the office at my usual time." Undisclosed requirements thrive in workplaces where nothing gets written down, and the same culture that didn't mention late days in your interview will not remember granting you an exception in a hallway conversation six months from now.

Then extend the habit. From this point on, keep your own record of what the job actually is — the scope you carry, the hours you work, the responsibilities that were added after you signed. Keep it outside your employer's systems, because if this story ends in an exit, your access to those systems is the first thing that disappears.

When the switch is a signal

One undisclosed requirement can be an oversight. A pattern — scope that keeps growing, expectations that keep shifting, "temporary" asks that become permanent — is a leading indicator that you'll be job-searching sooner than you planned. The people who handle that badly are the ones who wait until resignation day to gather evidence of what they did, and by then most of it is locked behind a login they no longer have.

Start documenting now, while everything is still in front of you: the projects you delivered, the results, the role you actually performed versus the one that was advertised. This is what KredVault is built for — a career record that lives with you rather than your employer, where the work can be confirmed by the people who saw it. It also changes how the story lands later. When a future interviewer asks why you left after eight months, "the role changed materially after I was hired" is credible when your record shows exactly what you carried.

Job changed under you? Keep your own record of what you actually do.

When a role drifts from what was promised, the person who pays for it most is the version of you interviewing next year — trying to explain a scope that was never written down anywhere you can reach. Capture your real responsibilities, projects, and results in a portable record you own and others can verify, so the story of what happened doesn't depend on an employer's memory.

Build your verified career record →