GDG Coding Jams
Build with AI. Together.
Share
← Back to the jams
Track 07

BulletProof

Paste resume + paste job → tailored bullets.

✅ Drop-in friendly2-hour jamShips in 45 min
💼
The demo

What it looks like when it’s working

In the room · 45 minutes

What you’ll build

Two text boxes — paste resume text, paste job posting text. One button. AI returns tailored resume bullets, ready to copy. No PDF parsing, no cover letter, no interview prep, no Word export.

The moment it clicks

This is actually better than what I'd write.

Things to think about

While you build

  • 'Not building' is the lesson today. Skip the cover letter, the PDF parsing, the ATS scoring — every one of those is the polished version.
  • Paste the whole job posting, not just the title. The full text is half the prompt's quality.
  • Read the bullets the AI returns out loud. If you wouldn't actually say them in an interview, your prompt needs work — not the AI.
  • Ruthless focus is the personality. What you refuse to build is what makes this ship in 45 minutes.
The 2-hour Jam rhythm

How the night flows

Every Coding Jam follows the same five-phase shape. Talking is short, building is long.

  1. 0:00 – 0:15
    Intro

    Grab a name tag and a slice, say hello to the instructor, and meet the people either side of you — you'll be asking them things later, so it pays to know their names now. Low pressure, high creativity, ship something messy. Then a quick word on what the room is building tonight, and you're off.

  2. 0:15 – 0:30
    Credits & setup

    The instructor shares the Google Cloud credits with the room. Everyone gets their environment ready — whichever tool they brought. Nobody should be installing anything once the build starts.

  3. 0:30 – 1:35
    Build

    Heads down, and enjoy it — this is the part everyone came for. The agent does the typing; you decide what it's making. Ask the room when you get stuck; someone two seats away hit the same wall ten minutes ago. Want more structure? The codelab walks the spec-driven route — Setup → Plan → Review → Build → API → Verify — but nobody has to follow it.

  4. 1:35 – 2:00
    Share & submit

    Show the room what you made — two minutes, screen-shared from your seat. Half-finished is welcome; the wobbly ones are usually the most interesting. Say what surprised you along the way, and cheer for everyone else while you're at it. Then submit your build before you leave. This is the one thing not to skip — it's what puts your name and your chapter on the showcase, and it takes about two minutes.

Polished version pulls in

Where to take it after the jam

The 45-minute build is the win in the room. These are the ideas you can pull in over the next week — your homework isn’t homework, it’s the polished version.

  • Match score + missing keywords
  • PDF parsing for resume input
  • Cover letter generator
  • Interview question generator
  • Networking message writer
  • Application tracker
  • ATS scoring
If you get stuck

Open one of these in the starter — safety nets, not requirements.

  • context/long-context-handling.md
  • context/text-diff-pattern.md
Pick another track

All independent — start anywhere.

See all jams →