Senior Software Development Engineer, DSO (Demand Science Optimization)
Posted 1
view
Amazon decides how many devices to build, where to ship them, and what to charge from a layer of inputs this team owns. You will lead the rebuild of that layer — agent-first, and designed so the systems reading it can't disagree with each other. That means the architectural calls: how these services should be designed, what they have to meet before we call them operationally ready, and where manual work gets replaced by automation.
The team's scope is growing, and you will shape how it grows.
What you will work on:
- Setting technical direction and architecture across the services the team owns
- Raising the engineering bar through design review, code review, and operational standards
- Aligning with engineers on partner teams on shared interfaces and ownership boundaries
- Replacing recurring manual work with automation and better design
- Mentoring engineers as they grow into deeper technical ownership
Key job responsibilities
- Design, build, and operate the most technically complex parts of the input layer, using AI-assisted development and agents to replace work that is manual today
- Set technical direction and architecture, including decisions to consolidate, rebuild, or retire systems
- Lead design and code reviews, and define the operational standards a service meets before the team owns it
- Partner with product managers, scientists, and engineers on other teams to turn requirements into designs and to align on shared interfaces and ownership boundaries
- Mentor engineers through design guidance, written documentation, and pairing
A day in the life
Your primary focus is the layer of inputs that Amazon's device planning, forecasting, and inventory systems all read from. A handful of services, and every build and allocation decision downstream depends on them agreeing.
You're rebuilding that layer to easily allow stakeholders to manage a whole product line's inputs for high-impact decisions. You'll make the calls on what that architecture looks like.
About the team
We own the inputs Amazon's device planning, forecasting, and inventory systems depend on — the data behind what gets built, where it ships, and at what price. Our customers are internal: the planners who own each product line, finance partners, and the science and engineering teams downstream. You'll work with them directly.
We're rebuilding it so each input lives in one place and stays correct without someone tending it, moving toward agent-based interfaces.
The team's scope is growing, and you will shape how it grows.
What you will work on:
- Setting technical direction and architecture across the services the team owns
- Raising the engineering bar through design review, code review, and operational standards
- Aligning with engineers on partner teams on shared interfaces and ownership boundaries
- Replacing recurring manual work with automation and better design
- Mentoring engineers as they grow into deeper technical ownership
Key job responsibilities
- Design, build, and operate the most technically complex parts of the input layer, using AI-assisted development and agents to replace work that is manual today
- Set technical direction and architecture, including decisions to consolidate, rebuild, or retire systems
- Lead design and code reviews, and define the operational standards a service meets before the team owns it
- Partner with product managers, scientists, and engineers on other teams to turn requirements into designs and to align on shared interfaces and ownership boundaries
- Mentor engineers through design guidance, written documentation, and pairing
A day in the life
Your primary focus is the layer of inputs that Amazon's device planning, forecasting, and inventory systems all read from. A handful of services, and every build and allocation decision downstream depends on them agreeing.
You're rebuilding that layer to easily allow stakeholders to manage a whole product line's inputs for high-impact decisions. You'll make the calls on what that architecture looks like.
About the team
We own the inputs Amazon's device planning, forecasting, and inventory systems depend on — the data behind what gets built, where it ships, and at what price. Our customers are internal: the planners who own each product line, finance partners, and the science and engineering teams downstream. You'll work with them directly.
We're rebuilding it so each input lives in one place and stays correct without someone tending it, moving toward agent-based interfaces.