Why Senior Engineers Fail Interviews (And Why Nobody Tells Them)
DexArticleSean Powell, Head of Engineering10 min read

What makes a ‘senior engineer’ genuinely senior?
Length of experience? Project success? Scope of what they've shipped? Whatever their last title said?
I've turned down plenty of engineers who had 'senior' right there on their CV and most of them weren't exactly bad candidates; they just weren't senior in the way the role needed, even though their last title said they were. By the time they're sitting across from me, their previous title doesn't tell me much about whether they'll be the right fit for the role.
Everyone's senior now. Some people earned it the hard way and some got it at a company so small the word meant something else entirely, while others were handed the title to stop them leaving. They all walk into the same interview loop, but many walk out without an offer and without much idea of what went wrong.
Which raises the question, why do senior engineers fail interviews and why do so many of them never find out?
Senior, but where exactly?
Seniority means completely different things depending on the context. A team of 5-10 people might not have a formal levelling framework in place. What's more important is a decent sense of where everyone sits, which is often as formal as it gets in that stage of their growth.
Of course that's not the case at other companies, especially those with a much bigger headcount. I was an engineer at Amazon where I worked on the Prime Video app for Smart TVs. Not Android, not iOS, not even web. My team had designers, data scientists, QA, analysts, product managers, technical product managers, plus a bench of other senior engineers. If I shipped something, someone else figured out whether it worked.
On my current team responsibilities are spread a lot more broadly, so people end up working on every part of the product at different points. When you ship a feature, you're the one who measures it. Nobody’s going to do it for you.
So it's the same word for two almost entirely unrelated jobs. Put a specialist web designer through our loop and they'd fly through anything web-related, then get asked how to measure whether a feature worked and realise that's always been someone else's job. Send one of my team to fill their role at Meta and they'd probably struggle the other way round.
Pay tells the same story. The Pragmatic Engineer's compensation research found senior engineers at local companies see a median total comp around £132K, whereas the same title at Google, Meta or Amazon medians near £256K (US figures converted). 'Senior' at a 10-person startup and 'senior' at a 10,000-person multinational are two very different things.
Even companies that put serious work into levelling struggle to pin it down. Camille Fournier's ladder from Rent the Runway is one of the most copied in the industry and defines seniority by scope of impact and autonomy, rather than years served. Monzo publishes its own framework openly and it's already on its fourth public revision. If a company with that kind of headcount still hasn't nailed the boundaries, it's clearly not easy.
How the title gets ahead of the person
There are three common ways someone ends up with a senior title before they're ready for a senior interview, and they usually happen for decent reasons.
The underpaid scenario
The one I see most is the retention promotion, which almost always happens the same way.
An engineer gets an external offer, or gets close enough to one to have a chat with their employer about their current role. The company can't match the full raise, or decides it won't. So they offer the senior title instead, maybe with a slight bump in salary. Then the engineer accepts because they feel recognised, get a bit more money and the scope of their role doesn't really change all that much.
That's basically the pitch if you're a team leader who can't get headcount budget approved and one of your engineers is about to hand in their notice.
It's rarely in bad faith. Most of those doing it are boxed into a comp band they didn't set, trying to keep a good employee while avoiding a budget conversation they're not going to win. A new title doesn't show up on a balance sheet, so nobody has to answer for what happens when the person tries to relay that title somewhere else. There's no audit trail, accountability or expiry date.
But the cost doesn't disappear, it just shows up later. Promote people for the wrong reasons and it gets hard to transition as you grow, because you end up with senior titles that don't match what the open market means by senior. Then whoever you bring in from outside is significantly more experienced than the people you already have holding the same one – and everyone on the team can tell which is which.
The fast-tracked high performer
This happens when someone’s genuinely excellent, so they get promoted quickly, well before the experience and tenure that usually come with the title have had time to build up. It's done for the right reasons and they've earned it on output, but the next company can't see that output. It sees a senior engineer with three years behind them and tests them against people who've had ten.
That gap is bigger than it sounds, because 'senior' covers a huge range. The Pragmatic Engineer's compensation survey considers senior around five to ten years of experience, while a thread on levels.fyi puts the dividing line at five years. By my own estimate, it can describe anywhere from two to ten years at a single company, because there's usually nothing between junior/associate and senior for the title to sit in.
Maybe I'm unusual in still seeing length of experience as a key indicator. Sure, an engineer with three years who's smashed it at their previous company can be just as sharp as someone with ten who's moved more slowly. But all else equal, ten years is still seven years ahead. Those extra years don't entitle you to anything, but they do mean you've been around for more of a project's failures and seen more things through their second and third iterations. Accumulate enough of that and it becomes instinct.
The company size gap
Sometimes the title was honest when they earned it, just at a completely different size or type of company to whoever's judging it now. I hold the title 'Head of Engineering' at Dex's six-person team and did consultancy work before Dex where the same title sat inside companies of 10 to 20 people. I obviously wouldn't be a head of engineering, or an equivalent, at a 500-person company because I'm just not at that level.
It happens the other way too. Say a company grows from 50 employees to 500 in three years, with the same person holding the CTO title the whole way through. Eventually the demands of their job (and the skills it requires) change completely because leading a few hundred engineers is very different to the one they were initially hired into.
Either way, whatever made someone senior somewhere else doesn't necessarily travel well.
What the interview is really looking for
An interview loop is the one moment someone outside the company puts a title to the test, and how much rigour that gets varies wildly.
Our own process runs a recruiter screen, a 45-minute conversation with me, a take-home exercise, an on-site interview where they walk through what they built and extend it live, a behavioural round, plus a fit conversation with Paddy, our CEO. That's light compared to a lot of companies, yet even the light version has six checkpoints.
Nobody in that process asks about the title. Anyone can write anything on a CV and most hiring managers don't have time to check the fine print, so we spend the whole time working out what the person has done and how they think.
A lot of that comes down to whether they can make decisions and stand behind them. The ones who struggle have often built something perfectly reasonable, but can't explain why they made the calls they made or they lock up when the requirements change halfway through. That's usually the gap between someone who's been handed well-scoped tickets and someone who's had to scope the work themselves.
The senior and staff bar matters here too. A senior is likely good at building new functionality and more isolated pieces of work. The staff differentiator is whether they can look at how the whole team works, how the tech fits together, be more strategic and mentor others. Someone who's been the most experienced engineer on a small team will often go for staff roles on the strength of that and then get measured against people who've been doing the team-wide stuff for years.
Why you might never find out
Personally, I wouldn't tell a rejected candidate their title didn't add up because I'd never want someone leaving worse than they came in, so if I don't think they'd be open to coming in at a lower comp then I'd give some constructive feedback without explicitly saying ‘you’re not senior level’. I don't think that's unusual. Most hiring managers will tell you where your answers fell short but very few will tell you your last title set expectations you couldn't meet.
The usual answer to all this is to ignore titles completely and optimise for pay instead, since they're too inconsistent across companies to mean much. Fair, as far as it goes. But a title can still get you filtered out of a process long before anyone talks about money.
Meanwhile, the company that handed out the title doesn't feel the brunt of title inflation, at least not in the short term. The engineer does, every time they get turned down for a senior role, until they work out what's going on and recalibrate.
Search any engineering forum for title inflation or downlevel and you'll find the same story over and over. Someone's title never quite matched what the wider market meant by it, and they only found out in another company's interview room. A candidate with 18 years' experience gets pulled down from a principal-level loop to a senior offer instead, officially over a tech-stack gap, an explanation that doesn't quite hold up given the hiring manager still wants to hire them.
Stefan Mai, a former Meta manager who now runs interview-prep startup Hello Interview, has described clients who cleared a senior loop and still got offered mid-level, once because Meta raised its experience bar for the advanced track to six years mid-process. Those candidates had no way of knowing the bar had moved and they still ended up a level below the one they'd interviewed for.
Doing something about it
If you've failed a few interviews for senior roles in a row or been given a title that doesn't seem to travel well, don't wait for your next interview to change tack.
Start collecting evidence while you still hold the job, and make it specific. The time you picked an approach, wrote down why, and it held up (or didn't, and you fixed it). The incident you handled from the first alert to the write-up without someone more senior stepping in. The feature you took from a vague ask to something the team could ship, then measured once it was live. The new starter you got up to speed. That's the material a real senior or staff case is built from, it's exactly what we're digging for in the on-site interview and none of it depends on the title on your business card.
The next thing sounds counterintuitive but hear me out. Downlevel yourself before someone else does it for you. A downgrade isn't a red flag and most tech recruiters are already calibrated to this. 'CTO' at a 20-person company often translates as founding engineer or senior somewhere bigger.
It changes the interview too. Go for a role off the back of a title that sounds bigger than your experience and you're judged against that title from the first call. Go in at a level you're comfortable at and you've got a much better chance of being the strongest candidate in the room, and far less chance of failing probation.
One last thing. If you find yourself on a streak of getting turned down, ask the hiring managers what they'd have needed to see to hire you as a senior. Most won't volunteer it, but plenty will answer if you ask directly and it's probably the closest thing to an honest read on your level you're going to get.
Your old company gave you the title, but it’s always the next one that decides what it's really worth.


