Sr. Enterprise Account Manager, Automotive & Manufacturing

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 preserve all substantive info. Remove boilerplate like EEO, legal, application deadline? The description includes "Application deadline: Sep 30, 2026". That is metadata; we can fold into short p or drop. Probably drop as minor metadata. Also remove "About The Team" sections? The posting includes "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are not required headings but we could include them under "About the role"? Actually "About the role" is a heading we should use for role description. The "About The Team" content is about team culture etc. Could be considered part of "About the role" or maybe we could create a section "About the team" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We need to extract: - About the role: description of role: "AWS seeks an experienced Account Manager to own and operate GTM strategy for a territory of Enterprise customers in the Automotive & Manufacturing industry. This district covers a diverse portfolio spanning enterprise software & SaaS, industrial automation & OT, automotive digital marketplaces, mobility technology & telematics, AI infrastructure, and emerging technology — requiring a versatile seller who can navigate complex multi-stakeholder environments across both direct enterprise and ISV/partner co-sell motions. In this role you will influence customers to build, shape, and accelerate their innovation priorities using AWS technologies and resources. You will manage a portfolio of accounts at various stages of cloud maturity — from greenfield to scaling — and drive adoption across workloads including cloud-native applications, AI/ML, infrastructure migration, IoT, autonomous systems, and marketplace solutions." Also "A day in the life" paragraph could be part of About the role. - Responsibilities: list of key job responsibilities bullet points. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe not explicit; could derive from responsibilities? But we should only include if posting actually states them. There's no separate Skills section. Could we infer skills from responsibilities? Probably not; we should not create a Skills section unless explicitly stated. So we may omit Skills. - Benefits: The posting mentions 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." Also sign-on payments, RSUs, sales incentives. So we have benefits content. - Pay: The posting includes salary ranges for various locations. So we have Pay info. - Schedule: Not mentioned. No schedule info. So omit Schedule. We must not include placeholder like "commensurate with experience". The salary ranges are specific. We need to format: Use

for section headings. Use

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

  for prose. We must not repeat job title. Not include Job ID. We need to preserve all substantive info. So include the bullet points exactly as given. Let's extract responsibilities bullet points: From "Key job responsibilities": - Lead a customer-obsessed business across a portfolio of enterprise, ISV, and digital-native accounts in the automotive and manufacturing sector - Accelerate customer adoption through comprehensive GTM strategy to achieve customer outcomes - Drive market share while achieving and exceeding revenue and non-revenue goals - Execute complex commercial agreements including multi-year cloud commitments and Marketplace private offers - Build and maintain executive relationships at VP and C-level across all accounts - Create and articulate compelling value propositions around AI/ML, cloud-native application modernization, large-scale infrastructure migration, IoT, and autonomous systems - Develop and execute account strategies that unlock new workloads and expand AWS consumption across accounts at varying stages of cloud maturity - Partner with Solutions Architects, ISV Sales Managers, and Partner teams to deliver integrated solutions - Drive AWS Marketplace adoption and co-sell motions with technology partners - Build and maintain a healthy, well-qualified sales pipeline We should keep them as list items. Basic Qualifications: - 7+ years of direct sales or business development in software, cloud or SaaS markets selling to C-level executives experience - 2+ years of solving problems with technology in the Automotive & Manufacturing industries experience - Experience executing complex commercial agreements (multi-year cloud commitments or equivalent) Note there is some duplication of "experience". We'll keep as is. Preferred Qualifications: - Experience selling to or partnering with ISVs in enterprise software, industrial automation, automotive technology, or AI/automation platforms - Demonstrated success driving AWS Marketplace adoption and co-sell motions with technology partners - 5+ years of direct customer engagement with VP and C-level executives in automotive, manufacturing, or industrial technology verticals - Familiarity with one or more of: cloud-native ERP, OT/ICS security, autonomous systems, connected vehicle platforms, AI/ML infrastructure, or digital marketplace technology - Experience managing a diverse portfolio of accounts at varying stages of cloud maturity and spend levels 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. - Also mention sign-on payments, restricted stock units (RSUs), and sales incentives. We could combine into a list. Pay: - USA, CA, San Francisco - 157,100.00 - 212,600.00 USD annually - USA, CA, Santa Monica - 142,800.00 - 193,200.00 USD annually - USA, IL, Chicago - 142,800.00 - 193,200.00 USD annually - USA, OR, Portland - 142,800.00 - 193,200.00 USD annually - USA, WA, Seattle - 142,800.00 - 193,200.00 USD annually We could present as list. Now About the role: combine the initial description and "A day in the life" paragraph. Let's craft prose: Paragraph 1: AWS seeks an experienced Account Manager to own and operate GTM strategy for a territory of Enterprise customers in the Automotive & Manufacturing industry. This district covers a diverse portfolio spanning enterprise software & SaaS, industrial automation & OT, automotive digital marketplaces, mobility technology & telematics, AI infrastructure, and emerging technology — requiring a versatile seller who can navigate complex multi-stakeholder environments across both direct enterprise and ISV/partner co-sell motions. In this role you will influence customers to build, shape, and accelerate their innovation priorities using AWS technologies and resources. You will manage a portfolio of accounts at various stages of cloud maturity — from greenfield to scaling — and drive adoption across workloads including cloud-native applications, AI/ML, infrastructure migration, IoT, autonomous systems, and marketplace solutions. Paragraph 2 (A day in the life): You'll engage automotive and manufacturing technology executives to understand their cloud transformation and AI priorities, collaborate with solution architects to design scalable solutions, and work alongside ISV and partner teams to deliver customer value. Your day might include executive briefings, pipeline reviews, commercial negotiations, and cross-functional collaboration to ensure customer success across a diverse portfolio that could span enterprise software platforms, industrial automation systems, digital automotive marketplaces, mobility and telematics solutions, or AI infrastructure workloads. We should not include "About The Team" etc. That's extra but maybe considered part of About the role? The instructions: "Prefer a few substantive sections over many thin ones." Could we include a section "About the team"? Not allowed heading. So we omit that content? But we must preserve ALL substantive information. The "About The Team" content is substantive. However we cannot create a heading not in list. Could we fold it into "About the role" as prose? That would preserve it. The content includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. That's substantive about team culture. We can include as a paragraph under About the role after the day in the life. That would be okay. Thus About the role will have multiple paragraphs: role description, day in the life, and team culture info. We need to ensure we don't include boilerplate like EEO, legal, etc. We'll omit those. Now produce HTML:

  About the role

  ...

  ...

  ...

  Then responsibilities:

  Responsibilities

  • ...
  ...
  Requirements:

  Requirements

  • ...
  ...
  Qualifications:

  Qualifications

  • ...
  ...
  Benefits:

  Benefits

  • ...
  • ...
  Pay:

  Pay

  • ...
  ...
  We should not include Schedule. Make sure no extra whitespace? It's fine. Now craft the content precisely. Let's write About the role paragraphs: Paragraph1: "AWS seeks an experienced Account Manager to own and operate GTM strategy for a territory of Enterprise customers in the Automotive & Manufacturing industry. This district covers a diverse portfolio spanning enterprise software & SaaS, industrial automation & OT, automotive digital marketplaces, mobility technology & telematics, AI infrastructure, and emerging technology — requiring a versatile seller who can navigate complex multi-stakeholder environments across both direct enterprise and ISV/partner co-sell motions. In this role you will influence customers to build, shape, and accelerate their innovation priorities using AWS technologies and resources. You will manage a portfolio of accounts at various stages of cloud maturity — from greenfield to scaling — and drive adoption across workloads including cloud-native applications, AI/ML, infrastructure migration, IoT, autonomous systems, and marketplace solutions." Paragraph2: "You'll engage automotive and manufacturing technology executives to understand their cloud transformation and AI priorities, collaborate with solution architects to design scalable solutions, and work alongside ISV and partner teams to deliver customer value. Your day might include executive briefings, pipeline reviews, commercial negotiations, and cross-functional collaboration to ensure customer success across a diverse portfolio that could span enterprise software platforms, industrial automation systems, digital automotive marketplaces, mobility and telematics solutions, or AI infrastructure workloads." Paragraph3 (team culture): Combine the bullet points from About The Team into prose? Could keep as list? But we are not supposed to create headings for team; we can embed as a paragraph summarizing. However we must preserve ALL substantive information; we could convert the bullet points into a list within the paragraph? But we cannot add new headings; we can still use
  inside About the role? The instruction: Use
  • for any list of duties/requirements/benefits. It doesn't forbid using lists elsewhere, but says for any list of duties/requirements/benefits. For other lists maybe okay but safer to keep as prose. However we risk losing some specifics. Could we embed as a list under About the role? It's not duties/requirements/benefits, but still a list. The instruction didn't prohibit using lists elsewhere, just said use <