Senior Cloud Infrastructure Engineer, Cloud Foundations

Lambda; United States; Remote; USD 150,000 - 210,000; Full time

Job summary

Lambda, The Superintelligence Cloud, is seeking a senior Cloud Foundations Engineer to design and operate the IaC execution platform and AWS account structure across multi-account environments.

You will drive governance, IAM, and networking foundations while building automation as a product, ensuring security and reliability for hundreds of engineers who self-serve.

Qualifications

• 6+ years of experience in cloud infrastructure, cloud platform, or cloud security engineering.
• Deep experience managing AWS at scale: multi-account orgs, IAM and permission boundaries, SCPs.
• Solid knowledge of infrastructure-as-code and tooling around it (Terraform)

Responsibilities

• Own and evolve the IaC execution platform (Terraform, Atlantis) across the company.
• Design and operate cloud account, access, and IAM structure; provisioning and permissions.
• Own the cloud network foundation: VPCs, Transit Gateway, DNS patterns across teams.
• Drive AWS cloud governance: tagging standards, guardrails, cost visibility.
• Implement least-privilege access and automation in line with policies; enable self-service.
• Shape team scope, priorities, and service boundaries; participate in on-call rotation.

Skills

Cloud infrastructure

AWS at scale

Terraform

Go/Python

Networking (VPC/DNS)

IAM/SCPs

Automation mindset

Tools

Terraform

Atlantis

Go

Python

Job description

Lambda, The Superintelligence Cloud, is a leader in AI cloud infrastructure serving tens of thousands of customers. Our customers range from AI researchers to enterprises and hyperscalers. Lambda's mission is to make compute as ubiquitous as electricity and give everyone the power of superintelligence. One person, one GPU.

If you'd like to build the world's best AI cloud, join us.*Note: This position requires presence in our San Francisco/San Jose/Bellevue office location 4 days per week; Lambda’s designated work from home day is currently Tuesday.

Cloud Foundations manages the account, access, and network foundation that Lambda's cloud infrastructure runs on, implementing governance and access controls in line with company policies. In practice that means AWS accounts and IAM, the VPC and transit network structure, DNS, and the Terraform execution platform that every change flows through.

This is a new team, and this role helps define it. Working closely with Security, GRC, IT, and the engineering teams that consume the foundation, this position turns policy into working controls and paved paths, so that hundreds of engineers can safely self-serve instead of filing requests.

What You’ll Do

• Own and evolve the IaC execution platform (Terraform, Atlantis): how infrastructure changes are proposed, reviewed, and applied across the company
• Design and operate Lambda's cloud account, access, and IAM structure: organizational hierarchy, provisioning, and permission models
• Own the cloud network foundation: VPCs, Transit Gateway, and DNS, including the patterns other teams build on
• Drive AWS cloud governance: tagging standards, compliance guardrails, and cost visibility and accountability
• Implement least-privilege access and compliance automation in line with company requirements and policies, replacing manual access and provisioning work with self-service
• Help shape how this new team operates: its scope, priorities, and service boundaries
• Participate in an on-call rotation and keep the systems you own well-documented, reliable, and observable

Who You Are

• 6+ years of experience in cloud infrastructure, cloud platform, or cloud security engineering, or a closely related discipline
• Deep experience managing AWS at scale: multi-account organizations, IAM and permission boundaries, SCPs, and resource organization
• Strong foundation in infrastructure-as-code (Terraform) and the tooling around it: modules, state management, and automated plan/apply workflows
• Solid cloud networking fundamentals: VPC design, transit and hybrid connectivity, DNS, and edge/CDN configuration
• Comfortable writing the automation and tooling that runs the foundation (Go and/or Python), and treating it as a product: real users, real quality standards, and things that actually get adopted
• Use AI tools as a natural part of how you work, and hold their output to the same bar as your own: you review it, verify it, and own what ships
• Build for the many, not for one team or one use case
• Comfortable with ambiguity a