Resume · job description
Lay a posting over your resume and read the overlap: what you have evidenced, what you have only half said, and what is simply not there. Then take a rewrite aimed at that job — built only from work you have actually done.
68/100
What the report actually says
5+ years backend engineering
covered · required
Six years across two payments companies.
Production Kubernetes experience
covered · required
Migrated 60 services from EC2 to EKS.
Experience with LLMs and agentic tooling
missing · required
Nothing in the resume supports this. It is the deciding gap.
Comfortable owning ambiguous problems
partial
Implied by the migration work, but never stated outright.
Keywords a screen looks for
Green already appears in your resume. Red does not.
4 required skills are not evidenced anywhere in your resume.
It names them. Tailoring cannot invent them — if you have the experience, it needs to be on the page first.
The rule
What it will do
What it will never do
Every change is logged with the part of the posting that prompted it, so you can check the whole thing before you send it. A resume that wins an interview you cannot survive is worse than no interview.
How it goes
Paste the text, drop in a link, or upload the file. Greenhouse and Lever links are read straight from their job feeds.
PDF, Word or plain text. Scans and photographs work too — the page images are read directly.
Every requirement in the posting, marked covered, partial or missing, each one quoted against your own words.
A resume reordered and rewritten for this job, as Word or PDF, with a log of every change and why it was made.
A posting and a resume is all it needs.