Associate Account Executive, Startups

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. We need to parse description. Let's extract content: - About the role: The description includes paragraphs describing role: "This is not your typical Sales Development role..." etc. We can put that as prose under About the role. - Responsibilities: There is a "Key job responsibilities" bullet list. Let's extract each bullet. List items: - Work with other sales team members to ensure the opportunity is understood and next steps are clearly defined via demonstrations, discovery, and qualification. - Utilize product knowledge and internal resources that will help you leverage technical skillsets to meet customers’ needs. - Achieve all input and output goals including: contacts sourced, leads qualified, customer calls complete, meetings scheduled, and opportunities created. - Drive net new business via customer acquisition by leveraging one-to-many and one-to-one outbound campaigns in addition to qualifying inbound opportunities from marketing and partner channels. - Expand services breadth and consumption within your existing customer base via account planning and territory management. - Accurately track activity and develop pipeline using a CRM (Salesforce), with the ability to leverage self-service reporting tools. - Innovate new and creative ways to engage with new customers and expand on existing customer relationships. - Understand the technology footprint, technical challenges, and business objectives that each one of your customers faces. - About The Team: This is a section about team culture, but not required heading; we could put under About the role or maybe a separate section like "About the Team". Not in allowed headings list; we have only those headings. Could incorporate into About the role or maybe "Requirements"? Better to put under About the role. - Basic Qualifications: list: Experience navigating prospective accounts from and into a senior executive level to identify new customer opportunities; Bachelor's degree or equivalent. - Preferred Qualifications: Sales or equivalent certification; Experience using Salesforce; Experience with Microsoft Office products and applications. - Benefits: description: "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." - Pay: "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." Then later: "USA, WA, Seattle - 31.39 - 54.90 USD hourly". So we have pay range. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Skills: Could be derived from preferred qualifications: Salesforce, Microsoft Office, maybe technical acumen. But we have a Skills section allowed. We could include skills like "Salesforce proficiency", "Microsoft Office", "Technical acumen", "Account research", "Prospecting", "CRM usage". However we must not invent details; we can only include what is stated. The posting mentions "Experience using Salesforce", "Experience with Microsoft Office products and applications", "Utilize product knowledge and internal resources that will help you leverage technical skillsets", "Understand the technology footprint". We could list those as skills. But we need to decide if we want a Skills section. The instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. However we have separate headings for Requirements, Qualifications, Skills. We could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills under Skills (like Salesforce, Microsoft Office). That seems reasonable. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "If you have a disability..." etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Learn more about our benefits at ..." link? The instruction: remove application instructions. The benefits link maybe considered application instruction? It's more info; but we can keep benefits description but drop the link. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly application instruction but could be considered reference; but safer to keep benefits description without the link. Also remove "Company - Amazon Web Services, Inc." maybe minor metadata; we can drop. Now produce HTML:

About the role

... prose ...

Responsibilities

• ...
...

Requirements

• Experience navigating prospective accounts from and into a senior executive level to identify new customer opportunities
• Bachelor's degree or equivalent

Qualifications

• Sales or equivalent certification
• Experience using Salesforce
• Experience with Microsoft Office products and applications

Skills

• Salesforce proficiency
• Microsoft Office proficiency
• Technical acumen and product knowledge
• Account research and prospecting
• CRM (Salesforce) tracking and pipeline development

But some of these may be inferred; we must not invent. "Technical acumen and product knowledge" is mentioned: "Utilize product knowledge and internal resources that will help you leverage technical skillsets". So we can phrase as "Product knowledge and technical skillset utilization". That's okay. "Account research and prospecting" is mentioned: "own all top of funnel activity, conduct high quality account research and source net new contacts at scale". So we can include. "CRM (Salesforce) tracking and pipeline development" is mentioned: "Accurately track activity and develop pipeline using a CRM (Salesforce)". So okay. Now Benefits:

Benefits

• Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
• Parental leave

Pay:

Pay

Base salary range: $31.39 – $54.90 USD hourly (Seattle, WA). Compensation includes sign-on payments, restricted stock units (RSUs), and sales incentives, finalized based on experience, qualifications, and location.

We should not include schedule. Now ensure we don't repeat job title. No headings for Job ID. Now produce only HTML fragment. Check for any duplicated content: we have not included boilerplate. Let's craft the About the role paragraph: combine the introductory paragraphs describing role, mission, etc. Must preserve all substantive information; we can't omit details. Need to include all substantive info from description, but we can condense into prose as long as we keep all info. However we must not invent or summarize away detail. Summarizing may lose detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details; we must keep all specifics. Summarizing may be considered summarizing away detail. Safer to keep the original sentences as is, maybe as multiple paragraphs. Thus we should keep the descriptive text verbatim (or close) but we can break into

tags. We must not omit any detail. Let's extract the descriptive paragraphs: From start: "This is not your typical Sales Development role. Do you crave an environment that is fast-paced and highly innovative? Do you aspire to continuously learn and grow? Join a growing team at the market leader for cloud services and help shape the future of the North America Sales organization! Take the lead in unlocking growth potential for both new and existing AWS customers. As an AWS Demand Generation Representative you will be part of shaping the future of how technology is deployed for AWS customers. The Amazon Web Services cloud platform helps companies of all sizes transform and reinvent their businesses to meet the needs of their customers and communities around the world. From enabling rapid and individually customized cancer treatments to helping Fortune 500 companies meet their carbon emissions goals, the AWS technology stack is the backbone of some of the most innovative solutions to the World’s most pressing problems. According to Gartner, AWS is the leading cloud provider, both in terms of ability to execute and completeness of vision. With only 5% of all IT spend in the cloud, we are still in the early stages of what is possible. Shape the future of how technology is deployed for our customers. Amazon Web Services is growing our Cloud Sales Center (CSC) team to help more companies make the move to AWS. If you are passionate about cloud technology, sales, and driving meaningful impact to a wide variety of customers, AWS could be the right fit for your next career move. AWS offers an innovative environment where you can advance your career through our growing sales organization on a learning and earning path. Our Demand Generation team acts as the flywheel for pipeline and talent within the AWS Global Sales organization, focusing on prospects and customers of all types by generating new business opportunities across thousands of accounts. As a Demand Generation Representative (DGR), you will have the exciting opportunity to help prospects and customers solve critical business challenges, pursue growth, and maximize business impact using AWS solutions. You will own all top of funnel activity, conduct high quality account research and source net new contacts at scale to execute high volume prospecting, lead qualification and opportunity generation for your assigned territories. You will partner closely with Account Teams to develop a deep understanding of the primary industries, accounts and personas within your territories, developing new relationships across all organizational levels (from from technical admins to Line of Business executives). You will collaborate with internal and external partners to develop and execute comprehensive prospecting plans that identify new customer use cases. Once engaged with a customer or prospect, you will use effective communication and technical acumen to uncover and understand their critical business issues." That's a big block. We can keep as one

or split into multiple

for readability but must not lose any content. Splitting into multiple

is fine as long as we keep all sentences. We'll output that as

...

maybe multiple

tags. Now after that we have "Key job responsibilities" heading; we will put under Responsibilities. After responsibilities we have "About The Team" section with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is substantive info about team and culture. We could include under About the role or maybe a separate section but not in allowed headings. Could incorporate into About the role as additional paragraphs. That would preserve all info. Thus About the role will include the initial description plus the About The Team content. Let's extract About The Team content: "About The Team 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 Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion