> Markdown version of [/jobs/ext/4177441-engineering-manager-infrastructure](https://www.wearedevelopers.com/jobs/ext/4177441-engineering-manager-infrastructure). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Engineering Manager, Infrastructure

- **Company:** SpotOn Inc
- **Location:** Detroit, MI, United States (Remote available)
- **Experience:** Experienced
- **Salary:** $180,000.0 - $215,000.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Amazon Web Services, Cloud Computing, Continuous Integration, Github, Octopus Deploy, PCI Data Security Standards, Kubernetes, Legacy Systems
- **Published:** October 29, 2026
- **Apply:** https://startup.jobs/platform-engineering-manager-spoton-com-10645003

## About the Role

* 3+ years managing engineers on platform, infrastructure, or developer-productivity teams.
 * Experience leading senior and staff-level engineers. You can set direction without being the deepest expert in the room.
 * Sound technical judgment in Kubernetes and cloud infrastructure (AWS preferred), and in CI/CD and GitOps delivery. You can assess designs, production risk, and trade-offs, and ask the questions that lead to durable solutions.
 * A track record of delivering cross-team platform migrations or adoption programs, including managing dependencies across many teams and communicating risk to leadership.
 * Experience owning production reliability: on-call health, incident response, and systemic follow-through.
 * Clear, direct communication with engineers, peer leaders, and non-technical stakeholders.

Helpful, not required

 * Hands-on experience with Argo CD, GitHub Actions, Karpenter, Kyverno, or Backstage.
 * Experience building internal developer platforms with a product mindset: golden paths, self-service, and developer experience metrics.
 * Experience in a PCI DSS or similarly regulated environment.
 * Experience applying AI tools to developer workflows or platform operations.
 * Experience leading a team distributed across US and European time zones, or a clear plan for doing it well.

## Description

* Lead and grow the team. Run 1:1s, set clear expectations, give candid feedback, and own performance and career development.
 * Free your staff engineers to lead technically. Take on the management and coordination work so they can concentrate on architecture, technical collaboration, and the hardest technical problems.
 * Collaborate with our other Platform EMs. We may be organized into several teams, but we are one platform domain first. The team boundaries are soft, existing only to help organize expertise.
 * Help drive operational efficiency. Building and maintaining an efficient and effective platform is a force multiplier for both humans and agents.
 * Help finish the platform consolidation. Drive the remaining legacy retirement work to completion. That means coordinating with service-owning teams across every R&D domain, keeping risks visible to leadership, and making sure post-migration cleanup has clear owners.
 * Run the fleet predictably. Make cluster upgrades, capacity work, and partner notifications routine and owned by the team. Balance interrupt-driven work against roadmap commitments.
 * Treat engineers as customers. Make the golden path the easiest path through good defaults, templates, documentation, and AI-assisted tooling. Use feedback from consuming teams to decide what to build next.
 * Own reliability and compliance. Lead incident response and learning for delivery and compute, follow through on systemic fixes, and partner with Security on PCI DSS controls for payments workloads.

What success looks like

First 90 days: You know the team, the platform, and its customers. Every engineer has regular 1:1s and clear expectations. You've got a grasp on how we work, the problems we face, and how we improve our ability to serve the business. You've worked with the other Infrastructure leaders on areas of ownership.

First year: There's a clear roadmap for your areas of ownership. We're placing bets and executing on them successfully. Legacy platforms are fully retired, and every cleanup item has an owner and is closed. Maintenance cycles continue to land on schedule without fire drills. Staff engineers spend their time on technical leadership, not coordination. Every engineer has a growth plan, and the team's interrupt load is measured and trending down.