Senior Software Engineer, Infrastructure

Engine is an AI-native platform for intelligent travel serving business travel, group travel, human agents, and AI agents. The Senior Software Engineer, Infrastructure will help lead the central infrastructure team by setting technical direction, building shared cloud and platform capabilities, improving reliability and developer workflows, and partnering with feature teams across the company.

Responsibilities:

• Set the technical direction for a major area of Engine's infrastructure over a multi-quarter horizon — where it's headed, what you're deliberately not building, and how platform investments compound rather than fragment
• Lead multiple infra initiatives in parallel, coordinating across the central team and with the feature teams who'll adopt what you build
• Design and ship the Terraform modules, pipeline patterns, and operational tooling that product teams adopt because they're better than the alternative — not because they're mandated
• Separate signal from noise across the feature-team requests that land on the central team. Decide what deserves a paved road, what belongs in team-owned space, and what shouldn't be built at all
• Own the boring-but-critical work: incident response, on-call quality, deployment reliability, vendor integration health
• Shape the guidelines, tools, and methods every engineer at Engine uses — and coach the feature engineers who apply them
• Represent the infra team in cross-functional conversations with product and engineering leadership. Our team meets twice a week — that's where you'll share what's shipping, align on priorities, and pressure-test decisions
• Reduce the SDLC step-function count across Engine. Every approval gate, every "ask infra first" workflow is a tax — your job is to lower it

Requirements:

• 6+ years building and operating production cloud infrastructure, with deep AWS expertise (multi-account, networking, IAM, security boundaries)
• Expert-level Terraform — you've designed reusable modules and have opinions about state, drift, and execution patterns
• Strong CI/CD background — GitHub Actions, reusable workflows, OIDC, secret management
• A track record of shipping platform infrastructure that feature teams actually adopt — you know how to build for internal customers without losing sight of what makes something feel like a product
• A bias toward enabling teams over gatekeeping. You'd rather build the paved road than approve the off-road permits
• Experience leading technical direction across multiple teams — making the trade-offs precisely, communicating them clearly, and bringing other engineers along
• Instinct for when a problem deserves a central solution and when it should stay with the team that hit it
• Cloudflare (WAF, DNS, zero-trust/WARP) at production scale
• Datadog, JFrog, or comparable vendor integration experience
• Background in cost observability or FinOps tooling
• History of working on a platform team that serves internal customers — you understand the difference between running a platform and running a gate