Some engineering managers measure their value by how much the team needs them. The best ones measure the opposite.
If you're the second kind — the leader who builds teams that make good calls without you in the room — keep reading.
Buildkite's Platform team runs the engine room: a Postgres-powered Rails monolith on AWS Fargate that sits in the critical path for engineering teams at Shopify, Uber, Pinterest, Canva, OpenAI, and Anthropic. They also build the deploy tooling the whole company relies on, dogfood new features before customers see them, and give product engineering the shared patterns that let them ship fast without breaking things.
It's the kind of team where the trade-offs are never simple. Proactive versus reactive work. Paying down tech debt versus shipping the next thing. The maintainable solution versus the clever one. Getting those calls right — and making the case for them upward, clearly and without drama — is the job.
You'd lead the team, not the codebase. That means real 1:1s that help people grow, roadmap planning with product and engineering leadership, and clearing obstacles before the team hits them.
You'd stay off the critical path for delivery — deliberately — while staying close enough to review changes, weigh in on technical plans, and roll your sleeves up when the team is stretched. You'd own the risk conversations in both directions: helping the team prioritise, and giving executives an honest picture when requirements and deadlines don't match reality.
And you'd hand the team genuine ownership of design and implementation, because you know that's when morale, speed, and quality all move together.
- You've led platform or SRE teams before — real production systems at scale, with on-call, compliance, and vendor relationships attached. You know this work from the inside, having done it as an engineer yourself.
- You default to trust. You delegate decisions to the people accountable for them, resist the urge to override, and have clear instincts about when a concern is worth raising and when the team learns more by finding out.
- You think in risk, not opinion. Whether you're descoping work, prioritising tech debt, or pushing back on an unrealistic deadline, you frame it in terms of impact and trade-offs — and people listen because of it.
The one thing we can't compromise on: you've managed engineers running large-scale production infrastructure. Not adjacent to it — accountable for it.
You're probably a strong fit if you:
- Get energy from making a team more capable than you are individually
- Are comfortable operating in ambiguity and would rather simplify than over-engineer
- Are genuinely curious about how AI is changing engineering work, and want to help a team experiment with it safely
This probably isn't the right role if you:
- Want to stay hands-on-keyboard as your main contribution
- Prefer detailed direction from above — the scaffolding here is light by design
- Find it hard to let a team make (and learn from) a recoverable mistake
- Work that matters right now. CI/CD is becoming the bottleneck of the AI era, and Buildkite is built for that moment.
- Real scale. The systems your team runs ship software to over a billion daily users.
- Remote, properly. We've worked this way since 2013 — async by default, built for deep focus.
- Small enough that it counts. ~150 people. What your team builds is visible, and so is how you lead it.
Every application gets a response — that's how we run our process. If this sounds like the way you already lead, apply, or reach out with questions first.
At Buildkite, we value diversity and celebrate all types of skills, backgrounds, and experiences. We’re dedicated to fostering an inclusive environment and providing reasonable accommodations throughout our recruitment process.
If you need any accommodations or support during the application or interview process, please reach out to us at [email protected].
