- You will work where software meets physical hardware. A bad firmware rollout does not just throw an error, it can take a machine offline, so the bar for getting it right is unusually high.
- Your scope is the whole fleet. Decisions you make about release process apply to millions of servers across every AWS region.
- You are building the mechanisms, not inheriting them. There is real room to design how this works rather than administer someone else's process.
- You will get deep in the technology. This is a hands-on technical role with engineers, not a status-reporting role.
If you like turning messy, high-stakes coordination into something that runs predictably, and you want to see your work land at a scale very few places can offer, we would like to talk to you. AWS engineers are shaping the way people use computers and designing the future of cloud computing technology, come help us make history!
Key job responsibilities
Own firmware release and deployment end to end, from a completed code change through qualification to a fully deployed fleet.
Publish and maintain the release schedule that the firmware teams plan against, and drive agreement on scope, sequencing, and dependencies between them.
Define the quality gates a release must pass at each stage, including hardware qualification and validation at our manufacturing partners, and hold teams to the entry and exit criteria.
Build and run the reporting that shows where every release stands, how much of the fleet is on the current version, and what is blocking progress, and present that to senior leadership on a regular cadence.
Own escalation for release blockers, including issues raised by manufacturing partners, and drive them to closure against a defined response time.
Turn what we learn from each release and each operational issue into a lasting change to the process, the gates, or the tooling.
Partner with firmware, hardware, manufacturing, security, and service teams to resolve competing priorities and keep releases moving.
Find the coordination that happens manually today and replace it with automation.
A day in the life
You will spend time with the firmware engineering teams, going deep on what is in the next release, what changed, what worries them, and whether it is ready to move to the next stage. These are technical conversations, not status checks, and you will be expected to hold your own in them.
You will spend time on releases already in flight. That means looking at how a staged rollout is progressing, deciding whether the data supports widening it, and pulling the handle to pause or roll back when it does not. When something fails qualification or a manufacturing partner reports a problem, you are the person who gets the right people on it and keeps it moving until it is closed.
You will spend time building. Writing down a gate that only existed in people's heads, replacing a manual status roll-up with something automated, tightening a handoff between two teams that keeps slipping, updating the release schedule as reality changes.
And you will spend time communicating. Giving leadership a clear read on where releases stand and what the risks are, aligning teams whose priorities are in tension, and making the case for a decision that not everyone will initially agree with.
