The recruiter who calls you has the employer's logo in her email signature, books interviews in the employer's calendar and talks about "our team". Then you look her up on LinkedIn and her profile lists a different company entirely. Nothing is wrong: you have probably met an RPO recruiter, and knowing it changes how you follow up, what you negotiate and where your data ends up.
What recruitment process outsourcing actually is
Recruitment process outsourcing (RPO) is an arrangement in which an employer hands part or all of its hiring to an outside firm. The provider's recruiters then work as if they were in-house. They use the employer's email domain, its applicant tracking system, its interview templates and often an internal-sounding job title such as "Talent Acquisition Partner".
The scope varies a lot from one contract to the next. Some employers outsource everything, from writing the job ad to issuing the offer letter. Others outsource a slice: one hiring wave for a new site, one hard-to-fill job family such as engineering or nursing, or just the early screening calls. In a project RPO, an outside team arrives for a few months to staff a launch, then leaves.
This is not the same as an agency recruiter who sends your CV to several clients and earns a fee per placement. The split between agency and in-house recruiters has its own article, as do how headhunters work and how recruiter fees are structured. The point that matters for this post is narrower. An RPO recruiter usually works for one client at a time, sits inside that client's process, and is paid under a service contract rather than a commission on your salary. Their targets are the client's hiring targets, and that shapes how they treat you.
How to tell you are dealing with an RPO recruiter
Most RPO setups are not secret, but nobody announces them either. A few clues tend to give it away.
- The email signature. It may carry the employer's brand on top and a small line underneath, something like "Talent Acquisition, on behalf of" followed by the employer's name.
- Two email domains. The first message comes from the employer's domain, then a calendar invite or a contract question arrives from another one. Or the recruiter copies in a colleague at a firm you have never heard of.
- The LinkedIn profile. The current role says "Recruiter at" a company you do not recognise, sometimes with the client hinted at in the description ("currently supporting a major retail client"), sometimes not at all.
- The phrase "on behalf of". It turns up in job ads, in privacy notices and in the footer of automated emails.
- The vocabulary. "My client", "the business" or "the hiring team over there" instead of "we".
If you are not sure, ask. "Are you part of the in-house team, or are you working with them as a partner?" is a normal question, and recruiters get it all the time. A genuine RPO recruiter will not be offended.
That mismatch between profile and email domain is also something scammers imitate, which is why a separate article in this series covers telling a fake recruiter from a real one. The short version: an RPO recruiter works inside the employer's real systems, and you can find the role on the employer's own careers page.
What changes for you as a candidate
Most of the time the experience feels like any large-company hiring process. A few things work differently, and they are worth knowing before your first call.
A process built for volume
RPO contracts are often measured on time to fill, number of hires and candidate satisfaction scores. That tends to produce a tidy, scripted process: the same screening questions for every candidate, fixed interview stages, templated rejection emails. The upside is predictability. The downside is that the recruiter may be juggling a long list of open roles and has little time to argue your case when your profile does not match the checklist.
The decision still sits with the hiring manager
The RPO recruiter screens, schedules and relays feedback. The hiring manager, an employee of the actual company, decides. When you prepare, prepare for that person. The recruiter's intake meeting with the manager defines what gets screened (there is a whole piece on that intake meeting), but an RPO recruiter rarely has the authority to push you through against the manager's view.
Less room to negotiate through the recruiter
Pay bands and offer rules usually come from the employer's HR team and are handed to the provider as fixed parameters. An RPO recruiter can relay a counter-offer, but they often cannot approve one, and they may have been told to close within the band. Make your case with clear numbers, ask the recruiter directly whether your request goes to the hiring manager or to HR, and be ready to raise it again with the manager if you reach the final stage. That is not going behind anyone's back. It is talking to the person who signs off.
An RPO recruiter controls the process. The employer controls the decision. Treat them as two different audiences.
Following up when the recruiter works for someone else
Follow-up gets messy because RPO teams rotate. Contracts end, recruiters move to another client, a project team packs up when the hiring wave is done. If your recruiter goes quiet or leaves mid-process (yes, there is an article on that too), the fix is slightly different in an RPO setup.
- Keep a copy of every email address. Note both domains if you see two. A message to the employer's address often lands in a shared inbox that the next recruiter can read.
- Ask early who your backup contact is. One question on the first call covers it: "If I can't reach you, who should I write to?"
- Thank the hiring manager after the interview. A short note is normal, and it gives you a line into the company that does not depend on the provider's staffing.
- Use the applicant portal. In most RPO setups your application lives in the employer's system, so the status you see there stays valid when the recruiter changes.
Keep your follow-ups short and include the job reference. Someone new may be reading your thread cold.
Your data may sit in more than one place
This is the part candidates rarely think about. When a provider runs hiring for an employer, your CV and interview notes commonly sit in the employer's applicant tracking system. Depending on the contract, they may also sit in the provider's own tools, for example a sourcing database or a CRM used across several clients. Arrangements differ, and only the privacy notice for that hiring process tells you what applies to you.
A few habits help:
- Read the privacy notice linked from the application form. It should say who controls your data and whether a provider processes it on the employer's behalf.
- Ask how long your data is kept if you are rejected, and whether the provider may contact you about other clients' roles. Some providers ask for your consent before doing so.
- Use your data rights where they exist. In the EU and the UK, data-protection rules generally let you request access to your personal data or its deletion. Send the request to the employer, and to the provider if the notice names one.
Keep your CV tidy and consistent, because the version stored in a provider's database may surface again for another client months later. If you build it from your LinkedIn profile with a tool such as Postulit, update both at the same time so the two versions tell the same story.
The takeaway
An RPO recruiter is a real recruiter doing a real job for an employer that has chosen to outsource hiring. It is not a red flag. It does change who decides (the hiring manager), who negotiates (often HR, through the recruiter) and who keeps your data (possibly two companies).
Before your next screening call, do one thing: compare the recruiter's LinkedIn profile with their email domain. If they differ, ask at the start of the call whether they work in-house or as a partner, and write down a second contact. That two-minute check tells you who you are really dealing with before you negotiate anything.