Skip to content

Temporal

Staff Software Engineer, Infrastructure Foundations

Temporal is hiring a Staff Software Engineer, Infrastructure Foundations for a remote role open to applicants in United States. It pays $170k-$278k a year and Level rates it ; you can apply on Temporal.

Level's read on this job

  • Level rates this software engineer role Little AI ●○○○: aI is not part of the work.
  • The listed pay starts close to the typical software engineer posting on Level.
  • The posting lists this role as remote.
  • Tools and skills the posting cites include Kubernetes, AWS and Google Cloud.
  • Level lists 80 other open roles at Temporal.

AI in this role

Design and build the next version of multi-cloud infrastructure platforms powering Temporal Cloud.

KubernetesAWSGoogle CloudAzure
infrastructuremulti-clouddistributed-systemssystem-architecture
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 Staff Software Engineer to design and build the next version of that platform. You will own a significant multi-component system, from the APIs other teams build on to how infrastructure state is modeled, changed, and recovered, and coordinate the engineers building its parts. You will stay close enough to the code to prove decisions out, build the capability roadmap for this area with the engineering manager, and lead through design reviews and the hardest incidents.

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. The abstractions you design are the ones every new cloud plugs into.

  • We build Temporal Cloud with Temporal. Cell creation, component deployment, and cloud provisioning run as Temporal workflows. You will shape how Temporal runs its own infrastructure on Temporal.

  • A platform transformation, not maintenance. HA/DR for our control infrastructure, a declarative model for the whole platform, and a deployment control plane, all designed while a live platform keeps running.

  • Everything sits on top of it. Nearly every team at Temporal depends on what we build, so the standards you set for this platform shape how those teams ship.

Responsibilities

  • Multi-cloud architecture: Design the abstraction model that makes AWS, GCP, and Azure read as one platform. Decide where provider differences in IAM, networking, quotas, and failure modes get absorbed, and how new regions and providers plug in.

  • Own a significant system: Design and build the multi-component platform end to end, and coordinate the engineers working on its parts. Make the system-level tradeoffs between conflicting requirements, and make them explicit.

  • Declarative infrastructure model: Define how components are described, versioned, and reconciled across Kubernetes workloads and supporting cloud resources. Set the approach for reproducible environments, drift visibility, and safe reconciliation.

  • Deployment control plane: Design the shared inventory, dependency awareness, rollout sequencing, and approvals that let many teams change production safely. Keep orchestration and safety policy cohesive while integrating with the frameworks that execute deployments.

  • Reliability by design: Spot architectural flaws before they cost us performance or reliability. Make bounded blast radius, progressive rollouts, observability, load and failure testing, and recovery part of every design. Stay cool in the hardest incidents, then bring what we learn back into the platform.

  • Roadmap and judgment: Build the capability roadmap for this area with the engineering manager. Scope big ideas down into well-understood pieces, evaluate the viability of requests from other teams, and weigh technical and business risk when the path isn't clear.

  • Raise the bar: Define the team's development process and operational best practices. Coach Senior engineers and invest in their growth, lead design reviews, and catch the critical PRs, as a keeper of standards who is seen as a value-add, not a blocker. Help hire the engineers who will build this with you.

  • Cross-team collaboration: Work with Traffic, Control Plane, Developer Productivity, Security, and service owners. Communicate complex designs clearly, influence toward the right course of action, and earn adoption through useful abstractions and dependable operations. Own compatibility and migration as the platform evolves.

Qualifications

  • 10+ years building software, including significant time designing and operating distributed infrastructure in production.

  • Production infrastructure experience on at least two of AWS, GCP, and Azure, including building, operationalizing, and scaling Kubernetes-based platforms across them.

  • Deep Kubernetes knowledge: scheduling, controllers and reconciliation, resource management, isolation, and upgrade safety.

  • A record of designing and building a significant multi-component system and coordinating other engineers to deliver it, ideally through a substantial infrastructure transition while production kept running.

  • Proficiency across a diverse set of technologies, with strong coding skills in Go or another systems language. You still write meaningful code.

  • Excellent written and verbal communication. You can explain complex systems, make tradeoffs explicit, and drive alignment with engineering and leadership.

  • Bachelor's degree in Computer Science or a related field, or equivalent practical experience.

Required Skills

  • Multi-cloud platform thinking: reusable abstractions that account for provider differences and stay secure, observable, and maintainable.

  • Kubernetes architecture and operations judgment, especially recovery under failure.

  • System-level tradeoffs and good judgment in ambiguous situations, balancing foundational work, customer needs, and unplanned operational demands.

  • Raising the bar through design reviews, code reviews, coaching, and clear technical writing.

Preferred Experience

  • All three providers. Building and operating infrastructure across AWS, GCP, and Azure, especially bringing a new provider onto an existing platform.

  • Building Kubernetes controllers and operators, including cloud resource controllers like Crossplane or AWS Controllers for Kubernetes (ACK).

  • Upstream open source contributions or maintainer experience in Kubernetes, CNCF, or similar infrastructure projects (conference talks are a bonus).

  • Deployment control planes, progressive delivery, dependency-aware rollouts, and safe migrations of production infrastructure.

  • Automating lifecycle management, such as patching and upgrades, for cloud native software across a large fleet.

  • Infrastructure services in Go and durable workflow orchestration using Temporal.

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.

How we rate this

Staff Software Engineer, Infrastructure Foundations at Temporal rates 0 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.

Classification

Little AI. AI is not part of the work.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

InfrastructureMulti CloudDistributed SystemsSystem ArchitectureKubernetesAWSGoogle CloudAzure

Also common in software engineer jobs at this level

Pay

This job starts at
$170k
Typical software engineer job
$167k

This posting starts close to the typical software engineer job. See software engineer jobs

Questions you could be asked

  1. Tell me about a project where infrastructure was part of your work. What did you do?
  2. Tell me about a project where multi cloud was part of your work. What did you do?
  3. Tell me about a project where distributed systems was part of your work. What did you do?
  4. Tell me about a project where system architecture was part of your work. What did you do?
  5. Walk me through how you've used Kubernetes in your day-to-day work.

Adapt your resume

  • List these exact terms on your resume: Infrastructure, Multi Cloud, Distributed Systems, System Architecture, and Kubernetes. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.

Get your CV reviewed before you apply

Send your CV and the role you want next. Your review arrives by email within 3 days.

Get new remote software engineer jobs by email

One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free.

Similar roles

Software Engineering roles that involve little AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at Temporal

More software engineer jobs

Related searches

Same AI level