Why a tracker matters
Candidates running more than 4 or 5 active UX processes hit the same wall: they start losing track. Confusing recruiters' names. Missing follow-up windows. Forgetting which stage a process is at. Sending the wrong cover note. Each slip is small; together they degrade conversion at exactly the moment when conversion matters most.
A simple tracker resolves this. The mechanics aren't complex; the discipline is in updating it consistently. The candidates who run 10+ processes successfully are usually the candidates who treat the tracker as a 5-minute daily ritual, not a 90-minute weekly catch-up.
The eight fields that matter
Eight columns that cover most processes
- Company. Just the name.
- Role title. The advertised title, not your interpretation.
- Salary band. The advertised band, or the band you established in the recruiter screen.
- Application date. When you submitted.
- Current stage. Standardised across all rows (see "Stages worth recording").
- Next action. What you need to do next, written as a verb.
- Next action due. Date. Drives the weekly review.
- Recruiter contact. Name and email, so you don't have to dig through inboxes.
Optional columns that help: priority rating (1–5), application source (LinkedIn / referral / direct), notes column for round-specific detail (interviewer names, scheduling friction, specific things they emphasised).
Stages worth recording
Standardised stage names matter — they let the candidate see at a glance how the pipeline is shaped. Eight stages cover most processes:
- Applied — submitted, no response yet.
- Recruiter screen scheduled — call booked but not yet had.
- Recruiter screen done — call completed, waiting for next step.
- Hiring manager scheduled — next round booked.
- Hiring manager done — round completed.
- Final stage — portfolio walkthrough, take-home, panel, executive, or any final-round combination.
- Offer received — verbal or written.
- Closed — either withdrawn, rejected, or declined.
For candidates running many processes, colour-coding the stages (warm tones for active early-stage, cool tones for late-stage, grey for closed) gives a fast visual read on pipeline health.
The weekly cadence
The operational rhythm that works: 5 minutes per day for updates as things happen; 30 minutes once a week for a structured pipeline review. Sunday evening or Monday morning are the most common review slots — they set the week's actions.
Weekly review questions: what processes need a follow-up this week? What processes have I lost track of (no contact in 10+ days)? Which processes am I no longer interested in and should formally withdraw from? What new applications should I add this week to maintain volume?
The withdrawal question is under-used. Candidates often let processes drift rather than formally withdrawing. Formal withdrawal is professional, takes 2 minutes, and protects future relationships with recruiters and hiring managers. "Thanks for the time so far. I've decided to focus on other opportunities and won't be continuing the process. I hope our paths cross again." is sufficient.
Follow-up patterns
Two follow-up patterns work consistently.
The thank-you note. Short note within 24 hours of each interview, addressed to whoever ran the round. Two paragraphs maximum. Reference one specific thing from the conversation. Don't restate the case study or repeat the interview itself.
The light nudge. If you haven't heard back within the timeline the recruiter named, one polite nudge after 5 to 7 working days is reasonable. "Hello [recruiter], I hope you're well. Just checking in on the timeline for the next steps you mentioned. Happy to wait if more time is needed — just want to make sure I'm not missing anything." Light, specific, not desperate.
Patterns that don't work: multiple follow-ups in short succession; asking for decisions on the company's behalf; expressing disappointment when timelines slip; trying to add urgency by mentioning competing offers when none exist. Each of these damages the application and is recognised quickly.
How many to run at once
Active applications should sit between 5 and 15. Below 5, single-process delays leave the candidate exposed and can stretch a search by months. Above 15, candidates start slipping on preparation depth and follow-up cadence, which reduces conversion across the entire pipeline.
The right number within that range depends on response rate. Candidates with strong senior portfolios who get responses on 30–50% of applications can run 5 to 8 active processes. Candidates with junior portfolios or less-typical backgrounds, who get 5–15% response rates, often need to maintain 12 to 18 active applications to keep pipeline moving.
The application volume management is where preparation depth often suffers. A useful rule: never submit an application you don't have time to interview for at full preparation depth. Volume should be sustainable, not aspirational.
Tracker template
A simple spreadsheet template with the eight fields, the eight stages, conditional formatting for due dates, and a separate sheet for closed processes is enough. Google Sheets is the most common implementation; Notion works equally well; specialised job-tracking apps tend to add overhead without proportional benefit.
For the broader interview view that the tracker supports, see interview preparation guide. For the offer stage that follows successful pipelines, see salary negotiation guide. For the early-career career-side context, see how to get your first UX job. For UK market context, see UX designer salary UK. For portfolio-side preparation that sets up successful applications, see portfolio examples and case study examples. The full interview question reference is in UX interview questions.
Frequently asked questions
How many UX jobs should I apply to at once?
8 to 15 active applications at any one time, depending on response rate. More than 15 becomes hard to manage; fewer than 5 leaves the candidate exposed to single-process delays.
Should I follow up after a UX job interview?
Yes, but lightly. One thank-you note within 24 hours per round. Aggressive follow-up damages applications.
What should a UX job application tracker include?
Eight fields: company, role, salary band, application date, current stage, next action, next action due, recruiter contact. Optional: priority, source, notes.