Ashbyis API-first by design. Unlike most ATS platforms, they don't offer a tiered menu of integration options or a built-in careers site builder. Their documentation points teams directly at their API for building an external careers page, describing it as “the most amount of effort, but also providing full flexibility.” Their own example of this done well is PostHog.
This is honest. It also means that choosing Ashby implicitly means the careers site is a separate problem to solve.
Why Ashby is API-first
Ashbyhas concentrated their product quality in the ATS and CRM. The hiring workflow, the reporting, the interview tooling — that's where they've chosen to compete. They haven't built a native careers site builder, and that appears to be a deliberate decision.
For teams using Ashby, this is worth naming clearly. You're not getting a careers page included in the product. You're getting an excellent ATS and a well-documented API. The candidate-facing experience is yours to build.
That separation has an upside. There's no mediocre built-in builder pulling you toward a compromise. Ashby's API is clean and well-maintained, and teams that build on it get genuine flexibility. The constraint is resource, not capability.
What building on the Ashby API involves
A basic Ashby careers site built on the API requires a frontend developer comfortable with React or equivalent, two to four weeks of build time at minimum, and ongoing maintenance as the API evolves.
That covers the technical build. It doesn't cover design, employer brand content, stakeholder review rounds, or launch. A properly scoped Ashby careers site project, built to a standard that reflects the quality of the ATS behind it, typically runs two to four months from brief to live and costs £30,000–£100,000 or more depending on scope.
PostHog built something like this. They have an engineering team and the inclination to build their own tooling. Most companies hiring on Ashby don't have three engineers available to scope, build, and maintain a careers site.
The consistency argument
The most compelling reason to invest in the Ashby candidate experience isn't about overcoming a limitation. It's about consistency.
Teams that choose Ashby have made a deliberate quality decision. The ATS is considered, the data is good, the hiring workflow is structured. A generic careers page undermines that signal. A candidate who encounters a polished, well-run interview process but hit a plain job listing on the way in notices the gap. The careers site should reflect the same standard as everything else in the process.
For a broader view of this decision across all ATS platforms, see our guide to ATS careers pages vs custom careers sites.
What the build looks like without the engineering overhead
Voyse connects to Ashby via the full API and delivers a careers site built around your brand, managed by your TA team without developer involvement. New roles sync from Ashby automatically. Templates can be mapped to different job types, departments, or regions using your Ashby data. The SEO architecture is fully controlled. Your team doesn't inherit a maintenance dependency.
For teams that chose Ashby because they care about quality, this is the logical extension into the candidate-facing experience. See how the Ashby integration works.
