After a few months of nights and weekends, I shipped resume.zoevera.com today and wanted to share it here before anywhere else.
What it does:
You paste your resume and a job description. Within 30 seconds you get:
- ATS match score — a percentage showing how well your resume matches the role before a human reads it
- Keyword gap analysis — exact terms the job description uses that your resume is missing, grouped by category (technical skills, tools, soft skills,
certifications)
- AI resume rewrite — your existing bullets rewritten to close those gaps, without inventing experience you don't have
- Cover letter rewrite — a targeted cover letter generated from the same job description, consistent with the rewritten resume
- "Hidden experience" recommendations — this is the part I'm most proud of: the tool identifies skills and experience the job description asks for
that you likely have but didn't mention. Things like "you've probably used Agile if you worked at a company this size" or "this role requires
stakeholder communication — your PM role implies that but your resume never says it." It prompts you to add those explicitly rather than assuming a
recruiter will infer them.
The problem I kept seeing: Most people write one resume and blast it everywhere. ATS systems (Workday, Greenhouse, Lever) do keyword matching before a
human ever reads it. A resume that's a 45% match for a role gets filtered out before anyone sees it — even if the candidate is qualified. The fix
isn't keyword stuffing — it's surfacing what you actually did in language that matches what the employer is looking for.
The tech, since this crowd appreciates it:
- Next.js 15 App Router, TypeScript, Tailwind
- Claude Sonnet for the rewrite (Haiku for the fast analysis pass)
- Stripe for payments, Resend for email, Vercel for hosting
- ISR with 24h revalidation on all content pages
- Free to scan, $12 for a full AI rewrite (no subscription required)
What I learned building it:
The hardest part wasn't the AI — it was the timeout math. A resume + job description is ~2,500 tokens in, 4,000 tokens out on Sonnet. Getting that to
reliably finish under Vercel's function limits without aborting mid-rewrite took more iteration than the actual product.
The second hardest part: the free tier. I wanted zero friction — no account, no credit card, just paste and go. Building an anonymous usage system
that degrades gracefully into a paywall without feeling hostile was trickier than expected.
The hidden experience recommendations required the most prompt engineering. Getting the model to suggest things confidently but not fabricate — "you
probably have this, go add it if so" vs. "you have this" — took a lot of iteration to get the tone right.
Where it stands: Early days. A handful of paying customers, a lot of free scans. I've published keyword guides for 50+ specific roles (nurse, data
scientist, software engineer, etc.) which is driving most of the organic traffic right now.
Happy to answer questions about the stack, the Claude API integration, the Stripe setup, the prompt architecture, or anything else. And if you try it
and something feels broken, I want to know.
---
Built solo. Feedback welcome.