We built our first job board back in 2011. It was rough around the edges, ran on classic ASP with a SQL Server backend, and the search was little more than a LIKE '%keyword%' query. It worked, though. Employers posted jobs, candidates found them, and we learned an enormous amount about what recruitment platforms actually need to do well.
Since then, we’ve built and maintained several job board platforms — including Jobs Cast, Bristol Jobs, and Job Leap — and the lessons have stacked up. This article is an honest look at what we’ve learned and what separates a decent job board from one that actually gains traction.
Search Quality Is Everything
A job board lives or dies by its search. If a candidate types “part-time admin Dolgellau” and gets irrelevant results, they leave and they don’t come back. We moved from SQL Server full-text search to Elastic Search several years ago and the difference was transformative.
Elastic Search gave us:
- Relevance scoring that actually reflects what candidates expect
- Faceted search so users can filter by location, salary range, job type, and sector without reloading the page
- Synonym handling — “PA” matches “personal assistant”, “dev” matches “developer”
- Geo-distance queries for radius-based location search
- Auto-complete suggestions that guide users toward productive searches
The move wasn’t trivial. We had to build an indexing pipeline, handle near-real-time updates when jobs are posted or expire, and tune the relevance scoring through weeks of testing with real queries. But the impact on user engagement was immediate and measurable.
A Word on Location Search
Location is the single most important search dimension on a regional job board. We geocode every job posting at ingestion time and store coordinates in the Elastic Search index. This lets candidates search within a radius of their postcode or town, which is far more useful than matching on a location text field. A candidate in Barmouth doesn’t care about a job listed as “Gwynedd” if it’s actually based in Caernarfon — the commute matters.
Two Very Different User Experiences
Job boards serve two audiences with fundamentally different needs, and getting the balance right is harder than it looks.
Candidates Want Speed and Simplicity
Candidates are often browsing on their phones during a lunch break or on the bus home. They want to search, scan results quickly, and either apply immediately or save the job for later. Every unnecessary click is a lost application.
We’ve found that the following principles make a real difference:
- One-click apply where possible, pre-filling from a stored profile
- Clear salary information — jobs that hide the salary get fewer applications, full stop
- Mobile-first design since over 65% of our job board traffic comes from mobile devices
- Email alerts that are genuinely well-targeted, not a daily spam cannon
Employers Want Control and Data
Employers are paying customers. They need a dashboard that shows them how their listings are performing, how many applications they’ve received, and how their spend compares to results. We build employer dashboards that show:
- Views and applications per listing over time
- Candidate quality metrics (complete profiles vs. incomplete)
- Comparison data against similar roles in the same region
- Easy reposting and editing tools
The temptation is to focus all design effort on the candidate side because that’s where the traffic is. But employer retention is what pays the bills.
Regional vs. National: Pick Your Battle
We’ve run both regional and national job boards, and the dynamics are completely different.
A regional job board like Bristol Jobs can dominate a local market by focusing on what the big aggregators can’t: local employer relationships, community presence, and hyper-relevant content. Indeed and Reed will always have more listings nationally, but a well-run regional board can be the first place local employers think of when they’re hiring.
A national or sector-specific board like Jobs Cast needs a different strategy. You’re competing on depth of expertise in a niche. For Jobs Cast, that niche is the IT channel — resellers, distributors, vendors. The audience is smaller but highly targeted, and employers will pay a premium to reach exactly the right candidates.
The mistake we see people make is trying to be everything to everyone. A generic national job board launched today would be throwing money into a pit. The market is sewn up. But there are still opportunities in specific sectors and regions where the big players don’t serve candidates or employers particularly well.
Monetisation That Actually Works
We’ve experimented with most revenue models over the years:
- Pay-per-post — simple, predictable, but doesn’t scale well
- Subscription packages — better for retention, employers commit to a volume of posts per month
- Featured listings — charging extra for premium placement in search results
- CV database access — letting employers search candidate profiles directly
- Programmatic advertising — backfilling unsold inventory with job ads from aggregator feeds
The model that works best depends on your market. For regional boards, subscription packages combined with featured listings have been our most reliable revenue stream. For niche boards, CV database access can command strong prices because the candidates are hard to find elsewhere.
One thing we’d caution against: don’t rely solely on job aggregator feeds for content. They can fill your board with listings, but the jobs aren’t exclusive, the employer has no relationship with you, and the revenue per click is minimal. Use them as a supplement, not a foundation.
SEO for Job Listings
Job listing SEO is its own discipline. Google for Jobs changed the landscape significantly, and structured data markup is now non-negotiable. Every listing needs proper JobPosting schema with accurate salary, location, and date information.
Beyond structured data, the fundamentals apply:
- Unique, descriptive job titles — not internal codes or jargon
- Location pages that target “[job type] jobs in [location]” searches
- Fresh content signals — regularly updated listings and expiry of stale posts
- Fast page load times — Google’s Core Web Vitals matter here as much as anywhere
We’ve seen well-optimised job boards pull significant organic traffic from Google, but it requires ongoing attention. Search engines are increasingly good at identifying thin or duplicate content, so boards that scrape listings from elsewhere without adding value will struggle.
The Technical Foundation
For anyone considering building a job board, here’s what we’d recommend as a technical starting point:
- .NET backend with a clean API layer — it handles the complexity of multi-tenant employer accounts, billing, and application workflows well
- Elastic Search for the candidate-facing search — the investment pays off quickly
- SQL Server for transactional data — employer accounts, applications, billing
- A modern frontend — we use Blazor, but React or Vue would serve equally well
- Background job processing for email alerts, indexing, and reporting
The architecture needs to handle spikes gracefully. Job boards see predictable traffic patterns — Monday mornings are busy, weekends are quiet — but a single viral listing can cause unexpected load.
Wrapping Up
Building a job board isn’t technically the hardest project we’ve taken on, but making one successful is genuinely challenging. The technology is the easy part. Understanding the recruitment market, building employer relationships, and delivering a search experience that keeps candidates coming back — that’s where the real work is.
If you’re interested in our job board platform or want to discuss a recruitment technology project, take a look at jobboardsolutions.com or get in touch with us directly. We’ve made most of the mistakes already, so you don’t have to.