recruiting process outsourcing rpo: scorecard, interviews, 90-day plan

# recruiting process outsourcing rpo: scorecard, interviews, 90-day plan

What should a busy hiring buyer decide first?

Start with the work the new hire must own. Write the scorecard, assign interview owners, and reserve time for feedback before asking a partner to source candidates. Then decide which parts of the process you want outside help to run.

Recruiting process outsourcing, usually called RPO, can cover an agreed portion of your recruiting process. Make that scope explicit. A search agreement should say who screens candidates, books interviews, handles feedback, and moves an offer toward acceptance.

Your hiring manager still needs to define a good hire. A provider cannot resolve an internal disagreement about whether you need a senior individual contributor or a team lead.

Write the scorecard around a real assignment

Replace a long tool list with a short account of the work. For example: "Own the billing service, review changes to payment handling, and help the team diagnose failed transactions."

That example gives interviewers something to test. It also helps candidates judge whether they want the job.

Use this scorecard as a starting template. Change the criteria to match the role.

Separate requirements from preferences. If the person must handle production incidents, assess that skill directly. If your framework can be learned during onboarding, decide whether it belongs in the rejection criteria.

Write down what a passing answer looks like before interviews begin. "Communicates well" is too loose. "Explains a technical risk and gives the next owner enough detail to act" is something an interviewer can assess.

For each criterion, use simple labels such as "meets," "does not meet," and "needs more evidence." Keep a separate space for observations. A blank field should trigger a question about what the interview covered.

Avoid letting a total score hide a failed requirement. A candidate who writes clear code may still lack the incident experience this role needs. Decide which requirements must pass on their own before reviewing applicants.

Reserve the decision time

Give each interview a purpose and an owner. Ask interviewers to submit evidence before the group debrief so the first speaker does not set everyone's view.

Agree on how to resolve a split decision. If the disagreement concerns a required skill, identify the missing evidence. Use a focused follow-up when needed, with a clear question to answer.

Do not add another general interview because the team feels uncertain. Name the uncertainty first.

Assign a backup decision-maker for absences. Reserve debrief time when you book the interviews, and tell candidates when they should expect an update. If the team misses that date, the person handling candidate contact should send a revised date.

What does hiring-time data tell you?

SHRM reports that median time to fill in 2025 was roughly a month and a half for executive and nonexecutive positions. It defines that period as job requisition to offer acceptance. SHRM's recruiting benchmark gives a broad planning reference.

Use that definition when comparing a provider's claim with your own hiring records. A clock that starts after budget approval measures something different from a clock that starts with the initial request.

The endpoint also changes the result. Receiving a shortlist, accepting an offer, and beginning paid work are separate events. Record each one.

Track the stages you can act on

Create a simple hiring log with dates for these events:

• Role and budget approved.
• Search requirements agreed.
• First candidates presented.
• Interviews completed.
• Offer accepted.
• First working day.

These are suggested tracking fields, not industry benchmarks. Add a reason when a stage stalls so you can distinguish sourcing problems from internal delays.

For example, a candidate may wait while your team changes the seniority level. Record the change and its date. Otherwise, the final hiring time hides the reason for the delay.

Review candidate quality alongside speed. Count how many presented candidates meet the written requirements and why others fall short. Use the same criteria throughout the search, or label the point where the requirements changed.

Track candidate withdrawals separately from employer rejections. Ask departing candidates for a reason without pressing them to disclose personal details. If people withdraw after learning the working hours, revisit how early you explain that requirement.

Ask how each result was calculated

Before relying on a hiring-speed claim, ask about the roles included and the reporting period. Check whether the figure is a median, an average, or a service target.

Also ask how paused searches and canceled roles are handled. A report that includes only successful placements answers a narrower question than a report covering every search.

Apply the same care to retention. Ask which hires are counted and when the measurement begins. For your own team, record whether departures followed a change in role, manager, or working arrangements.

Use these measures to find where the process needs work. Avoid setting a speed target that encourages interviewers to skip evidence your scorecard requires.

At a search review, choose the next action from the recorded problem. Weak technical matches call for a screening discussion. Candidates waiting for feedback call for a decision from your team. A single overall hiring-time figure cannot tell you which action to take.

How do hiring models differ for nearshore and Latin American teams?

Choose a model by identifying the work you need someone else to handle. Finding candidates, employing a selected person, and delivering a project are different assignments.

Use this table to frame provider discussions. Confirm the actual scope in the agreement.

Match the model to the bottleneck

If your recruiting team can source engineers but interviews keep stalling, fix interview capacity first. Adding candidate volume will leave more people waiting.

If you already have a finalist, focus the provider discussion on employment and onboarding. If you need a finished system delivered, define the output and its acceptance criteria before buying individual capacity.

For companies that want to hire remote tech talent, write the work location and expected shared hours into the role requirements. Ask each provider to confirm how the proposed arrangement supports those expectations.

Avoid using "remote" as a complete job specification. State whether the person must attend recurring meetings, join an on-call schedule, or travel. Candidates should know those requirements before investing time in interviews.

Write shared hours as a specific schedule with named time zones. Confirm how the schedule changes during the year, if at all. Also distinguish routine meeting attendance from incident coverage. A candidate's agreement to daytime overlap does not answer whether they can join an overnight rotation.

Keep the technical bar tied to your business

Non-tech companies that hire software engineers should assess the work their engineers will actually do. For an internal application, that may mean maintaining an integration and handling requests from business users.

A team building a customer-facing service may need a different exercise. Ask the candidate to explain failure handling, release choices, or the effect of a proposed change.

Likewise, staffing agencies that hire remote workers may cover roles far beyond engineering. Ask who evaluates technical work and what evidence reaches your interview panel. A broad remote staffing service still needs to show how it will assess your specific role.

For a temporary assignment, define the handover before the search begins. List the code, documentation, and access changes needed when the assignment ends. Ask temp agencies that hire remote workers how they coordinate that handover with your manager.

What should you ask a provider before the search starts?

Ask for a written operating plan that your hiring manager can use. It should identify each handoff, the person responsible, and the evidence required to move forward.

Start with the role itself. Give the provider the scorecard and ask them to explain which requirements they will assess. Resolve any disagreement before candidates receive conflicting accounts of the job.

Request evidence behind candidate recommendations

Ask to see the format of a candidate assessment, with personal details removed. Look for evidence that maps to your scorecard.

Useful questions include:

• Which skills do you assess directly, and which rely on candidate statements?
• Who reviews technical work?
• What does a failed assessment look like?
• Can our interviewer discuss the work sample with the candidate?
• How do you confirm availability and expected working hours?
• Who tells candidates about changes to the role or process?

Agree on how assessments handle AI tools. If the job permits their use, explain the rules for the exercise. Ask candidates to describe what they used and how they checked the result.

Keep the exercise bounded and relevant. State the expected effort in advance. Use a hypothetical task or sanitized example that does not require production access or confidential customer data.

Give candidates the same core task and evaluation criteria. Explain which tools they may use and how to request an accommodation. Avoid changing the difficulty halfway through a search without recording the change.

Give each interview a distinct job

The initial discussion should confirm mutual fit: the work, expected scope, and practical arrangements. Resolve clear mismatches before scheduling technical work.

Use the technical interview to examine how the candidate reasons through a task. Ask them to explain a test, identify a failure case, or revise a choice after receiving new information.

For example, give a backend candidate a small service that processes duplicate requests incorrectly. Ask them to describe the failure, propose a fix, and explain how they would test it. Judge the reasoning against the role's needs. Do not treat unfamiliarity with your preferred test library as a failed requirement unless the role demands it.

For a senior role, include a discussion of tradeoffs from past work. Separate the candidate's own decisions from the wider team's achievements.

A manager discussion should address expectations after joining. Describe how work is assigned, reviewed, and supported. Give the candidate room to question whether the role matches their experience.

After the interviews, return to the scorecard. Record the evidence for each required skill. Replace comments such as "strong candidate" with the observed behavior that supports the decision.

Set the first 90 days before the offer

Use this plan as a template. Adjust the scope for seniority and the system the person will join.

Give the new hire a task with a clear completion point. "Understand the architecture" needs a concrete check, such as explaining a request path or documenting a failure mode.

At each review, ask what prevented progress. Missing permissions, delayed reviews, and unclear requirements need owners. Record those constraints separately from the hire's performance.

For a remote hire, name the person to contact when the manager is unavailable. Put recurring meetings and shared working hours on the calendar before the first day.

Share the plan with the finalist before they accept. Ask which goals need more context or support. A senior engineer may spot a dependency your team overlooked, such as needing a product decision before changing a service.

Keep the plan editable after arrival. Record any scope change and agree on the revised goal together. Judge progress against the work the person could actually do with the access and support they received.

Settle costs and responsibility in writing

Request a quote for the actual role, seniority, and location. Ask which charges recur and which events can change the bill.

Confirm who handles employment documents and payroll. Have the appropriate internal reviewers check confidentiality, intellectual property, security access, and termination terms.

Read replacement terms as an operating process. Ask what starts a replacement search, who handles the handover, and what happens to charges during a gap.

Bring the role scorecard and intended start date to the discussion. Talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

How does Opus fit your hiring process?

Consider Opus against the responsibilities your team wants to assign to a partner. Keep your own technical scorecard and interview decision in place.

Opus reports that it delivers 3 vetted candidates in 5 days. Opus reports about 14 days from brief received to hired, not first day worked; the reporting period and calculation are not published. Opus describes its hiring process here.

For that reported hiring time:

Confirm the first working day separately. Build your project schedule around that agreed date and the onboarding work required before the person can contribute.

Review vetting against your scorecard

Opus reports that every candidate passes an 8-layer vetting process. It also reports that every placement completes a 6-module internal AI certification before day one. These are company-reported process claims. Opus explains the process.

Ask how the assessment covers your role's required skills. Request the evidence your technical interviewer needs to review, and decide which questions your team will assess directly.

Treat the AI certification as a topic for discussion. Ask how the candidate checks generated work and handles sensitive information. Use your own tool policy when setting expectations for the role.

Keep management responsibilities explicit

Opus charges one flat monthly rate per hire. It covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location.

The client chooses the finalist and manages day-to-day work. Opus's process description describes the division between employment support and daily management.

Your manager should therefore own the work queue, review cycle, and first 90-day plan. Assign those responsibilities before accepting a finalist. The manager needs time to review early work and answer questions about the system.

Bring a defined assignment, your scorecard, and the expected working arrangements to the provider call.

Talk to Opus about a role.

<!-- File save skipped: the workspace is read-only. This page has not been saved to the requested path. -->