When a TA team starts shopping for a “career site builder”, three very different products answer the call: the builder bundled into your ATS, a general-purpose website builder with a jobs widget bolted on, and a specialist custom build. Vendors in each camp talk as if the other two don't exist. They do, and the right answer depends on your brands, your volume and your engineering resource - not on who you happened to ask first.
Route one: the builder inside your ATS
Every ATS gives you something. They are not remotely equivalent. Pinpoint has the best native builder in the ATS market - genuinely usable, with real layout control before you hit its ceiling. Lever sells a Career Site Builder add-on alongside five other connection options of varying ambition. Greenhouse and Workable give you hosted default pages - functional, fast to switch on, and visibly templated. Ashby, API-first by design, gives you no builder at alland assumes you'll solve the careers site separately. At the enterprise end, SAP SuccessFactors' Career Site Builder is a product category of its own, usually configured by implementation partners.
Where this route wins: cost (often bundled or a modest add-on), speed (days, not weeks), and sync - jobs and apply flows just work, because the ATS owns both ends.
Where it runs out: the ceiling. One brand, one template family, limited layout and content flexibility, partial control of SEO and structured data, and a candidate experience that looks like the ATS, not like you. Native builders exist to keep you in the ATS ecosystem, and their roadmaps reflect that. If your employer brand is a differentiator - or you run several brands, regions or languages - you will hit the ceiling, usually within the first year.
Route two: a website builder plus a jobs widget
The DIY route: WordPress, Webflow or Squarespace for the site, with your ATS's JavaScript embed or iframe pulling in the job list. Total brand freedom, familiar tools, and your marketing team can edit it.
Where this route wins: design control and content flexibility, at content-site prices. For a small company with one brand and modest hiring, it can be entirely reasonable.
Where it runs out:the seams. Embedded job widgets inherit none of your design, structured job data for Google Jobs rarely gets implemented properly, and the apply flow usually redirects to the ATS domain - which is where candidates leak. Someone has to own plugins, updates, hosting and the integration when the ATS changes its embed. The build is cheap; the ownership isn't.
Route three: a specialist custom build
The third route is a careers-site specialist that designs and builds the site around your brand and connects natively to your ATS's API - the route we sell, so weigh this section accordingly. Done properly it means: your design system end to end, job pages with imagery and video per role, an apply flow that stays on your domain and submits straight into the ATS, structured data for Google Jobs from day one, and multi-brand, multi-region, multi-language on one platform.
Where it wins: everything the other routes cap - brand, conversion, SEO, scale across brands and markets, and accountability: one party owns design, build, hosting and the ATS integration.
Where it runs out: price and patience. Custom builds are typically quoted from £20,000 to £80,000+ depending on scope, and a traditional agency delivery takes months. If your hiring is modest and your brand requirements are simple, this is more machine than you need.
One development is changing the economics: agentic build tooling. Our own platform now stands up a complete, ATS-connected careers site from a designed mockup in a fraction of traditional delivery time - which is collapsing the cost gap between “builder” and “custom”, particularly for agencies and RPOs delivering client sites.
How to choose
Stay on your ATS builderif you have one brand, your hiring is steady rather than strategic, and candidates already convert. The bundled option is underrated when the ceiling doesn't bother you.
Go DIYif you have a strong web team that wants to own it, one brand, and you can accept an embedded or redirected apply experience - or you're early-stage and the careers page is one page.
Go custom when the employer brand is doing competitive work: multiple brands or markets, high-stakes or high-volume hiring, a careers site that needs to persuade rather than list. The threshold question: does the gap between your brand and your careers site cost you candidates? If yes, the build pays for itself in hires you stop losing.
Whichever route, insist on three things: structured job data that Google Jobs actually indexes, an apply flow that doesn't visibly change domain, and analytics that reach hire - not just visits. Those three separate careers sites that perform from careers sites that exist. If you want to talk through the custom route, here's what our recruitment website design service includes.
