“I can’t find a developer”: what if the problem is your job ad?

Is the developer shortage real?

Partly. Tech hiring stays competitive: the BLS projects 10% growth in software developer, QA analyst and tester jobs between 2025 and 2035, much faster than the average for all occupations. Demand is strongest, and supply tightest, for senior, DevOps and data profiles. If you’re finding one of those hard to fill, you’re not imagining it.

But the picture has two sides. After the 2021–2022 hiring frenzy, the market also cooled: openings came down from their peak and the number of applications per role rose. In other words, the pool of developers who are open to a move does exist, and on most stacks it has actually grown. So the real question isn’t “are there candidates?” but “does your job ad capture the ones who are out there?”

That’s where the lever nobody looks at is hiding. You can’t change the market. But your job ad, your salary range and your process — those you can change this afternoon.

Does your job ad make anyone want to apply?

Most developer job ads look alike: a list of technologies, a list of tasks, a list of expected qualities (“rigorous, self-starter, passionate”). A good developer reads ten of these a week. Yours has to tell them, in a few seconds, what they’ll be working on, with whom, and why it’s worth it. If it doesn’t answer that, they move on to the next one without even applying.

A few signals that drive candidates away without you realizing it:

One point that’s often underestimated: developers read a job ad as a sample of your engineering culture. A vague job description, stuffed with buzzwords or piling up fifteen mismatched technologies, suggests that nobody internally really knows what they’re doing. That may not be true at your company, but that’s the message that lands. Our guide to writing a developer job ad that attracts candidates walks through the fix, checklist included.

• A catch-all tech stack (“React, Angular, Vue, Python, Java, Go”) that suggests you don’t know what you’re looking for.
• No information about the team, the product or what the developer will actually build.
• A copy-paste of generic HR jargon, without a single sentence that speaks to the craft.
• Unrealistic requirements (“5 years of experience on a technology that’s only 3 years old”) that discredit the ad in the eyes of anyone who knows the field.

Is your salary advertised, and is it at market?

This is the sore subject, so let’s tackle it head-on. A job ad with no salary advertised is a filter that works against you. Many good developers simply don’t apply to a posting with no range, because they refuse to commit to a process only to discover after three interviews that the budget doesn’t add up. Hiding the figure doesn’t protect you, it costs you candidates; the data and the usual objections are in our guide on whether to show the salary in a developer job ad.

Second problem: aiming below market without knowing it. In tensionscore’s US benchmarks (national level, updated July 2026), a front-end, back-end, full-stack or mobile developer earns roughly $65k to $105k base as a junior, $95k to $138k at mid-level and $125k to $175k as a senior, with DevOps and data running higher. A mid-level full-stack developer, for instance, sits around $102k to $132k nationally — about $128k to $165k in major metros like the Bay Area, New York or Seattle, and $97k to $125k for fully remote roles. Treat these as benchmarks built on BLS and Robert Half data, not as a fixed scale.

If your offer is clearly below market for the profile you’re targeting, no well-written job ad will close the gap. And a detail many owners forget: base salary is only part of the cost. Employer payroll taxes and benefits come on top, and tensionscore budgets a fully loaded cost of about 1.3 times base. Thinking in fully loaded cost, rather than advertised base, often changes how your budget looks.

Is your hiring process too slow for the market?

You can have the best job ad and the right salary, and still lose your candidates by moving too slowly. A good developer who is actively looking often has several leads running in parallel. If it takes you ten days to reply to their application, then four interviews spread over six weeks, they’ll have signed elsewhere before your final meeting. The most qualified candidate is also the one who gets snapped up fastest.

Time-to-hire for a developer is measured in months: tensionscore’s benchmarks put it at one to three months for front-end and QA roles, two to four for back-end, full-stack and mobile, and up to five or six months for DevOps, data and tech-lead roles. Part of that is imposed on you by the market. But part of it comes from inside: feedback that drags, a decision-maker who’s never available, an oversized take-home test that discourages people. Those days are yours, and each one is expensive.

Because time-to-hire isn’t financially neutral. As long as the role is unfilled, the work isn’t done: product delays, an overloaded existing team, an opportunity pushed back. This cost of delay adds to the cost of recruitment itself — SHRM puts the average cost per hire at nearly $4,700, and a contingency recruiter typically charges 15% to 25% of first-year base salary (tensionscore budgets 20%). It’s this sum — fully loaded salary plus recruitment plus delay — that makes up the true cost of the first year.

How do you find out what’s blocking your job ad?

General advice only goes so far. Your blocker is specific. Maybe your job ad is excellent and your only problem is a salary one notch too low. Maybe it’s the reverse. You won’t find out by reading averages: you’ll find out by looking at your own text against the right benchmarks.

That’s exactly what our tool does. You paste in the text of your job ad and you get a tension report: a difficulty score out of 10, the estimated median time-to-hire for that profile, the true cost of the first year (fully loaded salary, cost of recruitment, cost of delay), the red flags that drive candidates away, and a recommended salary range calibrated against US market benchmarks. The calculation is entirely deterministic and draws on dated public sources (BLS wage data, the Robert Half salary guide, the Stack Overflow Developer Survey, SHRM): no figure is invented.

And if the diagnosis reveals that the role is tight and that you can’t afford to wait several months, there’s another path besides hiring a full-time employee at any cost. Bringing in an external developer, like those in the neodev collective, lets you ship while the longer recruitment runs its course; we compare the options in full-time hire, freelancer or agency. It isn’t the opposite of hiring: it’s often what gives you the time to hire well.