Global Account Manager, Media & Entertainment, Games and Sports

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Keep substantive info. We need to parse the description. Let's extract sections: - About the role: description paragraph(s) about role: "AWS is seeking a world class sales professional to manage and grow our global business relationship with one of the largest entertainment and technology companies in the world. This Global Account Manager role will have a primary focus on the customer’s media and entertainment lines of business, responsible for business development and account growth for this global account. The ideal candidate brings deep industry expertise, a builder mindset, and the ability to engage C-suite stakeholders with credible, outcome-driven conversations — while thriving in a highly collaborative, cross-functional environment. The pursuit and management of net new customer relationships and incremental line-of-business opportunities will be critical to the success of this role. You will build and maintain key relationships, develop and manage opportunities, monitor deployment projects and engage resources to scale. You will define a CXO relationship strategy across the account and engage AWS senior leadership executive sponsorship and alignment, advancing a strategic business partnership and maintaining a trusted advisor relationship at all levels of the customer organization." That's about the role. - Key job responsibilities: list bullet points: "The Global Account Manager (GAM) is responsible for teaming with the customer’s Line-of-Business (LOB) and IT Organizations to build strategic relationships across the account. The GAM is responsible for selling at the most strategic levels within the account and implementing a broad strategy for earning customer trust and service implementation. The GAM will work with all appropriate AWS resources (Executives, Solution Architects, Business Development, Marketing, Partners, Support, Service teams and Professional Services) to support customer interests. This includes dotted line responsibility for downstream sales and technical resources that may be geographically distributed." Then there is a subheading "Business Skills" with bullet list: "Strategic account planning and executive relationship building Ability to articulate business value for cloud solutions Strong collaboration across cross-functional teams Experience with partner ecosystem Excellent presentation and communication skills" Then "Cloud Knowledge": bullet list: "Understanding of core cloud services relevant to sports workloads (compute, storage, databases, analytics, ML/AI, security) Familiarity with cloud partner ecosystems and Professional Services capabilities Ability to connect customer business challenges to cloud-based solutions" Then "Opportunity Development & Execution": bullet list: "Drive opportunities with a focus on measurable business outcomes Collaborate with industry specialists to evangelize cloud services, partner solutions, and Professional Services. Participate in executive engagements with C-suite stakeholders" Then "A day in the life" maybe not needed? It's a heading but no content? Actually after that there is "About The Team" etc. Those are more about AWS culture, not specific to role. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it. The "About The Team" etc are generic AWS culture; maybe not specific to role. Could be considered boilerplate? It's not exactly boilerplate but it's generic company info. Might be considered not specific to role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" etc might be considered generic but not necessarily boilerplate. However they are not specific to the role; they are about AWS culture. The instruction says prefer a few substantive sections over many thin ones. Could combine into a "About AWS" section? But we have no explicit heading for that. The sections we can use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities (the bullet points), Skills (Business Skills, Cloud Knowledge, Opportunity Development & Execution could be under Skills), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits (benefits description), Pay (salary ranges), Schedule? Not mentioned. So we omit Schedule. We need to not repeat job title as heading. Use

for each section. We need to use

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

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should cut out the EEO statements, Los Angeles County specifics, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc. Job ID: A10544569". Also remove "Basic Qualifications" heading? Actually we need to use

  for section headings like Requirements, Qualifications, Skills, Benefits, Pay. So we can map Basic Qualifications to Requirements (

  Requirements

  ) and Preferred Qualifications to Qualifications (

  Qualifications

  ). The "Basic Qualifications" and "Preferred Qualifications" content should be placed under those sections. We need to keep the content exactly as given, but we can format as lists. Let's extract each piece. About the role: The paragraph(s) before "Key job responsibilities". We'll combine into a

  . Responsibilities: The bullet points under "Key job responsibilities" and subheadings Business Skills, Cloud Knowledge, Opportunity Development & Execution. Actually those are more like skills/responsibilities. But we can treat them as part of Responsibilities? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate Skills section. So we should put Business Skills, Cloud Knowledge, Opportunity Development & Execution under Skills. The responsibilities bullet points (the first three bullets) under Responsibilities. Thus:

  About the role

  AWS is seeking a world class sales professional to manage and grow our global business relationship with one of the largest entertainment and technology companies in the world. This Global Account Manager role will have a primary focus on the customer’s media and entertainment lines of business, responsible for business development and account growth for this global account. The ideal candidate brings deep industry expertise, a builder mindset, and the ability to engage C-suite stakeholders with credible, outcome-driven conversations — while thriving in a highly collaborative, cross-functional environment. The pursuit and management of net new customer relationships and incremental line-of-business opportunities will be critical to the success of this role. You will build and maintain key relationships, develop and manage opportunities, monitor deployment projects and engage resources to scale. You will define a CXO relationship strategy across the account and engage AWS senior leadership executive sponsorship and alignment, advancing a strategic business partnership and maintaining a trusted advisor relationship at all levels of the customer organization.

  Responsibilities

  • The Global Account Manager (GAM) is responsible for teaming with the customer’s Line-of-Business (LOB) and IT Organizations to build strategic relationships across the account.
  • The GAM is responsible for selling at the most strategic levels within the account and implementing a broad strategy for earning customer trust and service implementation.
  • The GAM will work with all appropriate AWS resources (Executives, Solution Architects, Business Development, Marketing, Partners, Support, Service teams and Professional Services) to support customer interests. This includes dotted line responsibility for downstream sales and technical resources that may be geographically distributed.

  Skills

  We need to list Business Skills, Cloud Knowledge, Opportunity Development & Execution as sub-items? Could be separate
  with each bullet being a skill. The original had headings but we can just list them as bullet points. Business Skills: - Strategic account planning and executive relationship building - Ability to articulate business value for cloud solutions - Strong collaboration across cross-functional teams - Experience with partner ecosystem - Excellent presentation and communication skills Cloud Knowledge: - Understanding of core cloud services relevant to sports workloads (compute, storage, databases, analytics, ML/AI, security) - Familiarity with cloud partner ecosystems and Professional Services capabilities - Ability to connect customer business challenges to cloud-based solutions Opportunity Development & Execution: - Drive opportunities with a focus on measurable business outcomes - Collaborate with industry specialists to evangelize cloud services, partner solutions, and Professional Services. - Participate in executive engagements with C-suite stakeholders We'll combine into one
  with all bullet points.

  Requirements

  Basic Qualifications: - 7+ years of direct sales or business development in software, cloud or SaaS markets selling to C-level executives experience We need to keep exactly as written: "7+ years of direct sales or business development in software, cloud or SaaS markets selling to C-level executives experience". It's a bit awkward but keep.

  Qualifications

  Preferred Qualifications: - Experience creating and implementing long-term transformational account strategies in a customer-facing role or equivalent - Experience collaborating with cross-functional teams including Marketing, Product Management, Customer Service, Operations, Legal, Finance, and Senior Leadership - 10+ years of technology related sales, business development or equivalent experience - 7+ years of hands-on work managing complex technology projects experience - Knowledge of AWS or technology as a service (IaaS, SaaS, PaaS) We need to keep exactly.

  Benefits

  We have 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. Learn more about our benefits at https://amazon.jobs/en/benefits." Also earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." That's compensation but could be part of Benefits? It's compensation elements. Might be part of Pay? But we have Pay section for salary ranges. We'll include sign-on payments, RSUs, sales incentives under Benefits? The instruction says Benefits section for benefits. Sign-on payments, RSUs, sales incentives are compensation components, maybe part of Pay. But we have Pay for base salary range. Could include them under Benefits as part of total compensation. Safer to put them under Benefits as they are part of package. We'll include them. Thus Benefits

  includes: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. 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." We should keep the link? It's not boilerplate; it's a benefits link. Keep.

  Pay

  We have salary ranges for three locations: - USA, CA, Santa Monica - 142,800.00 - 193,200.00 USD annually - USA, NJ, Jersey City - 157,100.00 - 212,600.00 USD annually - USA, NY, New York - 157,100.00 - 212,600.00 USD annually We need to preserve all. Could format as
  • each. Thus:

    Pay

    • USA, CA, Santa Monica - $142,800.00 - $193,200.00 USD