CSC Account Manager, West Engaged Startups
About the role
... description paragraph(s) ... maybe combine into one paragraph. We need to keep all substantive info from description: The first paragraph about AWS, then the sentence about seeking Startup Account Manager, responsibilities, etc. Actually the description includes responsibilities as well, but we will separate responsibilities into its own section. So we need to split: About the role should contain the introductory description about AWS and the role purpose, not the responsibilities list. Let's extract: "Trusted by more startups around the world, AWS makes the power of cloud computing accessible for all by giving founders everywhere access to the same technology that powers the world’s largest companies. With 20 years of experience gained from supporting hundreds of thousands of startups that have come before, we help founders prove that their world-changing ideas are possible, at any stage of growth or level of funding. This is why more startups, and over 80% of unicorns, build on AWS. As AWS continues to rapidly grow, we seek a Startup Account Manager to help drive the growth of high-potential early, mid, and late stage startups." That seems appropriate for About the role. Then Responsibilities: list from "Key job responsibilities" plus maybe earlier sentence "Your responsibilities will include driving revenue and user adoption, migrations, and ensuring new startups select AWS as their primary cloud provider. You will align closely ...". Actually those are also responsibilities. We should include all responsibility statements. Thus Responsibilities section should include: - driving revenue and user adoption, migrations, and ensuring new startups select AWS as their primary cloud provider. - align closely with counterparts in business development, marketing, solution architecture and partner teams to lead execution of coordinated go-to-market strategies and sales plays. - work closely with business development teams who are driving strategic support, global co-programming, and portfolio engagement to help drive top-of-funnel customer acquisition and accelerate seller cycles in the field. - be at the heart of latest trends like artificial intelligence (AI), machine learning (ML), serverless and IoT. - customers leverage state-of-the-art technologies on AWS to innovate and become the next disrupters, like today’s AirBnB, Slack, DoorDash, and Lyft. - passionate about startups, a self-starter with a strong entrepreneurial spirit who is prepared to work in a fast-paced, often ambiguous environment, execute against ambitious goals, and consistently embrace the Amazon Culture. (maybe this is more about candidate traits, but could be responsibilities? Actually it's about candidate attributes; but we can keep it in Responsibilities or maybe About the role. However it's more about candidate qualities; but we can keep in Responsibilities as part of expectations.) Then the bullet list under "Key job responsibilities": - Ensure customer success with early, mid and late stage startups. - Drive revenue and market share in a defined territory or industry vertical. - Accelerate customer adoption through well-developed sales engagements and successful GTM. Strategy (maybe typo) - Meet or exceed quarterly revenue and goal targets. - Develop and execute against a comprehensive account/territory plan. - Create & articulate compelling value propositions around AWS services. - Accelerate customer adoption by engaging Founders, CxO, Board of Directors and VC influencers - Work with partners to extend reach & drive adoption. - Develop long-term strategic relationships with key accounts. - Ensure customer satisfaction. - Expect moderate travel. (maybe schedule) We'll include all. Requirements: Basic Qualifications list: - 5+ years of full sales cycle, technology sales or equivalent business development, sales engineering/consulting or equivalent experience - Bachelor's degree or equivalent Qualifications: Preferred Qualifications list: - Experience using sales CRM tools such as Salesforce - Experience (technical or educational) in Engineering or Computer Science - Experience driving new business in greenfield accounts at the C-suite level or equivalent - Experience with customer relationship management, especially C-suite level customer engagement Skills: maybe we could combine some of these as skills, but we already have Preferred Qualifications. Could we treat Preferred Qualifications as Skills? The instruction says use sections for Skills if posting has real specific content. We have Preferred Qualifications which are skills/experience. Could rename to Skills? But we already have Qualifications section for preferred qualifications. Might be redundant. Better to have Qualifications (Preferred) and Skills maybe from something else? There's no explicit skills list besides those. Could we put Preferred Qualifications under Skills and keep Qualifications for Basic? But the instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map: - About the role: intro. - Responsibilities: duties. - Requirements: basic qualifications. - Qualifications: preferred qualifications. - Skills: maybe we could extract skill keywords from preferred qualifications? But we could also leave Skills empty? Not allowed: we must not emit a heading followed by filler/placeholder text. So we should only include Skills if there is real specific content. Do we have any explicit skills list? Not really. The preferred qualifications are more like qualifications/experience. Could treat them as Skills. But then we would have both Qualifications and Skills with similar content; maybe we can merge: Use Qualifications for preferred qualifications, and Skills for something else like "Experience using sales CRM tools such as Salesforce" etc. But that's still qualifications. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Preferred Qualifications and Skills into one section called Qualifications (or Skills). But we need to follow the headings list: they gave examples but not mandatory to use all. We can choose which sections to include. So we can include About the role, Responsibilities, Requirements (basic), Qualifications (preferred), Benefits, Pay, Schedule. That's seven sections. That seems fine. We'll not include Skills separate. Now Benefits: we have description of benefits. Pay: we have salary ranges for two locations. Should we present as list? Could be
- USA, TX, Austin - $92,400 - $160,000 USD annually
- USA, WA, Seattle - $92,400 - $160,000 USD annually . Keep the exact numbers. Schedule: "Expect moderate travel." Could be a paragraph. Now ensure we don't include boilerplate: remove equal opportunity statement, disability accommodation request, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; is that substantive? It's a reference to benefits page; could be considered part of benefits. Might keep but it's a link; maybe we keep as part of benefits paragraph. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10561714". Also remove "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." That's substantive about compensation; we should keep that as part of Pay section maybe. Thus Pay section should include that paragraph plus the specific ranges. Now ensure we preserve all substantive info: The paragraph about base salary range, sign-on payments, RSUs, sales incentives, final compensation determination, and also the benefits paragraph. Now we need to