Software Development Engineer, Amazon

• The work suits an engineer who likes a hard, loosely specified problem and wants to turn it into a designed, tested, cleanly operated system
• Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying
• 3+ years of non-internship professional software development experience
• 2+ years of non-internship experience designing or architecting (design patterns, reliability, and scaling) new and existing systems
• Experience programming with at least one software programming language: Java, Python, or TypeScript
• Bachelor's degree in Computer Science, a related field, or equivalent work experience
• This role requires you to be a national of an EU Member state

Desirable

• Amazon Security operates at a scale few engineers ever get to work at, and Epoxy is the team that builds the automation making that scale possible
• We are hiring a Software Development Engineer to build and operate the platforms that put threat detection on the AWS account fleet, remediate risk automatically, and give security responders the tooling they act on
• You do not need a security background. You need to be good at building systems
• Epoxy sits inside AWS Security and own four things. We onboard threat detection across the internal account fleet and audit that coverage continuously
• We give partner detection teams the machinery to remediate what they find, automatically, without a human in the path
• We run the foundational services the rest of AWS Security operations depends on: communications, workflow orchestration, data enrichment, and secure access. And because AWS Security runs these products on itself before anyone else does, we find the interesting failures first
• This is a build-it-and-run-in team, and we mean it in both directions. You own the operational health of what you ship, and we protect the capacity to do that properly: on-call is a real rotation with a bounded share in each sprint, not an ambient expectation on top of feature work
• You will work in Python and TypeScript on AWS primitives, and you will leave the systems you touch better than you found them
• Design and deliver features and components that solve difficult problems across AWS Security Epoxy's services, working independently from a well understood business goal even when the implementation is not fully specified
• Own the operational excellence of the systems you work on: instrument them, alarm on the right signals, and drive down operational load through automation rather than manual toil
• Write high quality, well tested code that meets a high engineering bar, and clear documentation and runbooks that let others maintain and extend your work
• Participate in the team on-call rotation, supporting our services and responding to high-severity requests from AWS Security operations and Partner Teams. You resolve issues, then eliminate their contributing causes with permanent fixes
• Improve the resiliency, scalability, and safety of systems that operate at very high scale, making sound trade-offs between short-term needs and long-term maintainability
• Raise the bar through code reviews, design reviews, operational readiness reviews, and post-incident analyses, giving useful and actionable feedback including to more senior engineers
• Mentor newer teammates and interns, and begin to influence partner teams by helping them adopt sound engineering and operational practices
• You pick up a feature request on one of Epoxy's services, break it into deliverable pieces, and ship it incrementally with tests and monitoring in place
• You review a teammate's design, ask the questions that surface a hidden resiliency risk, and help simplify the approach before code is written
• On an on-call week, you triage a high-severity issue, mitigate customer impact quickly, then open the follow-up work to make sure that class of failure cannot recur
• You spot a piece of manual operational work your team repeats every week and replace it with automation, giving the whole team time back
• You sync with a partner detection or response team to understand how they use an Epoxy capability, and feed what you learn back into the roadmap