Engineering Manager, Cloud Infrastructure

Brex · San Francisco, California, United States · Engineering · listed May 4, 2026

The shape of it

Seniority
Manager
Experience asked
3–5 years
Where
Hybrid
Stated pay
$240,000 – $300,000
Requirements listed
6
Length
746 words

In the posting’s own words

As the Engineering Manager for Cloud Infrastructure, you will lead a highly competent team of senior engineers responsible for the foundational AWS ecosystem that powers Brex. Your primary near-term mission will be driving our high-priority Business Continuity and Disaster Recovery (BCDR) initiative to completion, a company-level priority that involves multi-region failover and infrastructure-wide resilience. You will balance people leadership with deep technical involvement, earning the respect of a senior team while improving operational hygiene and cross-functional coordination across the entire engineering organization.

What it asks for · 6

  • Leadership Experience: 3+ years of experience directly managing software or infrastructure engineering teams.
  • Technical Depth: Deep hands-on experience with cloud infrastructure foundations, specifically AWS, Kubernetes, and Postgres.
  • Architectural Insight: Proven ability to design and implement complex infrastructure projects such as multi-region deployments or disaster recovery frameworks.
  • Collaborative Mindset: Strong communication skills with the ability to influence technical decisions across multiple autonomous teams.
  • Analytical Problem Solving: Ability to dive deep into technical issues while maintaining a high-level strategic view of organizational goals.
  • Engineering Background: 5+ years of experience in software or systems engineering.

Also a plus

  • Experience with Infrastructure as Code tools, specifically Terraform.
  • Background in managing cloud infrastructure cost optimization programs.
  • Experience with our tech stack components: Go, Kotlin, Python, or Elixir.
  • Passion for leveraging AI and LLM-assisted workflows to increase engineering velocity.

What the job covers

  • Lead and Grow: Manage and support a senior team of 6 ICs, fostering a culture of high ownership, autonomy, and technical excellence.
  • Drive BCDR Strategy: Oversee the execution of the multi-year BCDR initiative, ensuring multi-region infrastructure readiness and automated failover capabilities.
  • Technical Stewardship: Maintain and scale Brex’s core cloud infrastructure, including Kubernetes (EKS), RDS/Aurora/Postgres, networking (VPC), and AWS service integrations.
  • Cross-Functional Collaboration: Partner with product and engineering teams across Brex to drive adoption of new infrastructure capabilities and ensure successful migrations.
  • Operational Excellence: Improve team hygiene by establishing and improving best practices for work tracking (Linear), documentation, and incident response.
  • Resource Management: Effectively allocate resources to balance critical project delivery with long-term infrastructure stability.

Tools and skills named

Cloud & infra
  • AWS3×
  • Kubernetes2×
  • Terraform
Languages
  • Elixir
  • Go
  • Kotlin
  • Python
Ways of working
  • Cross-functional2×
  • Technical writing
Data
  • PostgreSQL2×
Models & research
  • LLM
Security & compliance
  • Security

Words the posting leans on

  • engineering10×
  • infrastructure10×
  • technical7×
  • experience6×
  • cloud infrastructure4×
  • deep4×
  • aws3×
  • excellence3×
  • multi-region3×
  • office3×
  • senior3×
  • software3×
  • autonomy2×
  • background2×
  • balance2×
  • bcdr initiative2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Brex

every open role at Brex

How this page was made

An automated read of a public job posting, fetched August 25, 2026 and last changed by Brex on June 10, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.