Job Application Tracker Printable (One-Page Log)

Twelve rows, one page, four status codes. Each row holds a company, a role, the date you applied, one circle for where the application stands, and a follow-up date. Print this page and fill it in by hand, or copy the table into a spreadsheet; the columns map one to one.

The status codes: A, I, R, O

AApplied. The application is out and nobody has replied yet.
IInterview. Any live conversation: phone screen, hiring manager call, final round.
RRejected. They said no, at whichever stage it happened.
OOther. You withdrew, the posting expired, the role was filled, or anything else the first three don't cover.

Circle exactly one code per row: the state the application is in right now. When it moves, cross out the old circle and mark the new one. The table answers one question, where each application stands today, so it keeps the current state rather than the full history.

The log

CompanyRoleAppliedStatus  A  I  R  OFollow-up on
Helio PayFrontend Engineer2026-09-08○●○○I2026-09-18
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○
 ○○○○

The first row is an example with a made-up company: applied Sep 8, in an interview now, follow-up set for Sep 18 if there's no reply. The eleven rows under it are yours.

Three tracking tips

These are opinions from running my own hunts this way, not rules.

  1. Log the application the same day you send it. In my experience the three details that go fuzzy fastest are the exact date, the role title as posted, and where you found it. Writing the row while the tab is still open takes a minute and saves all three.
  2. Put each follow-up date in a calendar you open daily. A date that lives only in this table gets checked when you happen to remember the table exists. A calendar entry pushes back at you. I use both, and the calendar is the one that has saved follow-ups for me.
  3. When a row turns R, write "closed" in its follow-up cell the same day. That way an empty follow-up cell means only one thing: the row is still live and owes you an answer. Blank cells that might mean anything are how pipelines quietly rot.

Weekly review: three questions

Once a week, read the table top to bottom and answer these in writing. Comparing answers week over week shows pipeline movement that a single glance won't.

  1. How many rows changed status this week, and in which direction did they move?
  2. Which follow-up dates have passed with no reply and no note written in the row?
  3. Where do the rows sit right now: mostly A, or spread across I and beyond?

About the R rows

R is a normal row type in this log. Every hunt that runs more than a few weeks collects them, at every stage.

One R is one decision, at one company, about one role, on one day. It says nothing about the other eleven rows.

A rejected row is also a finished row: it needs no follow-up date, and the attention it was holding goes back to the rows that are still open.

Twelve rows fill fast once the pipeline is real, and this log doesn't supply the applications themselves. The Web3 Remote Jobs & Hiring Database 2026 is where the next rows come from: 147 crypto companies hiring remote, each with a careers URL that was HTTP-checked on 2026-09-05, plus remote policy and open-role counts, in CSV and Markdown. When a row turns I, the interview follow-up template covers what to send. For a longer table with a day 3 / 10 / 21 cadence, see the printable job application tracker.

Get the Web3 Remote Jobs & Hiring Database — 147 companies →

CSV + Markdown, grouped by ecosystem. Personal and commercial use.