Resume checker for software engineers
Engineering resumes rarely fail on skills. They fail on formatting and on bullets that list a stack instead of a change. This checker scores both against the posting you are applying to.
What software engineers get screened on
01A technical screen usually starts from a term list built out of the posting: languages, frameworks, infrastructure, testing. A term that is not in the text is a miss, whether or not you have used it.
- TypeScript / JavaScriptSkills line, and once in a bullet that says what it built
- REST APIExperience bullet — name the service, not just the style
- Unit testingExperience bullet: what the tests caught or prevented
- CI/CDExperience bullet, next to the pipeline tool you actually used
- DockerSkills line, or a deployment bullet
- GitSkills line is enough; it is a baseline tool, not a differentiator
- Code reviewExperience bullet — say what the review changed
- AgileSkills line, once. Do not repeat it in every role
- KubernetesDeployment or platform bullet
- GraphQLExperience bullet: which client or gateway
- PostgreSQLSkills line, next to the other data stores
- MicroservicesUse it only if you split or owned services; otherwise describe the service
Two bullets, before and after
02Each rewrite reuses only the figures already in the original line. Nothing here invents a number you would have to defend in an interview.
Responsible for improving the performance of the checkout service (p95 went from 1.4s to 220ms).
Rebuilt the checkout service, cutting p95 response time from 1.4s to 220ms.
Same number, one verb. The first version makes the reader dig for the result; the second leads with it.
Worked on the Docker migration for 14 services.
Moved 14 services to Docker and Kubernetes, replacing manual deploys with a CI/CD pipeline.
“Worked on” hides whether you did the work or attended the meetings. Name the object and the change.
Where these resumes break
03- —A contact line built from icons in the Word header is frequently dropped before the body is parsed. Keep a plain text line on page one: name, email, phone, city.
- —A two-column template with a skills sidebar can extract your name sitting next to a leftover skill. One column, no sidebar.
- —“ReactJS” and “React” are different strings to an exact match. Write the term the posting uses, at least once, in plain text.
A sample, scored
04A made-up six-year candidate, written the way most engineering resumes are written: solid stack, two bullets that open with “Responsible for”. The score below is what this site computes for this file against this posting.
This sample was written for this page, not scraped from a real candidate. The score is computed by the same rules your file would run through, so it moves whenever the rules change — which is why it is not a hard-coded number.
Score your own file→