A role open 60 days is a project slipping

A senior role that stays open for two months isn't a hiring problem. It's a project falling behind as the search drags on.

Someone approved that headcount for a reason. The reason didn't go away when the recruiter came up empty.

Why the gap turns into spend

A company doesn't post a principal data engineer or a Salesforce architect for fun. There's a program behind the role, with a date attached, and a leader who promised that date to someone above them.

For the first few weeks, the leader waits. Good candidates take time. By week six they're covering the work themselves or spreading it across a team that's already full. By week eight the program date is at risk and they know it.

That's when outside capacity starts to make sense. The leader can't tell their boss the program slipped over one open seat. They can bring in a team to keep it moving and keep searching for the hire.

A services firm that shows up at week eight with capacity is solving the actual problem. A firm that shows up with resumes is competing with the recruiter who's already failed.

Where to see it

Job boards and company career pages are the obvious source. The trick is the date. Most postings show when they went up, or you can track them yourself week to week.

Reposts count. A role that disappears and reappears with a fresh date and the same description has been open longer than it looks. Compare the text.

LinkedIn tells you more. If the hiring manager is named, look at their recent posts. A leader who's posted the same role three times, each time with a little more urgency, is telling you the search isn't working.

The description itself has signal. I wrote about this in Job posts tell you the budget is real. The tech stack, the program name, the reporting line, the start-date language. "Immediate need" on a role that's been up for ten weeks says everything.

What makes it real

Senior and specialist roles are the strong version. Architects, principal engineers, data platform leads, security specialists, program leads for a named initiative. These are hard to fill and the work behind them can't wait.

A role tied to a named program is stronger. "Lead engineer for our claims modernization" is a project with a deadline. "Software engineer" is a backfill.

Know the difference. The difference between a backfill and a new program walks through it. A backfill for a departed engineer is a smaller signal than a new seat for a new program.

Noise is the evergreen posting. Some companies keep generic roles open year-round to collect resumes. Entry-level roles and high-volume positions don't count either. The clock only matters on roles that someone needs filled.

Who's carrying the weight

The hiring manager is the person to reach. They're doing two jobs right now, theirs and the open one, and they're the one explaining the slip in the weekly status meeting.

Their boss feels it next. A VP of engineering or CIO watching a program date move is a buyer with authority. The program sponsor on the business side feels it last but cares the most, since the outcome they were promised is the thing slipping.

Talent acquisition is the wrong door. They own the search, not the work. Pitching them capacity puts you in a vendor bucket next to staffing agencies.

Say a logistics company has had a principal data engineer for its routing platform posted for nine weeks. Here's an opener to the director of data engineering.

Your principal data engineer role for the routing platform has been up about nine weeks. That's a long time to cover a principal seat yourself on top of running the team. My guess is the platform migration was planned around that hire starting in the spring and the date is now quietly moving. Is that roughly where it is, or did the plan change?

Hook, trigger, misery, exit. Notice what's missing. No resumes. No mention of candidates. You're offering to keep the work moving, not to win the search.

When to move and what to pair it with

Sixty days is the line. Before that, the leader still believes the hire is coming. After ninety, the program has either been rescoped or they've found help. The window between is where you want to be.

It stacks with almost anything. Two or three senior roles open long at the same account tells you a whole program is understaffed. What a cluster of engineering job posts tells you covers that pattern. Pair a stale posting with a new leader who just announced the program and you know exactly who's under the clock.

Don't offer to fill the role. Offer to make the role less urgent. Cover the work, hand it back clean when the hire lands, and you've earned the next project.