§ CAPABILITY

Engineering Hiring Pipeline Design

The path a candidate takes from first contact to signed offer, measured at every step. Most good candidates are lost to timing rather than to judgement.

Who
Founder holds the engineering leadership seat; the delivery team executes underneath it.
Request a call How the work runs

What you're seeing

A strong candidate withdrew and the reason given was another offer.
Usually means The competing process finished first. That is a latency defect, not a competitiveness one, and it is visible in your own timestamps.
Candidates wait more than a few days between stages.
Usually means Scheduling is being handled by people whose calendars are already full. It is usually the single largest loss in the funnel and among the cheapest to fix.
The job description lists fourteen technologies.
Usually means The requirement list was assembled by committee, with each participant adding their own. It reads as a wish and it filters out exactly the senior candidates who read requirement lists literally.
Offers are constructed from scratch each time.
Usually means There is no levelling framework behind them. The result is internal pay inequity that nobody intended and that surfaces about a year later, usually all at once.

Lost to timing, not to judgement

Most good candidates are lost between stages rather than in them.

Nine days waiting for a second interview slot, because the two people who must run it have full calendars. Ten days of silence after a final round while a decision is coordinated. A take-home that arrives on a Friday with no deadline and no acknowledgement when it is submitted.

None of these is a judgement failure and none of them appears in a hiring post-mortem, because the candidate withdrew citing another offer and that reads as market conditions. It is not market conditions. It is latency, it is in your own applicant tracking data, and the candidates it costs you first are the ones with the most alternatives.

So the first artefact is the funnel with conversion and elapsed time at every stage. It usually moves the problem from where everyone was looking.

The role definition is upstream of everything

A job description listing fourteen technologies was assembled by committee, each participant adding the thing they care about.

It filters accurately — for people who read requirement lists as approximate. Senior engineers frequently read them literally and self-select out, which is the opposite of the intended effect. It also makes the screen impossible to run well, because there is no stated bar to screen against.

The replacement is a description of ownership: what this person will own within a year, what decisions are theirs, and what the first ninety days look like. That is answerable by the hiring manager, checkable by a candidate, and it produces a materially better first conversation.

The offer is a levelling decision

Offers negotiated case by case produce internal pay inequity that nobody intended.

It stays invisible for about a year, and then it is discovered — usually all at once, usually by the people who were underpaid, usually in a way that costs more than the original saving. The fix is not better negotiation, it is a levelling framework decided before offers go out, with the level assessed during the loop rather than argued afterwards.

That frequently means a compensation conversation the company was not planning to have yet, and it is worth having.

Where it sits

This capability sits under Engineering Hiring, which carries the whole thing end to end, and under Fractional CTO and Software Development, where a team is being built as part of a broader engagement.

It hands off in two directions. Interview Loop Design is what happens inside the stages this pipeline moves candidates between. And Onboarding & Ramp-Up is the other end of it — a hire who takes a quarter to contribute costs approximately what a failed hire costs, with the difference that nobody counts it.

How the work runs

  1. Measure the funnel

    Conversion and elapsed time at each stage. The stage where candidates leave is rarely the one people assume.

  2. Cut the scheduling latency

    Usually the largest single loss. A competing process that finishes first wins by default, however good your interviews are.

  3. Define the role properly

    What the person will own in their first year, and which requirements are real. Requirement lists assembled by committee filter out the people you want.

  4. Fix the offer stage

    Levelling decided before the offer, a written rationale, and a response window. Offers negotiated without a levelling framework produce internal inequity that surfaces a year later.

What arrives

  • A funnel with conversion and latency measured per stage
  • A scheduling process with a stated turnaround commitment
  • Role definitions written around ownership rather than technology lists
  • An offer process anchored to a levelling framework

What it costs your team

Around three hours a week from a hiring manager while the pipeline is rebuilt.

Next step

Tell us where this is breaking and we'll say what it takes to fix.

Request a call

How we decide

  • The funnel is measured before anything is redesigned

    Costs It requires applicant tracking data that is frequently incomplete, and cleaning it up takes time before any improvement lands.

    The stage where candidates actually leave is rarely the one people assume. Conversion and elapsed time per stage are cheap to extract and they consistently relocate the problem — usually from the interviews, where everyone's attention is, to the gaps between them, where nobody's is.

  • Scheduling gets a stated turnaround commitment

    Costs It requires interviewers to hold slots they may not use, which they experience as wasted time.

    A competing process that finishes first wins by default, however good your interviews are. Held slots that go unused are a real cost and a small one against losing a senior candidate to a nine-day gap. Naming the commitment also makes the failure visible rather than absorbed.

  • Roles are defined by ownership, not by technology lists

    Costs It means telling several stakeholders that their addition to the requirements is coming out.

    A list of fourteen technologies is a committee artefact and it filters out the people who read it accurately — which correlates with the seniority you were hiring for. What the person will own in their first year is answerable, checkable, and produces a much better conversation with a candidate.

  • Levelling is settled before offers go out

    Costs It forces a compensation conversation the company may not have planned to have yet.

    Offers negotiated without a framework produce two engineers doing the same work on different money, and no defensible answer when they discover it. That discovery is not hypothetical — it happens, it happens all at once, and it is more expensive to correct than to prevent.

Frequently Asked Questions

The sequence a candidate moves through from first contact to signed offer, including the parts that are not interviews: sourcing brief, screen, scheduling, the loop, the decision, the offer and the acceptance. Most of the measurable loss happens in the connective parts rather than in the interviews themselves.
Most often between stages rather than in them — waiting a week for a slot, or hearing nothing for ten days after a final round. Both are process defects, both are visible in the timestamps, and both are cheap to fix relative to what they cost.
No. Sourcing is a different business with a different cost structure, and a provider paid per placement cannot credibly conclude that the pipeline is the problem. We fix the process that sourced candidates then move through.
Two to three weeks from first contact to offer is achievable and competitive. Past four weeks you are systematically losing to processes that move faster, and the candidates you lose first are the ones with the most options.
What the person will own in their first year, what decisions they will make, who they will work with, and which requirements are genuinely required rather than aspirational. Technology lists are a poor proxy for all of that and they actively deter senior candidates.

Sources

Page reviewed