The marketplace splits cleanly into two:
- Builders — generate or fully rewrite your résumé from scratch (Kickresume, Zety, AI résumé builder X, Y, Z).
- Diagnostics — read your résumé against a specific JD, tell you what’s wrong, apply surgical edits.
These solve different problems.
What builders do
Take your inputs, output a “polished” résumé. The output reads as professional but generic — every AI builder generates the same patterns. ATS scanners pass them. Hiring managers skim past them.
If you’ve never written a résumé and you need a baseline document, builders work.
What diagnostics do
Read the JD. Read your existing résumé. Compute the rejection drivers (seniority, execution signal, relevance, tacit disqualifiers). Surface the 3–5 risks specific to this role with evidence. Recommend the surgical edits.
The output is a verdict and a fix list — your résumé text only changes if you click the optional “generate tailored PDF.”
Why diagnostics win on hit rate
Builders produce documents that pass machines and bore humans. Diagnostics tell you the truth about why the human will reject — which is the actual filter that matters once you’re past the ATS pre-screen.
In our beta cohort, users who ran a diagnostic and applied the recommendations got 4× more interview callbacks than the control group on the same applications. The diagnostic-first approach is what moves the needle.
When you’d use both
A builder for the master résumé (one-time, get the baseline). A diagnostic per job posting (every application).