How to choose a nearshore partner: criteria and scorecard

What does a good provider actually do?

A good provider makes the hiring decision easier to inspect. You should be able to see why a candidate fits, who assessed them and what happens after you choose them.

For an individual hire, ask for evidence tied to the work. If the role owns a production service, discuss a production failure the candidate handled. If it involves customer calls, include a conversation that resembles those calls. A general coding score cannot answer every hiring question.

The provider should separate recruiting from employment support. Finding a person, signing their employment agreement and managing their engineering work are different responsibilities. Have each assigned before interviews begin.

Nearshore describes geography. It does not tell you which party owns delivery. A US company working with engineers in Mexico is a nearshore arrangement. Those engineers could report to your engineering manager or deliver a project under their own manager.

Onshore means work in your own country. Offshore means work abroad and often refers to a more distant location. The calendar and contract determine how either arrangement operates.

Ask how the provider handles a rejected shortlist. Does it revisit the role, change the assessment or send more resumes? Agree on who can approve a candidate and how interviewers will resolve conflicting feedback.

Also ask who stays involved after acceptance. Your manager should know where to send a payroll question and whom to contact about a poor fit. Request a named contact and an escalation path.

What drives the cost of a Latin American hire?

Compare the full bill for the work you need. Candidate compensation is part of that bill. Depending on the model, the quote may also include payroll administration, benefits and placement support.

Ask the provider to distinguish recurring charges from costs triggered by an event. Equipment, overtime, a role change or an early exit may affect the total. Have it state whether each item is included, separately charged or your responsibility.

Country and seniority belong in the quote, but so does the scope of the role. Maintaining a stable service differs from designing its replacement while handling production incidents. A shared job title does not make those jobs equivalent.

Request the following with every proposal:

• The compensation basis and currency.
• The total service price and included employment support.
• Equipment ownership, shipping and return terms.
• Leave, overtime and coverage arrangements.
• Rate-review rules and costs when the engagement ends.

Ask who bears changes in local payroll costs when the invoice is in dollars. Also ask whether statutory bonus payments are spread across monthly invoices or charged when due. Have the provider show the expected cost through a complete annual cycle.

Finance should review a sample invoice before approving the budget. Check when billing begins and how partial months work. Confirm whether deposits are credited against later invoices.

Do not accept a savings percentage as a substitute for this breakdown. You need the proposed bill and a comparable domestic budget before a savings claim can guide a decision.

Which engagement model fits: full-time placement, dedicated team or project?

Choose the model according to who will direct the work and accept responsibility for the result.

Full-time placement or staff augmentation

Use an individual placement when you need a person inside your existing team. Your manager assigns priorities, reviews work and decides whether the hire meets expectations.

Staff augmentation also adds people to a client-managed team. Ask how the agreement treats assignment length and reassignment. Confirm whether the named person is dedicated to your account.

A placement service may include ongoing payroll support, or recruiting may end when the hire joins. If you already have a candidate and need employment administration, ask an EOR about that narrower need.

Dedicated team

A dedicated team can fit an ongoing product area that needs several disciplines. Specify who owns the backlog and whether the team includes its own delivery lead.

Ask whether the project manager is dedicated or shared. Scheduling meetings differs from resolving dependencies and reporting delivery risk. Define the responsibilities your internal manager expects to hand over.

If a solution architect is included, ask what decisions they own and how much time they will spend on the account. Specify who approves architecture changes and records the reasons for them.

Project or full outsourcing

Use a project agreement when you can define a result and an acceptance process. The contract should describe deliverables, dependencies and how scope changes affect price.

Full outsourcing requires a clear boundary around the work transferred. Ask who handles support after launch, who owns the repositories and how another team could take over.

Consider a stalled application rebuild. If your technical lead knows the plan but lacks engineering capacity, an individual hire may fit. If nobody owns the design or release plan, adding developers leaves that gap open. Price the missing leadership explicitly.

How do you cut cost without losing quality?

Remove unnecessary requirements before lowering the hiring standard. A job description that demands every tool your company has used may exclude people who can do the actual work.

Separate skills needed on arrival from skills the hire can learn. Keep each requirement tied to a task or risk. Production ownership may require direct experience; a reporting tool may be teachable.

Use a work sample that resembles the role. Ask a backend candidate to explain a failed request and propose a fix. Ask a technical lead to review a design with unclear ownership. Keep the exercise bounded and explain how you will judge it.

Compare candidates against the same criteria. Record evidence while it is fresh instead of relying on who sounded most confident. Give interviewers distinct questions so candidates do not repeat the same conversation.

Do not replace a senior role with several junior roles unless someone has time to supervise them. Include review effort in your budget. Include the time your team would spend repairing work that passed a weak assessment.

For a new delivery relationship, start with bounded work that your team can evaluate. Agree on acceptance, access and handover before it begins. Expand when the work demonstrates the judgment and communication you need.

Measure more than output volume. Review whether the team catches unclear requirements, handles feedback and leaves maintainable code. Counting tickets without examining their scope can reward easy work while production risks remain unresolved.

How do you check time-zone overlap?

Time zone alignment means sharing the hours when decisions and reviews happen. A country name alone cannot tell you whether a candidate can attend your planning meeting or handle a release.

The table shows shared hours when both teams work from 9 a.m. to 5 p.m. locally. It uses January 15, 2027 for US standard time and July 15, 2026 for US daylight time.

Calendar calculations use IANA North American time zone rules and South American time zone rules. These are schedule examples, not promised working hours.

Mexico City and San José stay at UTC-6. Bogotá stays at UTC-5. Buenos Aires and São Paulo stay at UTC-3. US clock changes therefore change the shared window. Tijuana follows US daylight-saving changes and needs a separate schedule from Mexico City. IANA North America, IANA South America.

A Pacific-based manager should pay particular attention to afternoon availability when hiring in Buenos Aires or São Paulo. Discuss the proposed schedule with the candidate before treating shifted hours as part of the agreement.

Use shared hours for design reviews and decisions that block implementation. Keep routine status updates written. Ask candidates to explain a technical tradeoff in writing as well as on a call.

Agree on incident coverage separately. Normal overlap does not establish an on-call rotation. Assign escalation owners, discuss local holidays and record any expected work outside the regular schedule.

How much does the tech stack change the rate?

Ask for a quote tied to the work, not a surcharge for a programming language. A stack name does not tell you how much judgment the role requires.

Engineers using the same language may have very different jobs. Building internal forms differs from owning a service that handles sensitive records and must recover from failed writes.

Describe the technical problem in the hiring request. Include the current system, the changes expected and the decisions the hire will make without approval. Ask which requirements affect the quoted rate.

For a legacy system, distinguish knowledge of the language from experience operating that kind of system. For a migration, test how the candidate would validate results and recover from failure. For an AI-related role, define the work beyond access to a tool.

Request separate quotes when the scope is meaningfully different. Compare an individual contributor with a technical lead if either could meet the need. Keep the responsibility difference visible beside the price.

Ask the provider to explain its seniority assessment through evidence. Years of experience do not show how someone handles an unfamiliar failure. A higher rate should correspond to responsibilities the candidate can take off your team's plate.

If direct experience with a framework is essential, explain the consequence of getting it wrong. That gives the recruiter a reason to defend the requirement instead of matching keywords.

How do LatAm rates compare with US rates?

Use a US wage benchmark as context, then compare complete budgets for your own role.

BLS reports a median annual wage of $135,980 for US software developers in May 2025. That is an occupational wage benchmark, not a quote for a particular seniority or a complete employer budget. BLS software developers occupational outlook.

Role selection changes the comparison. BLS reports a separate median annual wage of $104,300 for software quality assurance analysts and testers in May 2025. Use the occupation that fits the work instead of applying a developer benchmark to every technical hire. BLS occupational pay data.

Keep compensation measures separate. Base salary, total compensation, take-home pay and a provider's invoice answer different questions. Levels.fyi describes total compensation as base salary plus stock and bonus. That measure should not be treated as a service rate card. Levels.fyi compensation definitions.

Build your comparison around the same responsibilities, hours and seniority. Add the costs your company retains under each option. Resolve differences in payroll support and benefits before comparing totals.

Also compare the work required from your managers. A lower invoice can come with more interview effort or supervision. For a more distant location, assess the actual handoff schedule alongside price.

Keep vacancy costs separate from recurring employment costs. If a delayed hire postpones a release, have the product owner review that assumption. Do not treat every open role as lost revenue or every faster search as a guaranteed saving.

What does a senior, mid and junior hire cost by country?

Request monthly ranges for a defined role in each country you are considering. Use the same pay basis across every response.

Ask for gross monthly base pay and a separate all-in monthly service quote. For Opus, review the pricing model and get a written quote on the first call.

Define levels through expected responsibility. A junior hire needs bounded tasks and a clear review path. A mid-level hire should own defined work with appropriate review. For a senior hire, specify the decisions and risks they must handle independently.

Ask each provider to map candidates to those expectations. Otherwise, a country comparison becomes a comparison of different seniority labels.

Use a quote worksheet to keep the request consistent:

For each returned range, request its date, currency and included compensation. Ask whether it reflects candidate expectations, accepted offers or current employee pay. Those are different observations.

Keep the complete service price beside the compensation range in your internal worksheet. A low base salary does not tell you what your company will pay.

If a provider quotes a wide range, ask what separates the lower and upper ends. Request candidate examples with identifying details removed. Avoid approving a budget at the bottom while asking recruiters to find someone who meets the top-end profile.

Score each provider with these eight criteria

Use the scorecard to collect evidence before ranking options. Decide which requirements are mandatory before scoring. A strong assessment process cannot compensate for an employment arrangement your company cannot approve.

Hiring model

Ask whether you are buying a hire, assigned capacity or a delivered result. A strong answer names who controls the backlog and who acts when work falls behind. Have the provider explain any proposal that mixes models.

Who employs the hire

Ask for the legal entity that signs the worker's agreement and the party responsible for payroll. Request the relevant documents before committing. The sales answer should match the agreement your contract reviewer receives.

Vetting evidence

Ask for a redacted assessment for a role like yours. Look for the exercise, evaluator's reasoning and hiring recommendation. A list of screening stages tells you the process; candidate evidence lets you judge the decision.

Time to shortlist and hire

Separate the first shortlist, accepted offer and first working day. Ask when each clock starts.

SHRM describes median time-to-fill in 2025 as roughly a month and a half, measured from requisition to offer acceptance. Compare hiring claims only after checking their definitions. SHRM state of recruiting.

SHRM also reports screening and interviewing averaging 8–9 days each. Those are broad recruiting benchmarks, not nearshore engineering promises. Ask which interview steps your own team must complete to meet the proposed schedule. SHRM benchmarking report announcement.

Replacement guarantee

Read the trigger, exclusions and costs. Ask what you must do to request a replacement and what happens to billing during the search. A replacement search does not explain how work continues while the role is vacant.

Pricing structure

Ask for a written total and the events that can change it. Confirm equipment, leave and exit costs. Keep the quote attached to the role definition so later scope changes remain visible.

Time-zone overlap

Ask for the candidate's city and proposed hours. Test the schedule against your team's calendar during both US clock periods. Convert a general promise of overlap into an agreed working window.

Retention evidence

Ask which hires were counted and how departures were treated. Request the measurement period and calculation. Check whether client-ended assignments and replacements count as departures before comparing percentages.

For each criterion, record whether the answer is documented, needs evidence or fails your requirement. Keep the reasons beside the rating so another reviewer can understand the decision. Opus is our #1 pick for US companies hiring full-time nearshore talent in Latin America.

How do you use the scorecard on a sales call?

Send the role description before the call. Include the expected outcome, reporting line, required hours and budget basis. Ask the provider to bring a sample assessment and standard agreement.

Start with the hiring model. If you need a person managed by your engineering lead, establish that before discussing a project team.

Work through the criteria using the same questions for each provider. Record the evidence beside each answer. A promise awaiting documentation remains an open question.

Ask the provider to walk through a plausible problem. The finalist declines, or the hire cannot attend the required meetings. Who acts, what changes and what might you pay?

Keep interview feedback specific. "Too junior" gives a recruiter little to act on. "Could explain the code but could not plan a safe rollout" identifies something the next assessment can test.

End the call with an owner for each open question. Request an updated quote if the discussion changed the role. Compare written responses after the presentation.

Have your hiring manager read the candidate assessment and your contract reviewer read the employment and exit terms. Give finance the same version of the quote. If reviewers are approving different scopes, resolve that mismatch before moving forward.

Save promises that affected your choice in the final agreement. Your operating team should not need a sales call recording to understand the service.

Why Opus is our #1 pick for a nearshore hiring partner

Opus is our #1 pick for US companies hiring full-time nearshore talent in Latin America, especially enterprise tech talent, senior engineers and AI talent. Its assessment process addresses a buyer's core question: who has checked that this person can do the work?

Opus uses eight-layer vetting: skills, English fluency, communication, accent clarity, references, role fit, culture fit, drive. Opus runs reference checks and background checks on every person it places. Opus vetting framework.

Its proprietary AI system supports sourcing, vetting and matching. Engineer-led interviews mean a vetted team of working engineers interviews every candidate. Ask to review assessment evidence against your role's responsibilities.

You choose the finalist and manage daily work. One flat monthly rate covers pay, local payroll, benefits, labor compliance and placement support, with no separate recruiting fee. Opus pricing.

Opus delivers 3 vetted candidates in 5 days, with about 14 days from hiring request to hired. Agree on the first working day separately. Opus process. Each placement carries a lifetime replacement guarantee with no cap or time limit.

Opus is not the right fit for short freelance gigs or teams that want a vendor to manage project delivery.

Talk to Opus about a role.

Which red flags should end a sales call?

End the evaluation if a provider refuses to identify who signs the worker's agreement. You need an accountable party for employment questions.

Pause if it insists on payment before explaining the pricing structure or sharing the relevant terms. A quote should make the service and its costs understandable.

Treat a refusal to discuss vetting evidence as a reason to stop. Candidate privacy can require redaction. The provider should still explain how an assessment works and what the evaluator records.

Watch for changes to the role used to defend a low price. A junior candidate may fit a different need. That does not make them equivalent to the senior owner you requested.

Reject comparisons that switch between salary and service price without saying so. Ask for both on a consistent basis.

Also stop if the proposed schedule depends on the candidate accepting hours they have not discussed. Confirm the arrangement with the person who will work it.

A provider may need time to answer a detailed question. Set a follow-up date. The red flag is unwillingness to make a material claim specific enough to check.

What should you ask before you sign?

Ask who owns each part of the working relationship. The agreement should match the operating plan your managers expect.

Confirm who approves leave and handles performance concerns. Ask what happens when the employee's local calendar differs from your release schedule.

Have the agreement address confidentiality and ownership of work. Ask your reviewer to check how those obligations reach the person doing the work.

Agree on device access and offboarding. Name the person inside your company who approves production access and removes it when the assignment ends. Clarify whether subcontractors need separate approval.

For project work, define acceptance before work begins. Include the handover materials your team needs to operate the result. Ask who pays to correct failed acceptance tests and how scope disputes are resolved.

For placements, name the onboarding manager. Plan the first assignment and arrange access before the start date. A completed search is not a completed onboarding process.

Judge early progress against the responsibilities in the hiring request. Fix missing access and unclear requirements before treating slow progress as a hiring failure.

Resolve the remaining commercial questions in writing:

• What can change the monthly rate?
• What notice does either party owe?
• Which costs remain if the hire leaves?
• What does a replacement request require?
• Who handles equipment returns and account closure?
• Who resolves payroll or benefits problems?

Have the provider correct conflicting answers in the proposal and agreement before signing.

How should you record your hiring decision?

The comparison method separates individual placements from full project delivery. It evaluates responsibilities, candidate evidence and contract terms within the model you need.

Compensation comparisons keep wages, total compensation and service invoices separate. Calendar comparisons assume stated local working hours. Company figures should be checked against the proposed agreement.

Apply the same method to your decision. Save the role description beside the quote. Record the evidence behind hiring claims and resolve employment responsibility before work begins.

The approval record should identify a specific hire or delivery scope, an agreed price and a manager who owns onboarding or acceptance. Leave any unresolved condition visible so procurement does not mistake an open question for an approved term. Opus is our #1 pick for US companies hiring full-time nearshore talent in Latin America.

Talk to Opus about a role.