Full rebuild
Site and job center together. Positioning, design, build, search engine, feed integration, migration, and launch — the whole surface rebuilt as one system.
Typically 4 months
The job board is the business.
Every dollar you spend on recruiting lands on one page: the one where a candidate decides whether to apply. We build that page, and the search engine underneath it — where a typed sentence becomes filters, a misspelled specialty still finds the contract, and every application arrives in your ATS.
Free review · Send a URL, get a written teardown in 3 working days
Working demo
Type a sentence. Watch it become filters.
A cut-down build of the search we ship: typo tolerance, industry synonyms, and a natural-language pass that reads the query and sets the filters for you.
Shift
Every listing gets its own indexable page with JobPosting structured data.
Build this on your site
- Typo-tolerantTwo-character edit distance plus a synonym set built for your industry, so “emergancy dept” and “ED” both land on ER.
- Hybrid retrievalKeyword matching and vector similarity fused in one query, so a description can match without sharing a word with it.
- Sentence to filtersA model parses the typed phrase into specialty, state, shift, and pay filters — then the index does the rest.
What we build
Two things, and they are not the same project.
Most agencies build you a brochure and bolt a job list onto the end of it. The job center is the harder half — it's a search product with a content site around it, and it decides whether your recruiting spend converts.
The site
The part that earns trust before anyone looks at a contract.
- Brand and pagesPositioning, design, and copy structure built for one audience, not a template with your logo dropped in.
- Content your team can runWordPress set up so a recruiter can publish a blog post or update a benefits page without opening a ticket.
- Found on purposeClean information architecture, real page speed, and technical SEO that treats every job as a landing page.
- Recruiter pages that convertBios, direct lines, and contact routing that puts a name and a face next to the apply button.
The job center
A search product: ingest, index, search, apply, route.
Travel RN — ICU / Critical Care
Phoenix, AZ · Nights
Weekly gross$2,486
Duration13 wks
StartsSep 08
Shift3×12
Apply with résumé
No account required
Your brand, not ours — the candidate never sees a CortexStack screen
- Search that answersFilters shaped like the way candidates actually search: category, specialty, state, shift, weekly pay, contract length, start window.
- An apply flow with no account wallRésumé upload, autofill, mobile-first, and a confirmation the candidate believes.
- Straight into your ATSApplications land where your recruiters already work, with the job and the source attached.
- Alerts that bring people backText and email alerts by specialty and state, so the candidate who found nothing today hears about it when something opens.
How it runs
Five moving parts between your ATS and a filled contract.
We build against whatever your system already emits — a REST endpoint, an XML feed, or a nightly CSV. Nothing here asks your recruiters to change how they work.
This is the architecture running today on a board carrying thousands of live contracts.
-
01
Ingest
Jobs pull from your ATS on a half-hourly schedule, with a watchdog on the sync itself. Titles, specialties, and locations get normalised so “ICU”, “Critical Care”, and “CCU” stop being three different jobs.
-
02
Index
Everything lands in Typesense — facets, a synonym set for your industry, and an embedding per job — rebuilt as an atomic generation so a bad import can't take the board down.
-
03
Search
Keyword and vector retrieval fused in one query, a model that turns a typed sentence into filters, geo sort by distance, and a page per job that Google can rank on its own.
-
04
Apply
Short form, résumé upload, no account. The fewer screens between interest and submission, the more submissions you get.
-
05
Route
The lead posts back into your ATS carrying the job, the source, and the query. What people searched for and didn't find gets logged as its own report.
What ships every time
The parts nobody demos, written down anyway.
These aren't upgrades. They're the baseline every CortexStack build is held to.
Speed
Fast on a bad connection
Performance budgets set before design starts, and held. Your candidate is on a phone in a parking garage, not a fibre line.
Access
Usable by keyboard and screen reader
Labelled filters, visible focus, real contrast ratios. A job board that locks people out is a job board losing applicants.
Search
Structured data on every job
JobPosting schema, canonical rules, clean sitemaps — so your listings can show up in Google's job results instead of only on your board.
Ops
Staging, backups, monitoring
Nothing goes to production without a staging pass. Uptime and feed health are watched, and a broken feed pages us, not you.
Ownership
You own all of it
Your hosting, your repository, your data. No proprietary lock-in and no per-job licence fee for the privilege of posting your own contracts.
Handover
A team that can drive it
Documentation and a working session with the people who'll use it daily, so the site doesn't freeze the day we finish.
Three ways this usually starts.
Job center only
Your brand site stays. We replace the job board underneath it, index your feed, and rebuild the apply flow — usually the fastest path to more applications.
Typically 6–10 weeks
Care & growth
Ongoing work after launch: pages, campaigns, feed changes when your ATS shifts, and the monthly pass on what candidates searched for and didn't find.
Monthly, no lock-in
Send us your job board URL.
We'll go through it the way a candidate would — on a phone, at the end of a shift — and send back a written teardown of what's costing you applications. No pitch deck, no call required, and it's free whether or not you hire us.