opengreenhouseintegritypowersearch
Staff Software Engineer, DevOps/Infrastructure
Engine
LocationRemote - US
WorkplaceFull
Last observed2026-06-13 05:25:14.369509
Job idintegritypowersearch-hotel-engine:greenhouse:7726524003
About Engine At Engine, we’re transforming business travel into something personalized, rewarding, and simple. For too long, managing travel and spend has been overwhelming and fragmented — we’re here to change that. We believe the future of travel should be seamless and powered by technology that delights customers at every step. That’s why we’re building a platform that brings together corporate travel, a powerful charge card, and modern spend management in one place. To make this vision real, we’re looking for exceptional, mission-driven people to help redefine how businesses manage and experience travel. More than 30,000 companies already rely on Engine to support over 1 million travelers and billions in annual bookings each year. Cash flow positive with rapid growth, we pair exclusive Engine-only rates, industry-leading rewards, and intelligent automation to help businesses save money while delivering world-class personalization and convenience. Backed by Telescope Partners, Blackstone, and Permira, Engine has been recognized as one of the fastest-growing travel and fintech platforms in North America, with honors including the Deloitte Fast 500 and Built In’s Best Places to Work. As Staff Engineer on the Control Plane / Core team, you're one of a handful of people who set the technical direction for how every engineering team at Engine builds and ships. You won't be embedded in a single vertical — you're working on the substrate underneath all of them. You'll be hands-on with AWS control plane— multi-account architecture, account vending, VPC networking, organizational guardrails, IAM boundaries. CI/CD platform— template pipelines, shared GitHub Actions/workflows, org-level policies, secret distribution. You moderate what's shared; teams contribute upward. Terraform execution— Terraform Cloud workspaces, module registry, our internal modules, the tooling that lets a feature team stand up a namespace and start shipping in hours, not weeks. Networking & security— Cloudflare (WAF, DNS, WARP, page rules), core network topology, certificate management. Vendor integrations— Datadog, JFrog, Terraform Cloud, GitHub OIDC — the connective tissue between vendors and our accounts. Cost observability— tooling and dashboards that give teams visibility into what they own and spend. You'll also be a force multiplier for the embedded engineers: the patterns, modules, and primitives you build are what they hand to feature teams. When something embedded engineers keep solving locally needs to become a paved road, that's your work. What You'll Do Lead the technical evolution of the control plane — not just keep it running, but decide where it goes next. Design and ship platform primitives (Terraform modules, pipeline templates, account/networking patterns) that feature teams adopt because they're better than the alternative — not because they're mandated. Partner with embedded infra engineers to identify recurring friction across verticals and turn it into self-serve capability. Own the boring-but-critical work: AWS Organization hygiene, CI/CD reliability, vendor contracts and integration health, incident response on shared infrastructure. Mentor across the discipline. We hold infra standups twice a week — that's where you'll teach, learn, and stay aligned with the embedded engineers. Reduce the SDLC step-function count. Every new approval gate, every "ask infra first" workflow is a tax — your job is to lower it. What We're Looking For Required 8+ 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, run TFC at scale, and have opinions about state, drift, and execution patterns. Strong CI/CD background — GitHub Actions, reusable workflows, OIDC, secret management. Experience with platform engineering: shipping internal tools and abstractions that other engineers actually want to use. A bias toward
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.