HelloPM · AI Builder Series Explore builds →
Quest 3 · JD-to-resume customiser

JD-to-resume customiser

AutomationPDF generationJob searchLinkedIn post

The assignment

Build a tool that takes a job description and customises your resume to match. Outputs a finished PDF — not a chat-bound Gem.

Screenshot of Shohan Shetty's JD-to-resume customiser submission
JD-to-resume customiser — Quest 3, built by Shohan Shetty

What Shohan shipped

A resume-optimization tool built with Next.js, Supabase, and the Gemini API, designed to reframe a resume for ATS compatibility using an anti-hallucination system prompt.

View the LinkedIn post ↗ Shohan's full portfolio

Our read on this build

Shohan shipped a LinkedIn post. This read comes from the artifact and Shohan's own account of it — no scores, just what the build does and does not show.

What it demonstrates

  • It reads the posting before it rewrites: an ATS check.

What is not shown

  • Whether it produces a real downloadable resume file is not visible publicly, and that is the exact line this quest drew.
  • It is not clear the flow handles the next job description as easily as the first — reusability is what separates a tool from an artefact.

Take this awayUseful as a reference for the matching layer — the part worth pressure-testing in your own version is whether the output is genuinely sendable.


Why this quest matters

The output format is the product. A resume that only lives in a chat window can't be sent to a recruiter — forcing a real PDF is what turns a nice answer into a tool someone would actually use.

What separated the strongest builds

Across the 29 builds we could open for this quest, the same three or four things kept deciding whether one landed. Useful whether you are judging this one or attempting your own.

A finished file, not a chat answer

Something you could attach to an application: a formatted, downloadable PDF. The brief ruled out anything that only ever prints text into a chat window.

Matching that has actually read the JD

Responding to that specific posting's language and priorities and reordering real experience — as opposed to sprinkling its keywords into the same resume.

It survives the second job description

A pipeline you can run again on Monday, not one artful manual edit dressed up as a tool.

No numeric scores are published here. These pages are written reads of what each builder shipped — the build is the point, not a mark out of a hundred.

More from Shohan

Quest 1Quest 2Quest 3Quest 4Quest 5Quest 6Quest 7
← Back to Shohan's portfolio