Job Board App Starter · Industry version
Nursing Job Board Template
A job board built around licenses, specialties, and shifts — the fields clinical hiring actually runs on — in code you own.
A nurse doesn't apply to "Registered Nurse"; she applies to nights in a Level II ICU, 3x12s, in a state where her license works. This starter makes licensure, specialty, and shift structure part of the schema, so the board can answer the questions clinical candidates really ask.
- 6 core entities
- Two-sided roles
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic Job Board falls short
Clinical hiring is gated by credentials in a way generic boards can't express. An RN license is state-bound, a compact-state license travels, and a posting that requires ACLS or a specific certification isn't preference — it's a hard filter. When licensure lives in free text, every application is a coin flip and every recruiter re-screens by phone.
The unit of a nursing job is the shift pattern, not the title. Days versus nights, 3x12 versus 5x8, weekend programs, on-call expectations — these decide whether a candidate applies, and a schema without shift structure reduces them to adjectives buried in the fourth paragraph.
And a large share of the market isn't permanent at all. Travel and per-diem contracts carry duration, start date, and stipend structure — fields a permanent-job schema simply doesn't have. Boards that bolt contract work onto a permanent template end up with salary fields holding weekly rates and everyone doing math in the comments.
02 · Data model
The data model, adapted
Everything in the base Job Board starter —
job_companiesjobsjob_categoriesapplicantsapplicationssaved_jobs— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
license_requirements | Per-posting license and certification requirements — license type, state or compact status, and required certifications — enforced at apply. |
shift_types | Structured shift patterns (days, nights, rotating, 3x12, per-diem blocks) that postings declare and candidates filter by. |
contract_terms | Duration, start date, weekly rate, and stipend fields for travel and per-diem postings — the contract shape of a clinical job. |
03 · Screens
Modules through the industry lens
Credential-gated search and apply
01Candidates set their license state and certifications once on their profile; search then flags roles they're eligible for, and the apply flow warns on mismatches before submission. Recruiters stop paying the re-screening tax on every application.
Shift and contract filtering
02Filters read from shift_types and contract_terms, so "nights, 3x12, 13-week contract, starts within a month" is a query, not a scroll. Permanent and travel roles coexist without contaminating each other's fields.
Facility-side pipeline with credential visibility
03The employer pipeline shows each applicant's license state, compact status, and certifications inline, so a recruiter can move eligible candidates to interview without opening a single resume. Time-to-first-contact is the metric travel nurses judge a board on.
04 · In practice
Workflows it models
Posting a travel contract
01The facility sets specialty, shift pattern, duration, start date, and weekly rate as structured fields. The posting is filterable on all of them immediately, and expiry is automatic when the start date passes.
Compact-license matching
02A candidate with a compact-state license sees eligible roles across every compact state, not just her home state. That one query — impossible when licensure is free text — is the reason a nursing board earns its niche.
Rapid-fill for urgent needs
03An urgent posting notifies matching candidates whose profiles hit specialty, shift, and licensure — a targeted list, not a blast. Facilities measure the board on time-to-fill; this is the workflow that wins it.
Nursing Job Board template — frequently asked questions
Can it verify nursing licenses?
The starter structures licensure — type, state, compact status, certifications — and enforces requirements at apply. Automated verification against state registries is an integration you can add; because you own the code, it's an API call in your apply flow rather than a platform feature request.
Does it support travel and per-diem contracts alongside permanent roles?
Yes — contract_terms carries duration, start date, and weekly rate as their own fields, so travel postings don't masquerade as permanent jobs with strange salaries. Candidates filter by contract length and start window directly.
Can facilities and staffing agencies both post?
Both are employer accounts with scoped access; a flag distinguishes direct facilities from agencies if you want candidates to see the difference. Whether agencies are welcome is your marketplace policy, and enforcing it is your code.
Does this work for allied health, not just nursing?
The credential and shift structure generalizes — respiratory therapy, imaging, lab, PT all hire on license-state-certification lines. Extend license_requirements with the credentials your verticals use and the search follows the schema.
Related
Dual7 App Starters
Build your Nursing Job Board on your terms
A job board built around licenses, specialties, and shifts — the fields clinical hiring actually runs on — in code you own. Describe your version to start — the output is a project you own.