Skip to main content
Bluecoders

What an RPO Engagement Actually Looks Like, Step by Step

Cécilia FilleNovember 19, 2026

Summary: an RPO engagement runs in five stages: scoping the need, choosing the recruiter, immersion in your teams, operational recruiting, ongoing follow-up. You approve the recruiter before anything starts and keep the final hiring decision. This article details each stage, what you receive, what stays on your side and how to measure that the engagement is moving forward.

You already know what RPO is. The question that remains is different: what do the next few months actually look like once you sign? Who does what, from when, and how do you know it's progressing?

This is often the sticking point right before the decision. Sales pages describe a model, rarely a day-to-day reality. So here is the real sequence of an engagement, stage by stage, with what falls to you and what no longer does.

The stages of an RPO engagement in tech recruitment

Key takeaways

  • An RPO engagement is structured in five stages: scoping, choosing the recruiter, immersion, recruiting, follow-up.
  • You approve the recruiter before the engagement starts. It's not an assigned profile, it's a shared decision made during scoping.
  • Immersion takes a few days, long enough for the recruiter to understand your stack, your rituals and your implicit criteria.
  • You keep the final hiring decision. RPO absorbs the operational workload upstream, not the judgement call.
  • Duration is set by your hiring plan, not a standard package. It's defined during scoping and adjusted afterwards.

Stage 1: scoping

Everything starts with a conversation, not a contract. The goal is to understand your context before proposing anything: the roles to fill, your current organisation, what's getting in the way today.

This scoping stage defines the exact perimeter of the engagement: which roles, what volumes, what timelines, what tools, what duration. It also sets the ground rules, in particular how responsibilities are split between the recruiter and your teams.

One point deserves attention here rather than later: exclusion criteria. What you don't want is often more revealing than what you're looking for, and it's what keeps shortlists from missing the mark by week three.

Scoping is also where the format gets decided: full time or part time, on-site or remote, full scope or sourcing-focused. To understand what sets these options apart from a traditional agency, our article on recruitment agency versus RPO lays out the criteria for choosing.

Stage 2: choosing the recruiter

This is the most decisive stage, and the one many providers skip over.

The quality of an RPO engagement depends on a person, not a brand. A recruiter who knows your vertical identifies the right profiles and speaks the language of your engineers. A generalist will spend weeks figuring out what sets an SRE profile apart from an infrastructure engineer.

At Bluecoders, you're presented with one or more profiles, chosen for their specialisation in your field: development, data, DevOps, cybersecurity, deeptech, FinTech or defence. You approve before anything starts. Nothing is imposed.

This is the right moment to ask the concrete questions: which comparable roles has this recruiter worked on, which sourcing channels do they use, how do they approach passive candidates.

Stage 3: immersion

The recruiter joins your organisation. In practice, that means getting access to your tools, taking part in your team rituals and understanding your engineering culture from the inside.

This phase takes a few days, longer in complex technical environments. It covers product architecture, infrastructure constraints, working methodologies and, above all, the implicit selection criteria: the ones that appear in no job description but decide the outcome of an interview.

This is time that can't be compressed, and it's precisely what sets RPO apart from an external service. A recruiter who has understood your team presents relevant profiles from the first shortlists, rather than learning by elimination over three cycles.

Stage 4: recruiting

The engagement moves into operational mode. The recruiter takes charge of the full chain upstream of your decision:

  • Direct sourcing of candidates, including passive ones, via LinkedIn Recruiter, tech communities, GitHub, meetups and proprietary databases
  • Technical and cultural qualification of profiles before they're presented
  • Shortlist presentations, with a case for each profile put forward and the reasons behind those left out
  • Interview coordination with your teams
  • Offer management and candidate support through to acceptance
  • Onboarding follow-up, within the scope defined during scoping

The recruiter represents your employer brand to candidates at every interaction. This matters: how responsive and thorough the feedback is during the process directly affects your offer acceptance rate.

Stage 5: follow-up

An RPO engagement is steered continuously, not reviewed only at the end. Follow-up takes the form of regular check-ins, progress reporting and honest feedback, including when something isn't working.

This is what allows adjustments: rewording a brief that's producing nothing, widening a search scope, revisiting a salary band that's drifted out of step with the market. A setup that doesn't adjust is a setup that repeats its own mistakes.

What you receive during the engagement

This question comes up often, and the answer depends on the scope defined during scoping. On a standard engagement, you get:

  • Qualified shortlists, with the evaluation notes and the recruiter's reasoning for each profile
  • Regular reporting on pipeline status, role by role and stage by stage
  • Visibility into approached candidates, including those who didn't move forward and why
  • The methods and templates built during the engagement, reusable by your teams afterwards

This last point is often underrated. A well-run engagement leaves behind formalised evaluation criteria and structured hiring processes. That's an asset that stays, particularly useful if you're planning to bring the hiring function in-house in the medium term.

One point to agree on explicitly: sharing candidate data with a provider puts your GDPR compliance on the line. Retention period, legal basis, secure exchanges, ownership of the talent pools built during the engagement. These need to be set out in the contract from the start, not afterwards. Our article on the pros and cons of RPO details the points to cover before signing.

How long does an RPO engagement last?

There's no standard duration, and be wary of any provider who quotes one before understanding your need.

Duration is set during scoping, based on three variables:

  • The number of roles to fill and how they're staggered over time
  • The seniority and scarcity of the profiles sought, which mechanically lengthen cycles
  • The scope entrusted, as a full RPO engagement runs longer than support focused on sourcing alone

One simple principle applies: the engagement needs to be long enough for immersion to pay off. An engagement cut short before the recruiter is fully up to speed is a wasted investment, however talented the person assigned.

On pace, Bluecoders' median time-to-deal is 22 days between a role opening and an accepted offer, across all hires, according to 2026 data, against the 12 to 15 weeks often seen on the French market. That's a cadence indicator, not an engagement length, but it gives you an order of magnitude to plan around.

If your need is a single, well-defined role rather than a series of hires, contingency recruitment is often a better fit and a lighter commitment.

What stays on your side

Outsourcing doesn't mean stepping back. Three things stay with you, by design.

The hiring decision. The recruiter qualifies, presents and makes the case. You decide. No serious RPO setup makes this call on your behalf.

Technical interviews. Your engineers remain best placed to assess a candidate's real technical level. The recruiter prepares, coordinates and debriefs; they don't replace that judgement.

Availability for the process. This is what derails the most engagements. A recruiter who presents shortlists that nobody responds to for ten days loses the best candidates. RPO frees up workload, it doesn't excuse slow responses.

Our advice on working effectively with a recruitment agency details the client-side best practices, which apply directly here.

How do you know the engagement is working?

Five metrics are enough to make progress objective, provided they're defined during scoping rather than along the way:

  • Time-to-hire by role and by stage, to spot where the pipeline is slowing down
  • Offer acceptance rate, a sign of how well-targeted and well-prepared candidates are
  • Shortlist quality, measured by the ratio of profiles presented who actually make it to interview
  • Hiring manager satisfaction, collected formally rather than going on gut feel
  • Six-month retention rate, the only metric that truly validates whether the hires were the right fit

If any of these signals slips, that's something to raise at the next follow-up, not a finding to make at the end of the engagement.

Summary

An RPO engagement is nothing like a black box. Scoping, choosing the recruiter, immersion, recruiting, follow-up: each stage has clear expectations, and you keep control of the decisions that matter.

The two factors that determine the outcome are the recruiter's real specialisation and the quality of the initial scoping. Everything else is steered continuously. To compare providers on this specialisation criterion, see our comparison of tech RPO firms in France.

Our RPO model is built around a dedicated recruiter, specialised by tech vertical, whom you approve before anything starts, with daily rate (TJM) pricing known from the scoping stage. If you want to know what an engagement would look like in your context, let's talk about your need.

FAQ

How long does an RPO engagement last?

There's no standard duration. It's set during scoping based on the number of roles to fill, how they're staggered, the seniority of the profiles sought and the scope entrusted to the provider. The principle to remember is that an engagement needs to be long enough for the immersion phase to pay off, otherwise the investment is wasted.

Who makes the final hiring decision in an RPO engagement?

You do. The RPO recruiter sources, qualifies, presents profiles and makes the case for each recommendation, but the hiring decision belongs to you, as do the technical interviews run by your teams. RPO absorbs the operational workload upstream, not the judgement call.

Can you choose the recruiter assigned to the engagement?

Yes, and it's a point worth insisting on. You're presented with one or more profiles, chosen for their specialisation in your field, and you approve before anything starts. The quality of an engagement depends directly on the person assigned, not the provider's brand, which makes this approval decisive.

What happens to the candidate pool built during the engagement?

This is a point to agree on contractually from the outset, alongside the other aspects of candidate data handling: retention period, legal basis, secure exchanges. A well-scoped engagement spells out what's yours at the end, talent pools as well as the methods and evaluation templates built along the way.

How long before the first profiles are presented?

Immersion takes a few days, longer in complex technical environments, before the recruiter is fully up to speed. The first profiles follow quickly after that. As a benchmark, Bluecoders' median time-to-deal is 22 days between a role opening and an accepted offer, across all hires, according to 2026 data.

A recruitment need?

Describe what you need. A recruiter from your sector will call you back within 24 business hours.