Sr. Software Development Engineer, DC Console

Application deadline: Oct 20, 2026 AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion. Amazon's Data Center Bridge (DC Bridge) organization builds and operates the software that runs AWS's worldwide data centers. The DC Console team is hiring a senior, frontend-leaning full-stack engineer to set the technical direction for the platform that lets every builder in DC Bridge ship data center operator experiences, not just the team that owns the console. You should be a senior engineer with real depth in modern TypeScript, React, Rust or equivalent programming language. Browser fundamentals and high-volume real-time UX, and a track record of leading the design of systems other teams build on. Half of this role is platform engineering (build systems, deployment, and the mechanics of how frontend code gets to a browser), so you should be comfortable owning architecture that spans repositories, pipelines and teams you don't manage. You take personal pride in interfaces operators trust during an incident, and you raise the engineering bar of the people around you. Key job responsibilities - Own the architecture of the platform that lets engineering teams across the organization ship features into a shared operator console (independent packages, independent pipelines, composed into one product at runtime) and write the design documents that set its direction. - Define the contract between the console shell and the teams that build on it: navigation, routing, page registration and shared services, versioned so partner teams can upgrade on their own schedule. - Lead the resolution of the hardest cross-origin problems a federated frontend creates (authenticated module loading, edge authentication, content security policy, per-stage isolation, and graceful fallback when the module registry is unreachable) and make the security trade-offs explicit. - Drive self-service onboarding end to end, so a partner team gets a working module, account, CDN and pipeline in one step, including teams that bring their own backend. Measure time to first deploy and drive it down. - Set the operational bar for the platform: per-team health metrics, alarms, paging and user reports, so each feature team owns its own module's quality without owning the shell. - Plan and lead the migration of existing pages out of the monolith, sequencing work across teams and keeping every rollout reversible behind feature flags. - Guide the design of real-time visualizations of power and cooling data that operators rely on during site events. - Influence partner teams through design reviews, security reviews and office hours, so a federated frontend doesn't fragment into ten different products. - Mentor engineers on the team, review their designs and code, and help grow the next set of technical leads. A day in the life You'll split your time between hands-on code (React and TypeScript against Cloudscape, plus AWS CDK infrastructure) and technical leadership: reviewing a partner team's design, deciding how the shell ships a breaking change, or