Software Developement Engineer 2

Role: SD II

Ideal Candidate

The strongest candidate will likely demonstrate:

• Previous Amazon software development experience, ideally at an SDE II or comparable level
• At least three years of professional software development experience
• Strong Java development skills
• Hands-on backend application and service development
• Experience designing systems using sound architecture and design principles
• Ownership of projects across the full software development lifecycle
• A track record of releasing applications or products to actual end users
• Experience modifying and improving an existing production codebase
• Ability to create operational metrics and use them to evaluate system performance
• Strong examples aligned with Insist on the Highest Standards and Deliver Results
• Ability to work effectively with internal technical and business teams
• Experience mentoring junior software engineers
• Exposure to AI-assisted or AI-related software development

What the Engineer Will Be Expected to Do

 1. Hands-On Software Development

The engineer must be able to:

• Write new production code
• Work effectively within an existing codebase
• Enhance or refactor existing functionality
• Troubleshoot application-level issues
• Deliver maintainable, production-ready software

This is not a role for someone who has moved completely away from coding. The resume should show recent, substantive software development responsibilities.

2. Backend Services

The intake emphasizes Java and system design. Relevant backgrounds may include:

• Backend APIs
• Microservices
• Distributed services
• Event-driven applications
• Workflow or automation platforms
• High-volume data processing
• Internal enterprise applications
• Systems supporting operational decision-making

The team builds automation tools used in warehouse operations to help associates understand how, where, and what work should be performed. The environment processes billions of events and involves technology that the manager described as difficult to find at other companies.

3. Metrics and Operational Visibility

Candidates should have experience creating or integrating metrics into applications or backend services. Recruiters should listen for examples involving:

• Application health metrics
• Service performance indicators
• Operational dashboards
• Logging and monitoring
• Availability or latency measurements
• Business or workflow metrics
• Using metrics to identify defects or improve a service

These examples should be connected to software the candidate personally helped build, rather than only to a separate monitoring or support role.

4. End-to-End Project Ownership

“Drive project from end to end” should be interpreted as evidence that the candidate can move work through multiple stages, such as:

• Understanding requirements
• Evaluating technical options
• Designing a solution
• Developing the application or service
• Testing and reviewing the implementation
• Deploying or releasing the solution
• Monitoring results
• Addressing defects or follow-up improvements

The intake specifically identifies successful candidates as people who have developed applications and shipped products to end users.