How to Vet Offshore Developers: A 4-Stage Framework That Works

Vetting offshore developers is harder than vetting domestic candidates — and yet most US companies apply less rigor, not more. They assume resume credentials are equivalent, skip technical assessments, and hire on a 45-minute video call. Then they wonder why the results are inconsistent.

This framework is designed for US companies hiring software engineers in India and Eastern Europe. It has four stages, filters effectively at each stage, and takes 10–14 days from application to offer.

Stage 1: Credential Verification (Day 1–2)

Offshore resumes frequently contain credential inflation. Common inflations: claiming seniority that reflects title rather than actual responsibility, listing technologies 'worked with' briefly as core skills, including education credentials from institutions of widely varying quality.

What to verify

• GitHub profile: is there active code? What do the repositories show? Look at actual commits, not just starred projects
• LinkedIn: work history length vs claimed experience — does a claimed '8 years of experience' match the LinkedIn timeline?
• Education: IITs, NITs, BITS Pilani, and top state technical universities (IIIT Hyderabad, Jadavpur, etc.) are strong signal. Private university degrees without complementary work history are weaker signal
• Reference check framing: in India's culture, direct negative reference feedback is rare — ask specific behavioural questions ('Describe a project where this person struggled and how they handled it') rather than general 'was this person good?'

Stage 2: Async Technical Screen (Day 2–5)

The async screen is your most efficient filter. A 60–90 minute take-home assessment eliminates 60–70% of applicants who do not meet your technical threshold before you spend a single minute of interview time.

Assessment design principles

• One real problem, not a toy exercise: use an anonymized version of an actual problem your team has solved
• Time-boxed: state explicitly '60 minutes — we evaluate quality, not completeness'
• Evaluated on code quality, not just correct answer: readability, structure, error handling, test coverage matter
• Language-specific: test in the stack you actually use, not in whiteboard pseudocode

Red flags in async submissions

• Code that was clearly generated by AI without modification or understanding
• No error handling, no edge cases considered
• Hardcoded values, no separation of concerns
• Submission 15+ minutes over time limit without a note explaining why
• Communication quality issues in the submission write-up (unclear, grammatically poor, disorganized)

Stage 3: Technical Interview (Day 5–9)

The technical interview for offshore candidates should run 60–75 minutes with two interviewers: a senior engineer and the hiring manager. Structure:

First 15 minutes: async submission debrief

Walk through their take-home code together. Ask them to explain their approach, the tradeoffs they made, what they'd change with more time. This reveals whether they understood the problem, whether the code is genuinely theirs, and how they articulate technical decisions.

Middle 30 minutes: system design

For mid-senior candidates, present a simplified version of a system design problem relevant to your stack. You're not evaluating perfect architecture — you're evaluating how they think. Do they ask clarifying questions? Do they consider scale? Can they articulate tradeoffs?

Final 15 minutes: behavioral assessment

• 'Tell me about a time a production incident occurred and how you handled it'
• 'Describe a technical disagreement with a colleague and how it was resolved'
• 'How do you manage your work when requirements change mid-sprint?'

Stage 4: Working Style and Communication Screen (Day 9–12)

This is the most underrated stage and the most predictive of long-term success. A technically excellent offshore developer who cannot communicate asynchronously, who avoids raising problems, or who works in a fundamentally incompatible style with your team will underperform regardless of their coding skills.

The async communication test

Before the final interview, send the candidate a scenario via email or Slack: 'You're working on Feature X. You discover that the approach you were asked to use will not work because of [specific technical reason]. Your manager is asleep. What do you do?' Evaluate: speed of response, clarity of reasoning, autonomy in proposing an alternative, communication quality.

The final culture-fit call

30 minutes with the founder or team lead. This is not a technical interview — it's a working-relationship preview. Ask about their current work environment, their frustrations, what they want from their next role, and their experience working with US-based teams. Evaluate: communication confidence, intellectual curiosity, cultural fit with your team.

Reference Checks That Actually Work for Offshore Candidates

Call references provided — but also try to reach references not on the list. Ask the candidate: 'Can I speak with your current engineering manager?' If they're a senior candidate who claims strong relationships, they should have no hesitation. Reluctance to provide current manager as a reference is a yellow flag.

Ask references: 'On a scale of 1–10, how strong a communicator is this person with stakeholders outside engineering?' Follow up with: 'What would make them a 10?' This opens honest assessment without requiring direct negative feedback, which is culturally difficult to elicit in India.

Common Vetting Shortcuts That Fail

• Hiring purely on coding test score without communication screen — produces technically capable engineers who cannot update you asynchronously
• Skipping reference checks to move faster — costs 2x when you hire someone whose previous manager could have told you about a critical flaw
• Trusting agency-provided vetting exclusively — agencies have incentives to place candidates, not to protect your interests; always run your own screen
• One-interviewer process — offshore hiring decisions benefit from a second opinion; structured diverse perspectives catch different failure modes