Building a job search system that makes progress visible
A Notion job tracker I built for my own search and still use. One database, six views, five formulas and three rollups count the effort for me, so on a low-motivation day I can open it and see proof that something is happening.
The real problem isn't disorganization, it's invisible progress
Fragmented information
Details live in email, a spreadsheet, open browser tabs and mental notes. Nothing adds up to one picture.
Invisible progress
With no proof that effort turns into movement, the brain concludes nothing is happening. For people with ADHD or anxiety that means constant stress and real missed opportunities.
Manual overhead, then abandonment
Remembering what to do next is its own job. Complex trackers feel like homework, so they get dropped exactly when they are needed most.
| Source | Info | Status | Days | Next |
|---|---|---|---|---|
| Sheet | Acme Corp, PM role | Applied? | ??? | ??? |
| Reply from TechCo recruiter | Somewhere | 14? | Check inbox | |
| Tabs | DataFlow, bookmarked listing | Not applied | — | Apply? |
| Notes | Mental note: follow up w/ Sarah | Unknown | 21? | Remember? |
| Meridian Labs, interview invite? | Buried | 7? | Check spam | |
| Tabs | 3 open job listings | Unsaved | — | Don't close |
| Company | Position | Status | Days | Flag |
|---|---|---|---|---|
| Acme Corp | Product Manager | Interviewing | 8 | ✓ On track |
| TechCo | Operations Lead | Waiting | 16 | ⚠ Follow up |
| DataFlow | Systems Designer | Applied | 3 | ✓ Recent |
| Meridian Labs | Ops Analyst | Waiting | 22 | ⚠ Follow up |
| Brightpath | Project Coordinator | Offer | 31 | ★ Received |
| Nova Systems | Business Ops | Applied | 1 | ✓ New |
Left: how my search looked before. Right: the same search as one Notion database. Sample data, fictional companies.
Designing for emotional usability, not just organization
What I looked at
My own job search behavior, and conversations with other job seekers about where their trackers broke down.
The finding
Visibility drives motivation more than organization ever could. People who could see their application count reported higher satisfaction. Status clarity matters more than detail.
Two rules that followed
Anything that needs a manual tally gets abandoned, so every number must be automatic. And the system must tolerate gaps: no required fields, no shame for a week off.
| Why existing trackers fail | What happens |
|---|---|
| Manual maintenance | Breaks down the moment motivation dips |
| Fragmentation | More places to check means more stress |
| Complex pipelines | Hard to scan, so they stop being looked at |
| No visibility | No satisfaction, so no reason to come back |
| Inconsistent use | Data gaps that make the numbers feel untrue |
| Design principle | In this system |
|---|---|
| Single source of truth | All job search information in one place, tracked automatically |
| Visibility infrastructure | Automated counters that are tangible evidence of effort |
| Emotional usability | Built to be opened on a low-motivation day |
| Status-driven views | The database organizes itself around application state |
| Cognitive scaffolding | Clear next actions, obvious organization, visible progress |
One database, 15 properties, zero friction
Identification
Company, position, status, source, salary range, location.
Dates
Application date, follow-up date, last contact, interview date.
Formulas
Days Since Application counts the time. Needs Follow-up flags stale ones. Status Color makes the table scannable.
Materials
Resume variant, cover letter, portfolio, writing samples: what was sent, per application.
Application
Materials sent
Application
Follow-up
Application
Materials sent
Application
Follow-up
Offer
Interview notes
Application
Materials sent
Application
Interview progress
Application
Follow-up
Application
Materials sent
Application
Follow-up
Click a row to open it. The Days and Flag columns are formulas; nothing in them is typed. Sample data, fictional companies.
Views that organize themselves
Status does the sorting
Change a status and the application appears in the right view on its own. Move a card to Interviewing and it vanishes from Waiting.
Same data, six views
Board for high-energy days, table for admin, calendar for planning, dashboard for low-motivation check-ins, plus the Action Required and archive views.
Moving cards feels good
Dragging a card forward is the part people enjoy. I want to move cards, not update fields, so the board is where the status changes happen.
The board view. Sample data, fictional companies.
Making effort tangible without manual work
Counters that update themselves
Three rollups on a dashboard database count applications this week, applications all time, and active interviews. Nothing is tallied by hand, ever.
Rates from a formula
Response rate is interviews plus offers divided by total. The sample below reads 23% response, 8.5% interview, 2.1% offer.
External memory
Two triggers raise a flag: Waiting for more than 14 days, or a follow-up date that has passed. The Action Required view shows only those, so I never scan the whole list.
The dashboard, with the pipeline stage selected at the top. Each card is a rollup or formula; the small print says which.
The Action Required view. It is empty on a good day, and that is the point.
Results
Why this matters
Visibility > Organization
Making progress tangible solves the motivation problem that organization never could.
Automatic > Manual
Anything that needs upkeep gets abandoned in a low-motivation week.
Emotional > Efficient
Designing for how people feel matters more than optimizing throughput.
Exception > Comprehensive
Show what needs attention now, not everything. Less to look at, less overwhelm.