Guides / How to build

How to Build a Job Board: Postings, Applications and Paid Listings

How to build a niche job board: job postings, search, applications, paid listings, expiry, Google job search markup, and how to get the first employers.

Mythex Team · 2026-09-29 · 7 min read

To build a job board, pick a niche where employers struggle to reach the right candidates, build a clean list of jobs with filters that match how those candidates search, give each job its own well-structured page, and let employers post and pay for listings through a simple form and checkout. Decide early whether candidates apply on your site or on the employer's, because that choice decides how much personal data you handle. Getting both employers and candidates onto a new board is the hard part; the software is the easier part.

What a job board needs

The data

Jobs, companies, categories or role types, locations, and — if you take payments — orders or postings with a paid status and an expiry date. If you collect applications, add applications and CV files, linked to the job and visible only to that employer.

Permissions

• Anyone can see live, unexpired jobs.
• An employer can edit only their own postings.
• If you accept applications on-site, an employer sees only applications to their own jobs, and candidates see only their own.
• Admins can see and moderate everything.

CVs contain personal data: names, contact details, work history. If you store them, keep files private, delete them after a set period, and say clearly in your privacy notice how long you keep them.

Decisions and trade-offs

Niche

General job boards are crowded. Niche boards win on relevance: remote roles for a specific programming language, jobs in climate tech, nursing roles in one region, hospitality jobs in one city. A narrow niche also makes your filters obvious and your marketing easier.

Apply on-site or off-site

Off-site (a link to the employer's application page or an email address) is simpler: no CV storage, fewer privacy obligations, and employers keep using their own hiring tools. On-site gives candidates a consistent experience and lets you offer employers a simple applicant list, but you are then handling personal data and building part of an applicant tracking system. Most new boards start off-site.

Pricing

Common models are a flat price per post, a higher price for featured posts, discounted packs of several posts, or subscriptions for frequent hirers. Start with one price and one upgrade. Some boards post the first few jobs free to show activity; if you do this, be honest about which listings are paid, sponsored or gathered from elsewhere.

Expiry and freshness

Job seekers lose trust fast when they apply to filled roles. Give every job an expiry date (30 or 60 days is common), let employers mark roles as filled, and hide expired jobs automatically. The simplest approach is to filter by expiry date whenever jobs are listed, so nothing needs to run on a schedule to hide them.

Search visibility

Job pages can appear in Google's job search experience if they carry the right structured data. As of September 2026, Google's documentation lists required JobPosting properties including the job title, description, date posted, hiring organisation and job location (with separate guidance for remote jobs). It also says expired jobs should be removed — by setting a past validThrough date, returning a 404 or 410, or removing the markup — and that the markup belongs only on individual job pages, not on list pages. Check Google's current guidance before you implement it.

That makes page rendering important: job pages should be readable by search engines without relying on heavy client-side JavaScript. Our guide on SEO for AI-built websites explains the options.

A first prompt for an AI builder

Build a niche job board called GreenStack Jobs for software roles at climate and clean-energy companies. Job pages include title, company name and logo, location or "Remote" with allowed countries, salary range, employment type, seniority, description, and an "Apply" button that links to the employer's application URL. The home page lists live jobs newest first, with featured jobs pinned at the top, and filters for role type, remote/on-site, seniority and salary, kept in the URL. Employers use a "Post a job" form, preview their listing, and submit; postings wait in an admin queue for approval. Jobs expire 30 days after publishing and are hidden once expired. Each job page gets a unique title, meta description and JobPosting structured data. Use Next.js so job pages are server-rendered. Save data in a database and logos in file storage. Leave payment as a placeholder step — we will add Stripe Checkout next.

After the core works, add Stripe Checkout for the posting fee, then email alerts for candidates. How to add payments to your app covers checkout and webhooks.

Build steps

1. Choose the niche and list the filters candidates would use.
2. Collect a first set of real jobs — with permission, or by linking to the original listing.
3. Build job pages, the list and filters with that data.
4. Add the post-a-job form with preview and an admin approval queue.
5. Add payment for posts in test mode, then live mode: pay, then the job goes to review or live.
6. Add expiry and "mark as filled."
7. Add SEO basics and JobPosting markup to job pages, and a sitemap.
8. Launch a candidate channel — a weekly email of new jobs, or a community in your niche.
9. Add employer accounts so repeat customers can manage and renew posts.
10. Consider on-site applications only once employers ask for them.

Common mistakes

• Launching empty. Candidates leave a board with five jobs. Seed it with real, relevant roles.
• Leaving expired jobs up. It wastes candidates' time and can conflict with search engine guidelines.
• Posting jobs without the employer's knowledge in a misleading way. If you list roles from elsewhere, link to the source and do not imply the employer paid you.
• Hiding salary ranges. Many candidates filter by pay first; in some places salary ranges are legally required in job ads. Make the field prominent.
• Collecting CVs without a plan. Storing personal data you do not need is risk without reward.
• Weak moderation. Scam job posts appear on open boards. Review new employers before their posts go live.
• Structured data on list pages, or invented fields. Follow the search engine's guidelines exactly.

Costs and tools

Hosting, a database and storage for logos are the base costs. Payment processing fees apply to each paid post. An email provider sends job alerts and receipts. If you add on-site applications, CV storage and any virus scanning of uploads add a little more. Check current prices on each provider's own site.

When a ready-made product is the better choice

If you want a standard job board quickly, hosted job board software can give you posting, payments, alerts and employer accounts out of the box, usually for a monthly fee. It also suits communities or associations that simply want a jobs page next to an existing site. If you only need to hire for your own company, you do not need a job board at all — an applicant tracking system or a careers page will serve you better. Build your own when your niche needs unusual fields, filters or pricing, when the board is part of a bigger product, or when you want full control of the pages for search.

Building it with Mythex

Mythex can build the board in the prompt above: job pages, filters kept in the URL, a posting form with an admin queue, and expiry logic, with a dedicated Postgres database and file storage for logos. You can ask for Next.js so job pages are server-rendered, check them in the live preview, and publish to a public URL or your own domain on Pro. Employer login and payments are bring-your-own: you choose an auth approach and connect your own Stripe account, with keys stored as project secrets. Job alert emails use a provider such as Resend or Postmark with your own key.

The docs cover accepting payments with Stripe, sending email and SEO for published apps. For a recruitment-focused start, see the recruitment agency website builder; if you are tracking candidates for your own hiring instead, the hiring pipeline tracker template is closer. A job board is a kind of directory, so how to build a directory website is useful background too.