Additional Information
Come keep one of the world's largest Apache Kafka fleets healthy, secure, and always on. On Amazon MSK, you will build the automation that maintains hundreds of thousands of streaming hosts, so customers never have to think about the infrastructure underneath their applications.
This is infrastructure engineering at a scale where every change has to be safe by design. MSK is stateful: every host holds customer data that must stay replicated and in sync, so routine maintenance is never as simple as rebooting or replacing a host. Patching, repairing, and replacing nodes across a fleet this size means coordinating each action against the availability guarantees customers depend on, so that maintenance stays invisible to them.
You will design and build the automation that does this, turning hard operational problems into systems that run themselves. If you enjoy distributed systems, large-scale automation, and work whose reliability countless streaming applications quietly depend on, this is a rare place to do it.
Key job responsibilities
- Design, build, and operate automation that patches and maintains hundreds of thousands of stateful hosts, keeping fleet maintenance invisible to customers.
- Build systems that automatically detect unhealthy hosts and remediate them, balancing fast recovery against avoiding needless disruption.
- Develop rollout and rollback mechanisms that keep the blast radius of any change small at fleet scale, and that let changes be tested before they reach customers and reversed if something goes wrong.
- Own your services end to end: take part in on-call, debug production issues, and continually reduce the manual effort needed to operate the fleet.
- Write design documents, collaborate with engineers across MSK, and raise the engineering bar through design and code reviews.
A day in the life
No two days look the same, but most blend building with operating. You might spend the morning designing a safer way to roll out a fleet-wide change, pairing with a teammate on the review, and writing the automation that carries it out. In the afternoon you might dig into a signal that a small set of hosts is unhealthy, trace it to root cause, and improve the automation so it handles that case on its own next time. You will write design documents, review your teammates' code, and steadily push routine operational work out of human hands and into systems that run themselves. When you are on call, you keep the fleet healthy and feed every manual step you take back into automation, so the same issue does not page anyone twice.
Our team keeps Amazon MSK's managed Kafka fleet healthy, secure, and available, so customers never have to think about the infrastructure beneath their streaming applications. People choose MSK because they want Apache Kafka without the burden of operating it. Our mission is to make that promise real at very large scale: keeping the fleet patched and secure, automatically recovering hosts that become unhealthy, and renewing the certificates that protect data in transit, all without interrupting the applications running on top.
We believe operations should be automated, not heroic. We invest in systems that detect and resolve problems on their own, so the team spends its time building durable automation instead of reacting to pages, and we are increasingly using generative AI to strengthen those mechanisms. You will build alongside teammates who jointly own these systems, and you will partner with the wider MSK engineering, product, and operations groups that depend on the fleet staying healthy as the service grows. Your work shapes the reliability every MSK customer feels, and you will have real ownership of meaningful problems from design through operation.
Amazon Development Center U.s · Seattle, WA