Building a job board: what you actually need

Job boards look like a solved problem: get listings, show listings. Every operator discovers in month two that the listings were never the problem.

The five things that decide whether it works

1. Expiry. Nothing kills a niche board faster than dead listings. Users forgive a small index; they do not forgive applying to something that closed in March.
2. Deduplication. Four copies of one role makes a board of 400 feel like a board of 100 and look careless.
3. A defensible slice. "Jobs" is not a market. "Rust jobs in Europe with visa sponsorship" is.
4. Search that matches how people think. People search by outcome — remote, salary, visa — not by taxonomy.
5. A reason to come back. Alerts, saved searches, a weekly digest. Without one, every visit is a new acquisition.

The economics nobody mentions

The default assumption is that a board sells listings to employers. In practice, small boards usually start on the other side: aggregators supply listings free and pay the board per click. That inverts the model — the board is a traffic business, not a marketplace — and it changes what you should optimise.

A build order that works

1. Pick a slice narrow enough that you can name every employer in it.
2. Get listings into a database, however crudely. Manual is fine at first.
3. Solve expiry before design. A board of fifty live roles beats a board of five hundred where a third are dead.
4. Add one retention mechanism — an email alert is enough.
5. Only then worry about how it looks.

What to buy and what to build

The mistake almost everyone makes

Launching with the largest index you can assemble. A big index with stale entries is worse than a small curated one, because trust is the only thing a niche board has, and one dead listing spends more of it than ten live ones earn.