Security Engineer II, Stores AppSec
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse content:
- Description: "Application deadline: Sep 26, 2026 Amazon’s Stores AppSec Team is seeking a Security Engineer to help keep Amazon secure for its customers. In this role, you will attack Amazon’s services, applications, and websites to discover security issues and report them to our internal technology teams. This position will provide you with challenging opportunities, both technologically and as a leader, but will also be a great deal of fun if hacking Amazon alongside a team of highly skilled individuals sounds exciting to you. A Security Engineer at Amazon is expected to be strong in multiple domains. Engineers in this role work closely with teams throughout Information Security, as well as provide technical leadership and advice to teams and leaders throughout Amazon. You will be in direct contact with teams in a variety of business verticals, giving you first hand knowledge about how Amazon is built and how it operates at a deep, technical level. Additionally, you will leverage the knowledge you gain about Amazon to find new ways to break services, processes, and technologies throughout the company. Engineers in this role must show exemplary judgment in making technical trade-offs between short-term fixes and long-term security and business goals. You will demonstrate resilience and navigate ambiguous situations with composure and tact. You will be expected to provide thought leadership for the organization as you discover, invent, and innovate throughout the course of your duties. Above all else, a strong sense of customer obsession is necessary to focus on the ultimate goal of keeping Amazon and its customers secure."
That's basically about the role. Could be "About the role". We'll put that as About the role
and then
with that content (maybe trimmed). Remove "Application deadline: Sep 26, 2026" maybe as metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
for Application deadline. - Key job responsibilities: list of bullet points: "Your team has an emphasis on fast paced, highly visible engagements. You will be comfortable with a high level of ambiguity, exercising strong ownership, and be able to make high judgement decisions focusing on what is best for Amazon's Customers. Additionally, you should thrive in navigating complex stakeholder engagements a skill integral to the teams success. In This Role, You Will Primarily Be Conducting high quality application security reviews and penetration tests independently, or as part of a team Creating detailed engagement plans and thoroughly documenting findings, gaps, and remediation recommendations Contributing to team tooling, innovation, and improvements Communicating and collaborating with partner teams, service owners, Information Security, and senior leadership to influence, prioritize, and drive the resolution of discovered security findings" We can turn into
- items. Probably each sentence is a responsibility.
- About The Team: includes subsections: Diverse Experiences, Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. This could be considered "About the team" but not in allowed headings. We could maybe treat as "About the role" or maybe "Responsibilities"? But we have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About The Team" content could be considered part of "About the role" or maybe "Qualifications"? Not exactly. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for About the Team, but not a designated heading. Could we map it to "About the role"? Already used. Could we create a new heading? Not allowed; only those headings. So we must either fold that content into existing sections (like About the role) or drop it. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. We could add it under "About the role" as additional paragraphs.
- Basic Qualifications: list of items. That's "Requirements" or "Qualifications". We have both Requirements and Qualifications headings allowed. We could put Basic Qualifications under "Requirements". Preferred Qualifications under "Qualifications". Or we could combine.
- Skills: maybe we can extract skills from qualifications: programming languages, networking protocols, etc. Could create a Skills section.
- Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. That's benefits.
- Pay: "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." Then later: "USA, , - 159,300.00 - 202,400.00 USD annually". So we have pay range.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't repeat job title as heading. Not include Job ID.
We need to strip boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines.
We need to preserve all substantive info.
Let's craft content.
First, maybe a short metadata paragraph: "Application deadline: Sep 26, 2026". Could be a
before sections. Now sections:
About the role
Amazon’s Stores AppSec Team is seeking a Security Engineer to help keep Amazon secure for its customers. In this role, you will attack Amazon’s services, applications, and websites to discover security issues and report them to our internal technology teams. This position will provide you with challenging opportunities, both technologically and as a leader, but will also be a great deal of fun if hacking Amazon alongside a team of highly skilled individuals sounds exciting to you. A Security Engineer at Amazon is expected to be strong in multiple domains. Engineers in this role work closely with teams throughout Information Security, as well as provide technical leadership and advice to teams and leaders throughout Amazon. You will be in direct contact with teams in a variety of business verticals, giving you first hand knowledge about how Amazon is built and how it operates at a deep, technical level. Additionally, you will leverage the knowledge you gain about Amazon to find new ways to break services, processes, and technologies throughout the company. Engineers in this role must show exemplary judgment in making technical trade-offs between short-term fixes and long-term security and business goals. You will demonstrate resilience and navigate ambiguous situations with composure and tact. You will be expected to provide thought leadership for the organization as you discover, invent, and innovate throughout the course of your duties. Above all else, a strong sense of customer obsession is necessary to focus on the ultimate goal of keeping Amazon and its customers secure.
Maybe also include the "About The Team" content here as additional paragraphs. Add after that: "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.
" etc. We'll incorporate the subpoints. Now Responsibilities:Responsibilities
- Your team has an emphasis on fast paced, highly visible engagements.
- You will be comfortable with a high level of ambiguity, exercising strong ownership, and be able to make high judgement decisions focusing on what is best for Amazon's Customers.
- Additionally, you should thrive in navigating complex stakeholder engagements, a skill integral to the team's success.
- Conducting high quality application security reviews and penetration tests independently, or as part of a team.
- Creating detailed engagement plans and thoroughly documenting findings, gaps, and remediation recommendations.
- Contributing to team tooling, innovation, and improvements.
- Communicating and collaborating with partner teams, service owners, Information Security, and senior leadership to influence, prioritize, and drive the resolution of discovered security findings.
Requirements
- 3+ years of programming in Python, Ruby, Go, Swift, Java, .Net, C++ or similar object oriented language experience
- 2+ years of scripting, programming, and security code review in a common programming language (non-internship) experience
- 2+ years of troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non-internship) experience
- Bachelor's degree in a STEM field (Science, Technology, Engineering, Mathematics), or 2+ years of IT Security experience
- Knowledge of networking protocols such as HTTP, DNS and TCP/IP
- Knowledge of industry-based security vulnerabilities and remediation techniques
Qualifications
- 2+ years of any combination of the following: threat modeling experience, secure coding, identity management and authentication, software development, cryptography, system administration and network security experience
- Knowledge of command line tools to troubleshoot protocols, analyze log outputs, or automate basic tasks
- Experience with AWS products and services
- Experience in scripting, programming, or security code reviewing in a common language, such as Python, Java, or C++
- Experience performing security activities across one or more phases of the software development lifecycle (SDLC), such as security design review, threat modeling, secure code review, and security testing
Benefits
- Sign-on payments and restricted stock units (RSUs)
- Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans)
- Employee Assistance Program (EAP), Mental Health Support, Medical Advice Line
- Flexible Spending Accounts
- Adoption and Surrogacy Reimbursement coverage
- 401(k) matching
- Paid time off
- Parental leave
Pay
The base salary range for this position is $159,300.00 – $202,400.00 USD annually. The total Amazon package includes sign-on payments and restricted stock units (RSUs), with final compensation determined based on experience, qualifications, and location