Senior Software Engineer, Infrastructure Foundations

About the role

SUMMARY

Infrastructure Foundations builds and operates the multi-cloud platform underneath Temporal Cloud, turning the complexity of AWS, Google Cloud (GCP), and Azure into one cohesive platform the rest of Temporal builds on. Every cell we run is provisioned, managed, and safely changed by systems this team owns. When a customer's workflow runs, it runs on our work. We are heading into the next stage: Kubernetes-based infrastructure platforms built for the next orders of magnitude of growth.

We are looking for a Senior Software Engineer to own big pieces of that platform end to end. You will take a high-level problem, shape it into a well-designed solution, build it (mostly in Go), ship it safely, and help run it in production. There is a lot of greenfield here: new cloud footprints, high availability and disaster recovery, declarative infrastructure, and the tooling every other engineering team uses to ship.

What makes this team different

- Real multi-cloud, not multi-cloud on a slide. We run across AWS, GCP, and Azure and keep extending the platform to new providers. You will work through the differences between clouds, not around them.

- We build Temporal Cloud with Temporal. Cell creation, component deployment, and cloud provisioning run as Temporal workflows. You will get deep in both infrastructure and the product itself.

- Real greenfield next to real production. HA/DR for our control infrastructure, a declarative model for the whole platform, and new regions, all while keeping a live platform reliable.

- Everything sits on top of it. Nearly every team at Temporal depends on what we build, so the impact of your work shows up quickly.

Responsibilities

- Multi-cloud platform: Build the provider-specific pieces behind one consistent platform, from EKS, GKE, and AKS cluster differences to IAM, networking, and quotas. Help stand up new regions and extend the platform to new providers end to end, so other teams never have to think about which cloud they are on.

- Cluster and cell lifecycle: Own the systems that provision, upgrade, recover, and decommission Kubernetes clusters, node pools, and Temporal Cloud cells. Become the engineer who can implement any component in this area.

- Workflows and APIs: Write the Go services, Kubernetes controllers, and Temporal workflows behind automated cell creation, component deployment, and cloud resource provisioning. Keep the APIs straightforward for the teams that use them.

- Declarative infrastructure: Ship versioned component definitions that cover Kubernetes workloads and the cloud resources behind them. Build drift detection, change previews, and safe reconciliation so engineers know what is deployed and what is about to change.

- Safe change: Build progressive rollouts, rollout sequencing, and change visibility into the platform, and keep blast radius small by design. Estimate the performance and reliability impact of a design with data before it ships.