How to Evaluate a Recruitment Process Outsourcing Provider: 8 Questions Before You Sign

How do you evaluate a recruitment process outsourcing provider?

Treat it like a senior hire. Put the same eight questions to every provider in a working session and score the answers against what you can verify. The sourcing method, the named recruiter, the written shortlist format and the reporting tell you more than a proposal does. Anything you cannot see in a sample or hear from the person who would do the work is a claim, not a capability. The difference between embedded and traditional models is worth settling first.

Most procurement frameworks ask vendors to respond to a standard RFP: company background, client list, pricing, SLAs. For commodity services, this works reasonably well. For Recruitment Process Outsourcing, it misses the variables that actually determine whether the engagement will produce good engineering hires or an expensive lesson in misaligned expectations.

The quality of an RPO engagement depends on three things that an RFP rarely captures: the specific recruiter working on your searches, their sourcing methodology, and their domain depth in the kind of roles you are hiring. The questions below are designed to surface exactly these things.

Why standard procurement questions miss the point.

Procurement processes ask about scale, infrastructure, technology stack, and client references. These are proxies for quality, and they are weak proxies for RPO. A firm with 500 consultants and a marquee client list may assign a junior generalist to your account. A smaller specialist firm may have precisely the market knowledge you need, built over years of hiring in your specific domain.

The variables that actually predict engagement quality are: the capability and approach of the specific recruiter, the depth of their network in your talent market, their sourcing methodology for passive candidates, and their ability to calibrate a search when the first shortlist misses the mark. None of these appear in a standard RFP response.

Ask the eight questions below in a two-hour working conversation, not a presentation. The answers will tell you more than any proposal document.

Question 1: What is your sourcing thesis process?

A sourcing thesis is the strategic brief that sits underneath a job description. It answers three questions before any outreach begins: where are the right candidates, what will attract them, and what will differentiate this company in their eyes. A provider who builds a sourcing thesis per role is doing fundamentally different work from one who searches LinkedIn for the job title.

Ask the provider to describe their sourcing thesis process in concrete terms. What does it produce? How long does it take to build? Who writes it? A strong provider will describe a structured process: company mapping to identify where the target candidates currently work, signal-based identification using technical output and community activity, and brief-driven outreach that references something specific about the candidate rather than a generic message.

Red flag: any answer that amounts to "we search LinkedIn and our database." That describes a contingency agency, not an embedded RPO partner.

For RPO in India specifically, this matters enormously. The India engineering talent market is large but highly segmented. Senior product engineers, GCC engineers, and services company engineers are different candidate pools with different motivations and different outreach approaches. A provider without a structured sourcing thesis will mix these pools and produce a low-quality shortlist.

Question 2: What engineering roles have you placed in the last 12 months?

Ask for specifics, not generalities. Not "what industries do you serve" but "what roles have you actually filled recently, at what seniority levels, from which companies, hired into which types of organisations." The answer tells you whether this provider has genuine depth in your domain or is presenting a capability they have not actually exercised recently.

For technology hiring, domain depth matters because the candidate pool, the outreach messaging, and the assessment approach are all different at the senior IC level versus the manager level versus the C-suite. A provider who mostly fills mid-level roles at services companies has a fundamentally different network and methodology from one who regularly places senior engineers at product startups and global capability centres.

Ask specifically about placements in your target market, whether that is Bangalore, Hyderabad, Pune, or another India city. RPO services in India are not uniform across geographies. The talent pool composition, compensation benchmarks, and candidate motivations differ significantly between cities, and a provider without recent placements in your target city is building their market knowledge at your expense.

Question 3: How do you assess candidates before they reach the shortlist?

The difference between a CV dump and an assessed shortlist is the difference between a useful engagement and a waste of your engineering managers' time. Ask the provider to describe their candidate assessment process in detail. What does a shortlist submission look like? Does it include a written recommendation per candidate? What does that recommendation cover?

A well-run embedded RPO produces a shortlist where each candidate has: a brief on their background and technical depth, the specific reasons they are being put forward, the potential concerns, and a clear recommendation. The hiring manager's role at shortlist stage is to evaluate those recommendations and decide who to interview, not to re-screen from scratch.

If the provider cannot describe what a written shortlist recommendation looks like, they do not write one. This is a significant red flag for any engagement where your engineering managers' time is a constraint.

Question 4: What does your fee structure look like?

Fee structures in Recruitment Process Outsourcing come in three main forms: per-hire (a fixed fee per successful placement), monthly capacity (a fixed monthly fee for a defined level of recruiter time and active searches), and milestone-based fees (payments tied to defined stages such as brief sign-off, shortlist delivery, and offer acceptance). Each has a different incentive profile.

Ask the provider which model they use, how fees change if hiring volume increases or decreases mid-engagement, and what happens if a placed candidate leaves within the first 90 days. Ask whether there is a minimum commitment period and what the notice terms are for ending the engagement early.

A monthly capacity model aligned to a dedicated search commitment is typically the strongest incentive alignment for an embedded RPO engagement: the provider is accountable to the quality of the process, not just the speed of individual placements. Be cautious of providers who are unwilling to discuss fee structure openly before the first meeting. Transparency at this stage predicts transparency throughout the engagement.

Question 5: Can you show me an example sourcing report and pipeline update?

Ask to see a sanitised example of a weekly pipeline report from an existing engagement. This tells you what information you will actually receive during the relationship, not what the provider claims to deliver. A strong pipeline report covers: roles in active search, candidates at each stage of the funnel, recent outreach response rates, calibration feedback received, and the next actions planned.

A provider who cannot produce an example, or whose example consists of a spreadsheet with columns for Name and Status, is not running a structured reporting process. For engineering hiring programmes where leadership visibility into pipeline health is important, structured reporting is not optional.

The reporting format also tells you about accountability. A provider who sends informal WhatsApp updates is not operating with the level of process discipline that a serious hiring programme requires. For RPO services in India serving global technology companies, the reporting format needs to work across time zones and be readable by hiring managers who are not in daily contact with the recruiter.

Question 6: What does the setup process look like and how long does it take?

A well-structured embedded RPO engagement should produce a first assessed shortlist within 14 days of brief sign-off. The setup process covers: gaining access to your communication tools and ATS, one-on-ones with each hiring manager, brief development for the first wave of roles, and the initial sourcing run. Ask the provider to walk you through this timeline in detail.

Vague answers here indicate a lack of process discipline. A provider who says "we usually need a few weeks to get going" without a clear sequence of what happens in those weeks is not running a structured engagement model. The first two weeks are the highest-leverage period of an embedded RPO engagement: poor brief development in week one creates poor shortlists in week four, and the ripple effect carries through the entire search.

Ask specifically: on day 14, what will I have? A specific, answerable question. Strong providers will tell you: a sourcing thesis per active role, a set of target companies identified, an initial outreach campaign underway, and the first candidates in screening. Weak providers will give a vague answer about ramping up.

Question 7: Who specifically will be working on my searches?

In many recruitment firms, the person who presents in the pitch is not the person who works on your account. The relationship between the salesperson and the delivery team varies enormously, and the quality of the delivery team is the only variable that matters once the contract is signed.

Ask to meet the specific recruiter who will work on your engineering searches before you sign. Evaluate them directly: can they discuss your technical requirements fluently? Do they have an existing network in your target market? Can they describe the sourcing thesis they would build for your first open role?

Ask about their background: have they recruited exclusively in technology, or across multiple sectors? How long have they been recruiting senior engineering roles in India? What companies have they sourced from, and what is their current active network in your domain? The answers to these questions tell you more about the engagement you will actually receive than any proposal document the firm produces.

What to evaluate in an RPO provider.

Question 8: What does success look like and how will you measure it?

Ask the provider how they define a successful engagement. The answer reveals their value system. A provider who defines success as "placements made" is measuring activity, not quality. A provider who defines success as quality of hires, hiring manager satisfaction, offer acceptance rate, and 90-day retention is accountable to outcomes that align with your interests.

Ask what metrics they will report against throughout the engagement, and what happens if those metrics are not being met. A provider who cannot answer this question is not a provider who will be easy to hold accountable. The metrics conversation at the evaluation stage sets the expectation for the relationship: a provider who agrees to clear, measurable outcomes is one you can manage effectively.

Making the final decision.

After running these eight questions across two to four providers, the evaluation dimensions become clear: sourcing methodology, relevant domain experience, reporting transparency, fee structure alignment, and the specific recruiter quality. Weight these in that order.

A lower fee from a provider who cannot describe their sourcing methodology is not a better deal. The total cost of an engagement includes the value of engineering manager time spent reviewing poor shortlists, the cost of extended time-to-hire, and the opportunity cost of the role going unfilled. A specialist provider who charges a higher monthly capacity fee but delivers an assessed shortlist in 14 days produces a better economic outcome than a cheaper provider who delivers a CV dump in six weeks.

For technology companies using Talhive's RPO and Embedded Hiring services, the evaluation process starts with a working brief session, not a pitch. You meet the recruiter who will run your searches, you see the sourcing thesis process in action, and you have a clear picture of what week fourteen looks like before you sign anything. That is how the right engagement starts.

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.

How to score the answers you get.

The eight questions only help if every provider is scored the same way. Score on evidence, not on fluency. A confident answer with no example behind it should earn less than a plain answer you can check. The same applies to technical depth: ask how the provider would judge a candidate, and compare it with the standard in technical assessment for engineering hiring.

How to run the evaluation call.

Whether you are buying recruitment process outsourcing globally or for a single India team, the evidence you want is the same. Run the call as a working session rather than a presentation, and measure the outcome with the same metrics you will use later, such as those in the hiring metrics every VP Engineering should track.

Answers that should end the conversation.

How we run an evaluation.

We run the first conversation as a working session on one of your open roles. You meet the recruiter who would run the search, and we show how a sourcing thesis and an assessed shortlist are written. Our embedded model uses a monthly engagement fee plus milestone-based placement fees, with no lock-in beyond the first month, so a first mandate is a genuine test rather than a commitment you cannot leave. How embedded RPO works sets out the first 14 days in detail.

Frequently asked questions.