Every morning used to look the same: scroll LinkedIn alerts → open a JD → tailor my resume → Easy Apply or an external form → repeat. Lots of context-switching, easy to miss steps, and hard to track what I already applied to.
So I documented the whole process in a resume + application workspace:
What the agent does
- Scans today’s LinkedIn job listings (Browser MCP)
- Saves each JD and scores fit against my base resume
- Tailors a truthful, JD-aligned resume (no invented experience)
- Exports a PDF and pre-fills Easy Apply / external forms
What I still do
- Review the tailored resume and fit score
- Answer role-specific questions
- Click Submit (by design — I stay in control)
What’s in the repo
-
base-resume.md— single source of truth -
RUNBOOK.md— step-by-step daily batch -
jobs/<company-role>/— JD, analysis, tailored resume, PDF -
applications.csv+ queue — no duplicate applies - Cursor rules so tailoring stays consistent every run
One prompt to start the day:
Run today's job application batch per RUNBOOK.md
It’s not “auto-apply everything.” It’s prep at machine speed, decisions at human speed — which is how I want to job search as a PM.
If you’re job hunting with Cursor, I’d start with a runbook + a base resume + a hard rule: never submit without you.
Shorter version (if you prefer punchy)
Job search loop, documented in Cursor:
Discover → extract JD → fit score → tailor resume → PDF → Easy Apply prep → I click Submit.
Everything lives in a workspace: base resume, per-job folders, application log, and a RUNBOOK.md the agent follows daily.
Semi-automated, not reckless — speed on prep, judgment on submit.
Top comments (0)