Sample output
A full candidate report, end to end.
This is exactly what you see when you open a candidate in Resume Autopsy: a fit score, the MATCH / PARTIAL / MISS qualification checklist with evidence quotes, keyword coverage, and an interview transcript analysis. Sample data — no real candidate.
Jordan Mills identified as candidate — speaks first and consistently refers to personal ownership of infrastructure described on the resume
Demonstrated SkillsSkills from the job description that the candidate actively backed up with specific examples during the interview.
- Walked through a real multi-region EKS outage with clear ownership of the recovery — credible and specific, matches resume claims
- Articulated CI/CD architecture decisions with reasoning on trade-offs; referenced the 400-engineer GitHub Actions pipeline directly
- Demonstrated working knowledge of AWS cost optimization beyond surface-level answers — gave specific numbers from a previous cost-reduction initiative
Gaps AddressedResume weaknesses or missing areas that the candidate clarified or provided new context for during the interview.
- Team leadership gap from resume analysis partially resolved — candidate has mentored two junior engineers and led incident response, though no formal direct reports yet
Unsupported ClaimsResume strengths the candidate couldn't back up, contradicted, or walked back when questioned during the interview.
- Resume mentions 'chaos engineering familiarity' but candidate could not name a specific tool or describe a real fault injection exercise when asked directly
Notable ResponsesStandout moments from the interview — specific answers that were particularly strong, revealing, or memorable.
When pushed on scaling beyond current team size, gave a thoughtful answer about delegation patterns and hiring bar — signals leadership readiness
Proactively flagged a limitation in their CloudFormation knowledge without being asked — honesty is a good sign
CommunicationHow clearly and effectively the candidate communicated — structure, conciseness, and command of language.
Concise and technically precise. Answers stayed on-topic without prompting. No rambling, no over-explaining. Strong communicator for a senior IC.
Overall AssessmentOverall evaluation tying interview performance to role fit, referencing specific things the candidate said.
Resume score holds up under interview scrutiny. The chaos engineering gap is confirmed but candidate is self-aware about it. The leadership gap is smaller than the resume suggested. Recommend advancing to the team-fit round.
Seven years of dedicated DevOps experience across fintech infrastructure, with direct Kubernetes cluster management and CI/CD pipeline ownership at scale. The strongest alignment is in AWS and Terraform — the gap is in chaos engineering practices the JD lists as preferred.
Strengths
- Kubernetes at Scalehigh"Manages 30+ EKS clusters across 4 AWS regions" maps directly to the JD's multi-region cluster requirement.
- CI/CD Pipeline Ownershiphigh"Built GitHub Actions pipelines supporting 400+ engineers" — the JD asks for 500+, but the architecture transfers.
Gaps
- No Team Lead ExperiencedealbreakerThe JD requires managing a team of 3–5 engineers. The resume shows IC work only — no direct reports or people management mentioned.
- No Chaos EngineeringsignificantThe JD lists Gremlin or Litmus as preferred. No mention of chaos practices anywhere on the resume.
- CloudFormation GapminorThe JD lists CloudFormation alongside Terraform, but the candidate's IaC experience is Terraform-only.
Keywords
Experience Alignment
Seven years exceeds the five-year minimum. Staff-level scope aligns with the senior IC role. Fintech infrastructure background is a direct match for the industry context.
Overall Assessment
Strong shortlist candidate. The Kubernetes and CI/CD depth directly answers the core of the JD. Chaos engineering is a preference, not a requirement — worth probing in the technical screen rather than screening out.
AI-generated assessment — not a professional evaluation or predictor of hiring outcomes.
Run your own job description through it.
Paste a JD, upload a real candidate batch, and get a report like this for every applicant in minutes.