CSC Account Manager, West Engaged Startups

We need to output HTML fragment with sections: About the role? The description includes paragraphs about AWS, responsibilities, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Let's extract content: First paragraph: "Trusted by more startups around the world, AWS makes the power of cloud computing accessible for all by giving founders everywhere access to the same technology that powers the world’s largest companies. With 20 years of experience gained from supporting hundreds of thousands of startups that have come before, we help founders prove that their world-changing ideas are possible, at any stage of growth or level of funding. This is why more startups, and over 80% of unicorns, build on AWS. As AWS continues to rapidly grow, we seek a Startup Account Manager to help drive the growth of high-potential early, mid, and late stage startups. Your responsibilities will include driving revenue and user adoption, migrations, and ensuring new startups select AWS as their primary cloud provider. You will align closely with counterparts in business development, marketing, solution architecture and partner teams to lead execution of coordinated go-to-market strategies and sales plays. You will also work closely with business development teams who are driving strategic support, global co-programming, and portfolio engagement to help drive top-of-funnel customer acquisition and accelerate seller cycles in the field. You will be at the heart of latest trends like artificial intelligence (AI), machine learning (ML), serverless and IoT. Your customers leverage state-of-the-art technologies on AWS to innovate and become the next disrupters, like today’s AirBnB, Slack, DoorDash, and Lyft. You are passionate about startups, a self-starter with a strong entrepreneurial spirit who is prepared to work in a fast-paced, often ambiguous environment, execute against ambitious goals, and consistently embrace the Amazon Culture." Then "Key job responsibilities" list: bullet points. Then "About The Team" with subpoints: Diverse Experiences, Why AWS? (with subpoints: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Then "Basic Qualifications", "Preferred Qualifications". Then EEO statement, accommodation link, then salary range and benefits description, then location lines, then Company, Job ID. We need to produce sections: maybe About the role (intro), Responsibilities (list), Requirements (maybe combine Basic and Preferred Qualifications?), Qualifications (maybe separate?), Skills (maybe not explicit), Benefits (benefits described), Pay (salary range), Schedule (maybe not present). Travel mentioned: "Expect moderate travel." That could be Schedule? Not exactly schedule. Could be under Responsibilities? Might be a note. But we only include Schedule if posting actually states schedule (like full-time, part-time, shift). Not present. So omit Schedule. We need to avoid repeating job title as heading. So no heading for "Startup Account Manager". Also no Job ID heading. We need to include only sections with real content. Let's decide sections: - About the role: could be the introductory paragraph describing role and mission. That seems appropriate. - Responsibilities: the "Key job responsibilities" list. - Requirements: maybe combine Basic Qualifications and Preferred Qualifications? But we have separate headings Requirements and Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. Likely Requirements = Basic Qualifications. Qualifications = Preferred Qualifications. Skills maybe not present; we could omit if no specific skills list. Benefits = benefits description. Pay = salary range. Schedule maybe not present; omit. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities list, Requirements list (basic qualifications), Qualifications list (preferred qualifications), Benefits list (benefits). For prose, use

  . We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the exact wording? Probably we can keep the meaning but not omit details. We'll try to keep sentences. We need to remove boilerplate: EEO statement, accommodation link, navigation, duplicated lines. Also remove "Amazon is committed to a diverse and inclusive workplace..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe that's part of benefits but it's a link; we could keep the description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to learn more; could be considered boilerplate? Might be okay to keep but it's a link; but we can keep the description of benefits and drop the link. The instruction says preserve ALL substantive information; the link is not substantive? It's a reference. Might be okay to drop. We'll keep the benefits description. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10561714". Those are metadata; we can drop. Also remove location lines? They are location info; maybe we could keep as part of Pay? The posting includes location-specific salary ranges: "USA, TX, Austin - 92,400.00 - 160,000.00 USD annually" and "USA, WA, Seattle - 92,400.00 - 160,000.00 USD annually". That's substantive pay info; we should keep. Could embed in Pay section. Also "Expect moderate travel." That's substantive; maybe include under Responsibilities as a note or separate? Could be under Responsibilities as a bullet? Not a duty but a condition. Could be under Responsibilities as a note. We'll include as a bullet under Responsibilities. Now craft HTML. Structure:

  About the role

  ... intro paragraph ...

  Responsibilities

  • Ensure customer success with early, mid and late stage startups.
  • Drive revenue and market share in a defined territory or industry vertical.
  • Accelerate customer adoption through well-developed sales engagements and successful GTM strategy.
  • Meet or exceed quarterly revenue and goal targets.
  • Develop and execute against a comprehensive account/territory plan.
  • Create & articulate compelling value propositions around AWS services.
  • Accelerate customer adoption by engaging Founders, CxO, Board of Directors and VC influencers.
  • Work with partners to extend reach & drive adoption.
  • Develop long-term strategic relationships with key accounts.
  • Ensure customer satisfaction.
  • Expect moderate travel.
  Note: The original list had some bullet points with slight variations; we need to preserve all. Let's extract exactly from posting: "Key job responsibilities Ensure customer success with early, mid and late stage startups. Drive revenue and market share in a defined territory or industry vertical. Accelerate customer adoption through well-developed sales engagements and successful GTM. Strategy Meet or exceed quarterly revenue and goal targets. Develop and execute against a comprehensive account/territory plan. Create & articulate compelling value propositions around AWS services. Accelerate customer adoption by engaging Founders, CxO, Board of Directors and VC influencers Work with partners to extend reach & drive adoption. Develop long-term strategic relationships with key accounts. Ensure customer satisfaction. Expect moderate travel." There are some missing punctuation; we can keep as is. We'll make each sentence a bullet. Now Requirements (Basic Qualifications): "Basic Qualifications 5+ years of full sales cycle, technology sales or equivalent business development, sales engineering/consulting or equivalent experience Bachelor's degree or equivalent" We need to preserve as list? It's two items: experience and degree. Could be two bullets. Thus:

  Requirements

  • 5+ years of full sales cycle, technology sales or equivalent business development, sales engineering/consulting or equivalent experience
  • Bachelor's degree or equivalent
  Now Qualifications (Preferred Qualifications): "Preferred Qualifications Experience using sales CRM tools such as Salesforce Experience (technical or educational) in Engineering or Computer Science Experience driving new business in greenfield accounts at the C-suite level or equivalent Experience with customer relationship management, especially C-suite level customer engagement" We need to split into bullets. Thus:

  Qualifications

  • Experience using sales CRM tools such as Salesforce
  • Experience (technical or educational) in Engineering or Computer Science
  • Experience driving new business in greenfield accounts at the C-suite level or equivalent
  • Experience with customer relationship management, especially C-suite level customer engagement
  Now Benefits: The 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." We need to keep substantive info; we can drop the link sentence. So benefits list: - 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 earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." That's compensation elements; could be part of Pay or Benefits? It's part of compensation package. Could be included in Pay section along with salary range. The instruction: Pay section only if posting actually states them. It does state base salary range and mentions sign-on payments, RSUs, sales incentives. So we should include those in Pay. Thus Pay section:

  Pay

  • Base salary range: $92,400.00 - $160,000.00 USD annually (locations: Austin, TX; Seattle, WA)
  • Sign-on payments
  • Restricted stock units (RSUs)
  • Sales incentives
  We need to preserve location specifics: The posting had two lines: "USA, TX, Austin - 92,400.00 - 160,000.00 USD annually" and "USA, WA, Seattle - 92,400.00 - 160,000.00 USD annually". We can combine. Now we need to ensure we didn't miss any substantive info: The introductory paragraph also mentions "Trusted by more startups around the world..." etc. We'll keep that. Also "About The Team" section includes subpoints: Diverse Experiences, Why AWS? with subpoints Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is substantive info about team culture. Should we include as a section? Could be under About the role or maybe a separate section like "About the Team". But the allowed headings are limited to those listed; we could incorporate into About the role as prose. The instruction: Use

  for section headings (