If your company's careers page is hosted at apply.workable.com/yourcompany, you've already made a statement before a candidate has read a single job description. That URL tells them your careers experience lives on someone else's server. For a lot of companies, that's fine. For brands at a certain scale or ambition, it isn't.
Workableis a capable ATS with a large customer base. Their default careers page works. The question is whether “works” is sufficient for the talent market you're competing in.
Workable's three options
Workabledocuments three ways to connect a careers site. Here's what each means for a TA team:
The careers page builder is included on all plans. Workable hosts the page at apply.workable.com/yourcompany by default. A custom domain is available on Standard annual and Premier plans at additional cost. You can apply CSS and basic branding, and the structure is fixed. This is the route most Workable customers take because it's the path of least resistance.
The JavaScript widget embeds a job listing on your existing website. It inherits your site's CSS, so the jobs list takes on your brand's typography and colours to a degree. It's quick to implement. It doesn't give you employer brand capability beyond what your existing site already has.
The full API is Workable's highest-control option. Their own documentation describes it as requiring “a full website team including front-end developers.” Maximum flexibility, significant resource requirement.
One detail worth noting: Workable's custom domain is a paid upgrade on certain plans. That's an additional cost for something most TA teams would consider table stakes.
The subdomain question
Is apply.workable.com a problem? The honest answer depends on your audience and your market.
For a Series A startup hiring engineers who recognise Workable and know how the recruitment tech stack works, it's probably not a deciding factor. For an established consumer brand or enterprise employer competing for talent who don't know or care about your ATS, a third-party subdomain signals that the candidate experience wasn't a priority. It's a small signal, but it compounds. The question is what that signal costs you in the specific talent market you're operating in.
What the builder can and can't do
Workable's careers page builder handles the basics. You can apply your logo, set your brand colours, write custom page content, and list jobs by category. For teams who need something live quickly with minimal resource, it serves that purpose.
The structural constraints are real. You can adjust what's in the template but not the template itself. There's no CMS for employer brand content — no structured way to surface video, team photography, or hiring manager messages alongside job listings. Template mapping by job type isn't supported, so every role gets the same page structure regardless of seniority, department, or campaign. SEO control over page architecture is limited. Role-level conversion analytics aren't available.
For teams where employer brand content, template flexibility, or organic search are priorities, those constraints matter.
For a broader view of this trade-off across all ATS platforms, our guide to ATS careers pages vs custom careers sites covers the full picture.
The full API route
Workable's API gives you complete control, but at the cost Workable themselves name in their documentation: a full website team. That means frontend developers, design resource, ongoing maintenance as the API evolves, and a project timeline that extends well beyond what most TA teams can resource internally.
A properly scoped Workable API careers site build typically runs months from brief to launch, and requires continued engineering support once live.
What full control without the build looks like
Voyse connects directly to Workable via the full API and delivers a branded careers site your TA team manages without developer involvement. New roles sync from Workable automatically. Different job types, departments, and regions can be mapped to different templates using your Workable data. Employer brand content sits alongside job listings. SEO architecture is fully controlled. Your careers site lives on your domain from day one, with no paid plan upgrade required.
For teams where the default is holding their employer brand back, see how the Workable integration works.
