🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Join the Amazon Elastic Kubernetes Service (EKS) Control Plane team that manage the entire EKS fleet globally. We own the path from a customer's intent to a running cluster: the EKS API that accepts the request, the regional services that hold every cluster's desired state and orchestrate its lifecycle, the services that provision and repair the infrastructure that state describes, and the Kubernetes control plane that runs on it. We also own the availability commitment customers hold us to. And we own knowing what state every cluster is in: the health detection that catches a cluster broken by a change to the resources it depends on, the insights that tell a customer what will break before they upgrade, and the operational signals we stream back to them. Amazon EKS now supports Kubernetes version rollback, which we built to enable customers mitigate operational risk with in place updates; customers can update normally and watch the new version carry production traffic, and rollback within 7 days if it does not hold, with their cluster state, workloads, and volumes untouched. We also made the control plane resilient to Availability Zone issues with no customer action, which turned a single zonal impairment into a non-event. We run all of this for every EKS cluster across all commercial AWS Regions and AWS GovCloud, and on customer premises through AWS Outposts. Innovation takes a village, and this team is the catalyst for it. Other EKS teams launch on our API and lifecycle services. AWS partner services like Amazon GuardDuty build customer-facing security features integrating with services we own. We also own the EKS Model Context Protocol server and the AI capabilities that enable how agents work with EKS. This is an opportunity to operate and engineer distributed systems at scale, and to own the availability and resiliency of a service customers run their production workloads on. You will provide technical leadership and influence strategies to delight our customers. You will be solving challenging technical problems, often ones not solved before, alongside peers with remarkable technical expertise. The solutions you build will be high impact and rolled out to our large customer base across the world. If you are excited to work in a dynamic and collaborative environment to deliver results, we would love to hear from you! 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 again.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.