Sr Sales Manager - AI Applications, Spec Sales - Amazon Connect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the description. We need to extract: - About the role: description of position, context, etc. The first paragraph: "This position is part of the AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our customers succeed. Partner teams own the strategy, recruiting, development, and growth of our key technology and consulting partners. Together they provide our customers with the expertise and scale needed to build innovative solutions for their most complex challenges. Amazon Web Services (AWS) is proud to be the pioneer and widely recognized leader in Cloud Computing. Our web services provide IT infrastructure in-the-cloud that is used by hundreds of thousands of developers and businesses around the world. These customers range from start-ups to leading web companies to Global 500 companies in industries such as financial services, pharmaceuticals, and high technology. We’re looking for an accomplished Sales Leader deeply familiar with Contact Center as a Service and generative AI, to lead the CXE business (Amazon Connect) for the central US. The successful candidate will have overachieved throughout their career and built strong, deep relationships with F1000 and/or G2000 organizations. This leader will have a broad role – part market maker, part operator and part general manager – and will build a strategy focused on outcome-based selling, winning new customer segments and growing existing customer segments for the long term. As a self-starter willing to operate in a multifaceted way, you should also have experience in market development of cloud infrastructure and/or enterprise applications. The right candidate must possess top of the line leadership skills with the ability to execute on key business initiatives. The role will require working with the overall ecosystem to help secure lighthouse customers, drive top-line revenue for new services, and develop strategic partnerships. This is an exciting opportunity to drive the go-to-market definition and execution of AWS’s strategy for Amazon Connect for the central US. Our team is dedicated to supporting new members. We have a broad mix of experience levels and tenures, and we’re building an environment that celebrates knowledge sharing and mentorship. We care about your career growth and strive to assign projects based on what will help each team member develop into a better-rounded professional and enable them to take on more complex tasks in the future." That's about the role. - Responsibilities: "Key job responsibilities Your responsibilities will include driving strategic workloads to deepen business and technical relationships with customers and partners. You will invest your time in developing the high-performing team of sales experts and build mechanisms to enable the field organization to drive the day-to-day interactions that identify prospects for long-term business opportunities. You will focus on incubating new AWS Productivity Applications services, scaling existing AWS services, delivering workload/solution specific domain expertise to the broader field organization, and developing repeatable, packaged solutions to solve customer challenges. As the voice of the customer, your findings will influence product teams to help them evolve the products and address issues, concerns, and requests from the field. To be successful, you will need to analyze and determine key customer insights from business drivers, market trends, customer feedback, and operating metrics. You will be responsible for establishing clear goals for your team, including quotas. You must ensure that your team is managing opportunities effectively throughout the sales cycle and practicing good pipeline hygiene. You will be expected to plan and allocate for the best use of team resources in order to meet goals and quotas." We can list as bullet list. - About The Team: there is a section "About The Team" with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. The content includes paragraphs. We could treat as "About the Team" heading with paragraphs. But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings like About The Team? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those specific headings; but we can also include other headings if they have content. However they say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include sections like "About the Team" if content exists. But they gave examples; not exclusive. We need to decide which sections to include: About the role, Responsibilities, About the Team (maybe as "About the Team"), Qualifications (Basic Qualifications, Preferred Qualifications), Benefits, Pay (salary ranges), maybe Skills? There's no explicit Skills section but we could infer from qualifications. However they said prefer a few substantive sections over many thin ones. So we could combine Basic and Preferred Qualifications into a "Qualifications" section with bullet lists. Benefits: there is a paragraph describing 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. Learn more about our benefits at https://amazon.jobs/en/benefits." Pay: salary ranges listed for locations. Schedule: not mentioned; we should not create Schedule section. Thus sections: About the role, Responsibilities, About the Team, Qualifications, Benefits, Pay. We need to output HTML fragment only, no /. Use

for each heading. Use

for prose. Use

• for lists. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location preferences, etc. The location preferences appear in "LOCATIONS: Preference for Austin, TX, Chicago, IL, Atlanta, GA, New York, NY". That's substantive; we need to include somewhere. Could be in About the role or maybe a separate "Location" section but not in list of headings. Since we don't have a heading for Location, we could embed that info in About the role paragraph. But we must preserve it; we can add a sentence. Also "Our team is dedicated to supporting new members..." etc is already in About the role. We need to include the bullet list for responsibilities. Qualifications: Basic Qualifications: Bachelor's degree, 5+ years of sales/sales management in infrastructure or cloud technology leading a direct or indirect account team and experience leading leaders with proven results, Leadership experience in a customer-facing role in the CX/VDI technology industry. Preferred Qualifications: list of items. We need to keep them as bullet lists. Benefits: as described. Pay: list salary ranges per location. We need to avoid boilerplate like EEO, accommodation, etc. Remove those. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe we can keep as part of benefits but it's a link; it's not boilerplate? It's a reference; but it's not essential; but we can keep it as part of benefits paragraph. We must not include application instructions. Now produce HTML. Structure:

  About the role

  ... (including location preferences)

  Responsibilities

  • ...
  ...

  About the Team

  ... (including Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance)

  We could break About the Team into subpoints but not required; we can keep as paragraph.

  Qualifications

  Basic Qualifications

  maybe not allowed; they only said use

  for section headings. Could we use

  ? Not specified; they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings should be

  . For subheadings we could just use

  with bold? But better to keep as

  with items labeled. Could do Basic Qualifications: then list. Thus:

  Qualifications

  Basic Qualifications:

  • Bachelor's degree
  • 5+ years of sales/sales management in infrastructure or cloud technology leading a direct or indirect account team and experience leading leaders with proven results
  • Leadership experience in a customer-facing role in the CX/VDI technology industry

  Preferred Qualifications:

  • Experience in a people management or leadership role which includes coaching and developing others
  • Ability to motivate, encourage and coach others to develop strong relationship building and sales skills
  • Experience working with new product/service development teams and their outbound functions
  • Track record of building rapport with senior customer executives (e.g. CEO, CIO, CTO), building close relationships, and helping customers execute on large engagements
  • Experience and success in negotiating complex deals with customers and partners
  • Experience carrying quotas, while consistently exceeded them by doing the right thing for customers
  • Strong CX background with history of growing a Contact Center, VDI, or Unified Communications business
  But we used

  for strong headings; that's okay. Benefits:

  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. Learn more about our benefits at https://amazon.jobs/en/benefits.

  Pay:

  Pay

  USA, GA, Atlanta - $187,000.00 - $252,900.00 USD annually

  USA, NY, New York - $205,700.00 - $278,200.00 USD annually

  USA, TX, Austin - $187,000.00 - $252,900.00 USD annually

  USA, WA, Seattle - $187,000.00 - $252,900.00 USD annually

  We could combine into a list but it's fine. Now ensure we didn't include any boilerplate. Check for any leftover EEO etc: removed. Check for duplicated lines: we haven't duplicated. Check for location preferences: we included in About the role paragraph. Let's craft About the role paragraph: include all the description plus location preferences. We need to be careful not to miss any substantive info: The description includes many sentences; we need to preserve them. We'll combine into a paragraph but could be long; it's okay. Let's write:

  This position is part of the AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our