Network Development Engineer, Amazon Customer Service
Posted Updated
Description
This role sits at the intersection of live network troubleshooting, systems design, and cross-team coordination. You'll join a 24x7 on-call rotation, which means you'll be one of the engineers who picks up the phone when something is broken and drives it to resolution alongside application, systems, and production control teams. A lot of the problems you'll solve are high-ambiguity by design: voice calls where the audio is bad but the network looks healthy, systems configuration issues that only show up under load, situations where applying pattern recognition across prior incidents is what narrows the root cause from a dozen possibilities to one.
The work isn't just reactive. You'll design and architect network and systems improvements, coordinate tech change management with business operations, and partner with business owners, security engineers, and other tech teams to innovate on how transport across public and private networks runs for our users. You'll troubleshoot across team and organizational boundaries, making sure the transport layer holds up regardless of which side of the boundary a problem lives on.
What sets this role apart: it's a seat for someone who likes depth in network engineering but also wants to build and improve the systems they operate. If you enjoy solving the problem where nobody can tell you what's wrong, and you also want to leave the system better than you found it, this is the role.
Key job responsibilities
- Design and architect network and systems improvements to enhance transport infrastructure
- Coordinate technology change management initiatives with business operations teams
- Partner with business owners, security engineers, and cross-functional tech teams to innovate network transport solutions
- Troubleshoot complex issues across team and organizational boundaries to ensure transport layer reliability
- Operate and maintain network systems while continuously improving their performance and resilience
- Solve ambiguous technical problems where root causes are not immediately apparent
- Leave systems in better condition than found through proactive optimization and enhancement
- Build and improve the systems you operate on, balancing reactive support with strategic improvements
- Ensure transport layer stability regardless of where problems originate within the organization
A day in the life
Most days, your focus is design and improvement: writing architecture docs for a network upgrade, coordinating a change window with business operations, pairing with a security engineer on how a new control affects transport, or reviewing a teammate's design. When you're on call, the shape of the day flips. You're first-responder on incidents, driving root cause across teams and keeping stakeholders updated. Expect a few focused meetings a day and heads-down time for the rest. Beyond the regular work, there's room to pick up longer-horizon programs, mentor newer engineers, or lead a cross-team initiative when something interests you.
About the team
We're a small team that wears many hats. Most of us have a primary specialty: network engineering, software development, security consultation, or governance. We talk constantly, whether we're pattern-matching a weird incident, pairing on a design, or walking through why a network behaves one way in one site and differently in another. Our mission is to build and run the systems that keep a global operations program moving. Our customers are the program leaders, operating teams, security reviewers, and business owners we work with. We solve the hard problems together and we don't let each other go it alone.
The work isn't just reactive. You'll design and architect network and systems improvements, coordinate tech change management with business operations, and partner with business owners, security engineers, and other tech teams to innovate on how transport across public and private networks runs for our users. You'll troubleshoot across team and organizational boundaries, making sure the transport layer holds up regardless of which side of the boundary a problem lives on.
What sets this role apart: it's a seat for someone who likes depth in network engineering but also wants to build and improve the systems they operate. If you enjoy solving the problem where nobody can tell you what's wrong, and you also want to leave the system better than you found it, this is the role.
Key job responsibilities
- Design and architect network and systems improvements to enhance transport infrastructure
- Coordinate technology change management initiatives with business operations teams
- Partner with business owners, security engineers, and cross-functional tech teams to innovate network transport solutions
- Troubleshoot complex issues across team and organizational boundaries to ensure transport layer reliability
- Operate and maintain network systems while continuously improving their performance and resilience
- Solve ambiguous technical problems where root causes are not immediately apparent
- Leave systems in better condition than found through proactive optimization and enhancement
- Build and improve the systems you operate on, balancing reactive support with strategic improvements
- Ensure transport layer stability regardless of where problems originate within the organization
A day in the life
Most days, your focus is design and improvement: writing architecture docs for a network upgrade, coordinating a change window with business operations, pairing with a security engineer on how a new control affects transport, or reviewing a teammate's design. When you're on call, the shape of the day flips. You're first-responder on incidents, driving root cause across teams and keeping stakeholders updated. Expect a few focused meetings a day and heads-down time for the rest. Beyond the regular work, there's room to pick up longer-horizon programs, mentor newer engineers, or lead a cross-team initiative when something interests you.
About the team
We're a small team that wears many hats. Most of us have a primary specialty: network engineering, software development, security consultation, or governance. We talk constantly, whether we're pattern-matching a weird incident, pairing on a design, or walking through why a network behaves one way in one site and differently in another. Our mission is to build and run the systems that keep a global operations program moving. Our customers are the program leaders, operating teams, security reviewers, and business owners we work with. We solve the hard problems together and we don't let each other go it alone.