How does embedded RPO work?
Embedded recruitment process outsourcing works by placing a dedicated recruiter inside your hiring team and running a defined process from day one. In the first fortnight the recruiter learns the roles, writes a sourcing thesis with each hiring manager, runs targeted outreach and delivers an assessed shortlist. After that the same recruiter coordinates interviews, manages offers and sends a weekly pipeline report. This is what embedded RPO looks like in practice, who does what, and what you need to provide.
"We have never used a recruiter who sits inside the team. What actually happens in the first two weeks, what do you need from my hiring managers, and when do I see a real shortlist?"VP Engineering, Series B SaaS · hiring four backend engineers
The promise of Embedded RPO is a faster, higher-quality hiring process. But for most engineering leaders who have not worked with an embedded model before, the mechanics are unclear. What does the embedded recruiter actually do each day? What does the company need to provide? What should a shortlist look like, and when does it arrive?
This guide walks through the first 14 days of a Talhive embedded RPO engagement, stage by stage, so you know exactly what to expect before you start.
Why the first 14 days matter most.
The quality of week one determines the quality of month three. This is not a figure of speech. Every structural problem that will affect a search pipeline originates in the brief development phase. A vague brief produces vague sourcing, which produces a vague shortlist, which produces a frustrated hiring manager who says the recruiter is not delivering.
The reality is that the recruiter can only work with what the brief gives them. When that brief is a job description copy-pasted from a previous search, the sourcing strategy will be generic. When it is a proper brief that captures the specific technical problem, the team context, and the compelling reason a strong candidate should care, the sourcing strategy is precise.
The two-week window is also a diagnostic window. By day 14, you will know whether the engagement is calibrated correctly. The first shortlist tells you whether the recruiter understood the brief. The hiring manager's reaction to it tells the recruiter whether the brief was accurate. That calibration loop, run early, prevents the slow drift that afflicts searches that do not build feedback systematically.
The 14-day process, stage by stage.
-
1
Days 1 to 3: Immersion
The embedded recruiter joins the company's Slack or Teams workspace, gets access to the ATS and any shared hiring documents, and schedules one-on-one sessions with each hiring manager. These are not briefing calls in the traditional sense. They are conversations designed to understand the team's technical context, the dynamics between the people already there, the problems the incoming hire will own, and the environment they will be stepping into. The output is not a job description. It is a set of notes that will form the foundation of a sourcing thesis.
-
2
Days 4 to 7: Sourcing Thesis Development
The sourcing thesis is the document that separates an embedded RPO search from a generic agency mandate. It defines, in writing, three things: where the best candidates for this role are likely to be found (specific companies, communities, and signals, not just "LinkedIn"), what will attract them to this opportunity (the compelling case, grounded in what is actually true about this company, not marketing language), and what will differentiate the outreach in a market where every engineering leader receives multiple messages per week. Most agencies skip this step entirely and move straight to Boolean searches. The sourcing thesis takes longer upfront and produces materially better pipelines downstream.
-
3
Days 7 to 10: Active Sourcing
With the sourcing thesis written and reviewed by the hiring manager, active sourcing begins. This involves LinkedIn and GitHub sourcing based on the specific targets identified in the thesis, outreach to relevant engineering communities and networks, and personalised first-contact messages that reference the candidate's specific work or background. The target by day 10 is 60 to 80 relevant candidates identified and 20 to 30 in active conversation. These numbers are the output of thesis-based sourcing, not spray-and-pray outreach.
-
4
Days 10 to 14: Shortlist Assembly and Calibration
Screening calls run with candidates who have expressed interest and passed an initial assessment. The embedded recruiter is evaluating technical depth, motivation, and fit against the sourcing thesis, not just availability and rough profile match. The first three to four candidates who clear screening are shared with the hiring manager as a calibration shortlist: not the final list, but enough to get directional feedback on whether the search is on track. Each candidate comes with a written assessment covering strengths, concerns, and the recruiter's recommendation. RPO in India engagements that skip this calibration step typically need to rebuild the pipeline from scratch after six weeks of misaligned submissions.
The first shortlist is also a test of the brief. If the hiring manager's reaction surprises the recruiter, the brief was the problem, and day 14 is the cheapest time to find that out.
What a proper shortlist looks like.
A shortlist from an embedded RPO engagement is not a stack of CVs. Each candidate entry includes a written assessment structured around the brief: what they have built that is relevant, what their motivations are for considering a move, where the genuine question marks are, and a clear recommendation from the embedded recruiter on whether to advance to a first interview.
The hiring manager's job at shortlist stage is to evaluate those recommendations and provide calibration feedback, not to re-screen from scratch. If a hiring manager is spending more than 30 minutes per candidate at shortlist review, the shortlist has not been assessed enough before delivery.
The distinction between an assessed shortlist and a CV dump matters enormously in practice. An assessed shortlist with five candidates requires two to three hours of hiring manager time to review. A CV dump with fifteen profiles requires eight to ten. The embedded model pays for itself partly in the time it returns to engineering leaders who should be building product, not screening candidates.
How embedded RPO works vs how people think it works.
| Factor | What it actually is | What people assume |
|---|---|---|
| Sourcing method | Passive outreach, research-led pipeline | Database queries and job board posts |
| Recruiter relationship | Inside your team, continuous direct access | External vendor, transactional engagement |
| Fee model | Monthly fixed or milestone-based | Per-placement percentage |
| Knowledge | Builds institutional context over time | Resets with each new mandate |
| Volume fit | 5 to 30 senior roles per year | Any volume of any role type |
| Outcome metric | Quality, conversion rate, time-to-offer | Number of CVs submitted |
What happens after the first shortlist.
Once calibration feedback comes back from the hiring manager, the search strategy is adjusted if needed and the pipeline continues to build. Interview scheduling and coordination move to the embedded recruiter: they manage the candidate's experience through each stage, maintain regular touchpoints so candidates do not go dark, and surface problems early when a candidate's enthusiasm is cooling or a competing offer is materialising.
Offer management is one of the stages where embedded RPO consistently outperforms agency models. The embedded recruiter has full context on both sides: they know what the company can offer and what it cannot, and they have spent weeks in conversation with the candidate, understanding what matters to them. That context makes the close significantly more reliable than an agency making a call after four weeks of arm's-length involvement.
Pipeline reporting runs weekly throughout the engagement. Hiring managers and leadership receive a regular snapshot of funnel health: how many candidates are at each stage, what the conversion rates are, where the bottlenecks are, and what actions are being taken to address them. This visibility is one of the clearest structural advantages of Recruitment Process Outsourcing services over a multi-agency model, where pipeline data is fragmented across multiple vendor relationships and nobody owns the whole picture.
Send us one open role and tell us when the hiring manager is free in week one. We will map your first 14 days and tell you what we need from your side.
Plan the first 14 days →The variables that accelerate or slow the process.
The 14-day shortlist timeline assumes certain inputs are in place. Hiring managers who are available for the immersion sessions in week one, can provide feedback on the sourcing thesis within 24 to 48 hours, and review the calibration shortlist within two to three days of delivery will consistently see shortlists delivered on or ahead of schedule.
The most common source of delay is not sourcing difficulty. It is feedback latency. When a hiring manager takes ten days to review a four-candidate shortlist, the pipeline stalls. Candidates who were warm at the point of submission may have accepted other offers by the time the calibration call happens. An embedded RPO engagement requires a modest but consistent time investment from the hiring side: one hour per week per active search, and rapid feedback on shortlist submissions.
For more on how to build the brief that enables this process, see how to write an engineering hiring brief that produces better shortlists and how to build a sourcing thesis for engineering roles.
How the models compare: Talhive vs the alternatives.
The table below scores each hiring model against the factors that matter most when building a senior engineering team. Ratings reflect how well each model serves specialist and leadership hiring specifically.
| Criteria | Talhive Embedded RPO |
Traditional RPO Provider |
Staffing Agency |
Internal TA Team |
|---|---|---|---|---|
| Senior / passive talent access | ★★★★★ | ★★☆☆☆ | ★★☆☆☆ | ★★★☆☆ |
| Brief development quality | ★★★★★ | ★★★☆☆ | ★★☆☆☆ | ★★★★☆ |
| Sourcing depth | ★★★★★ | ★★★☆☆ | ★★☆☆☆ | ★★★☆☆ |
| Institutional knowledge | ★★★★★ | ★★☆☆☆ | ★☆☆☆☆ | ★★★★★ |
| Interview process support | ★★★★★ | ★★★☆☆ | ★★☆☆☆ | ★★★★☆ |
| India market depth | ★★★★★ | ★★★☆☆ | ★★★☆☆ | ★★★★☆ |
| Fee predictability | ★★★★☆ | ★★☆☆☆ | ★★★☆☆ | ★★★★★ |
| Time-to-offer (senior roles) | ★★★★★ | ★★★☆☆ | ★★☆☆☆ | ★★★☆☆ |
What to have ready before day one.
The 14-day timeline holds when a few inputs are in place. None of them is large, but each one that is missing costs days. A written hiring brief helps, though the recruiter will build the rest with you in week one.
How to tell it is working by day 14.
By the end of the second week you should be able to judge the engagement on evidence rather than activity. The shortlist should be judged the way you would assess any engineering candidate: on what the person has actually built.
Where the first fortnight goes wrong.
The immersion sessions get skipped because everyone assumes the document says enough. Sourcing starts from keywords.
Shortlist feedback goes to a channel where three people each assume another will answer.
How we run the first fortnight.
We start every engagement the same way: a Role Priority Matrix in week one, a calibration session with each hiring manager and a written sourcing thesis before any outreach goes out. Shortlists arrive with a written assessment for every candidate, and a pipeline report lands every Friday showing roles by stage and conversion. Average time to shortlist across our embedded engagements is 14 days. To see the model next to the alternatives, read how embedded and traditional RPO differ, and check the fee structures before you commit.
See how the first four weeks are structured, including what we deliver in each one.
See the embedded RPO model →