You have three senior roles to fill this quarter. How do you build the pipeline and close the people you want?

Do the arithmetic before promising the quarter

Three accepted offers is an outcome several stages downstream of anything you control, so the first move is to work backwards and see whether the quarter is even possible. The numbers below are not industry figures; they are the assumptions you should be making explicit for your own pipeline, and the point is the shape of the calculation rather than the values.

Stage	Assumed pass-through	Needed to yield three
Offers accepted	3 in 4 offers accepted	4 offers
Onsite loops	1 in 3 loops reaches an offer	12 loops
Screens	1 in 2 screens reaches a loop	24 screens
Candidates in conversation	1 in 3 replies becomes a screen	~70 credible approaches

Two conclusions fall out immediately. Seventy approaches in a quarter is not something that happens by posting a job advert and waiting, and twelve senior onsites is roughly forty interviewer-hours plus debriefs, which is real capacity taken off delivery. If either of those is unavailable, the honest answer is that you will fill two roles this quarter and the third next, and saying that in week one is worth more than discovering it in week eleven.

Recalculate as real data arrives, because the ratios tell you where the problem is. Plenty of candidates and no screens means the role is being marketed to the wrong people. Screens converting and loops not, in volume, usually means the screen is measuring something different from the loop. Offers declining means you are competing on the wrong axis, which is the most expensive failure because it happens after everyone's time is spent.

Sourcing is your job, not only the recruiter's

Inbound applications for a senior role skew towards people who are looking, which is not the same population as people who would be right. The channels that actually work for senior hiring need your name on them, and a manager who describes hiring as something the recruiter does is telling the interviewer how the last search went.

Referrals are the highest-yield channel available and almost always under-worked. The reason is that "let us know if you know anyone" produces nothing — it asks people to search their own memory with no prompt. What produces names is a specific, structured pass: sit down with each engineer for twenty minutes and go through the teams they have worked in, by name, asking who was good and what they were good at. Make the referral bonus visible, but understand that the reason people refer is that they want to work with someone again, and the reason they do not is that they are unsure whether the role is worth their reputation. That second obstacle is fixed by telling them honestly what the job is, including its irritations.

Your own outreach is worth doing personally for a small number of high-fit people rather than scaling a template. Two paragraphs from the hiring manager that mention something specific about the person's work outperform any volume of undifferentiated sequences, and this is one of the few places where being the manager rather than the recruiter is a genuine advantage. Watch also for the pipeline you have already built: past candidates who were close, people who declined an offer eighteen months ago, and engineers who left on good terms are all cheaper to convert than a cold approach.

The pitch has to contain something unflattering

Senior candidates with options are pattern-matching for a pitch that is too clean. Everybody says strong engineering culture, interesting problems and great people, and the sentences carry no information. What lands is specific and includes the trade-off, because the trade-off is what proves the rest is honest.

"Here is the shape of it. You would own the ingestion side of the platform — about a hundred connectors, six years old, with three years of accumulated compatibility work in it, and it is load-bearing for every customer we have. It is not greenfield and you would spend your first quarter in other people's code. What you would get is genuine authority over what happens to it, including the ability to argue for replacing parts of it, and a team of five who know the domain better than I do. The reason the role is open is that the previous lead moved to our data science group, not because anyone left unhappy. The parts you would probably dislike: on-call is one week in five and it does get paged, and we have a compliance review gate on schema changes that adds a few days."

Somebody who wants that job after hearing it will still want it in month three, which is where the value is. A pitch that oversells produces accepted offers and regretted joiners, and a senior hire who leaves in six months costs more than the vacancy did.

Speed and the close

For candidates with several processes running, elapsed time is often the deciding factor, and it is the one variable you control without spending money. A loop scheduled inside a week, a decision inside two working days of the onsite, and an offer that does not disappear into a compensation committee for a fortnight will win you people that a slower, better-paying company was also trying to hire. Scheduling is where most weeks are lost, so protect standing interview slots in the team's calendars rather than negotiating each one.

On the close itself, the mistake is treating it as a pricing negotiation. Money has to be defensible and roughly right, and once it is, the things that move senior candidates are usually the work, the person they will report to, the level and the scope, and whether they believe what they were told. So find out what the actual hesitation is rather than assuming it is the number: "what would make this an easy yes" is a question that gets answered. Where you cannot win on cash, say so plainly and compete where you can. Where the offer is genuinely worse in every dimension, let them go rather than persuading someone into a job they will resent, and keep the relationship — declined candidates are a pipeline.

When the quarter runs out

The question is really a test of what you do at week ten with one hire made, because that is when the bar bends. The organisation will not push you to lower it explicitly; the pressure arrives as fatigue, as a candidate who is nearly there, as the argument that a competent hire now beats a strong hire in two months. Interviewers want to hear that you move the date and not the standard, and that you can say why in terms of cost rather than principle: a mis-hire at senior level occupies the headcount anyway, absorbs your attention for two quarters, is only reversible slowly, and lowers what the team believes the level means.

What you can legitimately change instead is the shape of the search. Widening the pipeline is not the same as lowering the bar: reconsider whether the role really needs your exact stack or whether a strong engineer from an adjacent one would be productive in a quarter, look at candidates who are strong on the competencies that matter and average on the ones you over-weighted, revisit location and working-pattern constraints, and check whether an internal move plus a backfill at a lower level solves the same problem faster. Also consider what the vacancy is doing to the team: three unfilled roles for a quarter means the existing team is absorbing the work, and a manager who has not accounted for that has two problems rather than one.