Software Development Engineer, Selling Partner Experience Core Services

About the role

Millions of sellers list products on Amazon. You'll own the services that tell them what a valid listing needs, get their submissions live, and explain what to fix when one fails.

Selling on Amazon comes down to three things a seller has to get right: learn what a valid listing needs, get it submitted, and fix it when something goes wrong. We build for all three, in every marketplace where Amazon operates. Some of our services tell a seller what their category requires before they submit, and whether their product is already in our catalog. Others take listings in and update them, one at a time or thousands at once in a bulk feed, and carry them through to a live offer. When something breaks, ours are the services that say what went wrong, in the seller's own language, while there's still time to fix it.

You'll work on software that every seller and every seller tool passes through. The problems are API design, concurrency, event-driven processing, and data modeling over a catalog whose rules shift by product, by marketplace, and by seller. You'll own what you build, from design through production and the on-call rotation that follows, on a team cutting years of overlapping systems down to fewer and simpler ones. There's room to grow into owning a system end to end.

Key job responsibilities

- Own features end to end, from understanding what the customer needs through design, code, tests, deployment, documentation, and the operations that follow. This includes refactoring and removing software, not only writing new software.

- Design solutions to difficult problems where the goal is clear but the implementation is not. Reduce them to the simplest design that works, and review that design with senior engineers before you build it.

- Operate what you build. Take part in an on-call rotation, hold the line on the latency and availability sellers depend on, drive issues to a permanent root cause fix, and automate recurring work instead of absorbing it.

- Document how your systems are built, tested, secured, and operated, and train new engineers on them. Give useful review feedback to engineers at every level, including engineers more senior than you.

- Work with the customers and partner teams that depend on your services, and make priority calls between new features, operational work, and business commitments. Keep your tools current, including AI-assisted development, and stay accountable for the quality of everything you ship.

A day in the life

You join a team of six to twelve engineers, with a manager and senior engineers who read your designs and your code. A typical day looks like this:

- Participating in stand-ups, sprint planning, and retrospectives

- Writing, testing, and debugging code for ongoing projects

- Reviewing code and incorporating feedback from your team

- Collaborating on technical solutions in design and architecture reviews

- Working with stakeholders to understand requirements