Senior Security Engineer, Amazon

• Experience developing software code in one or more programming languages (java, python, etc.)
• Knowledge of information security technologies such as security design review, threat modeling, risk analysis, and software testing techniques
• Knowledge of security technology and concepts (Authentication, Authorization, Single sign-on, Cryptography, etc.)
• Experience in risk assessment and enabling organizations to make security decisions
• Experience working with operations and business teams to communicate problem impacts and understand business requirements
• Experience in enterprise software
• Bachelor's degree or above in Computer Science, Computer Engineering, Cybersecurity, or other related discipline
• 5+ years in professional penetration testing, source code auditing, bug hunting, or competitive CTF
• Demonstrated ability to find non-trivial vulnerabilities through offensive testing of web applications and services and through source code review
• Demonstrated mastery of two or more genuinely complex security domains such as networking, workload and tenant isolation, web application and API security, IAM, or cryptography, deep enough to find issues others miss and to encode that expertise into automation
• Experience building and steering AI agents to do useful security work, and reasoning about how those same agentic systems can be attacked
• Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed, we encourage you 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

Desirable

• We are looking for a Senior Security Engineer to join Point-in-Time Security Testing, AWS's expert security assurance function for the launches and architectures where security automation alone is not enough
• You will be a technical leader on a team, owning complex security testing engagements end-to-end, applying human judgment where it changes security outcomes and building automation for everything else
• Own security for a portfolio of testing engagements across your team and partner-orgs, as well as leading individual complex engagements. Set the testing strategy across interconnected microservice architectures, successive launch iterations, and cross-service campaigns, and decide where to spend expert effort across the whole service portfolio
• Perform penetration testing and AI-augmented source code review of complex proprietary AWS software, directing the tooling at trust boundaries, abuse cases, and attack paths it would not reach on its own, confirming what it reports, and setting the methodology your team follows when they do the same
• Take each agreed risk hypothesis to a documented conclusion, whether that means demonstrating the issue with proof-of-concept code, ruling out the attack path with sufficient evidence, or identifying a weakness in a shared mechanism or detection that affects services beyond the one under test
• Take on engagements where the customer case is understood but no security strategy exists yet, bring clarity to the ambiguity, and define the approach others will reuse. Challenge what a scope document assumes and identify what it misses, then keep the engagement moving when conditions change by building alternative test paths, re-scoping, and parallelizing work with dependent teams
• Trace attack paths across chained components and demonstrate compound risk that stays invisible when components are tested in isolation, including risk that crosses organizational and ownership boundaries
• Produce clear engagement results that record what you tested, why you chose those tests, what you found or ruled out, the limitations of the work, and the risk that remains, and write for non-engineering audiences in your domain when the decision sits with them
• Lead communication with developers, AppSec engineers, and other stakeholders when the scope is ambiguous or a fix is not straightforward, validate the fixes, work as an embedded security tester inside the development lifecycle when a launch calls for it, and lead escalations to closure with Senior Managers and Principal Engineers when a fix or a risk decision stalls
• Build the frameworks, runbooks, and rubrics that let the whole team test a new problem domain repeatably, not only automation for a single harness. Tune the harnesses that raise the precision of the team's AI tooling, measure where they produce false positives or miss attack patterns, and generalize what works into a mechanism the team adopts
• Leave reusable mechanisms behind, such as fuzzers, integration security tests, detection rules, tooling, or documented methodology, track their adoption, and where the work depends on teams with their own priorities, build the mechanisms that get security outcomes prioritized and tracked to delivery
• Set the peer-review bar for the team. Review test plans, scopes, runbooks, and reports from peers and other teams, question coverage gaps, add the missing test cases, and ensure the work fits into the bigger picture and stays extensible and low-cost to adopt
• Lead multi-engineer engagements and mentor multiple engineers across your own and related teams, are sought out for your expertise, and participate in promotion assessments