Topic 4 — The recruitment lifecycle

Goal: Follow a hire from an open role all the way to a signed offer.

Lesson 4.1 — One req, seven stages

On Yara's first Monday at Northwind Robotics, Marcus Beaufort drops a one-line Slack message on her: "Need a senior backend engineer. When can we have someone?" Then he goes quiet. Yara, three years of hitting sales quota behind her and exactly zero days of recruiting behind her, stares at the message and realizes she has no idea what happens between that sentence and a new engineer walking in the door.

What happens is a repeatable process, and learning its shape is the whole point of this topic. It's called the recruitment lifecycle (or hiring lifecycle): the standard set of stages every hire passes through, in order.

1. Intake — you sit with the hiring manager and pin down exactly what the role needs and who'd be great at it (Topic 8).
2. Sourcing — you go find people who could do the job, most of whom aren't applying anywhere (Topic 5).
3. Screening — a short recruiter call to check basic fit, interest, and logistics like comp and timing (Topic 6).
4. Interviews — the hiring team runs the candidate through deeper rounds, often several over a week or two.
5. Selection — everyone's feedback comes in, you synthesize it, and a decision gets made.
6. Offer & negotiation — you extend an offer and work toward a yes (Topic 7).
7. Closing & handoff — the candidate accepts, and you hand them to People Ops for onboarding.

Imani Okafor, the senior recruiter mentoring Yara, draws it on a whiteboard and taps each box. "Memorize this. Every hire you make walks left to right across these boxes, and when something goes wrong, it went wrong in one of them — you'll know which."

That last part is what makes the lifecycle worth more than a flowchart. Once Yara can name the seven stages, "when can we have someone?" becomes a sequence she can actually run.

Lesson 4.2 — Why it's a funnel, not a line

Yara's sales instinct kicks in fast, because the lifecycle has a shape she already knows cold: it's a funnel.

In her old SDR job, she'd load a hundred leads at the top knowing most would never reply, fewer would take a call, fewer still would become deals. Hiring works the same way. Many candidates enter at sourcing, and fewer survive each stage until, at the bottom, one person is hired.

The drop-off is steep and it's normal. Across the industry, roughly 30–50% of candidates are lost between stages — they don't reply to outreach, they pass on the role, they bomb a round, they take another offer. Stack those losses up and a single hire can require dozens to over 100 sourced candidates. For competitive tech roles the ratio runs even higher; some benchmarks put it near 200 applicants per hire.

You don't need a few perfect candidates. You need a wide top, because the funnel will eat most of them on the way down.

Here's the trap that catches every career-changer. Yara's first reflex was to find the one — source three brilliant engineers and assume one becomes the hire. Imani stopped her cold: "If you line up three, and two go cold and one fails the system-design round, you're back at zero on a Friday with Marcus three weeks deep." You don't source for the hire. You source for the funnel, and you size the top to survive everything the funnel takes out.

Lesson 4.3 — Keeping the pipeline healthy

So how many is enough? That's where pipeline health comes in: having enough live candidates at each stage that you'll still land a hire after the expected drop-off.

Think of it stage by stage for Marcus's backend role. If history says only about half your screened candidates pass the technical interview, and only about two in three offers get accepted, then carrying one finalist into the final round is gambling. Yara learns to keep several candidates moving in parallel — a few in screening, a couple in onsites, one or two close to an offer — so that one decline doesn't reset the whole search.

A pipeline is just that: the set of candidates currently somewhere in the funnel for a given role. A healthy one is full of names moving forward, with enough depth at each stage to absorb a loss.

And this reframes the entire job. Yara came in picturing a recruiter as someone who posts a role and waits for applications to land in an inbox. By week three she's learned the opposite: you don't wait for the funnel to fill, you fill it. You watch the levels at each stage, and the moment one runs thin you go feed it. Keeping a pipeline full and moving, on purpose, every day — that's the work.

Lesson 4.4 — Reading where the funnel leaks

A few weeks in, a search stalls, and Yara learns the skill that separates a recruiter who runs searches from one who just hopes. When a funnel isn't producing a hire, the question is never "is it broken?" It's where is it leaking. Each leak points to a different fix.

• Lots sourced, few reply. The top is wide but nobody's biting. That's an outreach or targeting problem — weak messages, or you're contacting the wrong people (Topic 5).
• Many screened, few pass the technical interview. People look right on paper and in your call, then fall apart in the room. That's a calibration problem — your bar and the hiring manager's don't match, or you're advancing the wrong profile (Topics 3 and 8).
• Many interviewed, offers keep getting declined. People go all the way and say no at the end. That's a comp, candidate-experience, or closing problem (Topic 7).

Yara's stall turns out to be the middle one. Six candidates reached Marcus's system-design round; five got passed on for "not deep enough." When she sits with Marcus, the picture sharpens: she'd been sending strong generalists, and he needed people who'd run distributed systems at scale. The funnel wasn't broken. It was miscalibrated at intake, and now she knows to fix the front of the process, not pump more bodies into the middle.

That's the move. You look at which stage the numbers fall off a cliff, and the location of the leak tells you what to repair.

Lesson 4.5 — Speed, momentum, and the conductor

There's one more force running underneath every stage, and it's the one Yara underestimates most: speed.

Candidates go cold when a process drags. Feedback owed for three days, a final round two weeks out, radio silence after an onsite — each gap chips away at how much someone wants the job. The best people are often off the market within about ten days of starting to look, while the average tech role takes weeks to fill, and in that gap they take a faster competitor's offer. Yara watches it happen: Devon Asante, a strong passive candidate she'd sourced and screened, sits four days waiting on feedback Marcus hasn't sent, then mentions he has a final round elsewhere. She learns to chase feedback like it's on fire, schedule the next step before the current one ends, and never let a candidate guess where they stand.

Which points at what the recruiter actually is across all of this: the conductor. A project manager for the hire. Yara drives the process — books the interviews, collects and synthesizes the feedback, unblocks the stuck steps, keeps everyone moving. But she does not make the final call.

You run the process. The hiring manager makes the decision.

Two more things make this land. From the candidate's side, Yara is Northwind — Devon's main contact, his advocate, his read on the whole company. A responsive recruiter creates a great experience; a silent one drives good people away (Topic 7). And none of this fits in her head: a dozen candidates across seven stages on multiple roles only stays manageable inside an ATS (applicant tracking system, Topic 9), the database that keeps anyone from falling through the cracks.

Worked example — Yara runs Devon's search end to end

Marcus needs a senior backend engineer. Watch one hire cross all seven boxes.

Intake. Yara sits Marcus down for thirty minutes and gets specific: not "a backend engineer" but someone who's run distributed systems at scale, comfortable with Go, senior level, comp band confirmed with Pri Venkat. The miscalibration that stalled her earlier search doesn't repeat, because she fixed it here.

Sourcing. Knowing the funnel will eat most of them, she doesn't line up three names. She sources around forty plausible engineers and reaches out. Devon Asante, happily employed and not looking, replies because her message actually spoke to his work.

Screening. A 30-minute call confirms Devon's interested, available, and inside the comp band. He moves forward; several others don't.

Interviews. The hiring team runs Devon through technical and system-design rounds. Yara schedules each one fast and preps him before every step.

Selection. Feedback lands. Yara synthesizes the notes, walks Marcus through them — and Marcus, not Yara, decides Devon's the one.

Offer & negotiation. Yara extends the offer with Pri's numbers and works through Devon's questions to a yes (Topic 7).

Closing & handoff. Devon signs. Yara hands him to Pri for onboarding and logs everything in the ATS.

Forty sourced. One hired. The funnel did exactly what funnels do, and Yara ran it on purpose at every stage instead of waiting for it to happen.