Sr. Account Executive - Amazon Business , Commercial Sector - Corporate Team

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the description. Key sections: - Description (intro paragraph) maybe "About the role"? Actually they have "Description" then "Key job responsibilities", "A day in the life", "About The Team", "Basic Qualifications", "Preferred Qualifications". Also they have salary ranges per location. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: could be the introductory paragraph describing the role, mission, etc. - Responsibilities: list of key job responsibilities and maybe "A day in the life" details. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe not explicitly listed; could combine some skills from qualifications? But we should not create a Skills section unless there is explicit skill list. The posting mentions "Experience positioning and selling innovative solutions", "Experience with Microsoft Office products", "Experience with sales CRM tools such as Salesforce", etc. Those are qualifications/requirements. Could treat them under Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Basic and Preferred Qualifications into a single "Qualifications" section, maybe with subheadings? But we only allowed headings as listed; we cannot add custom headings. So we need to decide which sections to include: About the role, Responsibilities, Qualifications (maybe combine Basic and Preferred), Benefits, Pay (since salary ranges are given). Schedule? Not mentioned. Benefits? They mention benefits: comprehensive benefits including health insurance etc. So we can include Benefits section. Pay: they give salary ranges per location. So we include Pay section. Schedule: not mentioned, so omit. Skills: not explicitly separate; we could omit. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information: intro paragraph, responsibilities list, day in the life details, about the team, basic qualifications, preferred qualifications, benefits description, salary ranges. We need to remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." and the accommodation link, also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep benefits description but not the link). Also remove "Company - Amazon.com Services LLC Job ID: A10559252" maybe fold minor metadata into a short

  or drop it. We could include a short paragraph with company and job ID? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a

  at end with "Company: Amazon.com Services LLC | Job ID: A10559252". That's minor metadata. Now we need to format. We'll produce:

  About the role

  Come be a part of a rapidly expanding $60 billion-dollar global business. At Amazon Business, a fast-growing startup passionate about building solutions, we set out every day to innovate and disrupt the status quo. We stand at the intersection of tech & retail in the B2B space developing innovative purchasing and procurement solutions to help businesses and organizations thrive. At Amazon Business, we strive to be the most recognized and preferred strategic partner for smart business buying. Bring your insight, imagination and a healthy disregard for the impossible. Join us in building and celebrating the value of Amazon Business to buyers and sellers of all sizes and industries. Unlock your career potential.

  Responsibilities

  • High activity and strategic prospecting into decision makers within territory to drive discovery meetings and identify selling opportunities
  • Deliver accurate weekly reporting on pipeline and customer spend adoption, including account status updates and insights learned during deployment
  • Provide strategic account engagement that helps customers implement solutions that solve industry-specific procurement challenges
  • Drive and accelerate spend adoption by advising customers on best practices for using Amazon Business solutions
  • Focus on automating service needs for customers, while working with Product and Technical teams to develop solutions that will increase solution adoption
  • Relay market needs and requirements back to internal Amazon teams, including Product, Technical, and Category Management teams
  • A day in the life: 2+ customer facing meetings/day to support with any and all account related questions, while uncovering opportunities to grow our partnership.
  • Responding to emails and following up on support tickets on behalf of our customers.
  • Heavy prospecting (phone, email, social media platforms) with the goal to book meetings to pitch AB as a solution for procurement needs.
  But note: "A day in the life" is more like a description; we could keep as a bullet or as a paragraph. The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. The day in the life is not a list but a description; we could treat as a paragraph. However we already have a list for responsibilities; we could add a

    after the list for day in the life. But we need to preserve all substantive information. Let's keep day in the life as a separate paragraph after the list. Thus:

    Responsibilities

    • High activity and strategic prospecting into decision makers within territory to drive discovery meetings and identify selling opportunities
    • Deliver accurate weekly reporting on pipeline and customer spend adoption, including account status updates and insights learned during deployment
    • Provide strategic account engagement that helps customers implement solutions that solve industry-specific procurement challenges
    • Drive and accelerate spend adoption by advising customers on best practices for using Amazon Business solutions
    • Focus on automating service needs for customers, while working with Product and Technical teams to develop solutions that will increase solution adoption
    • Relay market needs and requirements back to internal Amazon teams, including Product, Technical, and Category Management teams

    A day in the life: 2+ customer facing meetings/day to support with any and all account related questions, while uncovering opportunities to grow our partnership. Responding to emails and following up on support tickets on behalf of our customers. Heavy prospecting (phone, email, social media platforms) with the goal to book meetings to pitch AB as a solution for procurement needs.

    Now About The Team: could be part of About the role or maybe we could include in About the role paragraph. But we have already an About the role section; we could incorporate the team description there. However we need to preserve all substantive information; we can add a paragraph after About the role about the team. Thus About the role section could have two paragraphs: first the intro, second about the team. Let's do:

    About the role

    Come be a part of a rapidly expanding $60 billion-dollar global business. At Amazon Business, a fast-growing startup passionate about building solutions, we set out every day to innovate and disrupt the status quo. We stand at the intersection of tech & retail in the B2B space developing innovative purchasing and procurement solutions to help businesses and organizations thrive. At Amazon Business, we strive to be the most recognized and preferred strategic partner for smart business buying. Bring your insight, imagination and a healthy disregard for the impossible. Join us in building and celebrating the value of Amazon Business to buyers and sellers of all sizes and industries. Unlock your career potential.

    The Amazon Business team is dedicated to developing solutions that make it easy for business customers to source, procure, and manage supply chain using Amazon. Account Executives are an integral component to Amazon Business as a key customer facing representative. You have the opportunity to work with Consumer Packaging and Goods organizations, from prospecting to strategic account growth.

    Now Qualifications: we need to include Basic Qualifications and Preferred Qualifications. Could combine into one section with two sub-lists? But we only allowed headings; we could have a

    Qualifications

    and then maybe two
    lists with headings inside? Not allowed to add extra headings. Could we use

    to label "Basic Qualifications:" and then list? That would be prose. But we need to use

    • for any list of duties/requirements/benefits. So we can have a
      for Basic Qualifications and another
      for Preferred Qualifications, each preceded by a

      describing? That might be okay. However the instruction: Use

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

        for prose. So we can have a

        that says "Basic Qualifications:" then a

        . Similarly for Preferred. Thus:

        Qualifications

        Basic Qualifications

        • Experience positioning and selling innovative solutions to new and existing customers and market segments
        • Experience with Microsoft Office products and applications
        • Experience with sales CRM tools such as Salesforce or similar software
        • Bachelor's degree or equivalent
        • Bachelor's degree in a relevant field or equivalent work experience
        • 5+ years of B2B or enterprise sales with a focus on hunting new business experience
        • Experience in generating new opportunities with strong focus on pipeline tracking and deal execution through entire sales cycle
        • Experience positioning and selling technology to new customers and new market segments

        Preferred Qualifications

        • Knowledge of procurement and source to pay processes and solutions or equivalent experience
        • Experience identifying trends and needs to improve an already closed large-scale technology deal
        • Experience with MS Office Suite, CRMs (Salesforce) and other systems
        • 8+ years of sales experience selling to Fortune 1000 senior leadership
        • Experience selling to procurement and/or supply chain roles
        • Experience owning customer facing communication including leading in-person or virtual customer meetings, product demonstrations, or trainings
        • Demonstrated success identifying, prioritizing, developing, and growing a book of $500M-$5B strategic customer accounts
        Now Benefits: we need to include benefits description. They list: 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 they