Job Offer Process Map

A job search run as a process: two phases, five lanes, and a gate with two keys at every interview round.

Process design · A working system

Job Offer Process Map

Two phases, five lanes. Application runs every day and has one gate, owned by the candidate. Interview is triggered by an invite and repeats once per round, and every gate has two keys: the hiring side’s and the candidate’s.

Frame

Stage-GateStructure. Stages hold the work, gates hold the decisions. Outcomes: go, hold, kill, recycle.
BPMN swimlanesNotation. Lanes show who does each step; crossing a lane is a handoff.
PDCAThe round loop. Prep is Plan, interview is Do, retrospective is Check, next prep is Act.
event gate activity conditional or loop

Phase 1: Application

Daily cadence. One gate, owned by the candidate. Ends at the handoff to Interview.

On a phone, swipe the diagram sideways. The same steps are listed below.

  1. GateG0 readiness (Candidate). Entry criteria: master resume, STAR library, rule layer.
  2. EventDaily run (scheduled). Timer start.
  3. Collect (scheduled). Job boards and employer career sites.
  4. Score and report (scheduled). Ranked digest emailed.
  5. GateG1 disposition (Candidate). Go = Create. Hold = Pass, back to the resurfacing board. Kill = Decline, with a reason: title too high, pay too low, or pay doesn't fit the level.
  6. Tailor (Claude). Resume, cover letter, free-text answers.
  7. Submit (Candidate). On the employer's own board, never an aggregator.
  8. EventApplication submitted. Handoff to Interview.

Phase 2: Interview

Event-driven. The dashed frame is one round and repeats. Each round ends at a dual-key gate.

  1. EventInvite (recruiter). Message event, picked up by the email monitor.
  2. Schedule (Candidate). Accept, share availability.
  3. Prep docs (Claude). Plan: prep doc to read before, call doc open during.
  4. Interview (Candidate with the recruiter on the screener, the hiring side after that). Do: recorded with consent, transcribed. Portfolio walk in hiring manager and panel rounds, never the screener. Confirm the timeline before hanging up.
  5. Retrospective (Claude). Check: what landed, what to cut, what they were hanging on.
  6. GateBuild check (Candidate). Asked every round. On a yes, Claude builds it and it ships to the hiring side, where it can inform their decision. On a no, the round goes straight to the gate.
  7. GateDual-key gate. Hiring side: advance or reject, after a wait. Candidate: continue or withdraw, based on their burning questions.
  8. EventWithdraw. The candidate turns the key: the process ends on the candidate's side.
  9. Next round. Act: back to prep with what the retrospective found.
  10. EventOffer. Exits to negotiation and the accept/decline decision, both out of scope.
  11. EventReject, then Follow-up: warm email, ship any build in progress.
  12. EventRecycle. A new invite re-enters Phase 2 directly and skips Application.

Not drawn: the timer event when a promised timeline passes, which gives a legitimate reason to make contact again.

Build decision rule

Must-meet
An application exists. Someone on their side has named a problem in their own words. A plan-shaped answer can ship before the next gate.
Should-meet
The problem was confirmed when the candidate asked about it. It touches something on the resume, such as governance. It's a later round.
Backstop
At least one build per process. If none has fired by the last known round, force one.
Ship rule
Confirmed: ship later, in their language. Not confirmed: ship it anyway, framed as "this might not be it."

Vocabulary

Working term Standard term Frame
Stage 1 / Stage 2 Phase Stage-Gate
Interview round Stage Stage-Gate
Pass/fail after a round Gate, gatekeeper Stage-Gate
Create / Pass / Decline Go / Hold / Kill Stage-Gate
"Is this the build?" Gate criteria Stage-Gate
False terminal, reopened role Recycle, re-entry point Stage-Gate
Invite, rejection Message event BPMN
Missed timeline Timer event BPMN
Lies dormant Wait state BPMN
Build fires at some gate Conditional activity BPMN
Offer / decline End event BPMN
Prep doc, call doc, build Deliverable PM
Transcript Artifact PM
Daily run vs. invite-driven Cadence vs. event-driven Ops
Lock Baseline PM
Flag Parking lot, backlog PM / Agile
Discussed, not locked Open issue PM

Terms

JD
Job description: the employer's posting for the role.
ATS
Applicant tracking system: the employer's hiring software, which parses submitted resumes. Different systems parse the same resume differently.
Master resume
A long superset of every past role and result. Each tailored resume is cut down from it; nothing is written fresh.
STAR library
A collection of past-work stories in Situation, Task, Action, Result form, reused across resumes, cover letters, application answers and interviews.
Rule layer
The written rules for tailoring: what to claim, what not to claim, what never to do. Gaps are stated, never glossed.
Resurfacing board
Where held postings wait to be reconsidered on a later day.
Build
A piece of work made for one employer's named problem, usually a plan for how to solve it rather than a chart.
Portfolio walk
A short live screen-share of past builds during a hiring manager or panel interview. Never on the screener.

Open questions

  • Take-home / work-sample gate
  • Negotiation workstream
  • G1 go criteria (kill criteria are written; go criteria are not)
  • Resume length as a dial
  • ATS-aware formatting
Provenance
Process model v0, locked 2026-09-23. The source of truth is a Mermaid file, checked node by node and edge by edge against a written spec; this page is its rendered view. The build decision rule is inferred from past builds and accepted as a draft.