JobShifu/Job tracker

Job tracker Updated 2026-08-27

Know which resume got the interview

Every application tracked with the exact version you sent, so your pipeline tells you something you can act on.

JobShifu tracks every application from saved through applied, callback, interviewing and offer, and pins the exact resume version you sent with each one. Not the filename. The immutable document, so when a callback lands three weeks later you can open precisely what produced it.

Applications made through the browser extension log themselves, because the extension already knows which job you are on and which document you attached. That removes the step everyone skips.

The board in My Jobs. Drag a card as you go, and the resume you sent rides with it.

Why not just use a spreadsheet?

Spreadsheets work right up until they do not, and they fail in a predictable way.

A tracking sheet depends on you updating it at the precise moment you least want to: immediately after submitting an application, when you are tired and the next posting is already open. Miss it three times and the sheet becomes a partial record. A partial record is one you stop trusting, so you stop consulting it, so you stop updating it. Most job-search spreadsheets die in the third week.

But the deeper problem is not discipline. It is that a spreadsheet cannot answer the question you will most want answered.

Six weeks in, the useful question is not "where did I apply?" It is "what was I doing differently in the applications that worked?"

A spreadsheet stores a filename, at best. And resume_final_v3.pdf has been overwritten twice since you sent it.

The version you sent is the version you keep

Every application pins the exact resume version submitted, as an immutable record.

This is the single most useful thing a tracker can do, and it is why the tracker is worth having attached to the tailoring rather than living in a separate tool. Your application history stops being a list of companies that did not reply and becomes evidence about what works for you specifically.

When a recruiter calls about a job you applied for five weeks ago, you open the document they are holding. When three callbacks arrive in a month, you can look at what those three resumes had in common. Neither is possible if the record is a filename.

The stages, and why ghosting gets its own

Applications move through draft, applied, callback, interviewing and offer, then close in one of four ways.

Closed as	What it tells you
Rejected	They read it and said no. Where it happened in the pipeline is the signal.
Ghosted	Silence. Usually means the application was never really read.
Withdrawn	You stopped it. Not a failure, and not counted as one.
Accepted	The win state. Never styled as just another closed row.

Most trackers collapse the first two into "closed" or "no response," and that single decision destroys the most diagnostic number in the funnel.

Consider two people with identical rejection counts. The first is rejected after three interview rounds, repeatedly. Their resume is working; something later is not, and no amount of resume editing will help. The second hears nothing at all, forty times. Their applications are not being read, which is a resume, targeting or timing problem, and interview practice is wasted effort.

Same "closed" count. Opposite fixes. JobShifu reports rejection rate and ghost rate separately so you can tell which one you are.

How an application closes

Four endings, and two of them mean opposite things

Most trackers collapse the first two into “closed” or “no response”. That single decision throws away what the funnel was for.

Rejected

They read it and said no. Where in the pipeline it happened is the signal.

Ghosted

Silence. Usually means the application was never really read, which is a completely different problem from being read and turned down.

Withdrawn

You stopped it. Not a failure, and not counted as one.

Accepted

The win state. Never styled as just another closed row.

Two people with identical rejection counts can need opposite advice. Rejected after three interview rounds, repeatedly: the resume is working and something later is not. Silence forty times over: the applications are not being read, and editing the resume harder will not change that.

What the funnel actually tells you

Because every stage transition is timestamped, the pipeline reads as a diagnosis rather than a scoreboard.

Applications, but no callbacks. The document or the targeting. Check Fit before blaming the resume, since applying to jobs you are a poor match for produces exactly this shape.
Callbacks, but no interviews. Something between screen and interview. Often the screening questions or the phone screen rather than the resume.
Interviews, but no offers. Not a resume problem at all. The resume did its job. This is where preparation is the actual lever.

The point of the distinction is that these three states feel identical from the inside. All of them feel like the job hunt is not working, and all of them tempt you into rewriting your resume again, which helps in precisely one of the three cases.

Saving the same job twice

JobShifu recognises it and keeps one entry.

You find a role on a job board, then again on the company's careers page, then the extension sees it when you open the application. That is three encounters with one job. They resolve into a single record through a ladder of signals: the applicant tracking system's own identifier first, then the canonical URL, then the content itself.

When the match is only probable, it asks or warns rather than merging. Two genuinely different roles at the same company, with similar titles, are a real thing, and silently combining them would lose an application you actually made. Distinct identifiers at one organisation are treated as definitively different.

You can keep up to 1,000 live jobs, which is more than any real job hunt needs and is there so a stuck import cannot quietly fill your account.

Frequently asked questions

Why not just track job applications in a spreadsheet?

A spreadsheet works right up until it does not, and it fails in a predictable way: it depends on you updating it at the exact moment you least want to, which is straight after submitting an application when you are tired. Two weeks later the sheet is a partial record you no longer trust, so you stop consulting it, so you stop updating it.

The deeper problem is that a spreadsheet cannot tell you which resume you sent. It stores a filename at best, and the file has been overwritten since.

Does JobShifu track which resume I sent to which job?

Yes, and it pins the exact immutable version rather than a filename. When a callback arrives you can open the specific document that produced it, not the file that currently happens to sit at that path.

This is the single most useful thing a tracker can do, because it turns your application history into evidence about what actually works for you instead of a list of companies that did not reply.

What are the application stages?

Draft, applied, callback, interviewing, offer, and then four ways it can close: rejected, ghosted, withdrawn, accepted.

Ghosted is kept deliberately separate from rejected, because they are different failures with different fixes, and accepted is the win state and never styled as a closed-and-done failure alongside the others.

Why does JobShifu separate being ghosted from being rejected?

Because they point at different problems. A rejection after three interview rounds means your resume worked and something later did not. Silence after applying means the application never got read, which is a resume, targeting or timing problem.

Merge them into one "closed" bucket, as most trackers do, and the single most diagnostic number in the whole funnel disappears. JobShifu reports rejection rate and ghost rate separately for that reason.

Does the tracker update itself when I apply?

When you apply through the browser extension, the application is logged as you go, because the extension already knows which job you are on and which document you attached. That removes the exact step people skip.

Applications made outside the extension can be added manually, and JobShifu will still pin the resume version if you tailored one for that job.

What happens if I save the same job twice?

JobShifu recognises it. Saving the same posting from a job board and from the company's own careers page produces one entry rather than two, resolved through a ladder of increasingly weak signals: the applicant tracking system's own id first, then the canonical URL, then content.

When the match is only probable, it asks or warns rather than silently merging two records that might be different roles at the same company.

Stop losing track in week three.

Every application, every version, every outcome. Recorded as you go rather than remembered afterwards.

Get started free How it works