The opportunity
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.
What you'll do
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
What they're looking for
- + years of professional software engineering experience
- + 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
