System Development Engineer, Keya

Application deadline: Aug 3, 2026 The Keya team owns and operates the Customer Experience (CX) services that power AWS User Experience Products and Platforms (UXP2), Documentation, and SDKs within US Government dedicated cloud partitions. We are responsible for the scaling, reliability, and regional expansion of these services—ensuring that AWS's government customers have a seamless, secure, and performant experience across console, SDK, and documentation touchpoints. Key job responsibilities Our work spans the breadth of AWS: from build automation and service operations to development of tools that accelerate region launches and maintain experience parity across dedicated cloud environments. Our work spans the breadth of AWS: from build automation and service operations to development of tools that accelerate region launches and maintain experience parity across dedicated cloud environments. We are looking for a System Development Engineer I to help us build, scale, and operate critical services that directly impact how US Government customers interact with AWS. You'll work on a collaborative, geographically distributed team that values autonomy, ownership, and technical depth. A day in the life No two days on Keya look the same—but here's what a typical day might look like: You are a builder who thrives on solving real-world problems at scale. You're comfortable operating in ambiguity, you take ownership of outcomes (not just tasks), and you're energized by the challenge of keeping critical systems running reliably for customers who depend on them. You bring strong technical fundamentals, a bias for automation over manual work, and the curiosity to learn new systems quickly—because on Keya, you'll touch a lot of them. You start your morning reviewing service dashboards and alarms, checking the health of the CX services your team owns across dedicated cloud partitions. After standup with your distributed team, you dive into a design document for a new automation that will cut a manual region-launch task from hours to minutes. Mid-morning, you pair with a teammate to debug a latency spike in one of your APIs—tracing the issue across service boundaries, identifying a misconfigured retry policy, and pushing a fix through your CI/CD pipeline. After lunch, you join a cross-team architecture review with engineers from another AWS service team, providing input on how their changes will interact with your services in government partitions. Later in the afternoon, you're writing code—maybe building a new CloudWatch alarm integration, extending an internal CLI tool, or implementing a feature on your team's roadmap. You wrap up the day by updating your design doc based on feedback from a senior engineer and queuing up a code review for tomorrow.