🎁 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 →
We're building the infrastructure that shapes how EKS delivers managed software to its customers, and we need a Software Development Engineer to build it with us. If you want to write the code that lets hundreds of thousands of Kubernetes operators get fully managed platform capabilities without the operational overhead, this is your role. What You'll Own You'll own components at the core of EKS's next chapter. First, EKS Capabilities: the delivery platform that brings managed software experiences to customers as native, turnkey extensions of their clusters. You'll design and build how GitOps, continuous delivery, and future managed capabilities reach customers at scale, with secure multi-account and multi-region operations built in. Second, a cluster federation service that powers EKS-on-EKS: the internal infrastructure running EKS's own control plane workloads on Kubernetes, creating cell-based cluster sets with observability, autoscaling, and operational best practices baked in from the start. You'll take features from design through implementation, launch, and long-term operation, and you'll own the quality of what you ship. What You'll Solve The problems here are real and evolving. How do you deliver managed capabilities that feel native to customers without limiting the flexibility they expect from open source tooling? How do you securely federate clusters across account boundaries at scale? How do you operate multi-tenant control plane infrastructure across every AWS region while shipping new capabilities weekly? How do you build primitives that let your team and other EKS teams launch the next wave of managed experiences faster? You'll dig into these problems, propose designs, and deliver working systems. What You'll Do You'll design and implement distributed systems that run in production across all AWS regions. You'll write high quality code, review your teammates' code, and raise the operational bar for the services you own. You'll partner with senior and principal engineers to shape technical designs, work with product managers to turn customer needs into concrete features, and engage with open source communities where our work lives upstream. You'll participate in on-call and incident response for the services you build, and you'll help mentor engineers earlier in their careers. Why This Role EKS is one of AWS's fastest growing services. Managed capabilities and EKS-on-EKS infrastructure are the next wave, and this team is at the center of both. You'll own meaningful surface area early, make real technical decisions, and see your code reach customers who are actively pulling for what you're building. It's a place to grow deep distributed systems and Kubernetes expertise while shipping to production every week. Key job responsibilities Design, build, and operate managed platform services that run across all AWS regions Own the full lifecycle of the components you build: design, implementation, testing, launch, and operations Contribute to operational excellence: availability, on-call, incident response, safe deployments, and fault isolation Write and review code to a high bar of quality, security, and maintainability Partner with senior engineers, principal engineers, and product managers to shape feature direction and technical designs Help drive architecture decisions for multi-tenant, multi-region control plane infrastructure Turn ambiguous customer problems into concrete designs with measurable outcomes, and mentor engineers earlier in their careers A day in the life Your morning starts reviewing operational metrics and deployment health for the services you own, and picking up a code review or two from your teammates. By mid-morning you're in a design review debating how to safely roll out a new managed capability to thousands of clusters, and how your component fits into it. After lunch you're heads down implementing that rollout logic and writing tests for the edge cases. Later you're pairing with a teammate on a tricky system design question, then jumping onto an incident bridge because multi-region infrastructure doesn't wait. About the team We're a Vancouver based engineering team within Amazon EKS focused on how AWS delivers managed platform experiences to Kubernetes customers. We build the infrastructure that powers EKS capabilities and the internal substrate that runs EKS itself on Kubernetes. The team operates with high ownership and low bureaucracy: engineers ship to production weekly, influence product direction directly, and collaborate closely with open source communities. You'll work alongside distributed systems engineers, product managers, and principal engineers who care deeply about making Kubernetes simpler for everyone.
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.