Associate Account Executive , Enterprise Greenfield
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to include Pay section if salary range present. It is present: "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. Amazon also offers comprehensive benefits including ...". Also there are specific hourly ranges for locations: "USA, TX, Austin - 31.39 - 54.90 USD hourly" and "USA, VA, Arlington - 31.39 - 54.90 USD hourly". So we can include Pay section with those details.
Benefits section: mention health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page but we should not include application instructions; linking to benefits maybe okay as it's not application instruction. But we might keep description of benefits without the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not application instruction; it's informational. Might keep but could be considered navigation? Safer to keep the description but drop the URL? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive? It's a reference; but we could keep the text "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; maybe we keep as part of benefits section. It's not application instruction. We'll keep.
We need to avoid duplication: The description includes "Amazon is an equal opportunity employer..." which is EEO boilerplate; remove.
Also "If you have a disability..." accommodation; remove.
Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove.
Also "Company - Amazon Web Services, Inc." maybe minor metadata; we can put in a short p.
Job ID also minor metadata; drop.
Now structure:
We could have sections:
- About the role (intro paragraph(s) describing role, mission, etc.)
- Responsibilities (list of key job responsibilities)
- Qualifications (maybe split Basic and Preferred? Could combine into one Qualifications section with subheadings? But we only allowed
for section headings; we could have nested? Not specified. Probably just one Qualifications section with both basic and preferred as lists. Could separate Basic Qualifications and Preferred Qualifications as subheadings using ? Not allowed. So we could just have one Qualifications section with two lists labeled via
maybe. But we need to use
- for any list of duties/requirements/benefits. So we can have two
under Qualifications, each preceded by a indicating Basic Qualifications and Preferred Qualifications.
- Benefits (list)
- Pay (list or prose)
Potentially also "About The Team" section? The posting includes "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is substantive content about team and culture. Should we include as a section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This is real content. Could be a section "About the Team". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list "About the Team". But we could still use that heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive list. But likely they expect only those headings. Safer to stick to those headings. The "About The Team" content could be folded into "About the role" or maybe "Qualifications"? Not ideal. Could treat as part of "About the role". We'll incorporate relevant team/culture info into About the role section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
Now extract content.
About the role: combine introductory paragraphs before "Key job responsibilities". Also include "About The Team" content maybe.
Let's parse:
Description starts: "Description This is not your typical entry-level sales role — it's a launchpad. At Amazon, our peculiar culture and obsession with delighting customers extends to everything we do, including what we call our teams. While the industry knows this role as a SDR, BDR, Associate Account Executive, Amazon's customer-first DNA means we call our team members "Customer Acquisition Representatives" (CARs). It's more than a name, it reflects our belief that every interaction should start and end with the customer. As a CAR, you'll accelerate pipeline growth, navigate complex customer landscapes, shift gears between strategic thinking and high-impact execution, and put customers in the driver's seat of their cloud journey. Every CAR needs fuel, yours will be curiosity, coaching, and the full support of the world's leading cloud platform. As a CAR, you will take the lead in unlocking growth potential for both new and existing AWS customers. We are one of the principal sources of new pipeline that fuels the AWS engine – engaging the unengaged accounts and contacts to drive pipeline that turns into revenue. Using cutting-edge AI tools and data-driven insights, you'll identify whitespace opportunities and develop innovative strategies to reach unengaged accounts at scale. You'll be part of shaping how technology is deployed across thousands of organizations, from enabling rapid, 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. Your career path is clear. This role is designed as the entry point into AWS's North American sales organization. We don't need the perfect candidate, but we do want people who are curious, coachable, and willing to learn. We've developed hundreds of early-career professionals into full cycle sellers as Cloud Sales Representatives (CSRs), many within 18–24 months. You'll be paired with mentors and have access to structured development programs that accelerate your growth from day one. According to Gartner, AWS is the leading cloud provider in both 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, and with the explosion of generative AI, the opportunity has never been larger. You'll be at the forefront, equipped with the most advanced AI-powered sales technology in the industry. Consider this your pit crew advantage — the tools, training, and teammates that keep you performing at your best."
Then "Key job responsibilities" list.
After responsibilities, there is "We know great candidates don't always check every box. If you're excited about this role but your experience doesn't perfectly match, we encourage you to apply."
Then "About The Team" heading and subsections.
Then "Basic Qualifications" and "Preferred Qualifications".
Then EEO etc.
Then salary and benefits.
Thus About the role section should include the introductory paragraphs plus maybe the "We know great candidates..." encouragement and maybe the About The Team content.
We'll include About The Team content as part of About the role.
Now Responsibilities: list items from "Key job responsibilities". Let's extract each bullet:
- Partner closely with Account Teams to develop a deep understanding of the primary industries, accounts, and personas within your territories — building relationships from technical admins to Line of Business executives.
- Lead 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 across your assigned territories.
- Drive net-new business via customer acquisition by leveraging one-to-one and one-to-many outbound campaigns, in addition to qualifying leads from marketing and partner channels.
- Expand services breadth and consumption within your existing customer base via account planning and territory management.
- Deliver results against input and output goals, including: contacts sourced, leads qualified, customer calls completed, meetings scheduled, and opportunities created and launched.
- Leverage AI-powered sales intelligence platforms, predictive analytics, and automation tools to identify high-propensity accounts, prioritize outreach, and optimize pipeline development in Salesforce.
- Stay ahead of the curve with next-generation engagement strategies using generative AI, agentic workflows, and advanced personalization engines — you'll be on the cutting edge of how AI transforms B2B sales, continuously testing and iterating on new approaches to reach unengaged accounts.
- Collaborate with teammates to share best practices, contribute to team learning, and collectively raise the bar for customer engagement.
Now Qualifications: Basic Qualifications:
- Bachelor's degree or equivalent
- 2+ year(s) of experience in sales, business development, lead generation, or customer-facing roles (internships and non-traditional experience count)
Preferred Qualifications:
- 1+ years of experience in technology sales, SaaS, or cloud services
- Experience with outbound prospecting tools and techniques (cold calling, social selling, email sequencing)
- Experience leveraging or interest in leveraging AI tools to enhance sales workflows, research, and outreach
Now Benefits: from text: "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, restricted stock units (RSUs), and sales incentives." That's compensation but could be part of Pay.
Pay: includes base salary range: "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 location-specific ranges: "USA, TX, Austin - 31.39 - 54.90 USD hourly" and "USA, VA, Arlington - 31.39 - 54.90 USD hourly". Also mention sign-on payments, RSUs, sales incentives.
Thus Pay section should include those details.
Now we need to output HTML fragment only.
We'll structure:
About the role
... (combined intro paragraphs plus encouragement and About The Team content)
Responsibilities
- ...
...
Qualifications
Basic Qualifications
- ...
- ...
Preferred
for prose. We need to include Pay section if salary range present. It is present: "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. Amazon also offers comprehensive benefits including ...". Also there are specific hourly ranges for locations: "USA, TX, Austin - 31.39 - 54.90 USD hourly" and "USA, VA, Arlington - 31.39 - 54.90 USD hourly". So we can include Pay section with those details. Benefits section: mention health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page but we should not include application instructions; linking to benefits maybe okay as it's not application instruction. But we might keep description of benefits without the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not application instruction; it's informational. Might keep but could be considered navigation? Safer to keep the description but drop the URL? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive? It's a reference; but we could keep the text "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; maybe we keep as part of benefits section. It's not application instruction. We'll keep. We need to avoid duplication: The description includes "Amazon is an equal opportunity employer..." which is EEO boilerplate; remove. Also "If you have a disability..." accommodation; remove. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. Also "Company - Amazon Web Services, Inc." maybe minor metadata; we can put in a short p. Job ID also minor metadata; drop. Now structure: We could have sections: - About the role (intro paragraph(s) describing role, mission, etc.) - Responsibilities (list of key job responsibilities) - Qualifications (maybe split Basic and Preferred? Could combine into one Qualifications section with subheadings? But we only allowed
for section headings; we could have nested? Not specified. Probably just one Qualifications section with both basic and preferred as lists. Could separate Basic Qualifications and Preferred Qualifications as subheadings using ? Not allowed. So we could just have one Qualifications section with two lists labeled via
maybe. But we need to use
- for any list of duties/requirements/benefits. So we can have two
- under Qualifications, each preceded by a
- ... ...
- ...
- ...
indicating Basic Qualifications and Preferred Qualifications. - Benefits (list) - Pay (list or prose) Potentially also "About The Team" section? The posting includes "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is substantive content about team and culture. Should we include as a section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This is real content. Could be a section "About the Team". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list "About the Team". But we could still use that heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive list. But likely they expect only those headings. Safer to stick to those headings. The "About The Team" content could be folded into "About the role" or maybe "Qualifications"? Not ideal. Could treat as part of "About the role". We'll incorporate relevant team/culture info into About the role section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now extract content. About the role: combine introductory paragraphs before "Key job responsibilities". Also include "About The Team" content maybe. Let's parse: Description starts: "Description This is not your typical entry-level sales role — it's a launchpad. At Amazon, our peculiar culture and obsession with delighting customers extends to everything we do, including what we call our teams. While the industry knows this role as a SDR, BDR, Associate Account Executive, Amazon's customer-first DNA means we call our team members "Customer Acquisition Representatives" (CARs). It's more than a name, it reflects our belief that every interaction should start and end with the customer. As a CAR, you'll accelerate pipeline growth, navigate complex customer landscapes, shift gears between strategic thinking and high-impact execution, and put customers in the driver's seat of their cloud journey. Every CAR needs fuel, yours will be curiosity, coaching, and the full support of the world's leading cloud platform. As a CAR, you will take the lead in unlocking growth potential for both new and existing AWS customers. We are one of the principal sources of new pipeline that fuels the AWS engine – engaging the unengaged accounts and contacts to drive pipeline that turns into revenue. Using cutting-edge AI tools and data-driven insights, you'll identify whitespace opportunities and develop innovative strategies to reach unengaged accounts at scale. You'll be part of shaping how technology is deployed across thousands of organizations, from enabling rapid, 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. Your career path is clear. This role is designed as the entry point into AWS's North American sales organization. We don't need the perfect candidate, but we do want people who are curious, coachable, and willing to learn. We've developed hundreds of early-career professionals into full cycle sellers as Cloud Sales Representatives (CSRs), many within 18–24 months. You'll be paired with mentors and have access to structured development programs that accelerate your growth from day one. According to Gartner, AWS is the leading cloud provider in both 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, and with the explosion of generative AI, the opportunity has never been larger. You'll be at the forefront, equipped with the most advanced AI-powered sales technology in the industry. Consider this your pit crew advantage — the tools, training, and teammates that keep you performing at your best." Then "Key job responsibilities" list. After responsibilities, there is "We know great candidates don't always check every box. If you're excited about this role but your experience doesn't perfectly match, we encourage you to apply." Then "About The Team" heading and subsections. Then "Basic Qualifications" and "Preferred Qualifications". Then EEO etc. Then salary and benefits. Thus About the role section should include the introductory paragraphs plus maybe the "We know great candidates..." encouragement and maybe the About The Team content. We'll include About The Team content as part of About the role. Now Responsibilities: list items from "Key job responsibilities". Let's extract each bullet: - Partner closely with Account Teams to develop a deep understanding of the primary industries, accounts, and personas within your territories — building relationships from technical admins to Line of Business executives. - Lead 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 across your assigned territories. - Drive net-new business via customer acquisition by leveraging one-to-one and one-to-many outbound campaigns, in addition to qualifying leads from marketing and partner channels. - Expand services breadth and consumption within your existing customer base via account planning and territory management. - Deliver results against input and output goals, including: contacts sourced, leads qualified, customer calls completed, meetings scheduled, and opportunities created and launched. - Leverage AI-powered sales intelligence platforms, predictive analytics, and automation tools to identify high-propensity accounts, prioritize outreach, and optimize pipeline development in Salesforce. - Stay ahead of the curve with next-generation engagement strategies using generative AI, agentic workflows, and advanced personalization engines — you'll be on the cutting edge of how AI transforms B2B sales, continuously testing and iterating on new approaches to reach unengaged accounts. - Collaborate with teammates to share best practices, contribute to team learning, and collectively raise the bar for customer engagement. Now Qualifications: Basic Qualifications: - Bachelor's degree or equivalent - 2+ year(s) of experience in sales, business development, lead generation, or customer-facing roles (internships and non-traditional experience count) Preferred Qualifications: - 1+ years of experience in technology sales, SaaS, or cloud services - Experience with outbound prospecting tools and techniques (cold calling, social selling, email sequencing) - Experience leveraging or interest in leveraging AI tools to enhance sales workflows, research, and outreach Now Benefits: from text: "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, restricted stock units (RSUs), and sales incentives." That's compensation but could be part of Pay. Pay: includes base salary range: "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 location-specific ranges: "USA, TX, Austin - 31.39 - 54.90 USD hourly" and "USA, VA, Arlington - 31.39 - 54.90 USD hourly". Also mention sign-on payments, RSUs, sales incentives. Thus Pay section should include those details. Now we need to output HTML fragment only. We'll structure:
About the role
... (combined intro paragraphs plus encouragement and About The Team content)
Responsibilities
Qualifications
Basic Qualifications
Preferred