About the role
Who We Are
At Justworks, you’ll enjoy a welcoming and casual environment, great benefits, wellness program offerings, company retreats, and the ability to interact with and learn from leaders in the startup community. We work hard and care about our most prized asset - our people.
We’re helping businesses get off the ground by enabling them to focus on running their business. We solve HR issues. We’re data-driven and never stop iterating. If you’d like to work in a supportive, entrepreneurial environment, are interested in building something meaningful and having fun while doing it, we’d love to hear from you.
We're united by shared goals and shared motivations at Justworks. These are best summed up in our company values, which are reflected in our product and in our team.
Our Values
If this sounds like you, you’ll fit right in.
Who You Are
You have run Temporal in production — not just written workflows on top of it. You've operated a self-hosted cluster yourself, configured and maintained the datastores it depends on, and reasoned about retries, idempotency, and partial failure under real load. You've been the person other teams escalate to when something breaks. You think in terms of guarantees, and you can say concretely what teams building on a shared platform should be able to assume, and how you'd prove the platform is holding up its end.
You've also led a technical migration, infrastructure consolidation, or platform re-architecture across multiple stakeholder teams — sequencing risk, owning the decision record, and driving it to completion.
This is a senior individual contributor role on Shared Services, the team that owns and operates platform shared capabilities across Justworks engineering, so product teams can build on reliable, well-run foundations without owning that complexity themselves. You would be the team's de facto Temporal tech lead and its long-term technical authority on the platform.
The role spans both halves of platform engineering: operating and hardening a live system other teams depend on today, and building the scaffolding, conventions, and documentation that make it straightforward to build on tomorrow. You'll be hands-on with reliability and migration work, and you'll help shape what the platform becomes as more teams adopt it.
What You Will Work On
- Harden the shared Temporal cluster for multi-tenant readiness — capacity modeling, namespace isolation, and admission control
- Define the service promise: SLOs for Temporal-backed services, and alerting trustworthy enough that every page is worth waking someone for