The job application tracker
Every application, follow-up and interview in one place.
Almost everyone starts a job search with a spreadsheet and abandons it around application twenty. That's a real problem, because the moment you stop tracking is the moment your search stops improving — you lose the ability to tell why things aren't working, and every rejection becomes a mood rather than a data point.
Tracker replaces the spreadsheet with something built for the job: log each application with the company, role, date, the version of your resume you sent, and the contact if you have one. Move it through the pipeline as things progress — applied, screening, interview, offer, closed — and the board shows you the whole search at a glance rather than as a wall of rows you have to re-read.
The reason this matters more than it sounds is diagnosis. A job search is a funnel, and it breaks at exactly one place at a time. If you're sending applications and hearing nothing at all, the problem is upstream — targeting or your resume. If you're getting screens that don't convert to interviews, it's how you come across in that first conversation. If you're reaching interviews but not finals, it's interview skills. If you're reaching finals but not offers, it's fit or competition, and that's the stage where asking for feedback pays most. Those four diagnoses lead to completely different fixes, and without tracking you genuinely cannot tell them apart — which is why so many searches stall for months while the person works hard on the wrong thing.
Follow-ups are the other thing the spreadsheet always loses. One well-timed follow-up seven to ten days after applying is professional and occasionally decisive; three is a reason to stop considering you. Tracker keeps the dates so you send the first and not the third, and so a recruiter calling three weeks later doesn't catch you unable to remember which version of your story they read.
It also connects to the rest of your search rather than sitting in isolation. Applications captured by the browser extension can import straight in, so anything you autofill and submit is logged without retyping. Your profile, resume versions and answer bank are the same ones the other tools use, which means the record of what you sent is the actual thing you sent.
Everything is local-first: your pipeline lives in your browser, not in an account on someone's server, and there's no signup to start. If you want the wider system around it, the job search checklist covers the weekly rhythm this fits into, and this diagnostic explains how to read your funnel once you have a few weeks of data in it.
- ✓Pipeline board: applied → screening → interview → offer
- ✓Follow-up dates so you send one, not three
- ✓Import applications captured by the extension
- ✓Local-first, free, no signup
Why a spreadsheet fails once you are past twenty applications
Most job searches start with a spreadsheet: columns for company, role, date applied, status, contact person. It works for the first fifteen applications. By application twenty, the spreadsheet has become a wall of rows you have to scroll through to find anything, you have stopped updating it consistently, and you have lost the ability to tell why some applications convert to interviews and others vanish. The reason is not laziness—it is that a spreadsheet is not designed for a job search pipeline. A spreadsheet is a flat list that looks the same whether you have ten rows or three hundred. When you have thirty applications in different stages (some unanswered, some in screening, some in interview), a list is not a useful view. You need a pipeline view that shows you at a glance how many applications are stuck in each stage and which ones need your attention.
The moment you stop tracking is the moment your search stops improving. This sounds dramatic but it is measurable. A job search is a funnel that breaks at exactly one place at a time: either you are not getting interviews from applications, or you are getting interviews but they are not converting, or you are reaching later stages but not landing offers. Without data, you guess. You might spend weeks rehearsing interview answers when the real problem is that your resume is not strong enough to get you screened. You might tailor every cover letter when the real problem is that you are applying to jobs you are not qualified for. You might blame interview performance when the real problem is that your follow-up timing is bad and the company has already moved on. Each of these diagnoses has a different fix, and without tracking you genuinely cannot tell them apart.
A spreadsheet also loses data in tiny ways. You apply to a role, screenshot the job posting if you remember to, but a month later when the company calls, you cannot find the posting and do not remember what you said you were interested in. Or you update the status for one application and forget to update five others, so the view is stale and you do not know whether to follow up or not. Or you send two different versions of your resume to the same company by accident and have no record of which version is sitting in their inbox. A tracking system that is in front of you, not buried in a file, catches these small mistakes before they become interview surprises.
Reading your funnel to diagnose where your search is actually leaking
Once you have tracked twenty to thirty applications, you have data. Look at the numbers in each stage: applications sent, screening interviews scheduled, interviews conducted, offers received. Your funnel might look like this: 40 applications sent, 8 screening interviews, 4 real interviews, 1 offer. This tells a story. If your conversion rate from applied to screening is 20% (8 out of 40), that is reasonable. If your conversion from screening to interview is 50% (4 out of 8), that is good—you are telling a compelling story in the first conversation. If your conversion from interview to offer is 25% (1 out of 4), that is where the leak is. You are getting past the first screen and even to later-stage interviews, but something in those conversations is not resonating.
Different funnel shapes point to different fixes. If you are sending 40 applications and getting 2 screening interviews, your conversion is only 5%, and the problem is upstream—either your targeting (you are applying to jobs you are not qualified for), your resume (it is not passing ATS screening), or your cover letter (it is generic and does not signal fit). The fix here is to slow down, apply to fewer roles, and spend more time tailoring your resume to each role rather than mass-applying. If you are getting screening interviews but only a quarter convert to real interviews, the problem is how you come across in that first conversation. The fix is to rehearse your story, get feedback from friends or coaches, or record yourself and listen for filler words or unclear thinking.
If you are reaching later-stage interviews but not offers, the problem is usually fit or competition. You have passed the skills screen, which is good, but something in the conversation signals that you might not integrate well, or there is someone else competing for the role who seems safer or more aligned. Asking for feedback at this stage is worth doing even though most companies will not give you specifics—'Is there anything I could have clarified or any concern from the interview I could address?' sometimes surfaces something actionable. If the feedback is consistently 'you were great but we went with someone else,' the problem is not you, it is competition, and the fix is to apply to more roles and improve your odds rather than trying to win a single role where you are not the top choice.
Follow-up timing and keeping a record of what you actually sent
Follow-ups are a source of regret in job searches because people either do not do them or do them too many times. One follow-up seven to ten days after applying is professional, occasionally decisive, and a signal that you are serious. Two follow-ups cross into persistence that some people read as genuine interest and others read as slightly annoying. Three follow-ups is the point where you have moved from 'person following up' to 'person who does not take hints,' and most recruiters will have moved on. A tracking system that shows you the date you applied tells you exactly when seven days is up, so you send the follow-up on day eight instead of forgetting and sending it on day twenty-one. The timing matters because a follow-up right on schedule lands as professional diligence, whereas a late follow-up lands as 'I forgot about you and now I remembered.'
The other reason tracking matters is that it is the record of what you sent. A few weeks into your search, a recruiter calls: 'Hi, we are moving you to the next round of interviews for the engineering role you applied for in July. Are you still interested?' In that moment you might have applied to five engineering roles in July, and you cannot remember which company this is or what version of your resume they have. A tracking system tells you exactly which resume version, which job description, which specific role details, and when. This is not a small thing—if you described the role one way to the recruiter but your resume emphasises different skills, the interviewer will notice the inconsistency and assume you are either confused or applying to roles you do not understand.
A good tracking record also includes notes on why you applied. 'Found them through a recruiter intro from Sarah at Company B' or 'Applied cold because they are doing work in machine learning' or 'Was rejected before but am reapplying because the role changed.' These notes help you remember the story when the company calls, and they help you debug your strategy later. If you have notes that say you applied to companies doing X and you got zero interviews but applied to companies doing Y and got five interviews, that is a strong signal about where your skills and experience land in the market, and that is information that is worth having.
Frequently asked questions
How do I know when to follow up on a job application?
Follow up seven to ten days after you have applied. A tracker that logs the application date tells you exactly when that window is. One follow-up is professional and appropriate. A second follow-up can work if you have new relevant information, but a third signals you are not accepting the lack of response. Most recruiters treat two follow-ups as the ceiling.
Should I keep track of which version of my resume I sent to which company?
Yes. If a company calls to interview you three weeks later and you have sent five different resume versions to different companies, you need to know which one they received. A tracking system that logs which version you sent removes the guesswork. When the interviewer references something on your resume, you know exactly what they are looking at.
What should I track in a job application tracker?
At minimum: company name, role title, date applied, current status (applied, screening, interview, offer, closed), contact person if you have one, and date of last follow-up. Optionally add: the specific resume version sent, a link to the job posting, notes on why you applied, and interview feedback if you get any.
How do I use a tracker to figure out why my job search is not working?
Count the number of applications at each stage (sent, screening interview, real interview, offer). Your conversion rate from one stage to the next tells you where the leak is. If only 5% of applications convert to interviews, the problem is upstream (targeting or resume). If you get interviews but only 20% convert to offers, the problem is interview performance or fit.
Can a tracker help me remember what I told a company during a screening call?
Yes. Include notes from your screening call—what the recruiter asked, what you emphasised, what they seemed most interested in. When the company calls back for the next round, these notes remind you of the conversation so you stay consistent and can reference what you discussed before.
Part of Job search — 6 free tools in this set.
Part of JobStraight — the honest AI job-search platform. Runs in your browser; your data stays on your device.