Real output · Names anonymised
This is what a Hirelyzer analysis looks like.
A real analysis of a senior Backend Engineer role. Candidate names replaced with letters.
See it work
From a job description and a stack of CVs to a ranked shortlist.
Watch the full workflow in a few seconds — then scroll down for the detailed analysis it produces.
Start with the role
Hirelyzer reads the role and frames what a strong candidate looks like.
Senior Backend Engineer
- Location
- Remote · LATAM / Brazil
- Budget
- $6k–$8k / month
Must-have skills
Illustrative walkthrough with sample data — no real CVs are uploaded, processed, or stored.
Ranked shortlist — Senior Backend Engineer
| Candidate | Evidence strength | Summary |
|---|---|---|
ACandidate ATop match | 92% match | Strong technical fit, relevant domain experience |
BCandidate B | 84% match | Strong technical skills, limited scale experience |
CCandidate C | 76% match | Good fundamentals, gap in required stack |
DCandidate D | 61% match | Adjacent experience, career transition candidate |
ECandidate E | 44% match | Junior-level, insufficient seniority for this role |
Strong technical fit, relevant domain experience
Strong technical skills, limited scale experience
Good fundamentals, gap in required stack
Adjacent experience, career transition candidate
Junior-level, insufficient seniority for this role
Every candidate in your pool receives this level of analysis — ranked position, match reasoning, strengths, concerns, and interview questions.
Candidate A — Expanded view
92% evidence strength · Top match
Match reasoning
- 8 years Python/Django in production environments — matches JD requirement exactly
- Led backend team of 6 at previous company — aligns with team-lead requirement
- Shipped payment processing feature in PCI-DSS environment — directly relevant to role spec
- AWS certified, active since 2021 — infrastructure requirement met
Concerns
- No mention of Kubernetes — listed as preferred in JD, not confirmed
- Most recent role is contractor position — clarify availability and notice period
Suggested interview questions
- 1
You've led backend teams before — how did you approach onboarding engineers who were stronger technically than you expected?
- 2
Walk me through the PCI-DSS project — what were the constraints and how did the team adapt?
- 3
The role requires Kubernetes at a working level. How would you describe your current depth there and what would you need to get up to speed?
Candidate B — Expanded view
84% evidence strength
Match reasoning
- 6 years Node.js/TypeScript at two product companies — strong technical foundation
- Built REST and GraphQL APIs serving thousands of daily active users
- PostgreSQL and Redis throughout CV — matches required stack
- Computer Science degree — strong theoretical base for system design round
Concerns
- Largest team was 3 engineers — no evidence of operating at the 50M+ user scale in the JD
- No cloud certification listed — AWS/GCP exposure is implied but not confirmed
Suggested interview questions
- 1
Your current systems serve thousands of users. What's your mental model for scaling to 10x that — what breaks first?
- 2
Walk me through a production incident that slipped past your monitoring. What did you change afterwards?
- 3
What's the most complex async processing problem you've shipped, and how did you handle failure modes?
Candidate C — Expanded view
76% evidence strength
Match reasoning
- 5 years backend experience with strong Python fundamentals — core language requirement met
- Contributed to microservices migration at current company — relevant architecture experience
- PostgreSQL-heavy background with query performance tuning work evidenced
Concerns
- Stack is primarily FastAPI/Flask — no Django mentioned, which is a JD requirement
- No evidence of team lead responsibilities — role requires managing 2+ engineers
- Kubernetes not referenced anywhere in CV
Suggested interview questions
- 1
You've used FastAPI heavily. What would the learning curve look like moving to Django's ORM and admin patterns, and how would you approach it?
- 2
The role involves leading two engineers. Have you had informal mentorship or on-call coordination responsibilities we can build on?
- 3
Describe the most performance-critical query you've optimised. How did you identify the problem and what was the outcome?
We're onboarding recruiters gradually during our beta.
GDPR compliant · Secure file handling · No CV data used for training