Sr. Marketing Operations Manager, AWS Marketing Strategy, Operations, and Enablement

We need to output HTML fragment with headings

for 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, we need to decide sections. The description includes: - Description paragraph: "The Sr. Marketing Operations Manager role serves as a critical bridge..." That's about the role. So we can have

About the role

with that paragraph. - Key job responsibilities: bullet list of responsibilities (team player, establish structured collaboration mechanisms, enable understanding, deliver performance reporting). So we can have

Responsibilities

with

• items. - Basic Qualifications: list of qualifications (6+ years professional non-internship marketing experience, using data and metrics, Excel/Tableau, driving direction with cross-functional teams, using data to measure impact, presenting metrics to senior leadership, B2B high-tech). So we can have

  Requirements

  (or Qualifications?). The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements and Qualifications? Usually Requirements = basic qualifications, Qualifications = preferred? Or we could put basic under Requirements and preferred under Qualifications. Also Skills maybe from experience using Excel/Tableau, presenting metrics, etc. But we can also include skills under Skills section. We need to avoid filler sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes salary ranges for various locations: "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..., 401(k) matching, paid time off, and parental leave." So we have Pay and Benefits content. So we should include Pay and Benefits sections. Schedule: Not mentioned. So we should not include Schedule. We also have location specifics: multiple city salary ranges. We need to preserve all substantive information. So we need to include those salary ranges. We need to format Pay section: maybe a

  with the salary ranges. Could also use

  • for each location. Benefits: list of 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 RSUs. We should not repeat job title as heading. Do not put Job ID as heading. We need to remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie/legal. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics? That seems like legal boilerplate about Fair Chance Ordinance. Might be considered boilerplate? It's specific to location but still maybe legal. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Los Angeles County Fair Chance Ordinance text is legal boilerplate; we should remove it. Also the San Francisco Fair Chance Ordinance. Also the accommodation link. Also the "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction; remove. Also remove "Company - Amazon Web Services, Inc." maybe not needed but it's metadata; could be dropped as minor metadata. We need to preserve all substantive information: role description, responsibilities, basic qualifications, preferred qualifications, pay ranges, benefits, sign-on payments, RSUs. We also have "Preferred Qualifications 5+ years of post Master's, full-time relevant industry (professional or military) experience". That's a qualification. We also have "Experience using data and metrics to drive improvements" appears twice; we should deduplicate. We need to output only HTML fragment, no markdown fences. Let's craft sections:

    About the role

    The Sr. Marketing Operations Manager role serves as a critical bridge between AWS Marketing Strategy, Operations, and Enablement (MSOE) to Senior Leaders throughout AWS Marketing. In this role, you will work closely across AWS Marketing to continuously improve processes, drive execution excellence, and deliver marketing results. You will be aligned to an AWS Marketing Team and have direct responsibility for annual planning, budget management, headcount management, rhythms of the business, ad hoc reporting, and enablement. This will be done through your ability to orchestrate the right people and teams to deliver against a defined request, project, or program. This is a data-driven role that has the opportunity to influence marketing programs and the type of data the team looks at to make strategic decisions. This role also has the ability to improve AWS Marketing performance by developing policies, programs, training, and processes to increase team productivity, return on investment, and execution quality.

    Responsibilities

    • Team player comfortable and motivated working in a collaborative environment with the ability to build relationships with key stakeholders at all levels of seniority
    • Establish structured collaboration mechanisms: Build and maintain interlocks with teams such as AWS Marketing, AWS Sales Operations, AWS Sales, and AWS MSOE — ensuring seamless information flow between teams whether joining existing processes or establishing new ones.
    • Enable understanding of marketing strategy and measurement: Translate global marketing strategy into clear narratives explaining marketing measurement framework, measurement methodologies, investment allocation logic, and the rationale behind coverage decisions—providing content and materials that Marketing Leaders can use to ensure their audience whether sellers, partners, or other marketers understands what marketing does, how it's measured, and why.
    • Deliver performance reporting and insights at various altitudes (geo, channel, or segment) and formats (written narrative, PowerPoint presentation, oral presentation): Deliver comprehensive performance commentary and actionable insights to the AWS Marketing Leaders that make marketing's full impact visible, including pipeline results, and key trends in activity.

    Requirements

    • 6+ years of professional non‑internship marketing experience
    • Experience using data and metrics to drive improvements
    • Experience with Excel or Tableau (data manipulation, macros, charts and pivot tables)
    • Experience driving direction and alignment with large cross‑functional teams and agency partners
    • Experience using data and metrics to measure impact and determine improvements
    • Experience presenting metrics and progress to goal to senior leadership
    • Experience in a business‑to‑business (B2B) environment, high‑tech products/services

    Qualifications

    • 5+ years of post‑Master's, full‑time relevant industry (professional or military) experience

    Skills

    • Data analysis and metric‑driven decision making
    • Proficiency with Excel and/or Tableau
    • Cross‑functional team leadership and stakeholder management
    • Presentation and communication of insights to senior leadership
    • B2B high‑tech marketing expertise
    But we need to ensure we don't invent content. The Skills section should be derived from the posting; we can list skills explicitly mentioned: using data and metrics, Excel/Tableau, driving direction with cross-functional teams, presenting metrics to senior leadership, B2B environment. Those are skills. So we can list them as bullet points. We should avoid creating filler like "Skills" if we don't have explicit skill list; but we have those. It's okay. Now Pay section: We have base salary ranges for multiple locations. Also mention sign-on payments and RSUs. Also mention that final compensation based on experience, qualifications, location. We should include that. Thus:

    Pay

    • USA, CA, Mountain View: $130,000.00 – $185,000.00 USD annually
    • USA, CA, San Francisco: $130,000.00 – $185,000.00 USD annually
    • USA, NY, New York: $130,000.00 – $185,000.00 USD annually
    • USA, TX, Austin: $118,200.00 – $160,000.00 USD annually
    • USA, VA, Arlington: $118,200.00 – $160,000.00 USD annually
    • USA, WA, Seattle: $118,200.00 – $160,000.00 USD annually

    Final compensation will be determined based on experience, qualifications, and location. The package includes sign‑on payments and restricted stock units (RSUs).

    Benefits section: We have comprehensive 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 "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we can keep as part of benefits paragraph. Thus:

    Benefits

    • Health insurance (medical, dental, vision, prescription, Basic Life & AD&D, optional Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement)
    • 401(k) matching
    • Paid time off
    • Parental leave
    • Sign‑on payments and restricted stock units (RSUs) – noted also in Pay

    Learn more about Amazon benefits: https://amazon.jobs/en/benefits

    We need to avoid duplication: sign-on payments and RSUs already in Pay; we could keep them only in Pay. Benefits section could just list health insurance, 401(k), PTO, parental leave. The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits? But they are separate headings allowed. We'll keep both. We should not include Schedule. Now ensure we didn't include any boilerplate like EEO, etc. We removed those. Check for duplicated lines: we removed duplicate "Experience using data and metrics to drive improvements" appears twice in Basic Qualifications; we kept only one. Check for any leftover legal text: we removed Los Angeles County and San Francisco Fair Chance Ordinance paragraphs, accommodation link, etc. Check for "Our inclusive culture empowers Amazonians..." that's also boilerplate; remove. Check for "If you have a disability and need a workplace accommodation..." remove. Check for "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. Check for "Company - Amazon Web Services, Inc." drop. Check for "Job ID: A10552605" drop. Now output only HTML fragment. Let's craft final HTML. Be careful to use proper escaping for & etc. Use & if needed. In text we have "and/or". That's fine. We'll output:

    About the role

    ...