Security Engineer, Compliance Penetration Testing

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. Must preserve all substantive info. We need to parse the posting. Key parts: - Description: Application deadline: Sep 20, 2026 (maybe we can include 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 deadline in a short p maybe. - Amazon Stores Security is hiring a Security Engineer for our Application Security Compliance Penetration Testing (CPT) team. In this role you will attack Amazon's services, applications, and websites to find security issues, and work directly with the owning technology teams to get them resolved. CPT's testing is driven by Amazon's regulatory and compliance commitments, which means your findings support Amazon's ability to operate in regulated markets, and your reports are read by external auditors as well as internal teams. You will be in direct contact with teams across a range of business verticals, which gives you first hand knowledge of how Amazon is built and operated at a deep technical level. You will use that knowledge to find new ways to break services, processes, and technologies across the company, and to improve the tooling the team tests with. Engineers in this role are expected to show good judgment in making trade-offs between short term fixes and long term security goals, to navigate ambiguous situations with composure, and to bring a strong sense of customer obsession to the work of keeping Amazon and its customers secure. That's prose for About the role. - Key job responsibilities: list bullet points. - About The Team: includes subsections: Diverse Experiences, Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are more like benefits/culture. Could be placed under Benefits? But we have a Benefits section for actual benefits like health insurance, 401k, etc. The "About The Team" content is more about culture, not benefits. Could be placed under a section like "About the Team" but we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we can decide to include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule if they have content. We can also possibly add other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we shouldn't invent others. So we must map content to those headings. Thus: - About the role: prose describing role. - Responsibilities: list of key job responsibilities. - Requirements: basic qualifications? Or maybe Requirements = Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe combine some skill-based items from qualifications? Could extract skills like scripting language, networking protocols, etc. But we already have Requirements and Qualifications. Might be redundant. However we can still include Skills if there is specific skill content not covered elsewhere. The posting includes "Basic Qualifications" and "Preferred Qualifications". Those could map to Requirements and Qualifications respectively. Skills maybe we can include specific technical skills like "Experience with AWS products and services", "Experience testing service-oriented or RPC-based backend services", etc. But those are already in Preferred Qualifications. Could treat Skills as a subset of Qualifications? But we need to avoid empty sections. If we put Skills, we need specific content. We could extract skill bullets from both basic and preferred qualifications that are skill-oriented. But we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we just include About the role, Responsibilities, Requirements (basic), Qualifications (preferred), Benefits, Pay. Schedule not present, so omit. Skills maybe omit if thin. We need to include Pay: The posting includes salary range: "USA, , - 159,300.00 - 202,400.00 USD annually". Also mentions sign-on payments and RSUs. So we have Pay info. Benefits: The posting includes "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 learn more link. So we have Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include boilerplate like EEO, equal opportunity, legal, etc. Also remove duplicated lines. Also remove application deadline? Could include as a short p maybe under About the role? But instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p for metadata like "Application deadline: Sep 20, 2026". Probably best to put that as a p before sections. We must output only HTML fragment, no /, no markdown fences. Thus structure:

Application deadline: Sep 20, 2026

About the role

... prose ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Pay

... salary range ...

We must ensure we preserve all substantive information. Let's extract. About the role prose: combine the paragraphs after "Amazon Stores Security is hiring..." up to before "Key job responsibilities". Let's capture: "Amazon Stores Security is hiring a Security Engineer for our Application Security Compliance Penetration Testing (CPT) team. In this role you will attack Amazon's services, applications, and websites to find security issues, and work directly with the owning technology teams to get them resolved. CPT's testing is driven by Amazon's regulatory and compliance commitments, which means your findings support Amazon's ability to operate in regulated markets, and your reports are read by external auditors as well as internal teams. You will be in direct contact with teams across a range of business verticals, which gives you first hand knowledge of how Amazon is built and operated at a deep technical level. You will use that knowledge to find new ways to break services, processes, and technologies across the company, and to improve the tooling the team tests with. Engineers in this role are expected to show good judgment in making trade-offs between short term fixes and long term security goals, to navigate ambiguous situations with composure, and to bring a strong sense of customer obsession to the work of keeping Amazon and its customers secure." That's the About the role. Responsibilities bullet list: - Conducting high quality 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 That's it. Requirements (Basic Qualifications): - Bachelor's degree in a STEM field (Science, Technology, Engineering, Mathematics), or experience in IT Security - 2+ years of scripting language, or 2+ years of non-internship professional software development experience - Knowledge of networking protocols such as HTTP, DNS and TCP/IP - 3+ years of hands-on application penetration testing or offensive security assessments across web applications, APIs, or cloud services (non-internship) experience - Experience manually identifying, exploiting, and documenting application vulnerabilities, including authentication, authorization, business logic, and input validation flaws - Experience writing penetration test reports and communicating findings, severity, and remediation guidance directly to software development teams That's all. Qualifications (Preferred Qualifications): - 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 - Experience with AWS products and services - Experience testing service-oriented or RPC-based backend services in addition to web front ends - Experience building security automation, for example scripting or tooling that automates testing, finding triage, reporting, or evidence collection - Experience using AI or LLM-assisted tooling to accelerate security testing - Working knowledge of one or more regulatory or compliance frameworks such as PCI DSS, SOX, MAS TRM, RBI, or GDPR, and how their requirements translate into penetration testing scope and evidence - Familiarity with recognized testing standards such as OWASP ASVS, OWASP Top 10, or PTES - Offensive security certification such as OSCP, OSWE, GPEN, or PenTest+ That's it. Benefits: - 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 Also mention sign-on payments and restricted stock units (RSUs) maybe part of compensation, but we have Pay section for base salary range and sign-on payments and RSUs. So Benefits could exclude those; but we could include sign-on payments and RSUs under Pay. Let's see. Pay: - Base salary range: $159,300.00 - $202,400.00 USD annually - Sign-on payments - Restricted stock units (RSUs) - Final compensation determined based on experience, qualifications, location. We should preserve all substantive info. So include those. We also have "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we could include as a p maybe but it's a reference; could be included in Benefits as a link. But instruction: remove boilerplate? This is not boilerplate; it's a link to learn more. Could keep as a p. But we should not include navigation/legal/EEO etc. The link is fine. We also have location: "USA, , - 159,300.00 - 202,400.00 USD annually". The location seems empty after USA, maybe missing city. We'll just include the salary. We also have "Company - Amazon.com Services LLC" and "Job ID: A10541168". Those are minor metadata; we can drop or fold into short p. Probably drop. We also have "Los Angeles County applicants: ..." and "San Francisco Fair Chance Ordinance". Those are legal/EEO? They are about fair chance; might be considered legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove those sections. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability and