We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
Let's parse the posting.
Description: At Amazon we're working... (intro). Then details about Global Internal Audit, role, etc. Then "Up to 20% travel may be required, including international travel. This role can be based in Seattle or Arlington." That's schedule? Travel and location. Not schedule per se but location. Could be part of "About the role" maybe.
Key job responsibilities: list bullet points.
Basic Qualifications: list bullet points.
Preferred Qualifications: list bullet points.
Then EEO boilerplate etc.
Then "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. 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location salary ranges: USA, VA, Arlington - 121,200.00 - 163,900.00 USD annually; USA, WA, Seattle - 121,200.00 - 163,900.00 USD annually.
Thus we have Pay info (salary range). Benefits info (health insurance etc). Schedule? Not explicit schedule; maybe travel up to 20% could be considered schedule? But schedule is about work hours, not given. So we should not create Schedule section unless posting actually states them. It does not state regular schedule/hours. So omit Schedule.
We need sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe Basic Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe knowledge of Microsoft Office etc). Benefits (list). Pay (salary ranges). Ensure we don't create sections with filler.
We must not repeat job title. Use
for section headings.
We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like "lead end-to-end audits from risk assessment and scoping through fieldwork, reporting, and remediation tracking — managing multiple concurrent engagements", etc.
We need to keep bullet points exactly as in posting? We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the content verbatim, but we can format as list items. Should we keep exact phrasing? Likely yes.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, accommodation link, 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? It's a reference; maybe we can keep but it's not required. Safer to keep benefits description but maybe drop the link as it's not substantive? The instruction: preserve ALL substantive information; the link is not substantive but could be considered reference. I'd keep it as part of benefits? Might be considered boilerplate? It's a link to learn more; could be considered navigation. I'd drop it.
Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction.
Also remove "Company - Amazon.com Services LLC Job ID: A10541993". That's metadata.
Now construct HTML.
Sections:
About the role
At Amazon we're working to be the most customer-centric company on earth, and that includes protecting our customers and their data. To get there, we need exceptionally talented, and driven people. Global Internal Audit is a fast paced, dynamic team. We are one of many mechanisms at the company with the aim of continuous improvement. We focus on business and operational processes and the technologies that support them, looking for risks that could harm the company. We seek an Internal Audit Manager to join our AWS Internal Audit team and own the Infrastructure audit domain — covering data centers and operational infrastructure that underpins AWS's global cloud platform. You will be part of a team that values business depth, technical curiosity, and the ability to connect audit findings to business outcomes. The ideal candidate brings strong finance and accounting experience and can assess how infrastructure controls impact revenue integrity, financial reporting, and operational resilience. This is a high-visibility role where you will lead the planning, scoping, execution, and reporting of audits across AWS's infrastructure operations. You will dig deep into complex business and technical environments, identify the full range of risks, and translate them into actionable findings for senior leadership — including the CFO and Audit Committee of the Board of Directors. To be successful in this role, you will demonstrate high judgement, clear communication and a consistent track record of delivering results. You will thrive in a fast-paced environment, work autonomously in an ambiguous environment, and understand the importance of operationalizing key mechanisms and management reporting related to quality and professional practice standards. Up to 20% travel may be required, including international travel. This role can be based in Seattle or Arlington.
That's the intro.
Now Responsibilities:
Responsibilities
- Lead end-to-end audits from risk assessment and scoping through fieldwork, reporting, and remediation tracking — managing multiple concurrent engagements
- Design and execute Risk & Control Matrices (RCMs) for infrastructure-related audits, ensuring testing objectives are aligned with the most significant risks
- Draft audit findings that clearly articulate the risk, control gap, root cause, business impact, and recommended remediation — with proper context for both the audit report and Audit Committee (AC) memo
- Ensure all deliverables meet Internal Audit's quality bar with minimal revision
Now Requirements (Basic Qualifications):
Requirements
- 6+ years of compliance, audit or risk management experience
- 5+ years of program or project Management experience
- Knowledge of Microsoft Office products and applications at an advanced level
- Bachelor's degree or equivalent
Now Qualifications (Preferred Qualifications):
Qualifications
- Project Management Professional (PMP) or equivalent certification
- Experience leveraging technology and implementing lean principles / Six Sigma methodologies to drive process improvements or equivalent
- Master's degree or equivalent
Now Skills: maybe we could combine knowledge of Microsoft Office as skills, but we already have that in Requirements. Could create Skills section for "strong finance and accounting experience", "business depth, technical curiosity", etc. But we might not need separate Skills if we already covered. However instruction: Prefer a few substantive sections over many thin ones. We could merge Skills into Requirements or Qualifications. But we have to decide if we need Skills section. The posting mentions "strong finance and accounting experience", "ability to connect audit findings to business outcomes", "high judgement, clear communication". Those are skills. Could create a Skills section. But we already have Requirements (basic qualifications) and Qualifications (preferred). Might be okay to not have Skills. However the instruction says use sections only when posting has real, specific content for it. The posting does mention skills explicitly: "strong finance and accounting experience", "ability to connect audit findings to business outcomes", "high judgement, clear communication". Those are skills. Could create a Skills section with those bullet points. But we must not invent or summarize away detail. We can extract those phrases.
Let's create Skills section:
Skills
- Strong finance and accounting experience
- Ability to connect audit findings to business outcomes
- High judgement and clear communication
- Consistent track record of delivering results
- Ability to thrive in a fast-paced, ambiguous environment and work autonomously
- Understanding of operationalizing key mechanisms and management reporting related to quality and professional practice standards
But note some of these are also in the About the role paragraph. However we must preserve all substantive information; we can keep them in Skills section as well, but that would duplicate. The instruction says do NOT repeat job title as a heading and do NOT put Job ID etc. It doesn't forbid duplication of content across sections, but better to avoid duplication? Not explicitly forbidden. However "Preserve ALL substantive information" means we must not lose any; duplication is okay but could be considered redundant. I'd rather keep the About the role paragraph as is, and not duplicate in Skills. Instead we could extract skills not already captured elsewhere. The About the role paragraph includes many of those skill sentences. If we create Skills section, we would be repeating. Might be okay but could be considered unnecessary duplication. The instruction: "Prefer a few substantive sections over many thin ones." So better to avoid creating a Skills section if its content is already covered elsewhere. So we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: we need to list the benefits described.
Benefits paragraph: "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."
We can turn into list.
Also mention sign-on payments and RSUs? That's compensation, not benefits. Could be part of Pay? The posting says "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation details. Could be part of Pay section.
Thus Benefits section:
Benefits
- Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and 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
We need to preserve the exact phrasing? The original: "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)". It's a single phrase with commas. Splitting into list items may change phrasing but still preserve info. It's acceptable.
Now Pay section: include salary ranges and sign-on payments and RSUs.
We have two location salary ranges: Arlington and Seattle both same range. Also mention sign-on payments and RSUs.
Thus:
Pay
- Base salary range: $121,200.00 - $163,900.00 USD annually (Seattle, WA or Arlington, VA)
- Sign-on payments and restricted stock units (RSUs) included in total compensation
We could also mention that final compensation based on experience, qualifications, location. That's substantive. Include.
Thus:
Final