Hotel Engine is transforming business travel into something personalized and simple. As a Senior Software Engineer on the Control Plane/Core team, you will lead the technical direction, design platform primitives, and mentor engineers while enhancing the cloud infrastructure and CI/CD processes.
Responsibilities:
- 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
Requirements:
- 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 enabling teams over gatekeeping. You'd rather build the paved road than approve the off-road permits
- 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 in or alongside embedded/platform models — you understand the difference between a platform team and a ticket queue