Pr. ProServe Account Executive, WWPS EDU SLG

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. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. We need to parse the description. Key parts: - Description paragraph: "The Amazon Web Services Professional Services (ProServe) team is seeking a dynamic ProServe Account Executive (PAE) to join our team at Amazon Web Services (AWS). In this role, you'll be responsible for engaging new and existing customers in transformative projects involving IT Strategy, distributed architecture, and hybrid cloud operations. You'll work closely with ProServe Cloud Architects, Engagement Managers, and Delivery Consultants to drive customer success and business growth. As ProServe’s customer facing relationship owner you’ll be primarily focused on understanding and defining business outcomes for customers by building trust, identifying applicable AWS Professional Services offerings, and creating proposals and securing customer signoff of SOW’s. Following project launch, you will stay connected with the customer to ensure we are delivering the agreed customer business outcomes (CBO) as outlined in the SOW. Your experience in selling services within the technology/consulting sector, will equip you with the ability to translate technical concepts into business value for customers. You will demonstrate proficiency in business development, executing sales methodologies and managing CRM systems coupled with strong analytical, problem-solving, and project management abilities. PAEs performance will be measured against key metrics including but not limited to Revenue, Billable Bookings, and customer satisfaction (CSAT)." - Then "AWS Global Services" paragraph: description of AWS Global Services. Might be considered part of About the role? Could be separate "About the team"? Actually there is a section "About The Team" later. - "Key job responsibilities As an experienced services sales professional, you will be responsible for:" then bullet list (but not actual bullet list in text). The bullet points are sentences after colon: "Leading business development efforts by engaging customers and driving high-value engagements", "Collaborating with Amazon Global Sales (AGS) representatives to ensure a coordinated approach for key accounts", "Creating proposals, securing customer sign-off on Statements of Work (SOWs), and ensure successful project delivery", "Monitoring ongoing projects to ensure delivery of agreed CBOs and maximize revenue potential", "Advocating for customers while balancing AWS business objectives". So we need to put these under Responsibilities as

• . - Then "About The Team" heading appears, then paragraphs: "About AWS Diverse Experiences AWS values diverse experiences..." etc. This seems like "About the team" content. We'll treat as About the Team (maybe heading "About the team"). - Then "Why AWS?" with subpoints: "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Those could be part of Benefits? Actually they are about culture, not benefits. Could be part of "About the team" or separate "Culture". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Why AWS?" content to Benefits? Not exactly. Benefits are things like health insurance etc. The "Why AWS?" includes culture, mentorship, work-life balance. Could be considered Benefits? Might be okay to put under Benefits as they are employee benefits/culture. However we need to only include sections if posting has real specific content for it. The posting does have content about inclusive team culture, mentorship, work-life balance. So we can create a Benefits section with those points. - Then "Basic Qualifications" list: "Experience with sales targets, business development, and driving customer satisfaction", "8+ years of technology sales or account management experience", "Experience with cloud technologies and IT strategies". That's Requirements. - Then "Preferred Qualifications": list of skills: "Excellent communication, presentation, and negotiation skills", "Ability to build and maintain C-level client relationships", "Financial acumen with the ability to analyze and report on key performance metrics", "Technical proficiency to understand and articulate AWS services and solutions", "Strategic thinking and problem-solving skills", "Excellent storytelling and active listening abilities". That's Qualifications or Skills. We could split: Qualifications (preferred) and Skills (maybe). But we have both Qualifications and Skills headings allowed. We could put Preferred Qualifications under Qualifications, and maybe Skills under Skills? However the preferred qualifications list includes skills like communication, negotiation, etc. Could treat as Skills. But we need to avoid duplication. Perhaps we put Requirements (basic qualifications) under Requirements heading, and Preferred Qualifications under Qualifications heading. Then we could also have Skills heading if we want to separate out some skill-based items, but we could also just not use Skills if we already covered. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Preferred Qualifications and Skills into one Qualifications section. Or we could have Requirements (basic) and Qualifications (preferred). That seems fine. - Then EEO boilerplate etc to remove. - Then compensation paragraph: "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: list of locations with ranges. Thus we have Pay section: we need to include salary ranges. The posting includes base salary range for this position is listed below, then multiple location-specific ranges. So we should include Pay section with those details. We also have Benefits section: we already have some benefits from Why AWS? plus the comprehensive benefits list. We'll combine. We need to avoid repeating job title as heading. No Job ID. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

  About the role

  ... (the initial description paragraph plus maybe AWS Global Services paragraph? Actually AWS Global Services is more about the team; but we could include in About the role or About the team. Let's decide: About the role: description of role responsibilities high-level. Could include the first paragraph plus maybe the AWS Global Services paragraph? The AWS Global Services paragraph describes the organization; could be part of About the team. I'd put it under About the team. Thus About the role: first paragraph (the description). Could also include the sentence about performance measured against metrics? That's part of role description. We'll keep it. Then

  Responsibilities

  with
  • items. Then

    Requirements

    with
    • for basic qualifications. Then

      Qualifications

      with
      • for preferred qualifications. Then

        Benefits

        with

        combining Why AWS? points and comprehensive benefits list. Then

        Pay

        with

        containing base salary range statement and location-specific ranges. We should not include Schedule section as no info. We need to preserve all substantive information; do not invent or summarize away detail. So we must include all details from the posting. Let's extract exact text. First paragraph (description) exactly: "The Amazon Web Services Professional Services (ProServe) team is seeking a dynamic ProServe Account Executive (PAE) to join our team at Amazon Web Services (AWS). In this role, you'll be responsible for engaging new and existing customers in transformative projects involving IT Strategy, distributed architecture, and hybrid cloud operations. You'll work closely with ProServe Cloud Architects, Engagement Managers, and Delivery Consultants to drive customer success and business growth. As ProServe’s customer facing relationship owner you’ll be primarily focused on understanding and defining business outcomes for customers by building trust, identifying applicable AWS Professional Services offerings, and creating proposals and securing customer signoff of SOW’s. Following project launch, you will stay connected with the customer to ensure we are delivering the agreed customer business outcomes (CBO) as outlined in the SOW. Your experience in selling services within the technology/consulting sector, will equip you with the ability to translate technical concepts into business value for customers. You will demonstrate proficiency in business development, executing sales methodologies and managing CRM systems coupled with strong analytical, problem-solving, and project management abilities. PAEs performance will be measured against key metrics including but not limited to Revenue, Billable Bookings, and customer satisfaction (CSAT)." Note there is a typo: "PAEs performance". We'll keep as is. Second paragraph: "AWS Global Services AWS Global Services includes experts from across AWS who help our customers design, build, operate, and secure their cloud environments. Customers innovate with AWS Professional Services, upskill with AWS Training and Certification, optimize with AWS Support and Managed Services, and meet objectives with AWS Security Assurance Services. Our expertise and emerging technologies include AWS Partners, AWS Sovereign Cloud, AWS International Product, and the Generative AI Innovation Center. You’ll join a diverse team of technical experts in dozens of countries who help customers achieve more with the AWS cloud." We'll put that under About the Team. Now "Key job responsibilities As an experienced services sales professional, you will be responsible for:" then list. We'll capture each bullet exactly as in text: - Leading business development efforts by engaging customers and driving high-value engagements - Collaborating with Amazon Global Sales (AGS) representatives to ensure a coordinated approach for key accounts - Creating proposals, securing customer sign-off on Statements of Work (SOWs), and ensure successful project delivery - Monitoring ongoing projects to ensure delivery of agreed CBOs and maximize revenue potential - Advocating for customers while balancing AWS business objectives Now "About The Team" heading then paragraphs: "About AWS Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." Then "Why AWS?" then subpoints. We need to capture all that text under About the Team (maybe we split into About the team and Why AWS? but we only have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the "About AWS Diverse Experiences" and "Why AWS?" under Benefits? But they are more about culture and benefits. However we already have Benefits for compensation and culture. Could combine. But we also have "About The Team" heading in the original; we could create a section "About the team" but not in allowed headings. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we could also use other headings? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. It doesn't explicitly forbid other headings, but to be safe we should stick to those. So we need to map the About The Team content into one of those allowed headings. Likely "About the role" could include some team description, but we already used About the role for role description. Could we put the team description under About the role as well? Might be okay but could be mixing. Alternatively we could put the team description under Benefits? Not ideal. Maybe we could treat "About the team" as "About the role" because it's about the team you'll join. But the instruction says "About the role" for section headings e.g