Staff Software Engineer
Role details
Job location
Tech stack
Job description
The Core Experience team owns how companies and users first encounter Rippling, and how they operate within it every day. We build the onboarding flows that take companies from zero to running on Rippling, the self-serve growth infrastructure that lets customers discover and purchase products without a sales touch, and the foundational surfaces (home dashboard, navigation, user management, and company settings) that every Rippling user touches regardless of which product they're in.
We operate at the intersection of product surface and platform infrastructure: building reusable components that dozens of product teams depend on, scaling self-serve checkout and entitlement flows that need to be reliable at Rippling's full customer volume, and owning experiences that have to work coherently across a complex multi-product environment. If you like building foundational systems that multiply the output of teams around you and care deeply about the quality of what users actually experience, this is the work.
What you will do:
- Design and build backend systems that power Core Experience's highest-leverage surfaces: onboarding flows, self-serve purchasing, and the shared platform primitives other product teams rely on
- Take technical ownership end-to-end, from schema design and API contracts to performance, reliability, and observability in production
- Work directly with product and design to shape how features get built, not just implement what's handed to you
- Build for scale and reuse: the systems you design will be consumed by other engineering teams across Rippling, so correctness, documentation, and thoughtful abstraction matter
Requirements
- 8+ years of professional software engineering, with a strong track record in backend systems
- Systems thinking: You design for scale, fault tolerance, and correctness from the start. You understand the trade-offs between consistency and availability, and you know when simple is the right answer and when it isn't
- Full-stack range: You're backend-leaning but comfortable owning a feature end-to-end
- High agency: You identify the problem before you're asked, scope a solution, and execute. You don't need a well-defined ticket to make progress
- Platform instinct: You think about your work as infrastructure others will build on, and you write code and design APIs accordingly
- Tech stack: Deep proficiency in a modern backend language (Python, Go, Java, etc.) and strong data modeling skills across SQL and NoSQL