Skip to main content

The Role That Will Not Close: A Diagnostic for Tech Vacancies Open Six Months in a Market Full of Candidates

By Thoughtgears 9 min read
A young woman in a suit during a job interview, writing notes.

There is a particular kind of quiet in a hiring pipeline that has stopped moving. The role is still live. The agency still sends CVs. Somebody still owns it on a spreadsheet. And nothing has happened since April.

Most teams respond by raising the salary. It rarely works, because salary is usually not the binding constraint. Roles stay open because of strict location requirements, narrow stack demands and unrealistic seniority expectations, and money does not fix any of those (Techstaq, April 2026).

Meanwhile the cost accumulates in places nobody reports. The roadmap slips. A senior engineer covers the gap at partial capacity. Interview time gets spent on candidates who were never going to clear a bar nobody has written down.

The useful move is not another advert. It is a diagnostic. Below are five questions to run against a role that has been open too long, in the order they most often find the problem. Four of them are about your requirements. The fifth is about whether the role should exist in that shape at all.


Why a tech vacancy stays open when the candidates exist

Roughly 57% of EU firms say they cannot find qualified tech staff (Index.dev, 2026). That statistic gets used to explain every unfilled role, which is exactly the problem: it is true in aggregate and useless as a diagnosis.

The shortage is a shape, not a volume

Look at where demand actually concentrates. Cybersecurity, AI and machine learning, and cloud show sustained strength, while generalist and entry-level hiring has become more cautious (IT Job Board, Q3 2026). So a security architect and a mid-level backend developer sit in genuinely different markets.

If you are hiring the second and calling it a shortage, the shortage is not the reason. Something in your requirements is.

What the salary theory misses

Candidates are more settled than they were in 2021. Many are well paid, reasonably happy, and will move only for a clear improvement (Techstaq, April 2026). That changes what money buys. A 10% uplift moves someone who was already considering leaving. It does nothing for someone who was not.

Meanwhile senior and specialist processes now see longer timelines, more drop-out mid-process, and more counteroffers (Optima Europe, 2026). Those are all process failures rather than pay failures, and pay will not solve any of them.

Diagnostic one and two: the location constraint and the stack shopping list

Is the location requirement real or inherited?

Write down why the role requires someone within commuting distance of your office. If the answer is a specific, defensible reason (hardware access, a client site, a regulated environment), keep it and accept the smaller pool.

If the answer is that the team is hybrid three days a week because that is what was decided in 2023, you have made a policy decision that is costing you a hire. That may still be the right trade. Make it deliberately, and price it.

The pool difference is not marginal. A role open to one metropolitan area versus one open across Europe is a different search by an order of magnitude.

Is that a tech stack or a wish list?

Take the job description and mark each technical requirement as either “cannot do the job without this on day one” or “would learn in a fortnight”. Most engineering job descriptions have three or four genuine requirements and eight decorative ones.

The decorative ones do real damage. They deter capable applicants who self-select out, and they anchor your own screening on the wrong signals. Skills-based hiring shows 15% higher retention and 18% faster time-to-productivity than credential-based screening (Taleva, 2026), largely because it tests what the job needs rather than what the advert listed.

Diagnostic three: is the seniority band honest?

Two failures live here, and they look identical from the outside.

The title inflation problem

The first is asking for a senior engineer at a mid-level salary. This is more common than anyone admits, usually because the band was set two years ago and the market moved. Check your band against current benchmarks before concluding that nobody good applied.

The second is subtler: asking for seniority the role does not need. A “senior” label attached to work that is genuinely mid-level will attract senior candidates who leave within a year once they see the scope. That is not a hiring win.

Counteroffers and what they tell you

If you are losing people to counteroffers at offer stage, note what that means. You reached the end of a process with someone who was persuadable, and their current employer moved faster than you did on the thing that mattered to them.

Counteroffers are a speed and clarity signal more than a money signal. Candidates who receive a compelling, specific offer early rarely wait around to be counter-bid.

Diagnostic four: how long is your process, and where do people leave?

Count the stages. Then count the calendar days between first contact and offer, including the gaps where nothing happened because someone was on holiday.

Measuring drop-out by stage

Most teams do not track this and should. Take your last ten candidates and mark where each one stopped. A cluster at one stage tells you something specific: a take-home exercise that costs eight hours, a panel that reads as hostile, a two-week silence after the second interview.

Longer processes in Europe are partly structural: regulatory requirements genuinely lengthen time-to-hire in some markets (Taleva, 2026). That is not licence for a five-stage process with three-week gaps.

Cutting stages is not the same as lowering the bar. A well-designed three-stage process assesses more reliably than a sprawling five-stage one, because it is designed rather than accumulated.

Diagnostic five: is this a hiring problem at all?

The question that closes most six-month vacancies

Ask what the role needs to remember.

Some roles need continuity. Domain knowledge built over years, architectural ownership, on-call responsibility, the institutional memory of why a decision was made in 2023. Hire those permanently, fix the four issues above, and accept that it takes time.

Other roles do not. A bounded build, a migration with an end date, a specialist capability needed for two quarters, surge capacity against a launch. Those are capacity requirements that have been written up as job descriptions because a job description is the instrument everyone reaches for.

When you separate the two, the permanent list usually shrinks to one or two roles, which is a list you can actually fill with the attention it deserves. The rest can start in weeks.


Final Thoughts

A role that has been open six months is not waiting for the right candidate to appear. It is telling you something about how it was defined, and the longer it stays open the more expensive the message becomes.

Run the five questions in order. Most teams find their answer in the first two, because location and stack requirements accumulate quietly and nobody revisits them once the advert is written. If those come back clean, look hard at your process length and your drop-out points, which are the failures that pay rises cannot reach.

Then ask the fifth question honestly. Not every gap in a team is a person-shaped gap. Some of them are work-shaped, with a beginning and an end, and treating those as permanent headcount is the single most common reason a vacancy sits live from spring to autumn achieving nothing.

If you have a role in that position now, book a discovery call. We will run the diagnostic with you, and if the answer is that you should keep hiring, we will say so.

Ready to scale your tech team? Get in touch with Thoughtgears: we’d love to hear about your project.


FAQs

Why do tech vacancies stay open when there are candidates available?

Usually because of constraints rather than scarcity. Strict location requirements, narrow tech stack demands and unrealistic seniority expectations keep roles open even at competitive salaries (Techstaq, April 2026). The shortage is real in specialist areas, but it explains fewer unfilled roles than people assume.

Will raising the salary close a long-open role?

Sometimes, but it is the least likely fix. Candidates in 2026 are relatively settled and move for a clear overall improvement rather than a modest uplift. If your band is genuinely below market, correct it, then check whether that was really the blocker.

How long should a technical hiring process take?

Three well-designed stages inside three to four weeks is achievable for most roles. What matters more than the number is the gaps between stages. Two weeks of silence after a second interview loses candidates who were otherwise ready to accept.

How do I know if my job description is too narrow?

Mark each technical requirement as either essential on day one or learnable in a fortnight. If more than four sit in the first group, the description is probably filtering out people who could do the job well.

Is hybrid working costing us hires?

It costs you pool size, which may or may not matter. The test is whether the office requirement has a specific reason behind it. If it is inherited policy rather than an operational need, you are paying for it in time-to-hire without having decided to.

What does a high counteroffer rate tell us?

Usually that your process is slow or your offer is not specific enough about what changes for the candidate. Someone with a compelling, early, concrete offer rarely waits to be counter-bid by their current employer.

Should we track candidate drop-out by stage?

Yes, and most teams do not. Take your last ten candidates and mark where each stopped. Clusters point directly at the broken stage, whether that is an over-long take-home task or an unstructured panel.

What is skills-based hiring and does it help?

It means assessing what someone can do rather than which credentials or job titles they hold. It shows 15% higher retention and 18% faster time-to-productivity than credential-based screening (Taleva, 2026), largely because it tests for the actual work.

When should we stop recruiting and use augmented capacity instead?

When the work has a defined end, needs a specialist capability for a limited period, or is blocking a deadline that will not wait for a four-month search. Continuity-critical roles still deserve a permanent hire.

What has the role cost us while it has been open?

Unshipped roadmap value, senior time diverted to cover, the interview hours spent, and the delay to anything downstream. For a role open since spring, that total commonly exceeds a year of contracted capacity and it has produced nothing.

Disclaimer

This article is for general guidance only and reflects analysis based on sources available at the time of writing. Thoughtgears is not a legal, financial, employment, or tax adviser. Always seek qualified professional advice before making hiring, investment, or compliance decisions.

Need a dedicated development team?

Thoughtgears sources, vets and fully manages the engineers who work as your team – you simply direct the work. Book a free discovery call to scope what you need.

Book a discovery call

More from the blog

Book a call