Glossary · Search & process
RPO (recruitment process outsourcing)
RPO, recruitment process outsourcing, is when a company hands all or part of its hiring to an external provider as an ongoing, often embedded service.
Published Updated
RPO suits high-volume, repeatable hiring where scale and consistency matter most. It differs from executive search, which is a targeted, high-touch search for scarce senior talent that a listing won't reach.
The term is often used loosely for any outside recruiter, which blurs the one thing that defines it: RPO takes over a process, not a vacancy. A recruitment agency is engaged role by role; an executive search firm is engaged on a single senior mandate; an RPO provider runs some or all of the hiring machinery itself, continuously. Korn Ferry, which reports executive search and RPO as separate businesses in its annual report, describes its RPO line as high-volume, outsourced hiring solutions that deliver end-to-end talent acquisition services for enterprise clients.
Its neighbours sit on either side of it. Beneath it is in-house recruiting, which an RPO can supplement or replace; beside it is executive search, built for the scarce senior seats an RPO is not designed around; and around both sits employer branding, because an embedded provider recruits under the client's name and so spends the client's reputation with every candidate it touches.
In practice
Embedded is the operative word. Where an engagement is set up that way, the provider's recruiters work inside the client's systems, under the client's employer brand, sometimes with client email addresses, so a candidate need not know the recruiter is external. What the provider owns is set out in the contract, requisition by requisition: sourcing only, or sourcing through screening, scheduling, offer management, and onboarding. Commercial terms vary by provider and contract rather than following one standard model.
Engagements are scoped in tiers: a full programme covering all hiring, a project deal for one function or one growth push, or on-demand capacity for a spike in volume. The reasons given for buying it are process consistency and the ability to scale hiring capacity up and down without adding permanent recruiters. The model is bounded by seniority: filling a scarce C-suite seat turns less on running a defined process well than on reaching people who are not applying, which is what executive search is organised around.
Because the provider recruits under the client's name, the quality of its process becomes the company's employer brand: a slow reply or a careless rejection reaches the candidate as the company's conduct, not the provider's. Records raise the same question in another form. Candidate data gathered during an embedded engagement has to be accounted for, so the contract is where it is settled who holds it, for how long, and what happens to it when the engagement ends.
Every mandate The Quantum Club runs is exclusive to it, and the vast majority are never publicly listed; the club posts no public jobs at all. Placed, not posted.
Common questions
- What is the difference between RPO and a recruitment agency?
- An agency is engaged role by role and paid a fee tied to that role; an RPO provider runs hiring as a continuing service, typically working inside the company's brand and systems. How much of the process the provider covers is set by the contract, from sourcing alone to the full cycle including referrals and internal applicants. The commercial relationship is a service contract rather than a per-role fee.
- Does RPO replace an internal talent team?
- Not by definition. Which parts move to the provider is a contract decision: an engagement may leave strategy, employer branding, workforce planning, and the hiring decision with the company while the provider carries execution capacity. A full programme can absorb an entire function; a hybrid arrangement keeps some searches, senior or commercially sensitive ones for example, with internal recruiters.
- Is RPO suitable for executive hiring?
- Not as the main route for scarce senior seats, because the two are built for different problems. RPO is designed for repeatable hiring, where a defined process run consistently produces the result. Executive hiring inverts that: the pool is small, the strongest candidates are not applying, and reaching them depends on mapping, discretion, and standing relationships. Some providers run a separate executive practice, but the disciplines stay distinct under one roof.
- Who owns the employer brand in an RPO engagement?
- The company does, even when the provider's recruiters do the work. In an embedded model they write to candidates under the client's name, sometimes from client email addresses, so every interaction counts as the company's own. Service levels, candidate communication and how rejections are handled are therefore matters for the contract, not for the provider's habits, and they are worth reviewing as closely as price.
Sources
Placed, not posted.
Join as talent, or hire through the Club.