Software Development Manager, EC2 Core Consoles
Amazon
- Location
- US, VA, Arlington
- Employment
- Full Time
- Work model
- On-Site
- Level
- Mid
- Posted
- 21h ago
Skills
About this role
The EC2 Core Consoles team within AWS Customer Experience (CX) is looking for a strong technical leader to manage and grow an engineering team that builds the console experiences customers use to configure, operate, and understand their AWS networking and compute infrastructure. This team owns some of the most complex surfaces in AWS, serving millions of weekly active customers across VPC, Outposts, and cross-service experiences that help customers understand their infrastructure at scale. We are fundamentally rethinking how we build and who we build for. Our customers increasingly operate through agents and automation, not just direct console interaction. This team is building the next generation of experiences designed for both human and agent consumers: intelligent, adaptive interfaces that work whether a customer is navigating directly or their agent is executing on their behalf. We are integrating agentic development practices into how we work and building experiences that serve increasingly agent-driven use cases. This role is central to proving and scaling that approach on production surfaces used by millions. The ideal candidate has built and scaled engineering teams delivering customer-facing web applications, understands what it takes to move fast without sacrificing quality, and is comfortable defining the path when the product space is evolving faster than the roadmap. They have opinions about modern frontend development, experience with data-driven product decisions, and a track record of developing senior engineers. They lead from the front technically, staying hands-on with architecture and delivery while developing the engineers around them. They are comfortable operating across organizational boundaries, since this team's work touches multiple AWS service teams, platform teams, and product organizations simultaneously. This person will own customer outcomes across their surfaces, not just feature delivery. They will use telemetry, experimentation, and customer signals to identify and resolve the friction points that matter most. They will partner deeply with platform teams and contribute back solutions that benefit all of AWS. And they will develop a team that operates with increasing autonomy as the operating model matures. Key job responsibilities Own the end-to-end delivery of console experiences across your portfolio of AWS services, from problem identification through production validation. Define and evolve the team's operating model, integrating agentic development practices and continuous experimentation into how the team builds. Use telemetry, customer research, and support signals to proactively identify friction and drive resolution, not wait for escalation. Partner across AWS service teams, platform teams, and product organizations to shape how infrastructure capabilities surface to customers and agents. Build and develop a high-performing engineering team: hire strong, raise the bar, grow senior engineers, and create an environment where people do their best work. Stay technically engaged: review architecture decisions, evaluate trade-offs, and maintain the judgment to know when to go deep and when to delegate. Drive operational excellence: reduce toil, improve deployment practices, and push toward sustainable, low-maintenance systems. Represent the customer perspective in service team conversations, ensuring console experiences influence upstream API and product decisions rather than reacting to them. A day in the life You'll split time between people leadership, technical decisions, and cross-team partnership. A typical week involves reviewing architecture proposals with your engineers, using telemetry dashboards to spot customer friction, syncing with service teams on upcoming API changes, and coaching your senior engineers on ambiguous problems. You'll spend less time in status meetings and more time making judgment calls about what to build, how to validate it, and when to ship. About the