The careers page should read from the ATS
Technology
Rippling runs HR against one employee record: payroll, devices, benefits and hiring all point at the same object. The part of it that reaches a public website is the applicant tracking system, which publishes open roles through a job board endpoint that needs no credentials to read.
On Walden Robotics we connected the careers section straight to that endpoint. Recruiters open and close roles in Rippling, the site reflects it, and nobody in marketing or engineering is asked to mirror a job posting by hand into a CMS.
Hiring
Wiring a marketing site to the hiring system
- Recruiters publish, the website follows
On Walden Robotics open positions appear in the careers section automatically from Rippling's public ATS. There is no CMS entry to duplicate and no listing left standing after a role closes. The hiring system stays the single source of truth and the website is a read of it.
- The public board is a narrow surface
The public job board returns what Rippling chooses to expose. Structured compensation, custom application questions and anything about candidate state sit behind the authenticated API instead. Design the careers page around the fields you actually get back, not the ones a job description happens to mention.
- Cache it, a job board is not real time
Openings change a few times a month, so a request per pageview against somebody else's API buys nothing. Static generation with scheduled revalidation gives listings that are fresh enough, and keeps an outage at the HR vendor from taking down a page your recruiting spend points at.
