ABOUT THE TEAM

Infrastructure Engineering builds and runs the foundations Anduril operates on. That includes wired and wireless connectivity, our private backbone, private and public cloud, and the systems that run on them.

The InfraEng Platform Team owns the central hub for all of it: the console, CLI, and API the rest of the company uses to consume infrastructure. We do not build every capability ourselves. Partner teams own their domains, and we help them expose those capabilities through the hub.

We define and champion the shared patterns: one identity model, one authorization model built on RBAC and ABAC, one audit trail, and one set of ergonomics. Partner services meet the contract for their space, and the platform makes that contract easy to meet. The goal is to replace tickets with safe, bounded self-service across every team and provider.

ABOUT THE ROLE

You will be the first software engineer on the InfraEng Platform Team and one of the first in Infrastructure Engineering. A small codebase exists today. Part of your early work is deciding whether it is the right foundation to extend or whether to replace it.

From there, you will set the architecture, engineering standards, and delivery practices the team builds on. This is a hands-on role. You will go deep into networking, systems, and cloud when the problem requires it, and your fingerprints will be on everything this team ships.

WHAT YOU’LL DO

• Evaluate the existing codebase and set technical direction: keep, extend, or rebuild.
• Design and build the hub’s core: the APIs, services, and data models that expose infrastructure as self-service across AWS, Azure, and on-prem.
• Decide where control planes and data planes separate, where they nest, and where they should not. Document the reasoning so others can extend it.
• Define the contracts and patterns partner teams use to plug into the hub, then help them adopt those patterns. Partners own their domains; you own the hub and the patterns.
• Build a single identity and authorization layer (RBAC and ABAC) with a complete audit trail for every action the platform exposes.
• Ship backend services and the console, CLI, and API surfaces users touch. Most of this will be in Go, Python, or Java, but you will pick the right tool for the job.
• Turn common infrastructure requests into bounded self-service actions that take tickets off the critical path.
• Establish the CI/CD pipelines, source control practices, and deployment safety controls for a codebase with many contributors.
• Own what you build in production, including observability, on-call, incident response, and postmortems.
• Partner with connectivity, backbone, cloud, and product teams on shared interfaces. Influence their roadmaps without direct authority.
• Mentor the engineers who join the team after you.

REQUIRED QUALIFICATIONS

• 10+ years of software engineering experience, including building and operating platform or infrastructure software at scale.
• Strong proficiency in Go, Python, or Java, or equivalent languages suited to systems and platform work. You choose the language that fits the problem.
• Deep understanding of control plane and data plane design: desired state, reconciliation, failure isolation, and blast radius.
• Strong hands-on AWS or equivalent major cloud providers, experience across compute, networking, IAM, storage, and managed Kubernetes.
• Strong grounding in containers and ephemeral compute, such as Docker, Kubernetes, and immutable infrastructure patterns, or equivalent.
• Experience shipping both backend services and user-facing surfaces (console, CLI, or API) for large and varied user bases.
• A track record of designing CI/CD pipelines and branching and release strategies that keep deployments safe with many contributors. You know when to add a gate and when to remove one.
• Depth below the application layer in networking, systems, or cloud, and the willingness to learn the others.
• High ownership and operational excellence. You run what you build, measure it, and fix root causes.
• Proven ability to influence senior stakeholders and peer teams without authority.
• Must be eligible to obtain and maintain a US Secret Security clearance. 
  

   

PREFERRED QUALIFICATIONS

• Experience building or integrating with identity and authorization systems, such as OIDC, SAML, OPA, Cedar, or equivalent.
• Experience implementing RBAC or ABAC models within a product or system.
• Experience with Azure, on-prem, or equivalent environments, including abstractions that work across providers.
• Experience with Kubernetes controllers or operators, Crossplane, or equivalent infrastructure abstraction frameworks.
• Infrastructure as code at scale with Terraform, OpenTofu, or equivalent tools.
• Familiarity with enterprise networking or backbone infrastructure and how platforms expose it to users.
• Experience in regulated environments such as FedRAMP, DoD IL levels, CMMC, or equivalent.
• Front-end experience with TypeScript and React, or equivalent, for console development.