Opus uses eight vetting layers for senior hires: skills, English fluency, communication, accent clarity, references, role fit, culture fit, and drive. These cover what a candidate can do and how they work with a team. AI certification is separate and is completed before day one.
What to assess beyond the resume
A resume lists a candidate’s roles and projects. Interviews and work exercises can show how they explain a decision, approach a debugging problem, and respond when they do not know an answer.
Updated September 16, 2026: this revision clarifies that the eight published vetting areas organize role-specific evidence and do not replace your own assessment.
Opus uses the same eight vetting areas across roles. For a senior engineer, the work being discussed should reflect the responsibilities of the engineering role. Use the questions below to test each area.
The eight vetting layers
The Opus vetting process covers skills, English fluency, communication, accent clarity, references, role fit, culture fit, and drive. Each area answers a different hiring question:
Hiring-team worksheet based on Opus's published eight vetting areas
This is a public framework for structuring a hiring discussion. It is not Opus's internal scorecard or a reproduction of a private production artifact. Record evidence before group discussion, use the same questions for every candidate, and name the risk that remains.
| Vetting area | Evidence to record | Remaining risk |
|---|---|---|
| Skills | Relevant project, technical decisions, and a bounded work sample. | Can the candidate do this role's work in its tools and constraints? |
| English fluency | Spoken explanation and written handoff in the team's working language. | Where could language slow decisions or handoffs? |
| Communication | A decision explained to the person who needs to act on it. | What context might still be lost under pressure? |
| Accent clarity | Whether colleagues can understand the calls the role requires. | Could audio quality or unfamiliar terminology affect the result? |
| References | Specific examples from former colleagues about this work. | What remains untested because the reference did not observe it? |
| Role fit | Evidence tied to the responsibilities and expected outcomes. | Which part of the role has the weakest evidence? |
| Culture fit | Examples of feedback, collaboration, and autonomy. | Which working expectation still needs agreement? |
| Drive | Why the candidate wants this role and the work they want to take on. | What could change after the first assignment? |
The prompts below add role-specific questions for architecture decisions, communication with a product owner, independent delivery, mentoring, and references.
AI certification sits outside these eight layers. Opus describes a six-module certification completed before day one. It should not replace an assessment of the candidate’s skills or ability to work with your team.
How to assess communication
Ask a senior engineer to explain a recent architecture decision twice: first to another engineer, then to a non-technical product owner. Listen for whether the explanation changes for its audience. The product owner may need to understand a delivery tradeoff or customer impact without hearing every implementation detail.
A useful follow-up is to ask what information would have changed the decision. That gives the candidate room to explain uncertainty instead of defending every past choice.
Communication and accent clarity address different questions. An explanation may be easy to hear but hard to follow, or technically clear once a listener asks for a phrase to be repeated. Use the actual communication needs of the role when evaluating both. Poor microphone quality or a weak connection should not be mistaken for a candidate’s ability.
Use references to explore the role
Before a reference conversation, identify what you still need to learn. If the role involves mentoring, ask about a time the candidate helped another engineer make progress. If it requires independent delivery, ask what they owned and when they needed support.
Concrete examples are more useful than a general endorsement. Give the reference enough context about the proposed role, then ask questions tied to its responsibilities.
What retention can tell you
Opus reports 97% one-year retention. That is a reported placement outcome, not evidence that any particular vetting layer caused it. Interpreting a retention figure also requires knowing which placements were eligible to reach one year and when the measurement was taken. See how Opus describes its hiring metrics.
Vetting is intended to surface gaps in skills and expectations before a hire. Retention can also depend on the job itself: management, workload, compensation, and whether the work matches what was discussed during hiring. A process review should consider those conditions as well as candidate selection.
Apply the framework to your next hire
Start with the work you need the person to own. Agree on the evidence you want for each requirement, then use consistent questions across candidates. A useful assessment should help you make a decision; adding another interview without a clear question only adds time.
Opus recruits full-time Latin American talent and uses eight-layer vetting across its searches. Its published offer includes 3 vetted candidates in 5 days, plus a company-reported average of about 14 days from brief received to hired, and a lifetime replacement guarantee with no cap. For an engineering search, see how to hire senior engineers in 14 days or talk with Opus about the role.
Assess the candidate before you choose a provider
The eight-layer checklist above is Opus's published framework. When comparing providers, ask each to show its own process against your role brief; a useful buyer test is whether a candidate holds up against your own assessment, not just the provider's screening. Before signing with any provider, write the same brief you would give an internal hiring manager: the actual task, a permissioned and properly anonymized sample of real or realistic data or code, the specific questions you will ask, the rating anchors your reviewer will use, who that reviewer is, the time budget the candidate gets, and confirmation that your own hiring manager, not the provider, makes the final call.
Adapt that buyer-owned structure across functions, changing the task and evidence to fit each role. For a growth marketing hire, Opus's guide to hiring growth marketers in Latin America uses a paid, scoped exercise built from fictional or anonymized data and a reporting discrepancy. For a finance hire, Opus's GAAP and NetSuite finance manager guide uses a fictional close-review and reconciliation case. For an operations hire, Opus's guide to hiring senior operators uses a fictional scenario-based judgment screen tied to process artifacts. For a RevOps hire, Opus's RevOps work sample uses a fictional CRM change-control exercise. For an engineering hire, see Opus's guide to hiring senior engineers in about two weeks. The method behind all of these, a structured work sample reviewed against a fixed rubric, follows the general approach described in the US Office of Personnel Management's guidance on work samples and simulations. Citing that guidance describes a method, not a validation or endorsement of any specific exercise here.
Frequently asked questions
How does Opus vet senior remote engineers?
Opus uses eight vetting layers across roles: skills, English fluency, communication, accent clarity, references, role fit, culture fit, and drive. For an engineering hire, discuss evidence relevant to the technical responsibilities and team expectations of that role.
Is AI certification one of the eight vetting layers?
No. Opus describes AI certification separately from the eight vetting layers, with six modules completed before day one.
How can a hiring team assess communication clarity?
Ask the candidate to explain a recent architecture decision to an engineer and then a product owner. Look for whether the second explanation gives the product owner the information they need to make a decision.
What should a reference conversation cover?
Ask about work relevant to the proposed role, such as independent delivery, collaboration, or mentoring. Request specific examples and discuss any gaps that remain after the interviews.
Does the reported retention rate prove the vetting process works?
Opus reports 97% one-year retention. That figure describes an outcome; it does not isolate the effect of vetting from management, compensation, or other working conditions.
