Stage 05 of 12 — The Search
The Search
The Job Pursuit Operating System. Every role you’re tracking moves through 7 steps. Gate before effort — no deep work until hard constraints pass.
~4 min read
TL;DR
- —How to run a structured job search — not spray-and-pray applications
- —The difference between a target list and a pipeline, and why you need both
- —Skim if: you already have multiple active conversations with target employers
Gate before effort
No deep work until hard constraints (visa, comp floor, location) are confirmed to pass.
Evidence over claims
Every application assertion maps to a specific story with proof.
Value before ask
Network is contribution-first. Give before you ask for introductions.
▶▼JPOS step gates — what needs to be true to advance each step
Your pipeline is empty.
Add a role above. It moves through 7 steps — Discovery, Qualify, Research, Network, Applied, Interview, Offer. Everything is saved to your browser only. No account needed.
Tip: Export to JSON regularly so you don’t lose your pipeline if you clear browser data.
Weekly cadence
Mon
Pipeline triage. Step gates. Planning.
Tue
Research and positioning artifacts.
Wed
Outreach and conversations.
Thu
Applications and interview execution.
Fri
Follow-ups, metrics, PEDL updates.
PEDL after every stage close
Win or lose — capture and apply lessons. The search that doesn’t debrief is just chaos with paperwork.
What was your goal and strategy for this role?
What actually happened at each stage?
Two things that worked. Two things to change.
One thing you carry into the next role cycle.
Your pipeline data is stored locally in your browser. Nothing leaves your device.
Where people stall here
Building a perfect tracking system instead of applying. The pipeline is a tool, not a goal. Applications create information. Nothing else does.