My friend applied to 50+ jobs he was overqualified for. Zero interviews.
We ran his resume through Resume Wizard. 26% keyword match.
He had every skill they wanted—just used different wording. "Collaborated with stakeholders" vs "cross-functional team leadership." "Ubuntu" instead of "Linux." Same things. ATS didn't care.
He fixed the keywords in 30 minutes. Two weeks later: 3 interviews.
That's when I decided to build ResumeWizard.
What it does:
Tech stack: Next.js, TypeScript, compromise.js for NLP parsing
Traction so far: $29 (1 user in the first week)
Pricing: Free first analysis, $5 for 5 more, $29/mo unlimited
Link: https://www.resumewizard.pro
What I'm working on:
Questions for IH:
Would love your feedback! Happy to answer any questions about the tech or approach.
Nice write‑up. The keyword mismatch story is real — we’ve seen people accept a score only when it’s tied to concrete issues (missing keywords + where they belong, ATS parse errors, weak impact bullets).
Two ideas that might help conversion:
• Show a tiny “why” for each keyword gap (e.g., which job requirement it maps to) so it feels role‑specific.
• A quick before/after example can make the value tangible.
Re LinkedIn optimization: I’d keep it optional unless you can reuse the same role‑fit logic. We’re building a similar structured report at https://resume.easy-ai.me/ and the role context is what users mention most.