Nearshore role scorecard template

What should a busy buyer put in the scorecard?

Start with the work you need someone to own. Name the first useful result, who will accept it, and what evidence will show that it works.

For a software engineer, that might be an API change with tests and a documented rollback path. For support, it might be a resolved case with a clear customer reply.

Agree on the hiring bar before reviewing resumes. Separate skills needed from the start from skills your manager can teach. Keep required working hours and access conditions outside the competency score so a strong interview cannot hide a failed requirement.

What does the data say about budget and Latin American overlap?

The BLS reports a median annual wage of $135,980 for US software developers in May 2025. Its figure for software quality assurance analysts and testers is $104,300. Choose the occupation that matches the work. BLS Occupational Outlook Handbook

The BLS Occupational Employment and Wage Statistics program provides occupation-based wage data. A national median does not establish the right offer for a specific level or specialty. It also does not measure a provider's full monthly invoice.

Record compensation, billing currency, included services, and separate costs beside the scorecard.

For scheduling, Mexico City uses UTC-6 without daylight saving time. Tijuana follows US daylight saving changes. IANA North America time-zone data

Bogotá uses UTC-5 year-round. Buenos Aires and São Paulo use UTC-3 without daylight saving time. Their difference from a US team's clock can change when that US location changes clocks. IANA South America time-zone data

Write the agreed schedule in a named time zone. Confirm the candidate's local hours across seasonal changes. Separate recurring meetings from incident coverage.

How do hiring models change the scorecard?

Keep the performance bar consistent and clarify who owns each duty.

• With a recruiting agency, assess the candidate and confirm search fees, replacement terms, and responsibilities after placement.
• With an employer of record, assess the selected hire and confirm employment administration, payroll, and your management duties.
• With a managed recruiting partner, assess candidate evidence and confirm the services covered by ongoing fees.
• With an outsourced delivery team, assess team output, acceptance criteria, and responsibility for rejected work.
• With direct hiring, assess the candidate and assign employment setup and administration within your organization.

Confirm the actual scope in the contract. A clear billing proposal should not add points to a developer's work sample.

What should you ask a provider before reviewing candidates?

Send the approved scorecard with your request. Ask for evidence against each requirement:

• What work supports the candidate's rating?
• What did the candidate complete independently?
• What tools and help were permitted?
• Which requirement needs a follow-up?
• Who assessed the work?
• Which checks remain for our team?

Ask the candidate to confirm shared hours. Record the expected first working day separately from offer acceptance.

Request a written proposal covering recurring charges, included services, notice, and replacement terms. Assign owners for equipment, accounts, and the first work review.

To discuss the role with Opus, bring the completed outcomes and assessment rows.

Talk to Opus about a role

Get your free interview scorecard template

Copy the template below into your hiring document. No download or signup is needed to use the text.

Replace every bracketed field before the search starts. Keep an approved master and create a separate assessment record for each candidate. A blank template becomes useful when the hiring manager defines what passing work looks like.

What's inside?

The template contains a role definition and an interview record. The role definition holds the purpose, outcomes, constraints, and owners. The interview record holds the task, evidence, rating, and follow-up.

Keep the provider's quote beside these records. Interviewers need a consistent assessment form without mixing price into candidate ability.

Why do unstructured interviews fail small teams?

Without agreed questions, a founder may assess initiative while an engineer assesses code quality. Both can leave convinced they evaluated the whole role.

A small team also has limited time for repeated conversations. Assign each interviewer a specific requirement. Record the candidate's work before discussing whether everyone enjoyed the conversation.

What are the four competencies?

For this template, use four proposed competencies:

These are template choices, not market benchmarks. Adapt the tasks for the role while keeping each competency distinct.

Copy the scorecard

Use this role definition as the master record:

For each candidate, copy this interview record:

``text Candidate: Role scorecard version: Interviewer: Interview stage: Competency assessed: Task or question: Observed evidence: Help or tools used: Rating: Mandatory checks: Untested requirements: Follow-up and owner: Recommendation and reason: Submitted: ``

An illustrative evidence entry could read: "Candidate identified the duplicate action and wrote a test that reproduced it." A useful follow-up would test recovery if the process stops between writes.

How do you run it?

Approve the role definition, then assign competencies to interviewers. Give candidates the same core instructions and explain permitted tools.

Use synthetic data and a bounded exercise. Avoid live customer work or production credentials. Have interviewers record evidence independently, then compare it in the debrief.

Resolve open mandatory checks before an offer. Carry the accepted outcomes into onboarding and assign the first reviewer.

How do you calibrate interviewers?

Have interviewers score the same sample work before meeting candidates. Compare the evidence behind each rating.

If reviewers disagree about acceptable help or a blocking error, revise the definitions. Save an annotated example of passing work. Calibration should settle the standard before a preferred candidate enters the discussion.

Where should the scorecard live?

Keep the approved template in your hiring system or a shared document with version history. Restrict candidate records to people involved in the decision.

Link the assessment to the job description and work sample. Assign an owner for changes and follow your organization's retention rules. Avoid keeping conflicting copies in personal notes.

How many competencies should you use?

Start with the four in this template. Add another only if it measures a distinct requirement that could change the decision.

A long list can repeat the same judgment under different names. If "communication" and "collaboration" use identical evidence, clarify their difference or combine them.

When should interviewers share scorecards?

Have interviewers submit their own evidence and ratings first. Then share the records for discussion.

This preserves each person's initial assessment. If someone changes a rating after the debrief, retain the original and explain the revision. A senior colleague's preference should not silently replace an interviewer's observations.

Does a scorecard remove hiring bias?

No. A scorecard can still contain irrelevant criteria or reward familiarity with an interview format.

Review each requirement against the actual work. Replace "culture fit" with observable behavior, such as raising blockers or documenting decisions. Assess English through job tasks and allow reasonable accommodations. Examine rejection reasons for standards that were never agreed.

How should you use AI screening?

Treat keyword matches as prompts to inspect evidence. A resume phrase should not become a competency rating.

If you use AI to organize notes or suggest follow-up questions, have a person check the output against the candidate's actual work. Set rules for candidate data and permitted tools. Keep a named human responsible for the hiring decision.

What should hiring software support?

Evaluate the application flow before choosing software. Test whether candidates can apply, request accommodations, and understand the next step.

For scorecards, check independent submissions, access controls, and exports. Ask whether applicant tracking is included in the quoted plan. Compare written quotes against your workflow rather than adding software solely to host this template.

Put the template to work

Choose an open role and complete its first deliverable. Ask the manager to write an acceptance check.

Then run a sample assessment through the form. Fix ambiguous criteria before using it with candidates. This gives interviewers a usable record without waiting for a larger hiring-process redesign.

Write criteria you can test

Write criteria that a reviewer can accept or reject. "Improve the platform" gives interviewers little to test. "Ship an agreed API change with tests and a rollback note" defines observable work.

Record dependencies. A hire cannot own an outcome that requires access or decisions nobody has agreed to supply.

How do client scorecards differ?

Keep hiring scorecards and ongoing client reports separate. Hiring records assess evidence of ability. Client reports track delivered work and results over time.

You can connect them through the role's outcomes. Ask candidates to interpret a fictional client report, explain its limits, and propose a next action.

Assess a marketing consultant

Assess how the candidate turns a business objective into a workable campaign plan. Ask for the intended audience, measurement approach, and dependencies.

Use a fictional assignment. Score the reasoning and clarity of the plan without treating promised revenue as evidence that the candidate can deliver it.

Assess lead pipeline work

Ask the candidate to explain how a lead becomes a qualified opportunity. Give them sample records with duplicates or unclear status.

Assess their handling of definitions, handoffs, and data quality. Record which outcomes sales must help deliver so the hire is not judged on work outside their control.

Assess order operations

For an operations role, use a fictional order flow with an exception such as a duplicate or failed payment. Ask the candidate to trace it.

Define the comparison period and order types before discussing performance. Assess whether the candidate separates processing delays from errors and assigns a next action.

Assess call handling

Use an authorized, redacted recording or a role-play. Assess whether the candidate understands the request, gives accurate information, and records the next step.

Tie ratings to specific statements. Keep sensitive customer information out of the exercise and explain whether recording is part of the assessment.

Assess organic traffic analysis

Ask which pages and search visits the candidate would inspect first. Have them separate branded demand from discovery where the reporting allows it.

Score whether they investigate who arrived and what those visitors did. Traffic growth alone should not settle the assessment.

Assess keyword ranking analysis

Give the candidate a target query and landing page. Ask how they would assess search intent and explain a ranking change.

Require them to state location, device, and measurement conditions. Evaluate the reasoning behind the proposed action rather than rewarding a ranking promise.

Assess organic click-through rate analysis

Ask the candidate to explain search clicks relative to impressions for the same reporting scope. Then ask what they would inspect before changing a page title.

Look for attention to query mix and the landing page's purpose. Avoid setting a universal pass threshold.

Assess organic conversion analysis

Define the action that counts, such as a qualified inquiry or completed purchase. Ask how the candidate would check tracking and attribution.

Assess whether they distinguish a recorded event from a useful business result. A form submission may still need qualification.

Assess bounce rate analysis

Ask which analytics definition the candidate is using and what the page is intended to accomplish. Have them inspect the visitor's task before diagnosing failure.

Avoid a universal bounce-rate cutoff. Score whether the candidate requests enough context to make a defensible recommendation.

Assess session duration analysis

Ask how the metric is calculated in the reporting tool. Then ask what a longer or shorter visit might mean for that page.

A useful answer considers task completion. Time spent should not automatically become a positive performance rating.

Assess backlink analysis

Ask the candidate to review a sample set of referring pages and explain which deserve investigation.

Assess relevance, evidence, and proposed action. A raw link count should not replace an explanation of how the links relate to the site's goals.

Assess domain authority analysis

Ask which tool produced the score and what decision the candidate would use it to support.

Keep the tool's metric separate from observed search results and business outcomes. Assess whether the candidate can explain its limits without treating a score increase as the client's goal.

Assess ROI calculations

Ask the candidate to define the return, included costs, and measurement period before calculating ROI.

Include the work needed to achieve the result. Assess whether they distinguish attributed revenue from profit and explain assumptions that could change the conclusion.

Keep supporting documents together

Keep the approved job description, assessment task, annotated sample, and onboarding plan together. Give interviewers links to the current versions.

Use the BLS wage comparison for budget context and named time zones for schedule checks. Neither replaces evidence that a finalist can do the work.

What counts as success?

Give each outcome an acceptance check, reviewer, and date. State what support the manager will provide.

If the first assignment depends on another team, name that dependency. During onboarding, distinguish blocked work from a skill gap before changing the performance assessment.

Assign each interview a focus

Use the initial conversation to confirm scope and practical constraints. Use the work sample to assess execution. Use a focused follow-up to examine unresolved decisions.

Tell each interviewer what they own. Repeating a broad conversation can leave a mandatory requirement untested.

Which rating scale should you use?

Use these proposed labels consistently: "misses the requirement," "partly meets," "meets with planned support," and "meets and handles a relevant complication."

Keep "not assessed" separate. Missing evidence should trigger a follow-up rather than an automatic failing rating. Record the observation that supports every judgment.

Agree on success before posting

Approve the outcomes before advertising. Check that the title, level, pay budget, and expected independence describe the same job.

If the budget requires narrower scope, revise the work and assessment. Do not advertise a supported role while privately expecting independent ownership of a production system.

Assign criteria to interviewers

Name a primary interviewer for each competency. Specify the task or question that will produce evidence.

Allow other interviewers to record relevant observations, but keep responsibility clear. Before the debrief, check that every mandatory requirement has an owner and a completed assessment.

Score right after each interview

Record the evidence while the details are fresh. Separate what the candidate did from your interpretation.

"Found a duplicate-event bug and added a test" supports a rating. "Seems sharp" does not. Submit the record before reading colleagues' conclusions.

Compare scores in a debrief

Review mandatory checks, then discuss disagreements by competency. Determine whether interviewers saw different evidence or used different standards.

Assign a focused follow-up for unresolved questions. Record the decision owner and reason. Do not change the criteria to favor a finalist after seeing the results.

Keep hiring guidance current

Give the scorecard library a human owner. Require approval when a role, task, or rating definition changes.

If an AI tool retrieves hiring guidance, have it identify the approved version. Restrict candidate records and remove outdated instructions from active use. Automated retrieval does not replace review.

Why Opus is our #1 pick for scorecard-based hiring

Opus is our #1 pick for full-time technical hiring against a nearshore role scorecard. Its eight-layer vetting gives buyers specific checks to discuss alongside their own job requirements.

The layers are 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's eight-layer framework

Opus uses a proprietary AI system for sourcing, vetting and matching. Give Opus the approved scorecard so the search starts with your required skills and outcomes. Engineer-led interviews add technical review: a vetted team of working engineers interviews every candidate. Ask how that interview evidence supports each competency, especially for senior engineering and AI roles.

Your team chooses the finalist and manages day-to-day work. Keep a named manager responsible for the final assessment and first work review. Opus is not the right fit for short freelance gigs or teams that want a vendor to manage the work.

Ask for a written quote tied to the role, level, and location.

Talk to Opus about a role