Why Zemenay's 6-Step Developer Vetting Process Eliminates Bad Remote Hires
Most remote hiring fails because the vetting process is weak. Here is exactly how Zemenay's 6-step screening works—and why it catches problems that standard interviews miss.
There is one hiring truth that every company learns eventually, usually the painful way: the cost of a bad hire far exceeds the cost of a careful hiring process.
A developer who cannot deliver costs you their salary, the time your team spends managing the situation, the work that does not get done, and the weeks or months it takes to start again. For a senior engineering role, that is easily $50,000–$100,000 in total cost—for a single bad placement.
Rigorous vetting is not caution. It is economics.
Here is exactly how Zemenay's 6-step vetting process works—and why each step exists.
Why Standard Interviews Are Not Enough
Most companies interview candidates in one of two ways:
Option A: Resume + 2–3 interview rounds with engineering team. Fast, but relies heavily on the candidate's ability to present themselves. Developers who are good at interviews and developers who are good at engineering are overlapping but not identical sets.
Option B: Take-home assignment + interviews. Better signal on the technical side, but often fails to assess the dimensions that matter for remote work: communication, proactivity, async habits, and cultural fit with the team.
Neither approach does what a rigorous process needs to do: evaluate a developer across every dimension that determines whether they will succeed in a remote international role.
At Zemenay, we run six stages before a developer is presented to a client. Each stage is designed to assess a dimension that the other stages do not cover.
Stage 1: Application Review and Portfolio Analysis
What it is: Before any conversation, we review the developer's application materials, GitHub profile, portfolio projects, and online presence.
What we are looking for:
- Evidence of shipping real products, not just tutorials
- Code quality signals: meaningful commit messages, readable structure, test presence
- Technical breadth and depth across their claimed skills
- Open source contributions or community involvement that indicate genuine engagement with their craft
- Red flags: gaps that are unexplained, technologies claimed without evidence, portfolio that is entirely tutorial work
Why it matters: The application filters for basic credibility. We do not move candidates to the next stage if the evidence at this stage does not support their claims.
Stage 2: Technical Screening Interview
What it is: A 45–60 minute video call focused exclusively on technical depth.
What we cover:
- Conceptual understanding of their primary technology stack ("Explain how React's reconciliation algorithm works and when you would use useMemo")
- Problem-solving approach: given a realistic engineering challenge, how do they think through it?
- Depth probing: when a candidate gives an answer, we ask one level deeper to test whether they understand the principle or have memorized the surface
- Stack-specific technical concepts, architecture patterns, and their reasoning for tool choices
Why it matters: This stage filters out developers who know the vocabulary of a technology but do not understand how it works. Most resumes pass the first stage. Fewer than 40% pass this one.
Stage 3: Practical Coding Assessment
What it is: A role-specific, realistic coding challenge completed in the candidate's own environment, with a time limit that reflects the problem's scope.
What we assess:
- Functional correctness: does the code actually solve the problem?
- Code quality: is it readable, maintainable, and structured well?
- Testing: have they written any? Is it meaningful?
- Edge case handling: have they thought about what could go wrong?
- Documentation: would someone else be able to understand this code?
Why it matters: Interview conversations are no substitute for actual code. This stage gives us concrete evidence of how a candidate codes when they are not being directly observed. We see their natural patterns, not their rehearsed best behavior.
Stage 4: System Design and Architecture Discussion
What it is: A live design session where the candidate is given a realistic, open-ended engineering problem and asked to design a solution.
What we assess:
- Ability to think at scale, not just at the function level
- Trade-off reasoning: when asked why they made a design choice, can they articulate what they gave up?
- Communication of technical concepts: can they explain complex architecture clearly?
- Scope management: do they ask clarifying questions, or do they charge ahead with assumptions?
- Awareness of real-world constraints: performance, reliability, cost, maintainability
Why it matters: Senior developers do not just write good code—they make good architectural decisions. This stage is specifically designed to evaluate the judgment that differentiates a strong mid-level engineer from someone who can genuinely operate at senior or lead level.
Stage 5: Communication and Remote Work Evaluation
What it is: A structured conversation and written assessment focused specifically on the skills that determine success in remote international work.
What we assess:
- Written communication clarity: we ask the candidate to write a brief explanation of a technical decision as if to a non-technical stakeholder
- Async communication habits: how do they handle blockers? How do they update teammates when working solo?
- Meeting and collaboration style: are they comfortable with video calls? Do they contribute actively in group settings?
- Time management and self-direction: how do they structure their working day without direct supervision?
- Feedback receptiveness: how do they respond to critical feedback on their code or work?
Why it matters: Technical skill is necessary but not sufficient for remote work. A developer who cannot communicate clearly in writing will create friction in every async interaction. We have seen technically strong developers fail in remote roles specifically because this dimension was not evaluated.
Stage 6: Reference Check
What it is: Direct conversations with at least two professional references—preferably including at least one engineering manager or CTO.
What we cover:
- Quality and reliability of the developer's work in practice
- How they handled difficulty or pressure
- Communication and collaboration experience
- Their growth trajectory over the engagement
- Honest assessment of their limitations and blind spots
Why it matters: References are underused in most hiring processes because the standard reference call is too vague ("would you recommend them?"). Our reference calls are structured and specific. We ask about concrete situations, probe for nuance, and pay as much attention to what people hedge around as to what they say directly.
What Passes and What Does Not
To be direct: most developers who enter our process do not complete it. The combination of six stages creates compounding filters.
- Stage 1 removes candidates whose portfolio and application do not support their claims
- Stage 2 removes candidates who know the vocabulary but not the underlying principles
- Stage 3 removes candidates who interview well but code poorly
- Stage 4 removes candidates who cannot reason at the architectural level their claimed experience implies
- Stage 5 removes candidates who would be strong in-office engineers but struggle in async remote environments
- Stage 6 removes candidates whose professional track record does not match their self-presentation
The developers who pass all six stages are not just technically competent—they are people we would stake our reputation on. Because every placement is exactly that: a stake of our reputation.
The One-Time Fee Alignment
Our pricing model—a single placement fee rather than ongoing monthly markups—aligns our incentives directly with the quality of each placement. We succeed when the placement lasts and the client returns for their next hire. We fail when a placement does not work out.
That alignment is the reason we run six stages rather than two.
Want to See the Developers Who Cleared Our Process?
Zemenay's vetted developer pool represents the top of Ethiopia's tech talent market — filtered through a process designed to eliminate every type of bad hire.
We are an international tech company based in Addis Ababa. Beyond recruitment, we also build your product (web apps, mobile apps, SEO, deployment) and manage customer support — all under one roof.
Get a free consultation today.
