GDG Coding Jams
Build with AI. Together.
Share
← All tracks
Track

BulletProof

Paste a resume and a job posting, and get tailored bullets back.

2-hour jamBrief and starter repo includedWorks in both tools
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 export.

Follow the brief and the starter repo. The scope is fixed so it ships inside the build block.

“This is better than what I would have written.”

Where to take it after the jam

The polished version

Ideas to pull in over the week after the jam.

  • Match score and missing keywords
  • PDF parsing for resume input
  • Cover letter generator
  • Interview question generator
  • Application tracker
While you build

Things to keep in mind

  • What you refuse to build is the lesson. Skip the cover letter, the PDF parsing and the ATS scoring.
  • Paste the whole job posting, not just the title. The full text is half the prompt's quality.
  • Read the bullets out loud. If you would not say them in an interview, the prompt needs work.
Share your build →

Built something? Two minutes, and it lands in the showcase. Half-finished is fine.

The 2-hour jam rhythm

How the session flows

Every Coding Jam follows the same shape, whichever track the room takes.

  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.

Pick another track

All independent. Start anywhere.

See all tracks →