Nobody talks about what it's actually like to be the bad hire. There's no career advice column for it. The content is all about how to get the job, how to negotiate, how to get promoted. The part where things went wrong and you got let go — that part gets skipped.
So let's cover it.
First, a distinction almost nobody makes clearly: a performance problem and a fit problem are not the same thing.
A performance problem means you cannot do the work. Missing skills. Consistent errors. Insufficient output. That's a real thing that happens.
A fit problem is different. You can do the work — but how you do it, the speed you operate at, the environment you need to succeed, doesn't match the specific context you landed in. Wrong role. Wrong stage of company. Wrong operating style for the manager you got.
Most people who get let go have a fit problem, not a performance problem. That distinction matters a lot for what you do next.
Hiring managers are under pressure to fill roles fast. They're interviewing for the version of the role that exists today, not the one it will evolve into in six months. And the interview process is a performance context — you're both selling. The conditions that surface real fit problems rarely come up in a 45-minute conversation.
Here's the uncomfortable part: companies often don't know exactly what they need until they see someone who doesn't quite fit it. The job description is an approximation. The actual requirements only become visible in practice.
None of this is deceptive. It's just the nature of how hiring works at most organisations. Knowing that doesn't fix anything, but it stops you from internalising a story that isn't accurate.
"Culture fit" gets a lot of criticism, usually deserved. It's been used as cover for bias, for keeping teams homogeneous, for rejecting people who weren't like the founders. That criticism is valid.
But the underlying thing it's trying to describe is real. What culture fit actually measures — when the person using the term is being honest — is operating style.
Not personality. Operating style.
None of those is right or wrong universally. But some companies run on very specific defaults, and when yours don't match, it creates friction that's hard to name but easy to feel.
Nobody tells new hires this clearly, but the clock starts running on day one.
Managers form impressions quickly. Not always consciously, but quickly. In the first four to six weeks, they're reading your operating style, your instincts, how you handle your first ambiguous situation. Whether you ask the right questions. Whether you seem calibrated.
By day 90, most managers have a reasonably settled view. They may not have communicated it. They may still be hoping it shifts. But the preliminary conclusion is usually there.
There's often a gap between these two things, and it's larger than most people expect.
Priorities shift. A reorganisation happens. The manager who hired you leaves. The project you were brought in for gets deprioritised. The company has moved on to a different problem by the time you show up.
What you were hired to do and what the company actually needs you to do end up being different things. If your skills and instincts were calibrated for the original brief, you're now misaligned through no fault of your own.
This doesn't make it not your problem. But understanding it helps you respond correctly — which is not to work harder on the original brief, but to figure out what the brief has actually become.
One of the clearest signs that a manager has already decided something about you is that feedback stops.
This seems counterintuitive. You'd expect more feedback if there's a concern. But what usually happens is the opposite: once a manager mentally moves to a different phase — figuring out next steps — they stop investing in the correction conversation. Why spend time on development feedback for someone they've already mentally moved on from?
When feedback gets sparse, vague, or starts arriving through formal processes rather than direct conversation — that's information. Not cause for panic, but worth taking seriously. The feedback vacuum usually means something has been decided.
These tend to appear before anyone formally tells you there's a problem:
None of these individually means you're about to be let go. But together, they're worth taking seriously — and acting on while there's still time to course-correct.
Before accepting a job: what am I actually assuming about this role that I haven't verified?
The assumptions are usually about the operating environment. How autonomous it is. How collaborative. Whether the pace is something you'll find energising or draining. What success actually looks like in the first year. What the relationship between this role and the one above it actually is.
You ask about salary and start date. You don't always ask about your manager's communication style, how much direct feedback you'll get, or what the biggest internal challenge of the role is.
Those questions feel risky to ask. They're exactly what you need to know.
There are specific things you can ask in interviews that get you past the pitch and into the actual operating environment:
The answers won't always be complete. But they're more honest than anything in the job description.
Name it. Directly, and early.
"I want to make sure I'm focused on the right things. My read on the priorities is X — is that aligned with what you're seeing?"
This feels like admitting you're behind. The people who do it tend to stay in roles. The people who don't tend to be let go and then wish they'd said something six weeks earlier. Clarity is recoverable. Prolonged misalignment is harder to come back from.
The shift from "I failed" to "I was mismatched" is not just emotional — it's practical.
If you think you failed, the lesson is: work harder, look more committed, be more impressive in the next interview. That lesson doesn't address what actually went wrong.
If you understand it was a fit problem, the lesson is different: know yourself more accurately. Read environments more carefully before committing. Ask better questions. Pick roles where your operating style is an asset, not a liability.
That's the lesson that breaks the pattern. And most people — unless they do the analysis clearly — don't take it.