LinkedIn Professional Network  ·  View 04 of 30  ·  2 · People and journeys

Journey — Job Seeker, Search to Status

The journey with the most at stake for the member, and the silence after applying that decides how applications are stored.

Editable source SVG draw.io All views
Job seeker mobile-first, actively looking Goal — Apply to a role that fits in minutes, not an evening Trigger — A job alert, or a bad week at the current job Done when — Knows, without asking, where each application stands 1 · Look search + alerts 2 · Decide 3 · Apply ◆ moment of truth 4 · Wait days to weeks 5 · Hear back ◆ moment of truth What they do Searches a role Opens a job alert Reads the listing Sees who they know Taps Easy Apply Attaches a resume Checks My Jobs Reads the update Where Jobs search app + web Job page Apply sheet My Jobs Push · email How it feels Hopeful Neutral Anxious Behind the glass Galene jobs vertical Job recs · Venice Jobs service Graph: who you know Applications · MySQL Ambry resume Status events ATC notifications Where it hurts Closed jobs still listed Double submit on retry Silence after applying What would fix it De-index on close Warm intro via graph Idempotency key Status pushed on change How we know Search p95 ≤ 300 ms Save rate Apply success 99.95% Time to first status Reply within 14 days User Journey — Job Seeker, Search to Status The trough is the wait: an application with no status is a structural gap, not a UX one. v 1.0 · owner Product + Enterprise Architecture · date 2026-09

What the trough decides

  • Application state lives in MySQL behind a state machine, and every transition emits an event: silence is designed out rather than apologised for
  • Mobile clients retry on flaky networks, so apply takes an Idempotency-Key that is unique in the table
  • A closed job leaves Galene's live buffer within seconds through change capture, not at the next weekly base-index rebuild

Numbers

  • Search p95 under 300 ms; apply success at least 99.95%
  • Status change to notification created in under 1 s, delivered on the member's chosen channel
  • Resume uploaded on a signed URL, straight to Ambry

Where the set answers it

  • Search: view 19 · the application record: view 13
  • Apply under failure: view 26 · status to the member: view 20
  • Who may see an application: view 29
◀  Actors and Their Core Journeys All views Journey — Creator, Draft to Reach  ▶
Solution Architecture v1.0 · LinkedIn's own stack in LinkedIn-run colos · Enterprise Architecture · 2026-0904-journey-job-seeker