Amazon Elastic Kubernetes Service (EKS) is a fully managed Kubernetes service that enables customers to run Kubernetes seamlessly in both AWS Cloud and on-premises data centers. The EKS Management Plane team is responsible for the EKS API and the services behind it that take a customer's intent and turn it into a running, upgradeable, recoverable Kubernetes cluster, so customers can innovate with containers without becoming experts in the underlying technologies. We are looking for a Software Development Engineer to work on cluster lifecycle, availability, and insights: the state management and orchestration behind every cluster operation, the health detection that tells customers what is wrong before it impacts them, capabilities like Kubernetes version rollback that make a failed upgrade recoverable instead of terminal, and control plane evacuation that makes an Availability Zone impairment a non-event. In this role, you will: - Build and improve state machines and orchestration workflows that drive cluster create, update, and upgrade operations -Develop health-detection systems that surface actionable insights to customers before issues become outages - Contribute to resilience capabilities (rollback, failover, self-healing) from design through production - Collaborate with experienced engineers across EKS to solve problems that span multiple services and teams You will engineer distributed systems at scale and solve hard problems, often ones not solved before, alongside peers with deep expertise. We evaluate trade-offs in the open and give every engineer ownership of critical customer-facing systems. You will grow through end-to-end feature ownership and expanding your influence across the team. This position involves on-call responsibilities, typically for one week every two months. We don't like getting paged in the middle of the night or on the weekend, so we work to ensure that our systems are fault tolerant. When we do get paged, we work together to resolve the root cause so that we don't get paged for the same issue twice.