Embedded Recruitment:
Your 8-Week Getting-Started Guide

In ten-plus years of running embedded recruitment engagements - across a container-technology company, a strategic design studio, a German-UK tech business, a domain infrastructure provider, and a performance-marketing platform - I have seen one pattern repeat itself with near-perfect reliability: the engagements that fail do so in the first eight weeks. Not because the recruiter was poor, not because the market was thin, but because the setup was wrong. The brief was vague. The stakeholders were not aligned. The hiring manager had no time for calibration calls. The process had not been agreed before the first candidate was presented.

This guide is for founders, HR leads, and operations directors who are seriously evaluating embedded recruitment and want to know what the engagement actually looks like from the inside. Not the sales pitch - the reality. Week by week, what happens, what is expected of you, and what good looks like at each stage.

Before Week 1 - Getting the Brief Right

The single most common reason embedded recruitment underperforms is not a sourcing problem. It is a brief problem. Most agencies - contingency recruiters especially - accept a vague brief because they need to get moving. They take a job description, perhaps a salary band, and start sending CVs. The hiring manager rejects the first three shortlists, the recruiter loses trust, and within six weeks everyone is frustrated.

Before week one begins, an embedded engagement requires a proper kickoff - not a 20-minute introductory call but a structured working session, typically 90 minutes to two hours, with every relevant stakeholder in the room. The output of that session is a working brief document that covers:

• Team structure: who the hire reports to, who they work alongside, team size and composition, how the team currently functions.
• Culture nuance: what kind of working style actually fits this team - not what the values page says, but what the hiring manager genuinely values day-to-day. This is the thing most recruiters never ask.
• Must-have vs. nice-to-have: a clear, agreed, written distinction between non-negotiables and preferences. Without this, shortlist reviews become arguments about personal taste.
• Interview process: every stage, who is involved, what is being assessed at each stage, and how long each stage takes. This matters for candidate experience and timeline management.
• Offer approval chain: who has authority to approve an offer, what the budget ceiling actually is, and how quickly an offer can be turned around once a decision is made.

Skipping or rushing this stage does not save time. It costs time - usually four to six weeks of it, recovered at the worst possible moment: after a candidate has invested three interview stages and received an unexpected rejection.

Week 1 - Immersion

The first week of an embedded engagement is not about sourcing. It is about understanding. An embedded recruiter who starts sending LinkedIn messages on day one is an embedded recruiter who will need correcting by week three. The immersion week exists precisely to prevent that.

In practice, week one looks like this:

• Stakeholder interviews: one-to-one sessions with the hiring manager, the direct team lead if different, any relevant technical or functional heads, and ideally someone who was recently hired into a comparable role. The question is always the same: what does great actually look like, and what does it feel like to work here?
• Reviewing previous hires and rejections: looking at the last two or three successful hires - where they came from, what their background looked like - and reviewing any rejected candidates from previous attempts. Rejections are especially valuable; they tell you where the real filters are.
• Understanding team dynamics: what communication style dominates, how decisions get made, what the working rhythm looks like. This shapes how candidates are briefed and how the role is positioned in the market.
• Setting up communications infrastructure: a dedicated Slack channel (recruiter, hiring manager, relevant stakeholders), a shared interview calendar, and a weekly stand-up cadence - typically 30 minutes on Monday morning to review pipeline and agree priorities for the week.

Week 2 - Strategy and Sourcing Launch

With the brief locked and the immersion complete, week two is where the sourcing engine starts. But before a single outreach message goes out, the strategy needs to be agreed. This is another point where embedded differs from agency recruitment: you are not outsourcing the thinking, you are building shared ownership of the approach.

The week two deliverables are:

• Final job brief: the working document from the kickoff, refined with inputs from the immersion week, reviewed and approved by the hiring manager. This is the canonical reference for all screening and shortlisting decisions.
• Sourcing strategy: a written breakdown of where the target talent pool is, how it breaks down between active and passive candidates, and the primary channels. For most roles, this includes LinkedIn Recruiter search setup, job board strategy (which boards, which positioning), and referral activation within the existing team.
• Active vs. passive candidate mix: agreed upfront. Some roles are best filled by active candidates; others require 80% passive outreach. Getting this wrong wastes sourcing budget and recruiter time.
• Outreach messaging: personalised messaging templates agreed with the hiring manager. Not generic InMail scripts - actual positioning that speaks to why this opportunity is worth a conversation.
• Referral activation: a structured ask to the existing team, usually via Slack, with clear context on what they are looking for. Referrals close faster, integrate better, and have lower attrition - they should never be an afterthought.

By the end of week two, active outreach has begun, job postings are live, and the first set of inbound applications is starting to trickle in. The pipeline is not populated yet - but the machinery is running.

Weeks 3–4 - Pipeline Build

This is the phase where most of the sourcing volume happens and where the quality of the brief-setting work in weeks one and two pays dividends. A healthy pipeline at the end of week three typically looks like: 40–60 candidates in screening, 8–12 who have responded positively to outreach, and 3–5 who have completed a first recruiter screen.

By the end of week four: 80–120 candidates contacted, 15–25 conversations active, 8–12 screened, and 4–6 ready for hiring manager review. These numbers vary significantly by role seniority and market tightness - senior engineering roles in London take longer; commercial roles in mid-market SaaS move faster - but the ratios hold.

Shortlisting criteria

Shortlisting is not just filtering by keywords. It requires applying the must-have criteria established in the brief, calibrating against the cultural observations from week one, and making a judgment call about fit that a screening algorithm cannot make. This is where the recruiter's embedded knowledge earns its cost.

Hiring manager calibration calls

The single most common problem in weeks three and four is hiring manager availability. When calibration calls do not happen - because the hiring manager is busy, deprioritises them, or assumes the recruiter can just keep sending more CVs - the pipeline drifts. Shortlisting criteria are applied inconsistently. The recruiter fills in the gaps with assumptions. By week six, there is volume but low quality, and the hiring manager's confidence in the process has eroded.

Calibration calls in this phase are short - 20 to 30 minutes, once or twice a week - and the agenda is simple: review two or three screened profiles together, discuss what resonated and what did not, refine the criteria, and agree on who gets moved forward. That is the entire meeting. The recruiter runs it; the hiring manager provides signal.

Week 5 - First Shortlists

By week five, the sourcing volume has stabilised, the calibration calls have sharpened the shortlisting criteria, and the first formal shortlist is ready for presentation. What good shortlist delivery looks like is worth stating explicitly, because it is often done badly.

A well-structured shortlist contains three to five candidates - never more than five. Hiring managers who receive ten-candidate shortlists stop engaging with them properly. Three to five forces the recruiter to make hard editorial decisions, which is what they are there for.

Each candidate profile in the shortlist includes:

• A structured summary written specifically for this role - not a CV paste, but a narrative that connects the candidate's experience to the specific requirements.
• A recommended ranking with a brief rationale (e.g., "recommend as first-choice - strong match on X, slight gap on Y which we discussed and is manageable").
• Any relevant context from the screening conversation that does not appear in the CV: motivation for looking, notice period, flexibility on salary, specific questions or concerns they raised.
• Suggested interview approach for each candidate based on what needs to be probed.

After delivery, the recruiter walks the hiring manager through the shortlist - not via email, but on a 30-minute call - answers questions, agrees on who to progress, and takes ownership of scheduling all interviews within 48 hours of that call. Candidates who have been through a first recruiter screen and are waiting for a hiring manager interview should wait no more than five working days.

Weeks 6–7 - Offers and Decisions

By weeks six and seven, at least one candidate is at or near offer stage. How this phase is handled determines whether the hire happens or whether the process falls apart at the final hurdle - which, frustratingly, is where the majority of recruitment failures occur.

Offer management

Offer management is not "send the offer and wait." It requires active management of the candidate's decision-making process. Before an offer is made, the recruiter should know: the candidate's realistic floor on compensation, whether there are competing processes, what matters most to them beyond salary (title, flexibility, equity, growth), and what reservations they have that have not been fully addressed.

None of this information is obtained by asking once at the beginning. It is built through ongoing conversation throughout the process. An embedded recruiter who has been in regular contact with a candidate from week two knows vastly more about their decision-making than an agency recruiter who sent them a message in week five.

Counter-offer handling

Counter-offers are not surprises in a well-run process. They are anticipated, prepared for, and discussed with the candidate openly before the offer is made. The question is not "will your current employer make a counter-offer?" but "when your current employer makes a counter-offer, what is your decision framework?" Framing it this way surfaces genuine motivation rather than a reassuring answer designed to move the process forward.

Reference check timing

Reference checks should happen before offer acceptance, not after. Running them in parallel with the final interview - rather than as a post-offer condition - keeps the timeline tight and reduces the risk of a delay killing momentum after an acceptance. One verbal reference from the most relevant manager is usually sufficient; two is ideal. More than two is almost always bureaucratic cover rather than genuinely informative.

Week 8 and Beyond - First Hire and What Has Been Built

The first hire is a milestone, but in an embedded engagement it is not the endpoint - it is the first proof point. By week eight, the goal is not just to have made one hire. The goal is to have built the infrastructure to make the next two or three faster.

At the close of week eight, a well-run embedded engagement should leave behind:

• A populated ATS pipeline: every candidate who went through the process is logged with structured notes, outcome reasons, and a "warm/cold" assessment for future re-engagement. The pipeline for the next two or three roles is partially populated before sourcing for those roles has formally started.
• Screening criteria documentation: written, reviewed, and owned by the hiring manager. Not the recruiter's internal notes - a proper document that can be handed to a new recruiter, used for future interview training, or referenced when the role reopens in 18 months.
• Hiring manager brief templates: standardised brief formats for each role type filled in the engagement, so future kickoffs take 30 minutes instead of 90.
• Process documentation: a written record of the interview stages, assessment criteria, scoring frameworks, and offer approval chain. This is what makes embedded recruitment compound in value over time rather than resetting with every engagement.
• Onboarding handover: a structured briefing to the people manager and relevant HR contact, covering the new hire's motivations, concerns, first 30-day priorities, and any commitments made during the offer process that should be delivered on.

What Months 3, 6 and 12 Look Like

The eight-week getting-started guide answers the immediate question - how do we begin, what does the first engagement look like. But the full value of embedded recruitment only becomes visible at the three, six, and twelve-month mark, particularly when compared against what the same budget would have produced through a traditional agency model.

The cost trajectory tells only part of the story. The more important metric at month twelve is agency reliance. A company that has run embedded recruitment well for a year does not need to reach for an agency when a new role opens. It has a brief template, a sourcing playbook, a populated ATS, and a set of hiring managers who know how to brief a recruiter properly. That capability does not exist in a transactional agency model - it cannot, because the agency has no incentive to build it.

Time-to-fill also trends downward materially by month six. The third and fourth hires in an embedded engagement consistently close faster than the first two - not because the market is easier but because the internal process has fewer delays, the hiring managers have more confidence, and the ATS already contains warm candidates who were second-preference choices from earlier rounds and are now ready to re-engage.