Head of Partner Sales, AWS Industries, Retail and Consumer Goods, AWS Industries Partner Sales

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Description (intro paragraph) - Key job responsibilities (with subheadings: LEADERSHIP, SALES, ALLIANCES, OPERATIONS) - A day in the life (paragraph) - About The Team (paragraph) - Basic Qualifications (list) - Preferred Qualifications (list) - Then there is EEO boilerplate etc to remove. - Then Los Angeles County applicants etc (legal) remove. - Then inclusive culture etc remove. - Then accommodation link remove? It's part of EEO/boilerplate; remove. - Then The base salary range for this position is listed below. Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. 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, CA, San Francisco - 205,600.00 - 278,200.00 USD annually etc. - Then Company - Amazon.com LLC Job ID: A10552259 (metadata to drop or fold into short p). We need to decide sections. We have substantive content: About the role (description intro). Responsibilities (key job responsibilities). Qualifications (basic and preferred). Benefits (they list comprehensive benefits). Pay (they give base salary range and location-specific ranges). Schedule? Not mentioned. So we should not create Schedule section. We need to use

  for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Requirements" maybe combine Basic Qualifications? Or we could have "Qualifications" covering both basic and preferred. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include based on content. We have content for About the role (intro paragraph). Responsibilities (detailed). Qualifications (basic and preferred). Benefits (listed). Pay (salary ranges). Possibly Skills? Not explicitly separate; could be part of qualifications. We could omit Skills if no specific list. We need to avoid filler headings. So we will include sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't repeat job title as heading. Good. We need to use

  • for any list of duties/requirements/benefits. So for responsibilities we have subheadings LEADERSHIP, SALES, ALLIANCES, OPERATIONS each with bullet points? The text includes paragraphs under each heading, not bullet lists. But we can still treat each responsibility as prose? The instruction: Use
    • for any list of duties/requirements/benefits. If not a list, we can use

      . The responsibilities section includes paragraphs under each heading; we could keep them as

      under each

      subheading? But we only allowed

      for section headings; we could still use

      for subheadings? Not specified; but we can just keep them as

      with bold headings? Probably better to keep as

      with the heading text as part of paragraph? However we need to preserve ALL substantive information; we can keep the headings as plain text within

      (like **LEADERSHIP:**) but not as separate heading tags. That's okay. Simplify: For Responsibilities section, we can output

      Responsibilities

      then a

      containing the combined responsibilities text (maybe preserve the subheadings as bold). That would be acceptable. Similarly for Qualifications: we have Basic Qualifications (list) and Preferred Qualifications (list). We could combine into one

      • list? But they are distinct categories. Could output two

        subheadings? Not allowed? We could just make one list with all items, but we need to preserve distinction? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we merge them, we lose the distinction between basic and preferred. That's summarizing away detail. So we should keep them separate. We could use

        Qualifications

        then

        Basic Qualifications:

        then
        • ... items
        then

        Preferred Qualifications:

        then another
        • ... items
        . That preserves info. Similarly Benefits: we have a paragraph describing benefits. Could output as
        • items? The benefits paragraph includes a list inside parentheses: 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. That's a list; we could turn into
          • each item. But we need to preserve ALL substantive information; we can keep as

            with the list as is. However instruction says use

            • for any list of duties/requirements/benefits. So we should convert benefits list to
              • . Let's extract items: - 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, RSUs, sales incentives? That's compensation not benefits. The benefits paragraph also mentions "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." That's compensation; could be part of Pay section. Thus Benefits section: list those four items. Pay section: includes base salary range for position listed below, location-specific ranges, plus mention of sign-on payments, RSUs, sales incentives. Also note final compensation determined based on experience, qualifications, location. So we need to capture all that. We should not include filler like "commensurate with experience". Not present. We need to drop Job ID etc. Could fold into short

                maybe at end:

                Company: Amazon.com LLC

                but that's minor metadata; we could drop it entirely as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

                or drop it." So we can drop it or include a short p. Safer to drop. Now produce HTML. Structure:

                About the role

                ... intro paragraph ...

                Responsibilities

                ... responsibilities text ...

                Qualifications

                Basic Qualifications:

                • 10+ years of enterprise commercial sales experience
                • Experience operating in a matrixed environment and orchestrating cross-functional teams toward a shared revenue outcome.
                • Experience with customer relationship management, especially C-suite level customer engagement
                • Experience owning and delivering a revenue target for a team or territory.
                • 10+ Years owning metrics reporting and defining strategy for senior executives.

                Preferred Qualifications:

                • 5+ years of solving problems with technology in the Energy & Utilities industries experience
                • Experience leading partner, channel, or co-sell sales motions at scale.
                • Experience selling cloud, SaaS, or enterprise technology, and familiarity with AWS Marketplace, cloud migrations, and Generative AI use cases.
                • Track record of building and scaling high-performing sales teams, including developing internal talent into more senior roles.
                • MBA, JD, or equivalent advanced degree or experience.

                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

                Pay

                The base salary range for this position is listed below. Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. Final compensation will be determined based on factors including experience, qualifications, and location.

                • USA, CA, San Francisco - 205,600.00 - 278,200.00 USD annually
                • USA, CA, Santa Monica - 186,900.00 - 252,900.00 USD annually
                • USA, NY, New York - 205,600.00 - 278,200.00 USD annually
                • USA, VA, Arlington - 186,900.00 - 252,900.00 USD annually
                • USA, WA, Seattle - 186,900.00 - 252,900.00 USD annually
                We also need to include the "About The Team" paragraph and "A day in the life". Where to place? Could be part of About the role? The instruction: About the role heading could encompass description and team description. We have intro paragraph (Description) and About The Team paragraph and A day in the life. We could combine them under About the role. But we must preserve all substantive information; we can include them as separate

                under About the role. Thus About the role section: first paragraph (Description), then

                A day in the life ...

                , then

                About The Team ...

                . Ensure we keep the content exactly. Let's extract those paragraphs: Description: "The Sr Manager, Partner Sales leads a team of quota-carrying sales professionals responsible for driving partner-delivered revenue across the Retail and Consumer Goods territory. This is a people-management role that carries a team revenue number and demands pipeline generation, disciplined deal