Before we get into limitations: Pinpointis one of the best-designed ATS products on the market right now. The UX is considered. The documentation is good. The platform is actively developed — they ship features, respond to feedback, and engage with integration partners in a way that most ATS companies don't. Their MCP integration is the kind of technical work that puts them ahead of competitors still running on decade-old architecture.
We work with Pinpoint closely. We like the product and we like the team.
That's exactly why this piece is worth writing. Even the best ATS careers site builder in the market has a ceiling. Some teams will hit it.
What Pinpoint's careers site builder actually does
Pinpoint's built-in careers site builder is better than the default offering from Greenhouse or Lever. It's worth being specific about why, because the comparison matters for understanding where the limits are.
It's no-code. Your TA team can build and manage the careers site without involving a developer or raising a ticket with IT. Most ATS careers builders are nominally no-code until you try to do anything beyond the simplest customisation. Pinpoint's holds up further than most.
It supports rich content. Video, employee testimonials, custom pages, content blocks — Pinpoint's builder gives you real surface area to tell your employer brand story, not just a list of jobs.
It handles multi-language. For teams hiring across multiple markets, Pinpoint's native language support means you can serve candidates in their own language without building a separate site or relying on browser translation.
And it syncs live. Every job you post in Pinpoint appears on your careers site automatically. No manual publishing, no copy-paste, no lag.
For a mid-market team with a single brand, hiring across a handful of markets, with a TA team that wants to own their careers presence without developer dependency, Pinpoint's builder is a strong answer. It may be all you need.
Where the ceiling is
The limitations are about what any native careers builder is structurally constrained from doing, however well built.
Structural flexibility. Pinpoint's builder gives you blocks to arrange and content to populate. It doesn't give you full control over the underlying page architecture. If your employer brand team has a specific vision for how a careers page should be structured, and that layout doesn't fit the available block types, you'll be working around the template.
One custom domain per careers site. Pinpoint supports one custom domain per careers site instance. For a single-brand organisation, that's fine. A multi-brand organisation that needs genuinely separate careers experiences — distinct brand identities with different visual languages — will need multiple instances or a compromise on brand separation.
SEO control. Pinpoint's builder gives you a careers site but not full control over the SEO architecture: page titles, meta descriptions, canonical URL structure, heading hierarchy across job pages. For teams where organic search is a meaningful candidate acquisition channel, those constraints will eventually show up in the data.
Template mapping by job properties. Pinpoint's native builder doesn't support applying different visual templates to different job types based on ATS data. Your Early Careers roles look the same as your executive appointments. Your Distribution Centre vacancies look the same as your Head Office roles. Personalisation at that level of granularity requires the full API build.
Who hits the ceiling
Not everyone does.
A 300-person company with one brand, hiring in three or four markets, with a TA team that owns their careers content, will typically find Pinpoint's builder handles their needs. The ceiling is real but high enough that many teams never reach it.
The teams who hit it tend to share certain characteristics: multi-brand organisations who need distinct candidate experiences per brand; companies with meaningful Early Careers programmes that need their own visual identity and tone; teams that have produced serious employer brand content — video, photography, written stories — and need structural flexibility to surface it; and organisations where careers site SEO is a strategic priority.
For a broader look at how to think through this decision, see our guide to ATS careers pages vs custom careers sites.
The full API route — and what it costs
Pinpoint has a full API. It's well-documented, actively maintained, and good to build against, consistent with everything else about how they approach their platform. Their own documentation describes Option 4 as offering “full customisation and flexibility” while noting it “usually comes with a heavy tech lift on your dev team.”
That's accurate. A properly scoped Pinpoint API careers site build, with design, employer brand content integration, template mapping, and testing, is a significant project. The API quality makes it a better build experience than most, but it doesn't change the resource equation for a TA team without dedicated engineering support.
What full control without the build looks like
Voyse integrates with Pinpoint via the full API. We use Pinpoint's custom fields to map jobs to different templates automatically, so your Early Careers roles, sub-brand vacancies, and campaign-specific hiring pushes each get the right visual treatment without manual intervention. Your TA team manages the content. New roles sync from Pinpoint automatically. The SEO architecture is fully controlled.
Pinpoint is an excellent ATS. For teams that have outgrown the native careers builder, or know they will, see how the Pinpoint integration works.
