How to build a hiring plan your recruiting function can actually execute

Here is the situation Adam Kovacs sees most often. A company closes a Series A or hits a board-approved growth milestone. The operating plan says: add 40 engineers in 18 months. The talent function has one recruiter who has been managing 3-4 open roles at a time.

The math does not work. But it is invisible in the plan because the plan models seats, not the pipeline activities needed to fill them.

What actually needs to happen before a single engineer is hired:

• Identify the right sourcing channels for the role types (2-4 weeks for specialized roles where posting does not work)
• Define the technical bar with the hiring team (1 week per role cluster, minimum)
• Build a structured interview process for each new role type (1-2 weeks, and often skipped)
• Train hiring managers on how to conduct those interviews consistently
• Activate sourcing and run the first pipeline to calibration (3-5 weeks for specialized roles, longer if the brief is not tight)

A 40-engineer plan with a 100-day start requires a recruiting function operating at scale on day 1. That function almost never exists on day 1. The people who approved the headcount number and the people who have to deliver it are usually looking at two different realities, and neither conversation has been had yet.

Three questions should get answered before the headcount plan is locked. They take about three hours total to work through with whoever owns recruiting and the leads of the functions hiring.

One: What is the actual time-to-fill for each role type, under current conditions? Not time-to-fill as reported in an ATS with candidate-declined stages filtered out. Actual calendar days from req open to accepted offer. If you do not have this data, use 60-90 days for technical roles as a working assumption until you do. The median time-to-fill across all roles was 44 days in SHRM's 2025 benchmark, and technical and senior-level roles in competitive markets run significantly longer.

Two: What is the maximum concurrent role load the current recruiting function can support without pipeline quality dropping? This is different from "how many reqs are open right now." Most recruiters can manage 8-10 open reqs, but pipeline quality on all of them degrades past 6-7 for technical roles that require active sourcing.

Three: What needs to be built or changed before the first hire in a new role category can close? If you have never hired a data engineer before, you do not have a sourcing strategy for data engineers, a structured interview process for them, or a hiring manager who has calibrated what "senior" means for that role on your team. Those need to exist before the search starts, or you will spend 8 weeks filtering a pipeline that is wrong.

Answering these three questions does not require an external audit. It requires the time and honesty to look at what your recruiting function can actually do.

Three practical paths, in order of preference.

Sequence the hires by lead time, not by priority rank. Long-lead roles need to start first, even if they are not the most urgent on the org chart. Starting them last because they are hard is how you end up 90 days into the plan with no pipeline on the roles that matter most.

Add recruiting capacity before the gap appears, not after it does. Whether that is a contract recruiter, a recruiting operations partner, or a retained search engagement, the capacity needs to be in place before the pipeline work starts, not hired in week 10 when the miss is already visible.

Right-size the headcount plan to what the recruiting function can actually deliver in the timeline. Then reset expectations with the board. A plan that says "we will hire 28 engineers in 18 months with this recruiting function" and delivers 28 is better than a plan that says 40 and delivers 22.

The talent plan should start with the operating plan, not after it. Companies that do this well treat recruiting capacity as an infrastructure problem: something you build in advance so it is ready when you need it.

The thing worth checking in your own plan: does it say how many people you need to hire, or does it also say how the recruiting function will be staffed and sequenced to hit that number?