Senior Customer Success Specialist, Connect Specialty Sales, Customer Success Specialists - Amazon Connect
About the role
... description ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
... salary ranges ...
We must ensure we preserve all substantive info. Let's extract About the role content: From description: "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. AWS is one of Amazon’s fastest growing businesses, servicing millions of customers in more than 190 countries, reshaping the way global enterprises consume information technology and powering the developers who are building the next generation of global industry leaders. AWS customers include some of the most innovative startups like Netflix, Pinterest, Airbnb, and Instagram as well as some of the largest global enterprises like Shell International, Unilever, Hitachi, Sharp, Bristol-Myers Squibb, and Samsung. AWS is seeking an experienced Contact Center as a Service (CCaaS) Customer Success Specialist for Amazon Connect. Connect was born out of Amazon’s own need for the best CCaaS solution that works at scale, while improving customer experience. Today, Connect is one of AWS's fastest growing services, leveraging native generative AI capabilities to improve customer and employee experiences. As a Connect Customer Success Specialist, you will act as a strategic advisor to customers, helping them innovate and optimize their contact center and customer experience through adoption of the Connect capabilities. You will lead cross-functional field teams in sales, solutions architecture, partner sales, product, and will work at the CxO level with customers to maximize the value of their Connect investment. The ideal candidate will have enterprise sales and/or consulting experience in Contact Center as a Service or similar SaaS solutions in areas such as telecommunications, VoIP, and/or or CRM/ERP applications. You will be passionate about customer experience and advocacy and bring the voice of the customer into the product development process. You will enjoy solving complex problems; our customers will rely on your guidance to scale Connect across their complex global businesses, overcoming technical and organizational roadblocks on the way." We can keep that as About the role. Responsibilities: "Key job responsibilities" list: - Serve as the primary point of contact for a portfolio of strategic customer accounts, managing relationships and being a strategic advisor, driving enterprise-wide adoption of Connect. - Deliver compelling presentations, product demos, sample solutions and programs, events, and discussions to enable customer success. - Build customer skills and proficiency with Connect. - Engage with C-level stakeholders to understand the value proposition of Connect and uncover new areas of business value. - Develop account plans in conjunction with field teams. - Meet annual revenue targets through increased adoption of Connect. - Work with partners and ISVs to extend reach & drive adoption of AWS solutions. Also "A day in the life" paragraph: "The Amazon Connect Customer Success Specialist (CSS) will create a matrix environment with resources from our partner community, Professional Services, AWS account teams, and Connect service team members to drive customer success. A CSS will run attach service plays, customer engagements to drive adoption of migrating services, work with our partner community to scale and align key members of the services team for optimization and retention efforts. Last, a CSS will uncover cases that align to Connect unique business value to be shared with AWS Marketing." We could include that as part of Responsibilities (maybe as additional bullet). Or we could add as separate paragraph under Responsibilities. Since it's descriptive, we can add as aafter the list, but still within Responsibilities section. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a list for the bullet responsibilities, then a
for the day in the life prose. Requirements (Basic Qualifications): - 5+ years of leading large-scale, technical or engineering programs with a proven record of thought leadership, business case development, realizing customer benefits, and successful program completion experience - 2+ years of customer-facing work, engaging with customer executives, technologists or partners to solve business problems with advanced technologies experience - Bachelor's degree in science, technology, engineering, math, business or equivalent - Experience leading technical and non-technical transformation project teams with a proven ability to work across broad functional teams We should keep as list. Qualifications (Preferred Qualifications): - PMP certification, or SCRUM/Agile, SAFe certification - Experience implementing cloud services including migrations and modernization projects or similar We should keep as list. Benefits: The posting says: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So benefits include sign-on payments and RSUs as part of compensation but could be under Pay? Actually they said "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation. Benefits: health insurance, 401(k) matching, paid time off, parental leave. Also maybe mention "comprehensive benefits". We'll include those. We must not include the link to learn more about benefits (that's application instruction? It's a link but maybe considered boilerplate; we should drop it). So we omit the link. Pay: Base salary ranges for locations: "USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually", "USA, NY, New York - 169,000.00 - 228,600.00 USD annually", "USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually". Also mention sign-on payments and RSUs. We'll include that. We must not include "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." That's substantive; we can keep that sentence as prose. Thus Pay section:
The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location.
Then maybe a- with each location? Could be list. Since it's a list of ranges, we can use
- USA, GA, Atlanta - $153,600 - $207,800 USD annually ... etc. Use numbers without .00? Keep as given. We should not include schedule. Now we need to output only HTML fragment, no markdown fences. Let's craft. Check for any duplicated lines: Ensure we don't repeat. We must not include any boilerplate like "Amazon is an equal opportunity employer..." etc. Remove. Also remove "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" as they are not under our headings; but they are substantive about team culture. Could we include them under About the role? The About the role section could incorporate some of that? But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding extra content under About the role that includes team culture. However we must not invent sections. We could add a paragraph under About the role that includes the team culture info. That would preserve substantive info. Let's see if we want to include that. The "About The Team" section includes: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are substantive.