Skip to content
Nick Vidal

All work

Personal project · 2026 · Built with Claude, Notion, Google Drive, and Indeed

An AI job-search system that won't make things up

After 20 years in the Air Force, I had two decades of evaluations and no civilian resume that a recruiter, or their screening software, would understand. Applying everywhere wasn't working, and generic AI resume tools padded my experience with things I never did.

  1. 1Posting

    A job posting from Indeed, or pasted in

  2. 2Notion check

    Claude reads the Operating Manual and Search Playbook

  3. 3Assessment

    Can I compete? Would I enjoy it? Apply, Investigate, or Pass

  4. 4Resume

    Built only from the verified master resume

  5. 5Drive folder

    Saved to a folder for that job

  6. 6Tracker

    Logged and linked back in the job tracker

How a posting moves through the system. An illustration, with no real data.

What I built

A Claude project does the reading and drafting. The rules, the evidence, and the results live in Notion and Google Drive, where I can see and change them.

  • A Claude project connected to Notion, Google Drive, and Indeed through MCP.
  • A Notion Operating Manual that Claude reads at the start of every session: my preferences, the assessment workflow, resume rules, and an ATS template. The rules live in one place I can edit, not in a static prompt.
  • A job tracker that logs each posting with two separate ratings, "Can I compete?" and "Would I enjoy the work?", plus a recommendation: Apply, Investigate, or Pass.
  • Automatic tailored resumes, built only from a master resume of verified evidence, saved to a Drive folder per job and linked back to the tracker.
  • A Search Playbook where lessons from each posting (misleading titles, screening gates, travel traps) feed the next assessment.

Guardrails

  • No guessing: every fact about me must trace to the master resume or my own corrections; anything else is marked unknown.
  • Changes to the rules happen only after I approve them, with a dated change log.
  • OPSEC: sensitive military work is described in general terms only.

What testing caught

The first version wrote 4-page resumes that weren't ATS-friendly and assumed my retirement status instead of asking. I added an explicit no-guessing rule, a two-page ATS standard with a fixed template, a keyword check against each posting, and approval-only changes. The next resume came in at two pages with every claim traceable.

What I'm measuring

It's brand new, so there are no numbers yet. I'm tracking how many postings it assesses, how often it makes an honest Pass call on a role that looked right by title, and how many tailored resumes it builds and files. I'll put real numbers here once there are some.

Give it away

A step-by-step guide with pictures. About 30 minutes, no tech background needed.

Download the free kit (PDF)