The "Overqualified" Verdict: What It Really Means When You're Turned Down

I've had the same conversation more times than I can count over the past few months. A candidate, often with a PhD, sometimes with twenty years of leadership experience, doesn't get an interview. Or they do, they perform well, and the feedback comes back: overqualified.

It's one of the strangest rejections in hiring. Nobody tells a candidate they're "too capable" for a role and means it as a compliment. What they usually mean is something closer to: I don't know what to do with you, and I'm not sure I trust you to stay.

What "overqualified" is actually code for

Very little of it is really about capability. Research on this from Carnegie Mellon found that hiring managers tend to be, in the researchers' words, "pretty myopic" about it. They're evaluating someone against one specific job rather than against what that person could bring to the organisation as a whole. Seen through that narrow lens, a PhD or a former director applying for a role two rungs below their last one doesn't look like an asset. It looks like a flight risk, someone who will get bored, ask for more money down the line, or leave the moment something better comes along.

Outside technical and research fields, PhD holders run into a second, more specific version of this. There's a quiet assumption that years spent deep in academic research produce someone who is too theoretical, too far removed from how a business actually runs day to day. Brilliant in the seminar room, the thinking goes, but not in touch with the real world of budgets, deadlines, and difficult customers. The stereotype is someone who wants to sit above the detail, debating the framework, rather than in it, chasing the deadline. It's rarely said outright in a rejection. It just quietly shapes the shortlist.

For most candidates, it doesn't hold up. Running a research programme for four or five years involves exactly the kind of grinding, unglamorous execution the stereotype assumes is missing: managing a budget, supervising people, hitting deadlines with no flexibility in them, solving problems nobody else wanted to touch. That track record gets lost the moment a hiring manager sees "PhD" at the top of a CV and quietly recategorises the whole thing as academic, rather than reading what the years actually involved.

There's also a quieter layer underneath all of this: ego. Some managers hesitate to hire someone more credentialed than themselves. Nobody puts that on a rejection email, but it sits behind more of these decisions than most organisations would like to admit.

Interestingly, this bias doesn't land evenly. A study out of UC San Diego and Carnegie Mellon found that identically overqualified men and women were read quite differently by hiring managers. Overqualified men were more likely to be seen as flight risks and passed over. Overqualified women, given the same CV, were more often read as committed and likely to stay. Neither reading was really about the person in front of them. Both were assumptions, filling in a gap the hiring manager hadn't actually tested.

The cost nobody accounts for

What gets missed in all of this is the cost of the false negative. A candidate screened out for being "too much" doesn't just represent one lost hire. It represents institutional knowledge, mentoring capacity, and speed to competence that a business quietly walks away from, usually without ever measuring what it gave up. Compare that to the far more visible cost of a bad hire, and it's easy to see why caution wins by default. Nobody gets fired for rejecting an overqualified candidate. Plenty of people get questioned for hiring someone who then leaves in eight months.

That asymmetry is understandable. It's also expensive, and it's rarely examined.

If you're on the receiving end of this

If you recognise yourself in this, the instinct is often to downplay the PhD, trim the CV, make yourself look smaller. I'd push back on that. The better move is to close the gap the hiring manager is actually worried about, directly.

Say why this role, specifically, and say it in a way that's credible rather than deferential. Talk about what you want next, not just what you've already done. If your research or academic work involved managing people, budgets, or ambiguity under pressure, name that plainly, in the same language the business uses for itself. And where you can, go through people rather than portals. A referral does something a CV alone can't: it answers the "will they actually stay and fit in" question before it's even asked.

If you're the one doing the hiring

The more useful question isn't "is this person overqualified for the job as written." It's "what would this person be capable of a year from now, and have we written the job narrowly enough to miss that." Sometimes the honest answer is that the role genuinely can't stretch to hold someone at that level, and that's a fair reason to pass. But it's worth being sure that's the real reason, rather than a comfortable label standing in for a harder conversation about risk, ego, or a job description that was never really built with someone this capable in mind.

Overqualified is rarely a fact about the candidate. More often, it's a decision the organisation made about its own tolerance for ambition in the room.

If you're navigating this from the candidate side, whether you're repositioning after redundancy, moving out of academia, or trying to get taken seriously for the level you're actually operating at, this is exactly the kind of thing I work through with clients. Get in touch if it would help to talk it through.