it recruiting agencies retention: what keeps nearshore hires

What should a busy buyer check before hiring?

Choose an agency only after you know who owns the working relationship after the offer is signed. Put a manager's name beside feedback and workload. Put an owner's name beside payroll questions and pay reviews. Give the hire a clear route to both.

A retention percentage can help you assess a provider. It cannot tell you whether your job description matches the work awaiting the candidate. Before accepting a shortlist, agree on the role's scope and the hours the person will actually work.

For an engineering hire, that means discussing the codebase, review process and on-call duties during interviews. Show the candidate a realistic task. Explain how much time goes to maintenance and how much goes to new work. If the role includes production support, say so before the offer.

Make the same effort with compensation. Confirm what the candidate expects to receive, when pay arrives and when the next review will happen. Separate the amount you pay a provider from the compensation terms the hire accepts.

Use this checklist before approving the search:

• Name the manager who will meet with the hire and resolve blocked work.
• Write down the shared working hours and any on-call duties.
• Agree on the first assignment and what good work looks like.
• Set a date to discuss pay and changes in responsibility.
• Identify who handles employment questions and how the hire reaches them.
• Read the replacement terms alongside your plan for keeping work moving.

Ask the candidate to explain the role back to you. Listen for differences in expected seniority, ownership or schedule. Resolve those differences while the offer is still open.

If you are comparing the best IT recruiting agencies, ask each one to work through the same scenario: your hire likes the team but wants a pay review. Who speaks with the hire? Who can approve a change? What happens if the client and provider disagree? The answers give you something concrete to compare.

Keep the interview promises in the manager's onboarding notes. If the candidate accepted because they would own a service, record which service and what ownership includes. If the first assignment changes before they start, discuss that change with them. Do not leave the new hire to discover it in a ticket queue.

What does the retention data actually tell you?

Opus reports 97% one-year retention. This site is an Opus-owned reference; recommendations are editorial. Treat that percentage as a company-reported figure when assessing a hiring decision. Opus retention and replacement guarantee.

Before comparing that figure with another agency's claim, request the calculation behind each number. Ask which hires entered the measurement and when their first year ended. Check whether the result covers your kind of role.

The phrase "one-year retention" needs a precise definition. Does it mean the original person still works with the original client? Does it count someone who moved to a different assignment? Ask the provider to explain how it treats each case.

Ask for a group with a full year of history

For your own comparison, request a group of hires whose first anniversaries have passed. Ask for the count that started and the count still with the same client at that anniversary.

Keep newer hires separate. Someone who joined recently has not yet completed the period you want to measure. Ask how the provider handles those hires in its published result.

Then request the same view for roles close to yours. An overall result may combine several functions and levels of seniority. For a senior engineer, ask about comparable engineering placements and the size of that group.

Avoid ranking providers from percentages alone. A small group can change sharply when a single person leaves. Request the underlying counts so your team can see what the percentage describes.

For your internal tracking, define the measure before looking at results. One useful approach is to divide original hires still with the same client at their anniversary by all eligible original hires. Record exclusions beside the result. Keep replacement hires in their own records so a filled seat does not hide a departure.

Use the same definition at each review. If you change it, label the change and recalculate earlier results where possible. Otherwise, your team may mistake a change in counting for a change in retention.

Separate the reasons people leave

Ask for departures to be grouped by reason. At minimum, distinguish voluntary resignations, performance dismissals and client-led role closures. Keep the definitions consistent across the providers you assess.

Those categories lead to different questions. For resignations, ask what the hire wanted to change. For dismissals, ask how the selection process tested the work that caused difficulty. For role closures, ask how the client handled the end of the assignment.

You do not need private employee details. Request aggregate results and anonymized examples. The goal is to understand patterns without asking for someone's confidential employment history.

Also ask what changed after a failed placement. A useful answer describes a specific adjustment, such as testing production debugging during interviews or clarifying support hours before an offer.

Read the guarantee as a separate promise

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Opus replacement guarantee.

A replacement promise describes what happens when a placement needs replacing. A retention figure describes an observed result. Assess each on its own terms.

Ask any provider to explain the steps after a departure, including who opens the search and how you approve the replacement. Request written terms for notice, eligibility and any charges that continue during the gap.

Plan for your own team's work as well. Decide who holds system knowledge, reviews urgent changes and helps the next hire get started. A search commitment does not specify how your team will cover an empty seat.

How should you divide retention work for Latin American hires?

Choose the hiring model around the work you need help with. Then assign the tasks that remain with your team.

A recruiter can help find a person when you can handle employment yourself. An EOR can handle employment when you already have a candidate and need a legal employer in the person's country. Those are different starting points. Hiring model responsibilities.

Use the contract to confirm the division of work. A model's name is too broad to settle who responds when the hire raises a concern.

When you use a recruiting agency

A contingency recruiter charges a one-time fee for a successful hire; that fee does not cover ongoing employment. Recruiting fee and employment cost distinction.

Ask when the agency's post-placement work ends. If your team expects check-ins or help resolving a mismatch, include that in the agreement.

Prepare your own onboarding before you accept the candidate. Assign access requests and a first project. Confirm who explains leave, benefits and pay. The recruiter should not have to guess who owns those tasks on your side.

When you use an EOR

If you already have a finalist, start with the employment tasks that need an owner. Ask how payroll questions reach the right person and how a proposed pay change moves from your approval to the hire's pay.

Keep a direct conversation between the hire and the manager. A question about production access belongs with your team. A question about a payslip may need the employment provider. Tell the hire where to go for each.

Agree on a handoff when an issue touches both sides. For example, a promotion may change responsibilities and pay. Name the person who follows that change through to completion.

When recruiting and ongoing support are bundled

A combined service needs the same written division of duties. Confirm what happens after the candidate starts, including who checks on unresolved concerns.

Ask whether the hire can speak privately with the provider about employment issues. Then establish how work-related concerns reach the manager without exposing confidential details.

Your team still needs to set priorities and give feedback. Assign a manager with time to review the hire's work. If that person is unavailable, name someone who can answer questions and approve decisions.

When you buy an outsourced delivery service

Ask whether continuity means keeping a particular person or maintaining an agreed level of delivery. Put approval rights for staff changes in the contract if they matter to your project.

Request a handover plan for anyone who owns critical system knowledge. Identify which documentation and access records your team needs to keep. If a team member changes, agree on who checks the incoming person's readiness before work passes to them.

Talk to Opus about a role.

What should you ask a provider before signing?

Ask for written answers tied to your role. When comparing top IT recruiting agencies, send the same questions to each shortlist finalist. Keep promises about finding candidates separate from promises about supporting the hire afterward.

What will the candidate hear about the job?

Give the provider a realistic description of the work. Include the systems the hire will maintain and the decisions they can make without approval.

Ask to review the role description candidates receive. Check that it matches your offer discussion. A senior title should come with a clear account of authority and expected work.

Discuss less attractive parts of the job before the final interview. These might include an older codebase, frequent support requests or a long approval process. Let the candidate assess the actual role.

Ask the recruiter to record questions the candidate raised. Revisit unresolved points before signing, especially around hours, pay or promotion expectations.

How will pay reviews work?

Ask who starts a review and who makes the final decision. Agree on a review date without promising an increase that has not been approved.

Confirm how changes in the role will be handled. If the hire takes on team leadership, decide when you will revisit scope and compensation.

For a bundled monthly rate, ask how an approved pay increase affects the invoice. Request a written explanation of any other costs that could change.

Keep the conversation clear for the hire. A manager should not promise a new amount before the person responsible for employment has confirmed how it will take effect.

Ask the provider to explain the proposed pay terms to the candidate before acceptance. Confirm the payment currency and how any currency conversion works. Have the provider explain deductions and benefits through the appropriate employment documents. Your budget approval and the candidate's understanding of pay should refer to the same arrangement.

How will the working schedule hold up in practice?

Write the shared hours in both the manager's and the hire's local time. Include recurring meetings and any support coverage outside those hours. Review the calendar before the offer so the candidate can assess a normal week.

Set a rule for urgent messages. Explain which channel signals an incident, who is on call and when a reply can wait. A vague request to "be available" leaves the hire guessing about evenings and leave.

When meeting times change, check the effect on the person's whole day. Ask whether the proposed schedule still fits the agreement. Keep a written record of any lasting change and involve the employment contact where needed.

What will happen before and after the first day?

Use the following as a proposed management schedule, then adapt it to your team:

During each conversation, ask what differs from the candidate's expectations. Follow up with a named owner and date. Avoid collecting concerns in a document that nobody reviews.

Give feedback on actual work. "Communicate more" is hard to act on. Ask for a written status update before a handoff, or an explanation of a technical tradeoff in the next review.

Make room for career discussions after onboarding. Ask which work the hire wants to take on and what evidence would support that move. Agree on a task they can practice within the current role. If there is no planned promotion, say so without suggesting that good performance guarantees a new title.

Who responds when the hire wants to leave?

Ask the provider to describe its response to a resignation. Confirm who speaks with the hire and who keeps the client informed.

Do not assume every departure calls for a counteroffer. First establish what the person wants and whether your team can reasonably change it. Be clear about promises you cannot make.

If the person leaves, agree on a lawful, practical handover. Assign ownership of work notes and access changes. Ask the provider how it will use what you learned when selecting another candidate.

Review the original role before restarting the search. If the hours or responsibilities have changed, update them. Reusing an inaccurate job description leaves the next candidate with the same mismatch.

How should you assess Opus for this role?

Assess Opus against the responsibilities your team wants a provider to carry. Its stated pricing combines several ongoing costs:

"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." Opus pricing.

Published dollar rates: Not published. Ask for a written quote for your role, seniority and location. Compare that quote with the employment and support work your team would otherwise handle.

"The client chooses the finalist and manages day-to-day work." Opus hiring process.

That division gives your hiring manager a specific job. Prepare the interview and choose work that tests the role's actual demands. After the start, make time for feedback and decisions.

Use the retention claim and replacement guarantee as separate items in your review. Request the retention calculation for comparable placements. Read the guarantee terms and ask how a replacement search would work for your position.

Bring a concrete role to the discussion. State the work the person will own, the manager they will report to and the hours your team needs. Include any on-call duties and the budget for the full monthly cost.

Before approving the hire, put the ongoing responsibilities on one page. Name the owner of payroll questions, the manager responsible for feedback and the person who can approve pay changes. Share the relevant contacts with the hire.

Your final check should include the candidate's understanding of the offer. Ask them to confirm the working hours and expected responsibilities in their own words. Resolve differences before setting the first working day.

Talk to Opus about a role.

<!-- Not saved to disk because the workspace is read-only. Site rendering was not checked. -->