Security Engineer II, Stores AppSec

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description. First, job title is not needed as heading. We need to include sections: - About the role: likely the introductory paragraph(s) describing role. The description starts: "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 about the role. - Responsibilities: "Key job 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 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 format as list. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe combine? But we have separate sections for Skills; we could list technical skills from qualifications. However we could also put skills under Requirements? The instruction says use sections as appropriate. We have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. Skills maybe not needed separately if covered. But we could still include Skills if there is explicit skill list. The posting includes "Knowledge of networking protocols such as HTTP, DNS and TCP/IP", "Knowledge of industry-based security vulnerabilities and remediation techniques". Those could be skills. Also "Experience with AWS products and services", etc. Might be better to put under Skills. But we need to avoid filler sections. We'll include sections that have content. Pay: The posting includes salary ranges: "USA, NY, New York - 159,300.00 - 212,800.00 USD annually" and "USA, TX, Austin - 159,300.00 - 202,400.00 USD annually". Also mentions sign-on payments and RSUs, benefits. So we have Pay info. Benefits: The posting mentions comprehensive benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits. So we have Benefits. Schedule: Not mentioned explicitly. No schedule info. So we should not include Schedule. Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine knowledge items), Benefits, Pay. We need to ensure we don't repeat job title. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like salary ranges, benefits specifics. We need to remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe keep as part of benefits? It's a link; but it's not substantive detail? Might be considered boilerplate. Probably remove. We need to keep the salary ranges and mention sign-on payments and RSUs. We need to keep benefits list: 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, parental leave. We need to keep the "Work/Life Balance" maybe as part of benefits? It's a benefit description. Could include under Benefits as prose. We need to keep "Training & Career Growth", "Inclusive Team Culture", "Diverse Experiences", "Why Amazon Security?" maybe those are not required sections but could be part of About the role or separate? The instruction says include a section only when posting has real specific content for it. Those are sections like "About The Team" etc. Could be considered as part of About the role or maybe we could create a section "About the Team". But the allowed headings list includes only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. So we can incorporate team culture etc into About the role or Benefits? Probably About the role can include description of team and culture. Thus we will craft About the role paragraph(s) covering role description, team culture, why Amazon security, inclusive team culture, training & career growth, work/life balance. Now we need to produce HTML. Let's draft:

  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 internal technology teams. The position offers challenging technical and leadership opportunities, working closely with Information Security teams and providing technical leadership and advice across Amazon. You will engage with various business verticals to gain deep technical insight into how Amazon is built and operated, and leverage that knowledge to find new ways to break services, processes, and technologies. Engineers must show exemplary judgment in balancing short‑term fixes with long‑term security and business goals, demonstrate resilience in ambiguous situations, and provide thought leadership through discovery, invention, and innovation. A strong sense of customer obsession is essential to keep Amazon and its customers secure.

  That's about role. Now Responsibilities:

  Responsibilities

  • Comfortable with high ambiguity, exercising strong ownership, and making high‑judgment decisions focused on what is best for Amazon’s customers.
  • Thriving in navigating complex stakeholder engagements.
  • 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 resolution of discovered security findings.
  Now Requirements (Basic Qualifications):

  Requirements

  • 3+ years of programming in Python, Ruby, Go, Swift, Java, .Net, C++ or similar object‑oriented language.
  • 2+ years of scripting, programming, and security code review in a common programming language (non‑internship).
  • 2+ years of troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non‑internship).
  • 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.
  Now Qualifications (Preferred Qualifications):

  Qualifications

  • 2+ years of any combination of: threat modeling experience, secure coding, identity management and authentication, software development, cryptography, system administration and network security.
  • Experience with 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.
  Now Skills: Could list specific technical skills from above but we already covered. Maybe we can create a Skills section summarizing technical proficiencies: programming languages, scripting, command line, AWS, networking, threat modeling, secure coding, etc. But to avoid duplication, we could skip Skills if content already covered. However instruction says prefer a few substantive sections over many thin ones. We already have many sections; maybe we can combine Skills into Requirements/Qualifications. But we already have those. So we could omit Skills section. Now Benefits:

  Benefits

  • Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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.
  • Parental leave.
  • Work‑life harmony: flexible work hours and arrangements.
  • Ongoing DEI events, learning experiences, and inclusive team culture.
  • Training and career‑growth resources, knowledge‑sharing, and career‑advancing opportunities.
  Now Pay:

  Pay

  The base salary range for this position is:

  • USA, NY, New York – $159,300.00 – $212,800.00 USD annually
  • USA, TX, Austin – $159,300.00 – $202,400.00 USD annually

  Amazon’s total compensation package includes sign‑on payments and restricted stock units (RSUs). Final compensation is determined based on experience, qualifications, and location.

  We should not include Schedule. Now ensure we didn't include any boilerplate like EEO, accommodation link, etc. We removed those. Check for any leftover boilerplate: The phrase "Amazon is an equal opportunity employer..." removed. The accommodation link removed. The "If the country/region you’re applying in isn’t listed..." removed. The "Learn more about our benefits at https://amazon.jobs/en/benefits." removed. The "Company - Amazon.com Services LLC" maybe not needed; we could drop.