Justworks Senior Software Engineer at Justworks operates and hardens the shared Temporal platform for multi-tenant readiness. This role involves managing capacity, defining SLOs, and enabling multi-cluster availability.
Responsibilities
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
Build the golden paths and conventions that let other teams build workflows on the shared platform safely, with less hand-holding over time
Enable multi-cluster availability, so tenant workloads keep running through a cluster or regional failure
Own capacity and cost efficiency as the shared platform scales to more tenant teams and workflow volume
Partner with tenant teams on workflow design, idempotency, and safe retry patterns as they onboard
Rotate on the shared platform's on-call schedule — incident response, root-causing production issues, writing postmortems, and continuously tuning alerts and SLOs
How You Will Do Your Work
Good judgment — the exercise of critical thinking, analyzing and assessing problems and implications, identifying patterns, making connections of underlying issues, understanding risks and developing mitigation strategies, and taking ownership of the outcome.
Resourcefulness — taking a can-do approach, even in the face of obstacles and constraints by assessing what's in front of you and effectively and efficiently optimizing what you have, whether it's working on something new or thinking about how to do something better.
Teamwork and communication — putting our collective best together through documentation, collaboration, relationship-building, listening, empathy, recruiting, and evangelism.
Qualification
You've also led a technical migration2+ years of hands-onA specific language beyond GoA particular cloud or Kubernetes flavorOrchestrationInfrastructureLanguagesService communication
Required
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.
5+ years of professional software engineering experience
2+ years of hands-on, production experience operating self-hosted Temporal — running the cluster itself, not only writing workflows against one. This is a hard requirement, not a nice-to-have: experience with another workflow orchestrator does not substitute, and Temporal Cloud alone does not meet the self-host requirement
Experience operating a distributed system in production at scale — retries, idempotency, partial failure, and the datastores and storage configuration it depends on
Operational depth in Temporal internals and cluster administration — how the cluster is configured, maintained, and tuned, and how its constraints shape workflow design
Experience securing and troubleshooting service-to-service communication between clients, workers, and the cluster
Experience leading a technical migration or infrastructure consolidation across multiple stakeholder teams
Experience defining SLOs and alerting for a platform-level service, including per-namespace / per-tenant observability and routing problems to the owning team
Experience with Kubernetes and container orchestration in production
Strong Golang proficiency plus at least one additional language
Preferred
These are the parts of the profile we consider coachable — hands-on Temporal depth matters more than any of them:
A specific language beyond Go
A particular cloud or Kubernetes flavor
A prior formal "migration lead" title — someone with deep Temporal chops can grow into leading the migration without that exact label on a resume
