Sr Sales Manager - AI Applications, Spec Sales - Amazon Connect
or drop it. We need to include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. We need to prefer few substantive sections over many thin ones. We need to output only HTML fragment, no /, no markdown fences. Thus we need to decide which sections to include. Let's extract content: - Description: includes overview of ASP, AWS, role description. Could be "About the role" or maybe "Responsibilities". The description includes responsibilities later. - "Key job responsibilities" section: bullet list of responsibilities. - "About The Team" section: includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is more about team/culture. - "Basic Qualifications" and "Preferred Qualifications": these are qualifications. - There's also "LOCATIONS: Preference for Austin, TX, Chicago, IL, Atlanta, GA, New York, NY". That's location info. - Pay: "The base salary range for this position is listed below." Then lists ranges for various locations. So we have pay info. - Benefits: mention of comprehensive benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also link. Thus we can have sections: About the role (maybe from description), Responsibilities (from Key job responsibilities), Qualifications (maybe combine Basic and Preferred), Benefits, Pay, Schedule? No schedule info given. So we should not include Schedule. We need to decide about "Skills" section: maybe not needed if qualifications cover. We need to avoid filler like "commensurate with experience". Not present. We need to not repeat job title. We need to include location maybe as a short paragraph. We need to drop duplicated lines: there may be duplicates like "Amazon is an equal opportunity employer..." which is EEO boilerplate; we should remove that. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at https://..." maybe keep benefits description but drop link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits may be considered navigation? It's a link to benefits page; but it's part of benefits description. Might be okay to keep but maybe drop as it's a link. Safer to keep benefits description but drop the link? The instruction says remove application instructions; not necessarily links. But to be safe, we can keep benefits description without the link. We need to preserve all substantive information: so we need to keep the salary ranges, benefits description, qualifications, responsibilities, about the team, location. We need to format using
for section headings, - for any list of duties/requirements/benefits, and
for prose.
Thus we need to decide which content is list vs prose.
Responsibilities: list of duties; we can make
- .
Qualifications: Basic and Preferred; could be two lists or combine.
Benefits: list of benefits.
About the Team: could be prose paragraphs.
Location: maybe a short paragraph.
Pay: maybe a paragraph with salary ranges.
We need to avoid creating sections with filler.
Thus sections:
- About the role (maybe from initial description). Could be a paragraph summarizing role.
- Responsibilities (list)
- Qualifications (list) maybe split into Basic and Preferred as subheadings? But we only allowed h3 for section headings; we could have h3 for Qualifications and then inside maybe
for Basic and Preferred? Or we could have two sections: Basic Qualifications and Preferred Qualifications each as h3. That's okay if they have real content. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists Qualifications as an example; but we could also have Basic Qualifications and Preferred Qualifications as separate headings? Might be okay but they'd be variations. Safer to have one Qualifications section with two sublists maybe using
to label.
But we need to use
- for any list of duties/requirements/benefits. So for qualifications we can make a list.
Thus:
About the role
...
Responsibilities
- ...
Qualifications
- Basic: ...
- Preferred: ...
maybe.
But we need to preserve all details: 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.
We need to keep all that.
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."
We can list each as - .
Pay: The base salary range for this position is listed below. Then lists ranges for locations: 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 present as a
- each location range.
Location: "LOCATIONS: Preference for Austin, TX, Chicago, IL, Atlanta, GA, New York, NY". Could be a
.
About The Team: includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is a lot of content; we could make a section "About the Team" with paragraphs.
We need to avoid duplication: The "About The Team" section includes headings like Diverse Experiences, Why AWS?, etc. Those are subheadings inside; but we only need to output h3 for main sections. We could keep the content as paragraphs.
We need to remove boilerplate: The EEO statement, accommodation link, etc. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction; remove.
Also "Company - Amazon Web Services, Inc." maybe minor metadata; we could drop or fold into a short p.
Job ID: also drop.
Thus final HTML:
About the role
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.
Responsibilities
- Drive strategic workloads to deepen business and technical relationships with customers and partners.
- Invest 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.
- 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.
- Analyze and determine key customer insights from business drivers, market trends, customer feedback, and operating metrics.
- Establish clear goals for your team, including quotas.
- Ensure that your team is managing opportunities effectively throughout the sales cycle and practicing good pipeline hygiene.
- Plan and allocate for the best use of team resources in order to meet goals and quotas.
About the Team
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.
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.
Why AWS?: Amazon Web
for prose. Thus we need to decide which content is list vs prose. Responsibilities: list of duties; we can make
- .
Qualifications: Basic and Preferred; could be two lists or combine.
Benefits: list of benefits.
About the Team: could be prose paragraphs.
Location: maybe a short paragraph.
Pay: maybe a paragraph with salary ranges.
We need to avoid creating sections with filler.
Thus sections:
- About the role (maybe from initial description). Could be a paragraph summarizing role.
- Responsibilities (list)
- Qualifications (list) maybe split into Basic and Preferred as subheadings? But we only allowed h3 for section headings; we could have h3 for Qualifications and then inside maybe
for Basic and Preferred? Or we could have two sections: Basic Qualifications and Preferred Qualifications each as h3. That's okay if they have real content. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists Qualifications as an example; but we could also have Basic Qualifications and Preferred Qualifications as separate headings? Might be okay but they'd be variations. Safer to have one Qualifications section with two sublists maybe using
to label. But we need to use
- for any list of duties/requirements/benefits. So for qualifications we can make a list.
Thus:
About the role
...
Responsibilities
- ...
Qualifications
- Basic: ...
- Preferred: ...
- .
Pay: The base salary range for this position is listed below. Then lists ranges for locations: 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 present as a
- each location range.
Location: "LOCATIONS: Preference for Austin, TX, Chicago, IL, Atlanta, GA, New York, NY". Could be a
. About The Team: includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is a lot of content; we could make a section "About the Team" with paragraphs. We need to avoid duplication: The "About The Team" section includes headings like Diverse Experiences, Why AWS?, etc. Those are subheadings inside; but we only need to output h3 for main sections. We could keep the content as paragraphs. We need to remove boilerplate: The EEO statement, accommodation link, etc. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction; remove. Also "Company - Amazon Web Services, Inc." maybe minor metadata; we could drop or fold into a short p. Job ID: also drop. Thus final HTML:
About the role
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.
Responsibilities
- Drive strategic workloads to deepen business and technical relationships with customers and partners.
- Invest 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.
- 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.
- Analyze and determine key customer insights from business drivers, market trends, customer feedback, and operating metrics.
- Establish clear goals for your team, including quotas.
- Ensure that your team is managing opportunities effectively throughout the sales cycle and practicing good pipeline hygiene.
- Plan and allocate for the best use of team resources in order to meet goals and quotas.
About the Team
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.
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.
Why AWS?: Amazon Web
- each location range.
Location: "LOCATIONS: Preference for Austin, TX, Chicago, IL, Atlanta, GA, New York, NY". Could be a
- for any list of duties/requirements/benefits. So for qualifications we can make a list.
Thus: