Recruiting · App Starter
Job Board Template
A working two-sided job board — public search, employer admin, application pipeline — generated into a codebase you own.
Describe your niche and Dual7 generates the board around it: six connected entities, a searchable public front, and an employer side that manages postings and reviews candidates. It ships as a real full-stack app, so the listing fee, the categories, and the apply flow are all yours to change.
- 6 core entities
- Two-sided roles
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
A job board is a marketplace, and marketplaces live or die on their schema. Six entities carry both sides — the employers posting and the candidates applying — and every screen below is a view over these tables.
| table | what it holds |
|---|---|
job_companies | Employers on the board — profile, logo, locations, and every posting and application rolled up under one record. |
jobs | The postings themselves: title, description, location, type, salary range, status, and expiry — the rows behind search. |
job_categories | The taxonomy candidates browse by — functions, seniority levels, or whatever slicing your niche actually uses. |
applicants | Candidate profiles with contact details, resume link, and a history of every application they have submitted. |
applications | One row per candidate per job, carrying status, stage, and notes — the pipeline employers work through. |
saved_jobs | Bookmarks tying applicants to postings, feeding return visits and the email nudges that convert them. |
02 · Screens
Signature modules
Public job search
01Keyword search plus filters for category, location, and job type, reading straight from the jobs table. Listings render with structured data for job-search engines, so postings can surface in aggregator results without a syndication deal.
Apply flow
02A candidate applies in one screen — profile details, resume, and any screening questions the employer configured. The submission creates the applicant and application rows in one transaction, so no half-completed applications leak into the pipeline.
Employer admin
03Employers manage their own postings: draft, publish, edit, close, and repost. Each company sees only its own jobs and applicants, which is the access model a two-sided board needs and the part most generic site builders get wrong.
Application pipeline
04Applications move through stages — new, reviewing, interviewing, offer, closed — on a board scoped per posting. Status changes are timestamped, so employers can see how long candidates sit untouched and you can see which employers actually engage.
03 · Process
How it works
- 1You
Describe your board
Tell Dual7 who it serves — the niche, the categories, whether employers self-serve or you curate. The starter supplies the two-sided structure; your description shapes the vocabulary.
- 2Vibe mode
Iterate on both sides in Vibe mode
Generate the working board, then refine it conversationally — add a screening question, change the pipeline stages, put a price on featured listings. Each edit is a change to code you can read.
- 3Governed mode
Launch through the governed pipeline
Take it live through Dual7's approval gates: reviewed, audit-trailed, and deployed on your infrastructure with candidate data in your own database.
04 · Fit
Who the Job Board starter is for
Founders building a niche board
The generic mega-boards are noisy exactly where a niche is quiet. If you know an industry well enough to name its ten real job categories, this starter gives you the marketplace mechanics — postings, applications, employer accounts — so your work goes into supply and demand, not CRUD screens.
Associations and communities with an audience
A trade association or professional community already has the hard part: employers who want its members. A board turns that audience into recurring revenue through listing fees, and owning the code means the margin isn't shared with a platform.
Staffing firms replacing the inbox
When openings arrive by email and candidates by referral, the pipeline lives in someone's head. Running roles through a board you own gives every req a record, every candidate a status, and every consultant the same view.
Internal talent teams
Companies posting across many brands or regions can run one internal board — each business unit gets an employer account, recruiting sees one pipeline, and nobody reconciles spreadsheets from five subsidiaries.
05 · Yours
Customize it, own it
Make it yours
The generated board is a starting shape. Rename categories to your niche's real vocabulary, add fields postings actually need — clearance level, license required, visa sponsorship — and the search filters follow the schema. Pricing is yours to design: free listings, paid posts, featured placement, or employer subscriptions are all edits to your own billing logic.
Structural changes stay ordinary code changes: add an alerts entity that emails candidates matching saved searches, wire a payment provider into posting checkout, or expose an API for partner sites to syndicate listings. The output is a normal full-stack application with no runtime dependency on Dual7, so your team can take any of it further by hand.
Why a starter, not a subscription
Job board platforms charge rent on your marketplace: monthly software fees, per-posting charges, or a slice of every transaction between employers you recruited and candidates you attracted. This starter generates the marketplace as source code in your repository — the employer relationships, the candidate database, and the pricing model are assets you hold, not features you lease.
That matters more for boards than most apps, because a board's value compounds. Every posting, applicant, and application enriches data you can only fully use if you own it — cohort analyses, salary benchmarks, employer scorecards. On a rented platform that data is a report you're allowed to view; in your own database it's a query.
06 · Industries
Industry versions
Job Board template — frequently asked questions
What does the job board template include out of the box?
A working two-sided board generated into code you own: six entities (job_companies, jobs, job_categories, applicants, applications, saved_jobs), public search with filters, a one-screen apply flow, employer self-serve admin, and a staged application pipeline. It deploys to your infrastructure with all candidate data in your database.
Can employers post and manage their own listings?
Yes — employer accounts are scoped so each company manages only its own postings and sees only its own applicants. You choose the posture: open self-serve signup, invite-only curation, or admin-approved postings, and switching between them is an edit to your own code.
How do I charge for job postings?
The starter models postings and employers; monetization is a customization you own rather than a platform's fee schedule. Common patterns — pay-per-post, featured upgrades, employer subscriptions — are each a billing integration plus a flag on the jobs table, added in Vibe mode or by your own developers.
Will postings show up in job-search aggregators?
Listing pages render posting structured data, which is what aggregator crawlers read to index jobs. Because you own the templates, you control exactly what's exposed — salary ranges, remote status, expiry — and can adjust markup as aggregator requirements evolve.
Can candidates upload resumes?
The apply flow takes a resume upload and stores it against the applicant record, with the file living in storage you control. If your niche prefers profiles or portfolio links over documents, the apply form is your code — swap the field, and the pipeline view follows.
Is this better than building a job board on a site builder?
Site builders handle the public listing page but strain at the two-sided part — scoped employer logins, application state, pipelines. This starter generates that relational core as a real application, which is the difference between a page of jobs and a marketplace.
Related
Dual7 App Starters
Build your Job Board on your terms
A working two-sided job board — public search, employer admin, application pipeline — generated into a codebase you own. Describe your version to start — the output is a project you own.