Your best engineers are spending 30% of their time in hiring loops. Not building. Not shipping. Screening resumes, sitting through phone calls, and calibrating on candidates they'll never meet again. That time isn't free. It compounds. Here's how to know if your process is the problem.

Sign 1: Your engineers review resumes before any technical signal exists

If a resume lands in an engineer's queue before that candidate has demonstrated anything, you've already misdirected expensive hours.

Resume reading is pattern matching against a document that was written to impress, not to inform. An engineer reviewing a resume is doing editorial work, not technical judgment.

The fix isn't a better resume format. It's removing resumes from the engineer's workflow entirely until there's a real work signal to evaluate.

Sign 2: You're calibrating on "years of experience"

Five years of Java experience tells you someone has been near Java for five years. It says nothing about the quality of that proximity.

I've seen engineers with two years of experience outperform people with eight, consistently, because the context of those years matters more than the count. A developer grinding production fires at a three-person startup learns faster than someone maintaining legacy code at a slow enterprise.

Years-of-experience filtering is a shortcut that feels rigorous but isn't.

Sign 3: Phone screens are eating your senior engineers' afternoons

The 30-minute "technical pre-screen" is often an elaborate way to confirm what a basic task would reveal in the same amount of time.

When a senior engineer is doing first-round phone screens, you've assigned a $200/hour person to do a $30/hour job. Worse, their judgment on a phone call is subjective, inconsistent, and impossible to compare across candidates.

This isn't a people problem. It's a process design problem.

Sign 4: You can't explain why two candidates got different scores

If your shortlisting criteria can't survive a five-minute audit, they're not criteria. They're vibes.

Inconsistency at the screening stage doesn't just slow you down. It means you're making high-variance decisions with low-quality inputs, and calling it a process.

Sign 5: You shortlist people who can't ship on day one

The clearest sign your screening is broken is a bad hire. Not incompetence—mismatch. Someone who interviewed well, answered all the right questions, and then struggled with real tasks once they joined.

If your screening process can't distinguish between someone who talks about debugging a production incident and someone who can actually debug one, you're measuring presentation, not capability.

Real capability only shows up when someone has to do the actual thing.

Sign 6: Your hiring cycle routinely runs past six weeks

A six-week hiring cycle for a mid-level engineer is almost always a process bottleneck, not a talent market problem.

When screening is manual and sequential—resumes go to HR, then to a tech lead, then to a call, then to a test—you're introducing handoff delays at every step. Each handoff is a place where context gets lost, enthusiasm drops, and candidates accept other offers.

Parallel evaluation of all candidates against a consistent task, early in the funnel, compresses this dramatically.

Sign 7: You're still running the same process you ran three years ago

Hiring volume has changed. Candidate behavior has changed. The tools available to engineers on the job have changed. Your screening process probably hasn't.

Three years ago, a take-home assignment filtered well. Now, AI can complete most of them in under twenty minutes. Coding challenges that tested for algorithmic recall made sense when that recall was actually required on the job. It isn't anymore.

A process that isn't adapting to new conditions isn't stable. It's stagnant.

What to do instead

The core shift is simple, even if it's uncomfortable to admit: stop evaluating candidates on what they say, and start evaluating them on what they do under real conditions.

That means:

• Get a work signal before any engineer touches a resume

• Use short, job-relevant tasks that reveal judgment, not just syntax

• Evaluate all candidates against the same task so you're comparing real outputs

• Save your engineers' time for the ten candidates who've already proven they can do the work

The hiring funnel should narrow based on demonstrated ability, not polished documentation.

The real insight

Most engineering leaders know their screening process is inefficient. The problem isn't awareness. It's that the alternative feels risky until you've seen it work.

But the actual risk is the current system: opaque decisions, inconsistent signals, and expensive engineers spending their best hours on work that produces almost no useful information.

The resume was never a reliable indicator of engineering ability. You've probably known that for years. The question is whether your process reflects it.