Remote Job Search Tracker (2-Page Printable)

Page one is a 12-row log for remote applications: company, role, date, a stage circle for where things stand, and a follow-up date. Page two rolls the rows up: a pipeline count by stage, a weekly goal you set yourself, four opinion tips, and a small interview-prep box. Print both pages, or copy the tables into a spreadsheet; the columns map one to one.

The stages: applied, screen, interview, offer

Each log row has four circles. Circle the one matching the stage the application is in right now:

Applied	Sent. No reply yet.
Screen	A recruiter or hiring-manager call is booked or done.
Interview	Live rounds beyond the screen: team, technical, or final.
Offer	Terms are on the table. The row stops here; accepting is outside this tracker.

When an application moves, cross out the old circle and mark the new one. One circle per row, the current state, not the history.

Page 1 — application log

Company	Remote role	Date	Stage applied / screen / interview / offer	Follow-up on
Northwind Ledger	Support Engineer	2026-09-08	●○○○applied	2026-09-15
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○
			○○○○

The first row is an example with a made-up company: applied Sep 8, follow-up set for Sep 15 if there's no reply. The eleven rows under it are yours. The company column is a write-in: this page stays neutral about which companies you target.

Page 2 — pipeline, weekly goal, prep

Stage pipeline

Once a week, count your log rows by stage and write the number in. Five slots so you can add one stage of your own:

Stage	Count
Applied	write-in
Screen	write-in
Interview	write-in
Offer	write-in
	write-in

Counts answer one question, where the volume sits this week. An all-applied pipeline reads very differently from one with rows past screen, and the table shows which of the two you have.

Weekly goal

This week I will send new applications.

Four opinion tips

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

Follow up once, then leave the row alone. One polite nudge after the follow-up date. A second and third message rarely pull a reply forward, and the time goes further into the next application.
Set the follow-up date when you apply, not when you remember. Same day, while the posting is still open in a tab. A date written later is a guess; one written now is a plan.
Filter remote postings twice. Once on the words "remote", once on the location line. Some listings say remote and then name a timezone or a country in the small print. Thirty seconds of checking beats a wasted row.
Count weekly, decide monthly. Weekly counts move too much to steer by. Four or five of them in a row show a pattern worth acting on: where rows stall, and which stage needs volume.

Interview-prep box

Before any live round, write one line for each:

The work I'd be doing, in my own words:

One thing I built or shipped that connects to it:

One question I have about the team or the role:

Twelve rows fill fast once the pipeline is real, and this tracker doesn't supply the applications themselves. The Web3 Remote Jobs & Hiring Database 2026 is where the next rows come from: 147 crypto companies with live remote-hiring signals, each with a careers URL that was HTTP-checked on 2026-09-05, plus remote policy and open-role counts, in CSV and Markdown.

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

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