Software Development Engineer , Service Resource Management

Amazon.com, Inc.
Seattle, WA, United States
3 days ago
Apply on www.amazon.jobs
Prepare application

Role details

Contract type
Internship / Graduate position
Employment type
Full-time (> 32 hours)
Experience level
Experienced
Experience required
3 years minimum
Compensation
$143,700.0 - $194,400.0
Working hours
Regular working hours

Tech stack

Java (Programming Language) JavaScript (Programming Language) Application Programming Interfaces (APIs) Artificial Intelligence Network Analysis Code Review Software Debugging Python (Programming Language) Software Engineering TypeScript Backend Information Technology
+1 more
Network Optimization

Job description

We are hiring a Software Development Engineer on the Service Resource Management team which is part of Amazon Customer service (CS) to help build a network optimization product, as part of a broader effort to improve how Amazon’s global Customer Service network runs. Our work helps leaders review network performance with more clarity, understand what is driving drift from plan, make better site and resource decisions, and use automation where repeatable decisions can be trusted.

In this role, you will own meaningful parts of the product end to end and work across service behavior, data logic, and product experience to make leadership review, network analysis, and day-to-day operating decisions clearer, faster, and more actionable.

We are looking for an engineer who can make sound decisions with incomplete information, turn partially defined problems into reliable solutions, and improve systems by fixing causes rather than symptoms. You should be comfortable bringing facts, tradeoffs, and risks into the conversation and helping move important decisions toward clear follow-through. Because the team is building toward a more AI-native way of operating, you should also be comfortable evaluating where AI-assisted analysis, automation, rules, and conventional software each fit best in a production workflow.

Key job responsibilities

  • Own the design and delivery of one or more workflows or subsystems, such as analytics services, anomaly-review experiences, investigation tooling, data quality controls, or operator-facing product flows
  • Build reliable backend systems and supporting jobs that turn internal data into clear and trustworthy product behavior, and automate repeatable decision paths where the evidence is strong enough to do so safely
  • Define and document metric logic, edge-case handling, operational behavior, and design tradeoffs so other engineers and business partners can understand, question, and extend your area
  • Improve observability, data quality, and operational health, and remove recurring pain points by fixing root causes rather than treating symptoms
  • Partner with product, domain stakeholders, and peer engineers to clarify requirements, surface tradeoffs early, and turn them into implementation plans
  • Mentor newer engineers through code reviews, design feedback, debugging support, and day-to-day collaboration.
  • Contribute to workflows that use AI-assisted analysis or automation where it improves clarity, speed, or decision quality

A day in the life A typical day in this role is a mix of ownership, technical judgment, and follow-through. You might spend part of the day driving a subsystem change from design through implementation, tracing an issue across service behavior and the underlying data path, and working with product or domain partners to decide what action is justified by the evidence. You will also spend time improving the clarity of the system itself, whether that means simplifying a workflow, tightening a metric definition, or making a recommendation easier for leaders to trust.

About the team The Service Resource Management team builds products that help Amazon Customer Service leaders make better decisions about how the global network runs. We want to be a team that can talk about hard things clearly and early. At this level, that means bringing facts, tradeoffs, and risks into the conversation, challenging assumptions respectfully, moving quickly without outrunning the evidence, and helping the team leave important discussions with clear decisions and durable follow-through.

Requirements

3+ years of non-internship professional software development experience

  • Bachelor’s degree or foreign equivalent in computer science or equivalent
  • Strong programming ability in at least one modern language such as TypeScript, JavaScript, Python, Java, or similar.
  • Experience designing or implementing backend services, APIs, or scheduled processing workflows.
  • Strong communication skills and the ability to work through disagreements with constructive technical reasoning., Experience building operator-facing, analytics, or decision-support products.
  • Experience with AWS services and production observability practices.
  • Experience documenting system behavior, operational expectations, and design decisions for other engineers
  • Experience with time-series metrics, anomaly-review workflows, data quality systems, or related product patterns.

Benefits & conditions

The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits.

USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually

Apply for this position

This job is hosted externally. Click below to view the full posting and apply.

Apply on www.amazon.jobs
Prepare application

Good distractions

Talks and stories from around this role — technically off-topic, practically not.

1:52 min

Structuring and scaling the backend engineering team

Stefan Lingler Stefan Lingler +1 · Coffee With Developers

1:00 min

Misconceptions about TypeScript safety capabilities

Simone Sanfratello · JS Congress

3:39 min

Addressing code review surrender and process exploitation

Laura Tacho Laura Tacho · World Congress 2026 Europe

1:06 min

Developer experience and project variety at scale

Alexandra Petri · World Congress 2023

1:12 min

Choosing TypeScript for complex backend applications

Maximilian Otto Maximilian Otto · World Congress 2024

3:16 min

Selecting diverse programming languages across backend services

Markus Dorner · Coffee With Developers

Videos

See all

Related articles

See all