SMF·HUNTR
Can a prompt replace Huntr?
Résumés & job search — application pipeline board
Exhibit tracking slip
Verdict
Underneath the resume tools and the extension, Huntr is a board with five columns and a notes field, and at forty dollars a month it is one of the clearest one-sitting rebuilds in this catalogue. The version you write can do one thing Huntr cannot: answer questions about your own search, because you control the schema and every stage change is a row you can query.
Exhibit A — The prompt
Received on31.07.2026Build a job-search tracker whose real output is statistics about your own search.
Schema first. An `application` row holds company, role, source, posting URL, salary range if published and the date you found it. A separate `event` table holds one row per state change: `{application_id, stage, occurred_at, note}`. The current stage is derived from the latest event, never stored on the application. This is the decision that makes the rest work.
The board is a simple five-column view — found, applied, screening, interview, closed — where dragging a card writes an event. Closing a card asks for one of a fixed set of outcomes: rejected, withdrawn, offer declined, offer accepted, ghosted. "Ghosted" is set automatically by a nightly job when an applied-or-later application has had no event for 30 days, and it is the outcome most searches actually produce, so make it a first-class value rather than a blank.
Then build the report page, which is the point: applications per week; response rate per source; median days from applied to first human contact; the conversion rate between each pair of adjacent stages; and a list of applications gone quiet with the number of days beside each. All of it is SQL over the event table.
Capture is manual: a form with company, role and URL, plus a paste box for the description. Do not build a browser extension for arbitrary job boards in this build — see the Careerflow entry for why that is a separate project with its own maintenance bill.
Do not add automated follow-up emails. A templated nudge sent by a script reads exactly like what it is.
Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 one-click saving from job boards you have not configured
- B.2 the mobile app for updating a stage from a phone
- B.3 the built-in resume builder and tailoring tools
- B.4 reminders delivered by email or push rather than by you opening the app
Prior art
- Reactive ResumeLicense: MIT
Exhibit C — Why people still pay: polish and job-board coverage
A job search is stressful and short, and paying forty dollars for two months rather than building anything is a rational trade when the alternative competes with the actual applications.
Questions
Can I import my Huntr board?
Huntr exports to CSV. Each row becomes one application plus one event at whatever stage it currently sits in, dated the export day. You lose the history of how it got there, because Huntr's export gives you the current state rather than the transitions — which is precisely the data this build exists to keep.
Will it work on my phone?
Only if you host it somewhere and open it in a mobile browser. There is no app and no offline mode, so updating a stage from a train platform is the thing you will miss first.
What does it cost to run?
Nothing on your own machine. On a small VPS with a domain, about five dollars a month — an eighth of the Pro plan, though you are now also the person who patches it.
What is the one thing that does not survive the rebuild?
Saving a job in one click from a board you stumbled onto. Every application in your version starts with you pasting a URL, and during a heavy week that friction is real.
Related tools
Receipt