A
A senior seat open 4+ months, quietly stalling your roadmap
The role that has been through three rounds of interviews, three declined offers, or simply no pipeline. The gap is real and compounding.
You told us A, B, or C. Here is what we are actually seeing across the companies we work with — patterns, numbers, and what separates the teams getting this right from those quietly falling behind.
Based on my conversations with hiring leaders in 2026 · Barbora Jenšík, Recberry · 10 min read
A
The role that has been through three rounds of interviews, three declined offers, or simply no pipeline. The gap is real and compounding.
B
Great on paper. Strong in interviews. But when things got messy, the judgment simply wasn't there. The kind of hire that costs more than a vacancy.
C
You are running hiring on intuition and hope. No signal on the cost of vacancy. No signal on quality of hire past 90 days. No feedback loop.
The most common response we hear when a company experiences A and B in the same year is that they had bad luck — the wrong candidate at the wrong time, a slow market, a difficult role. We understand the impulse. It is easier than the alternative.
The alternative is this: you are running one hiring process built for a market that no longer exists. A market that had plenty of applicants, predictable junior pipelines feeding the senior layer, and senior talent who actually applied to job posts. That market is gone.
"Most companies are running a 2018 hiring process in a 2026 talent market. The gap between those two realities is what shows up as A, B, and C."
What follows is what we are actually seeing across the companies we work with. Not frameworks. Not theory. Patterns — with the numbers behind them.
If a senior engineering role has been open for four months or more, there is almost certainly a structural reason — not a sourcing volume problem. The instinct is to post more, reach more, screen more. The data does not support that response.
Senior engineers with genuine tacit knowledge — the kind built over a decade of shipping, breaking and fixing real systems — are staying in place longer, moving less, and when they do consider moving, it is almost never because they saw a job post.
They move because someone they trust surfaced an opportunity before it was urgent. Before a role went live. Before there was any pressure on either side. The companies filling senior technical roles fastest are not those with the best job descriptions — they are the ones who had already built the relationship.
Per month
A four-month vacancy on a €120k senior role is not a hiring problem. It is a €60,000+ business problem.
Posting the same JD to more platforms and expecting different results
Measuring recruiter activity (CVs screened, calls made) instead of pipeline quality
Starting the search when the role is urgent — already too late for passive senior talent
Competing on speed with companies who started building relationships 6 months ago
Using salary as the primary lever — senior engineers move for trajectory and trust, not just compensation
What good looks like: Companies that fill senior roles in under 8 weeks operate a continuous pipeline — not a reactive search. They have mapped the 15–20 senior engineers they would want to hire in the next 18 months and are in genuine conversation before any role opens.
This is the harder one to talk about. A senior hire who passed every stage of a well-designed interview process, had strong references, presented confidently — and then, once in the role, consistently deferred decisions that should have been theirs. Escalated when escalation was not needed. Froze when things got uncertain.
This is not an interview failure. It is an interview design failure. Most technical interview processes are optimised to test codified knowledge. They are very good at identifying people who can explain distributed systems, write clean code under observation, and answer structured questions about previous decisions. They are almost useless at evaluating tacit judgment — the thing that actually separates good senior engineers from great ones.
"The interview was designed to test what they know. The role required them to know what to do when they don't know. Those are different tests."
It is not seniority. It is not years of experience. It is the ability to make good decisions under genuine ambiguity — when the requirements are unclear, the data is incomplete, the team is divided, and something has to move. You cannot rehearse it. You cannot fake it across six weeks in a real role.
Structured behavioural questions reward people who narrate past decisions well — not people who make good decisions now
Technical exercises test codified knowledge in a low-stakes setting — the opposite of how tacit judgment is exercised
Reference checks go to references chosen by the candidate
Panels evaluate confidence and communication — which correlates poorly with judgment under pressure
Hiring managers rarely probe the decisions the candidate did not make — where judgment actually shows
Industry research says 46% of new hires fail within 18 months (Leadership IQ). That hasn't been my experience. The senior and VP hires I've placed have stayed. Where senior hires do fail, it's usually because the company doesn't yet have the know-how to onboard and use them.
Technical depth on known domains
Ability to explain past projects clearly
Culture fit and communication style
Speed of answers to structured questions
Confidence and presentation
How they talk about past failures and reversals
What they pushed back on — and why
Decisions made with incomplete information
How they respond when you challenge their answer
What they say they don’t know
What good looks like: Teams that consistently hire senior engineers with real judgment redesign the interview around ambiguity — not capability. They present real, unresolved problems from inside the company — not sanitised case studies. They watch for discomfort tolerance, not just answer quality.
If you chose C, you are not in bad company. The majority of scaling tech companies we speak with are running hiring on intuition, historical patterns, and optimism. They have no reliable signal on the cost of an open senior seat. They have no structured way to assess hire quality past the first 90 days. And they have no feedback loop connecting hiring outcomes to hiring decisions.
This is not a data problem. Most companies have more data than they use. It is a systems problem — there is no mechanism that connects what happened in the hiring process to what happened six months later in the role.
"The companies that have felt both A and B in the same year are almost always the ones running a hiring process that was never designed to prevent either one."
Time-to-fill is tracked. Cost of vacancy is not.
Offer acceptance rate is monitored. Quality-of-hire at 6 months is not.
Interview pass rates are known. Interview predictive validity is not.
Hiring manager satisfaction at 30 days is collected. At 12 months — rarely.
Sourcing channel data exists. Signal quality per channel is almost never compared.
Cost of vacancy — calculated weekly, per open senior role
Quality of hire score — hiring manager assessment at 30/90/180 days
Pipeline coverage ratio — qualified candidates in active conversation vs. projected openings
Interview-to-hire predictive score — did what we saw in process match what we got in role?
What good looks like: Teams that have solved C have a closed feedback loop between hiring process and outcomes. Every hire is reviewed at 90 and 180 days. Over time, the process learns what to look for and what to discount.
A and B and C are not separate problems. They are symptoms of the same underlying reality: most companies built their hiring infrastructure during a period when there was an abundance of applicants, a functioning junior pipeline feeding the senior layer, and senior talent who participated in the same market as everyone else. That period ended gradually — and then quickly.
The Stanford Digital Economy Lab data (Brynjolfsson, Chandar & Chen, 2026) makes the mechanism clear. AI is compressing entry-level hiring in AI-exposed fields — software, data, operations, finance, HR — while senior workers in those same fields are flat or growing. The junior pipeline feeding into the levels below senior is thinning. The career ladder that used to produce senior talent organically from within is broken at the bottom rungs.
The implication: Companies competing for senior technical talent in 2026 are not competing against a pool of active applicants. They are competing against relationships and trust other companies built with passive talent. If your hiring process only activates when a role opens, you are already behind.
This is not about adding a new tool. It is about restructuring when and how the hiring function operates.
1
Identify the 10–15 senior roles that are likely to open based on roadmap and growth trajectory. This is the list your pipeline should be built around — before the urgency forces your hand.
2
The goal is not a list of people who have applied. It is a list of people you know, whose judgment you have assessed informally, and who know enough about your company to consider a move when the timing is right for them.
3
Introduce at least one unstructured, genuinely ambiguous scenario drawn from a real situation inside your company. Watch for discomfort tolerance, the quality of the questions they ask, and what they say they do not know. Calibrate your panel debrief to these signals — not interview performance.
4
Every senior hire should be assessed by the hiring manager at 30, 90 and 180 days against the signals that emerged during the process. Over 6–8 hires, patterns emerge that change what you weight in future interviews. This is how the process learns.
5
Once you know what an open senior seat is actually costing you per month, the investment in a proactive system calculates itself. Most companies that do this exercise for the first time move within a quarter.
If you have felt A, B, or C — or all three — the audit below is where we start. Twenty minutes, no prep required, and a straight answer on what would actually move the needle for your team.
We look at your current setup and tell you directly: what is working, what is not, and what a proactive system would look like for your specific stage.
Book the Audit →An 8–12 week structured engagement that audits, redesigns and deploys a TA setup your team owns. Fixed fee. No retainer. No fluff.
Learn More →AI-native platform that connects companies with senior talent before roles open. Built for the way this market actually works.
Join Waitlist →Twenty minutes, no prep, no pitch deck. Just an honest look at your current setup and a straight answer on what would move the needle.
© 2026 Recberry · Research: Stanford Digital Economy Lab, Brynjolfsson, Chandar & Chen (2026) · LinkedIn Global Talent Trends (2026) · Korn Ferry Compensation Data (2026) · WEF Future of Jobs Report
Arrived from an external link? Browse the other reports in this series or see the full list.
What 4 million recruiter messages reveal about single-touch response rates — and why the passive market is not on job boards.
Read report →Three patterns breaking senior technical hiring — vacancy, quality-of-hire, and no feedback loop.
Read report →Stanford payroll data on who is actually applying — and what it means for senior hiring.
Read report →