Description

This is a Senior Principal Engineer role for Containers in AWS Compute Abstractions — a technical owner across AWS ECS, AWS EKS, AWS Fargate, AWS Batch, and AWS ECR. The role raises the level of abstraction until the operator describes a workload and the platform runs it well underneath, on a platform that cannot stop running while it changes.

Key job responsibilities
• Own technical direction for Containers — architecture, standards, and what gets built and, just as often, what gets stopped.
• Go deep in the work — design reviews, code, operational readiness — on orchestration, scheduling, isolation, and registry systems.
• Own the integrated Containers strategy — how the products fit together as one offering — and the technical direction of the container products across ECS, EKS, Fargate, Batch, and ECR.
• Drive the integration work that makes the container products stronger together than apart, and make that the fastest path for the teams building it.
• Move AI-driven capabilities in Containers from prototype into production owned and operated by the organization.
• Build, prototype, and ship — settle disputed direction by making the thing.
• Raise the bar across the Containers engineering teams through design reviews, mentorship, and technical judgment.
• Engage directly with customers running their most critical container workloads, and turn what you learn into architecture.
• Contribute to and shape the open-source projects Containers depends on — containerd, Kubernetes — and represent the organization in those communities.


A day in the life
A morning goes to a scheduling and bin-packing review, where a placement change would lift host utilization but risks a regression in task-rebalancing behavior customers rely on; the call sits with this role to make and defend. Midday it prototypes the change and lands the direction in code. It closes in the container open-source community, steering an RFC on a project the portfolio depends on toward the architecture Containers is moving to.