Sr. Security Services SA, AWS Industries - Customer Acceleration Team - Security Specialists

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. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse description. Sections present: - About the role: The description starts with "DESCRIPTION ..." then details about role. Could treat that as About the role. - Responsibilities: There's a "Key job responsibilities" bullet list. - Requirements: There's "BASIC QUALIFICATIONS" and "PREFERRED QUALIFICATIONS". Could combine as Requirements? Or separate Qualifications and Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for About the role (description). Responsibilities (Key job responsibilities). Requirements (BASIC QUALIFICATIONS). Qualifications (PREFERRED QUALIFICATIONS). Skills maybe not explicit separate; could be part of qualifications. Benefits: there is a paragraph about benefits (health insurance, 401k, etc). Pay: there is salary range: "USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually". Also mention sign-on payments and RSUs. Schedule: not mentioned. So we should not include Schedule. We must not include placeholder text like "commensurate with experience". The salary range is specific, so include Pay. We must not repeat job title. Not include Job ID. We must remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove "About The Team" duplicated? There's "About The Team" then later "About The Team Diverse Experiences". That's part of description but we need to keep substantive info. The "About The Team" section includes mission, customers served, etc. That could be part of About the role or maybe separate? But we only have headings list; we could include "About the role" covering the initial description and maybe also team info. However we have separate "About The Team" content that is substantive. Should we create a separate section? Not in allowed headings list. The allowed headings are those listed; we cannot add others. So we must fit content into those headings. Could put team info under About the role or maybe under Responsibilities? Better to put under About the role (makes sense). So About the role will include the initial description plus team mission etc. Responsibilities: list from "Key job responsibilities". Requirements: BASIC QUALIFICATIONS. Qualifications: PREFERRED QUALIFICATIONS. Skills: maybe not needed; we could omit if no specific skills section. Could combine skills into Qualifications? But we have both Requirements and Qualifications headings; we can use Requirements for basic qualifications, Qualifications for preferred qualifications. Skills could be omitted. Benefits: paragraph about benefits. Pay: salary range and sign-on/RSUs. Schedule: none -> omit. We must not include filler like "commensurate with experience". Not present. We must preserve all substantive info; not invent or summarize away detail. So we need to keep details like list of AWS services, etc. We need to format as HTML: use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine initial description and About The Team content (excluding duplicated headings). We'll need to write prose paragraphs. We need to be careful not to lose any specifics. Let's extract About the role content: From description: "The AWS Industries Customer Acceleration Team is building a first-of-its-kind Security Services SA function dedicated to the largest, most complex enterprise customers on the planet. This is a founding role where you will define how AWS goes deep on security services adoption - paired 1:1 with a dedicated Security Specialist Seller, owning architecture and customer outcomes across a named portfolio of our top customers. You will serve as the long-term security architect for enterprise customers within an Industry, designing solutions across detection and response, identity governance, data protection, and network security You will engage CISOs and security engineering leaders as a technical peer - leading architecture reviews, security assessments, and proof-of-concept guidance You will drive measurable adoption of the AWS Security Services portfolio including Security Hub, GuardDuty, Inspector, Detective, IAM Identity Center, Macie, Security Lake, Network Firewall, WAF, and emerging capabilities as they launch You will help customers secure their generative AI and agentic AI workloads by architecting security controls that keep pace with their innovation velocity You will shape the roadmap by translating field patterns and customer friction into structured product feedback This team is pre-playbook. The engagement models you build and the wins you deliver will become the foundation as the function scales" Then later "About The Team You will join a newly formed team of Security Services Solutions Architects within AWS Industries. The mission is to accelerate enterprise customer adoption of AWS security services by pairing deep technical expertise with a dedicated commercial go-to-market motion. You will work closely with account teams, security strategy roles, and AWS Partners to help customers build confident, secure operations on AWS. The customers you serve span Financial Services, Healthcare, Technology, Manufacturing, Energy, Telecommunications, Media, and Retail - and they are navigating real complexity: securing AI at scale, rethinking identity models, and keeping pace with a rapidly evolving threat landscape." Also "About The Team Diverse Experiences AWS values diverse experiences..." etc. That's more about encouraging applicants; could be considered part of About the role? Might be considered boilerplate? It's about diversity encouragement; not exactly boilerplate but could be considered part of company culture. However we have Benefits section for benefits; we could include diversity encouragement under About the role maybe. But we need to preserve all substantive info; it's substantive about AWS values. We'll include it as part of About the role. Also "Why AWS?" etc. That's also substantive about AWS. Could include. But we must avoid too many sections; we can include all that prose under About the role. Now Responsibilities: list from "Key job responsibilities". Let's extract bullet points: - Serve as the long-term security architect for a defined set of enterprise customers within one to two industry verticals guiding their adoption of AWS security services from initial discovery through launch readiness - Operate as one half of a dedicated two-person team with a Security Specialist Seller - you own solution architecture, technical validation, and customer confidence; your seller owns opportunity origination and deal strategy - Drive adoption of the AWS Security Services portfolio (Security Hub, GuardDuty, Inspector, Detective, IAM Identity Center, Macie, Security Lake, Network Firewall, WAF, and more) across three motions: deepening adoption at existing accounts, enabling CISO-org relationships, and supporting competitive displacement - Lead technical conversations with CISOs, VP-level security leaders, and engineering teams including architecture reviews, security assessments, and proof-of-concept guidance - Help customers architect security for generative AI and agentic AI workloads - Translate recurring customer friction, customer obsession, and market evolutions into structured product feedback that shapes the AWS security services roadmap - Publish reusable assets (reference architectures, blogs, workshops, conference sessions) that scale impact beyond individual engagements - Own at least one team-level initiative per year that raises the bar for the function as it scales Also "A day in the life" description includes examples; could be considered part of responsibilities? It's more narrative; but we could include as prose under Responsibilities maybe. However the instruction: Use

  • for any list of duties/requirements/benefits. The "A day in the life" is not a list but prose; we could include as

    under Responsibilities. But we already have a list; we could add a paragraph after the list. But we must preserve all substantive info; we can include that as a paragraph. Now Requirements: BASIC QUALIFICATIONS list: - Experience in a technical role within a sales organization - Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients - Bachelor's degree in computer science, engineering, mathematics or equivalent, or experience in a professional field or military - Experience in IT development or implementation/consulting in the software or Internet industries - Experience within specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics). - Experience in design, implementation, or consulting in applications and infrastructures - Experience with presentations and speaking with executives, IT, management, and developers We need to keep each as list items. Qualifications: PREFERRED QUALIFICATIONS list: - Experience in infrastructure architecture, database architecture and networking - Knowledge of AWS services, market segments, customer base and industry verticals Also maybe "Amazon is an equal opportunity employer..." is EEO boilerplate; we should remove. Now Benefits: paragraph about 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. Learn more about our benefits at https://amazon.jobs/en/benefits." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation; could be part of Pay. 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. USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually" We need to include that as prose maybe with list? Not a list; just paragraph. We must not include "Learn more about our benefits at ..."? That's a link; we can keep as part of Benefits paragraph. Now we need to ensure we don't include any boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove "Los Angeles County applicants:" etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc. Also remove "Our inclusive culture empowers Amazonians..." maybe keep as part of About the role? It's about culture; could be considered substantive. But we already have a lot; we can include it under About the role as part of Why AWS? Actually "Our inclusive culture empowers Amazonians to deliver the best results for our customers." That's a statement; we can keep. But we must be careful not to include too much fluff; but it's substantive. Now craft HTML. We'll have sections:

    About the role

    ... (combined prose)

    Responsibilities

    • ...
    ...

    A day in the life ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    ...

    Pay

    ...

    We must not include Schedule. Now we need to write the prose for About the role, ensuring we keep all specifics. Let's draft About the role paragraph(s): We can split into multiple

    tags. Content to include: - AWS Industries Customer Acceleration Team building first-of-its-kind Security Services SA function dedicated to largest, most complex enterprise customers. - Found