Three weeks into a search, it is easy to lose track of how many jobs you have applied to, which recruiter promised to call back, and which version of your resume went where. That is when follow-ups get missed and interviews start to blur together. A plain spreadsheet fixes this in an evening, and it gives you the numbers to see which part of your search is not working.
Columns that earn their place
A spreadsheet beats a notes app here because you can sort, filter, and count. Use one row per application, including roles where a recruiter approached you first, with these columns:
| Column | Example | Why it matters |
|---|---|---|
| Company and role | Company A, Backend Engineer II | The basics |
| Link and job ID | Official posting address and requisition number | Recruiters ask for the ID, and postings disappear |
| Source | Job board, referral, recruiter outreach, careers page | Shows which channels produce replies |
| Date applied | 6 Oct | Sets your follow-up timing |
| Resume version | backend-v3 | Shows which version gets responses |
| Contact | Recruiter or referrer, and how to reach them | Tells you who to follow up with |
| Stage | Applied, Screen, Technical, Final, Offer, Closed | Feeds your funnel numbers |
| Next action and date | Follow up with recruiter, 14 Oct | The column you sort by every morning |
| Notes | Asked about notice period; pay structure discussed | Context for the next conversation |
Paste the full job description into the row, or a linked document, when you apply. Postings can vanish before your first interview, and their exact wording is what you will prepare from.
Stages, and what moves an application between them
Keep the stages few, and define each by an event rather than a feeling:
- Saved: you intend to apply. Give it a date or delete it.
- Applied: the application is submitted.
- Screen: a recruiter or HR call is booked or done.
- Technical: any online assessment, take-home task, or technical interview.
- Final: hiring manager, HR, or final-round conversations.
- Offer: a written offer is in hand.
- Closed: rejected, withdrawn, or no response, always with the reason and the date.
The next-action column is what makes a tracker useful rather than a record of disappointment. Every open row needs one, even if it is only “close as no response on 30 October”. Sort by that date each morning and you have the day’s to-do list. Keep closed rows instead of deleting them; they are the data for everything below.
Measure your funnel and find the leak
Each week, update four counts: applications sent, responses (any human reply or screening call), interviews, and offers. Every few weeks, look at how many applications make it from each step to the next. Ignore conversion rates quoted online, which mix different roles, markets, and definitions; compare with your own earlier weeks instead, and wait until you have a few dozen applications before reading much into the ratios.
| Where it leaks | Likely causes | What to change |
|---|---|---|
| Applications get no response | Wrong level or role family; must-haves not visible in the top half of the resume; applying late; location mismatches | Tighten targeting, rework the top of the resume, apply within a day or two, ask for referrals |
| Screens do not lead to technical rounds | Notice period, location, or pay expectations out of range; a vague account of your current work | Prepare a two-minute walkthrough of your role, and be clear early about notice and expectations |
| Technical rounds do not lead to final rounds | Gaps in coding, system design, or fundamentals | Find the pattern in your interview notes and follow a structured preparation plan |
| Final rounds do not lead to offers | Thin examples of ownership, unclear motivation, or a stronger candidate late in the process | Prepare specific stories from your work, and ask the recruiter for feedback |
Fix the earliest leak first, because better interview preparation cannot help if applications are not turning into screens. For example, if forty applications produced two replies, rework your targeting and resume before you practise more interview questions; if eight screening calls produced one technical round, look hard at how those calls went, starting with what you said about notice period and expectations.
When and how to follow up
A follow-up works when it goes to a named person, gives them something easy to act on, and arrives after a reasonable wait:
- Applied through a portal, no contact: do not chase. Put the effort into finding a referral instead.
- Applied with a referral or a recruiter contact: follow up once after about a week, and ask your referrer to check the status if nothing moves.
- After a screen or interview: ask at the end of the call when you should expect to hear back. If that date passes, follow up one or two working days later.
- After a final round: the same, and mention another process nearing an offer if, and only if, it is true.
Three sample messages, short enough to read on a phone. The names and details are examples.
After applying, to a recruiter you have been in touch with: “Hi Priya, I applied for the Backend Engineer II role (job ID 48213) on 6 October. I have spent two years running Kafka consumers for order processing, which lines up with the event-driven work in the posting. Happy to send anything that helps with screening.”
After an interview: “Thank you for your time today, Arjun. I kept thinking about the duplicate-webhook question: rather than checking for an existing event in code before inserting, I would put a unique constraint on the event ID, since two retries can pass that check at the same moment. Looking forward to hearing about next steps by Friday, as you mentioned.”
After the promised date passes (keep the last sentence only if it is true): “Hi Neha, following up on my final round for the SDE II role on 14 October. You mentioned a decision within a week; is there an update on timing? I have another process nearing an offer, so a rough date would help me plan.”
A thank-you note will not rescue a weak round, but a specific one reminds the panel who you are and shows you kept thinking about the problem.
When the employer goes silent
Silence after an application, often called ghosting, is normal and rarely personal: the role went on hold, was filled internally or by an earlier candidate, or the recruiter moved on. Silence after interviews is ruder, but common enough to plan for:
- Send one follow-up after the promised date, as above.
- If nothing comes back, send a shorter one a week later asking if you should consider the role closed, for example: “If the role has closed or moved ahead, no problem at all; a one-line reply would help me plan.”
- Then mark the row “Closed: no response” with the date, and stop.
Do not escalate across channels by calling personal numbers or messaging every interviewer, and do not send an angry message. Recruiters move between companies and remember candidates; the same person may bring you a better role next year. If silence keeps happening at the same stage, treat it as a funnel signal rather than a verdict on you, and see handling rejection in a long job search.
Interview notes that pay off later
Write notes within an hour of each round, while you still remember the questions. Keep them in the tracker row or a linked document:
- Interviewers’ names and roles, and what they said about the team and its problems.
- Every question you were asked, with a line on how you answered.
- Where you struggled, and the better answer you worked out afterwards.
- Anything said about notice period, joining date, pay structure, or work mode.
- The next step and the date you were given.
These notes do three jobs. They prepare you for later rounds at the same company, which often build on earlier ones. Read across companies, they show which topics keep catching you out, and that becomes your preparation list. At offer stage, they remind you what was said about pay structure, notice buyouts, and joining dates when you negotiate the offer.
Set it up tonight
- Create a spreadsheet with the columns above and a drop-down list for the stage.
- Add every application from the last month you can remember, with your best guess at the dates.
- Give every open row a next action and a date.
- Close anything older than a month with no reply as “no response”.
- Book a recurring fifteen-minute slot each week to update the counts and choose one thing to change.