Temporal Technologies
From Temporal Technologies's careers page
Status: listed on the employer's own careers page when we last checked (daily). Confirm on their site before applying.
We are looking for a Senior Software Engineer to own big pieces of that platform end to end.
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.
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.
Reliability and operations: Join the team's on-call rotation and step up during incidents. Get to the bottom of the "mysterious" issues by digging into Kubernetes clusters, workflow histories, and dashboards, then fix the system so it doesn't happen again. Actively prevent tech debt and cut toil with better runbooks, metrics, and automation.
Ownership and growth: Lead projects on your own, from clarifying fuzzy requirements to pulling in the right people to a well-tested launch. Contribute to the design of the platform's major pieces, write clear design docs, and be someone others seek out for code reviews on significant changes. Mentor less senior engineers and help interview the next ones.
Collaboration: Partner with Traffic, Control Plane, Developer Productivity, Security, and service owners to deliver secure defaults.
8+ years building software, with significant time on infrastructure or distributed systems in production.
Hands-on experience building and operating Kubernetes-based infrastructure at scale, including cluster lifecycle, upgrades, resource management, and recovery under failure.
Strong coding skills in Go or another systems language, and interest in making Go your primary language.
Deep experience with at least one major public cloud (AWS, GCP, or Azure), including IAM, networking, and quotas. Multi-cloud experience is a big plus.
A record of owning production systems: on-call, incident response, postmortems, and the fixes that follow.
A record of leading projects on your own, from an unclear problem to a well-designed, well-tested result.
Clear written communication. You can explain a design and its tradeoffs in a doc others can act on.
Bachelor's degree in Computer Science or a related field, or equivalent practical experience.
Required Skills
Designing with provider differences in mind: knowing where clouds diverge and building so those differences don't leak into the teams on top.
Distributed-systems fundamentals, including concurrency, consistency, failure handling, and idempotency.
Infrastructure as code and declarative thinking with Terraform, Helm, or similar tools, and a working understanding of reconciliation.
Operational judgment: knowing when to ship, when to slow down, and how to roll back.
Multi-cloud production experience is the biggest plus for this role. Building or operating infrastructure on more than one of AWS, GCP, and Azure, especially standing up a new provider or region, or abstracting the differences between them.
Writing Kubernetes controllers or operators, or working with cloud resource controllers like Crossplane or AWS Controllers for Kubernetes (ACK).
Running Karpenter, Helm, and Terraform in production.
High availability and disaster recovery work, such as multi-region data layers, automated recovery, and deployments built to survive regional outages.
Temporal or other durable workflow orchestration.
Tech you'll work with
Languages: Go (primary)
Infrastructure: Kubernetes (EKS, GKE, AKS), Karpenter, Helm, Terraform, and Temporal (we dogfood extensively)
Cloud providers: AWS, GCP, Azure
Temporal Technologies is an Equal Opportunity Employer. Temporal Technologies does not discriminate on the basis of race, religion, color, sex, gender identity, sexual orientation, age, non-disqualifying physical or mental disability, national origin, veteran status, or any other basis covered by appropriate law. All employment is decided on the basis of qualifications, merit, and business need. We embrace and celebrate differences and diversity.
Temporal is committed to providing access, equal opportunity, and reasonable accommodation for individuals with disabilities in employment, its services, programs, and activities. If you need to request a reasonable accommodation, please let your Recruiter know so we can assist.
Scores your resume against this job the way resume scanners do: the job's hard and soft skills, searchability, recruiter tips and formatting.
Create a free account to see your score. Your resume stays in this browser until then, and we never store it.
Already a member? Sign in