Sr Enterprise Sales Leader
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real, specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..."? That's maybe part of benefits but we need to include benefits if present. The posting includes 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." Also earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." Also "The base salary range for this position is listed below." Then location and salary range: "USA, NY, New York - 205,700.00 - 278,200.00 USD annually". So we have Pay section (salary range). Benefits section (list). Schedule? Not mentioned. Responsibilities? The description includes responsibilities: "own driving adoption of Amazon Web Services within our Energy vertical. As a second line sales leader, you will build a business focused on helping enterprise customers innovate and exceed revenue goals. This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and our customers. You will establish and maintain high-level relationships within key accounts, driving innovation and next-gen capabilities across infrastructure and business application landscapes." That's responsibilities. Also maybe "About The Team" and "About AWS" could be considered "About the role"? But we have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have Basic Qualifications and Preferred Qualifications. Those go under Requirements or Qualifications. We'll use "Qualifications" heading for both basic and preferred? Could separate into Requirements (basic) and Preferred Qualifications (preferred). But we need to avoid thin sections. Perhaps combine into one "Qualifications" section with subpoints? But we must use - for any list of duties/requirements/benefits. So we can have a
Qualifications
then - for each qualification item. Could separate basic and preferred as separate lists? Might be okay.
Skills? Not explicitly listed besides "business savvy and sales leadership background". Could be part of responsibilities. We may not need a Skills section if not explicit.
Responsibilities: we can list bullet points.
About the role: maybe we can combine description paragraph into
under About the role heading.
We must not include headings with filler text. So we need to ensure each heading has substantive content.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
- Description paragraph: "As AWS continues to rapidly grow, we seek a Sr. Sales Leader to own driving adoption of Amazon Web Services within our Energy vertical. As a second line sales leader, you will build a business focused on helping enterprise customers innovate and exceed revenue goals. This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and our customers. You will establish and maintain high-level relationships within key accounts, driving innovation and next-gen capabilities across infrastructure and business application landscapes."
That's responsibilities.
- About The Team paragraph: "AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and unwavering support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow."
- About AWS paragraph: "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."
- Diverse Experiences paragraph: "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? Actually there are subheadings: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are sections under "Why AWS?" but we may treat them as part of Benefits? They are more about culture. Could be considered as part of "Benefits"? Not exactly. The instruction says use headings like Benefits, Pay, Schedule. So we may not need to create separate headings for Inclusive Team Culture etc. However we could include them under Benefits? But they are not benefits like insurance etc. Might be better to omit those sections because they are not explicitly requested headings. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. So we could combine culture info into a "Benefits" section? But benefits usually refer to compensation/benefits. The culture sections are not benefits. Might be better to create a section "About AWS" or "About the Team". However the examples didn't list those but they said e.g., meaning we can use other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings, but we can use others if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the pattern. However they also say "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (maybe combine description), Responsibilities, Qualifications, Benefits, Pay. That's five sections.
We need to include all substantive info: description, about the team, about AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance. Those are all substantive but could be folded into "About the role" or "About AWS" etc. But we risk losing detail if we just paraphrase. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the exact sentences? Not necessarily exact, but we must not lose detail. We can include them as paragraphs under appropriate headings.
We could have a section "About AWS and the Team" that includes the paragraphs about team, AWS, diverse experiences, inclusive culture, mentorship, work-life balance. That would preserve all.
But we need to avoid creating thin sections. One big section is okay.
Thus:
About the role
... description paragraph ...
Responsibilities
- ... maybe break responsibilities into bullet points? The description paragraph already covers responsibilities. Could we just keep as paragraph under About the role and not have Responsibilities? But we need to include responsibilities if present. The description includes responsibilities; we could treat that as responsibilities. But we already used About the role for description. Might duplicate.
Better: Use About the role for brief overview, Responsibilities for bullet list of duties. Let's extract responsibilities as bullet points:
- Own driving adoption of Amazon Web Services within the Energy vertical.
- As a second line sales leader, build a business focused on helping enterprise customers innovate and exceed revenue goals.
- Bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and customers.
- Establish and maintain high-level relationships within key accounts.
- Drive innovation and next-gen capabilities across infrastructure and business application landscapes.
We need to ensure we don't lose any detail from description. The description also includes "This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team..." That's a qualification rather than responsibility. Actually it's a requirement. So we should move that to Qualifications.
Thus responsibilities bullets: own driving adoption; build business; establish/maintain high-level relationships; drive innovation and next-gen capabilities.
Now About the role could be a short overview: "As AWS continues to rapidly grow, we seek a Sr. Sales Leader to own driving adoption of Amazon Web Services within our Energy vertical." That's basically the first sentence. But we already used that in responsibilities. Might be okay to have About the role as a brief summary.
Qualifications: Basic Qualifications: 10+ years of technology sales experience; Experience in sales team management. Preferred Qualifications: Bachelor's degree or equivalent.
We could also include "business savvy and sales leadership background" as a qualification (maybe from description). But that's more like a skill. We'll put under Qualifications.
Thus Qualifications section:
- 10+ years of technology sales experience
- Experience in sales team management
- Bachelor's degree or equivalent (preferred)
- Business savvy and sales leadership background
But we need to differentiate basic vs preferred? Not required.
Skills: Not explicitly listed besides maybe "business savvy and sales leadership background". Could omit Skills section.
Benefits: list: sign-on payments, restricted stock units (RSUs), sales incentives; 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, parental leave. Also mention inclusive team culture, mentorship & career growth, work/life balance? Those are more cultural benefits but could be included under Benefits as bullet points? Might be okay.
But we should not invent details. We have those paragraphs: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. We'll include them as bullet points under Benefits.
Pay: Salary range: USA, NY, New York - 205,700.00 - 278,200.00 USD annually. Also mention base salary range, sign-on payments, RSUs, sales incentives (these are part of compensation). We'll put under Pay: base salary range, plus note about sign-on payments, RSUs, sales incentives.
Schedule: Not mentioned, so omit.
Now we need to ensure we don't include boilerplate: remove equal opportunity employer lines, accommodation link, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we should remove as it's application instruction? It's not exactly instruction but it's a link; we can drop.
Also remove "Company - Amazon Web Services, Inc. Job ID: A10540962". That's metadata; we can
Qualifications
then- for each qualification item. Could separate basic and preferred as separate lists? Might be okay.
Skills? Not explicitly listed besides "business savvy and sales leadership background". Could be part of responsibilities. We may not need a Skills section if not explicit.
Responsibilities: we can list bullet points.
About the role: maybe we can combine description paragraph into
under About the role heading. We must not include headings with filler text. So we need to ensure each heading has substantive content. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: - Description paragraph: "As AWS continues to rapidly grow, we seek a Sr. Sales Leader to own driving adoption of Amazon Web Services within our Energy vertical. As a second line sales leader, you will build a business focused on helping enterprise customers innovate and exceed revenue goals. This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and our customers. You will establish and maintain high-level relationships within key accounts, driving innovation and next-gen capabilities across infrastructure and business application landscapes." That's responsibilities. - About The Team paragraph: "AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and unwavering support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow." - About AWS paragraph: "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." - Diverse Experiences paragraph: "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? Actually there are subheadings: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are sections under "Why AWS?" but we may treat them as part of Benefits? They are more about culture. Could be considered as part of "Benefits"? Not exactly. The instruction says use headings like Benefits, Pay, Schedule. So we may not need to create separate headings for Inclusive Team Culture etc. However we could include them under Benefits? But they are not benefits like insurance etc. Might be better to omit those sections because they are not explicitly requested headings. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. So we could combine culture info into a "Benefits" section? But benefits usually refer to compensation/benefits. The culture sections are not benefits. Might be better to create a section "About AWS" or "About the Team". However the examples didn't list those but they said e.g., meaning we can use other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings, but we can use others if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the pattern. However they also say "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (maybe combine description), Responsibilities, Qualifications, Benefits, Pay. That's five sections. We need to include all substantive info: description, about the team, about AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance. Those are all substantive but could be folded into "About the role" or "About AWS" etc. But we risk losing detail if we just paraphrase. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the exact sentences? Not necessarily exact, but we must not lose detail. We can include them as paragraphs under appropriate headings. We could have a section "About AWS and the Team" that includes the paragraphs about team, AWS, diverse experiences, inclusive culture, mentorship, work-life balance. That would preserve all. But we need to avoid creating thin sections. One big section is okay. Thus:
About the role
... description paragraph ...
Responsibilities
- ... maybe break responsibilities into bullet points? The description paragraph already covers responsibilities. Could we just keep as paragraph under About the role and not have Responsibilities? But we need to include responsibilities if present. The description includes responsibilities; we could treat that as responsibilities. But we already used About the role for description. Might duplicate.
Better: Use About the role for brief overview, Responsibilities for bullet list of duties. Let's extract responsibilities as bullet points:
- Own driving adoption of Amazon Web Services within the Energy vertical.
- As a second line sales leader, build a business focused on helping enterprise customers innovate and exceed revenue goals.
- Bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and customers.
- Establish and maintain high-level relationships within key accounts.
- Drive innovation and next-gen capabilities across infrastructure and business application landscapes.
We need to ensure we don't lose any detail from description. The description also includes "This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team..." That's a qualification rather than responsibility. Actually it's a requirement. So we should move that to Qualifications.
Thus responsibilities bullets: own driving adoption; build business; establish/maintain high-level relationships; drive innovation and next-gen capabilities.
Now About the role could be a short overview: "As AWS continues to rapidly grow, we seek a Sr. Sales Leader to own driving adoption of Amazon Web Services within our Energy vertical." That's basically the first sentence. But we already used that in responsibilities. Might be okay to have About the role as a brief summary.
Qualifications: Basic Qualifications: 10+ years of technology sales experience; Experience in sales team management. Preferred Qualifications: Bachelor's degree or equivalent.
We could also include "business savvy and sales leadership background" as a qualification (maybe from description). But that's more like a skill. We'll put under Qualifications.
Thus Qualifications section:
- 10+ years of technology sales experience
- Experience in sales team management
- Bachelor's degree or equivalent (preferred)
- Business savvy and sales leadership background
- ... maybe break responsibilities into bullet points? The description paragraph already covers responsibilities. Could we just keep as paragraph under About the role and not have Responsibilities? But we need to include responsibilities if present. The description includes responsibilities; we could treat that as responsibilities. But we already used About the role for description. Might duplicate.
Better: Use About the role for brief overview, Responsibilities for bullet list of duties. Let's extract responsibilities as bullet points:
- Own driving adoption of Amazon Web Services within the Energy vertical.
- As a second line sales leader, build a business focused on helping enterprise customers innovate and exceed revenue goals.
- Bring together a cross functional team including sales, partner and product teams to deliver accelerated business growth for AWS and customers.
- Establish and maintain high-level relationships within key accounts.
- Drive innovation and next-gen capabilities across infrastructure and business application landscapes.
We need to ensure we don't lose any detail from description. The description also includes "This leader must have the business savvy and sales leadership background necessary to bring together a cross functional team..." That's a qualification rather than responsibility. Actually it's a requirement. So we should move that to Qualifications.
Thus responsibilities bullets: own driving adoption; build business; establish/maintain high-level relationships; drive innovation and next-gen capabilities.
Now About the role could be a short overview: "As AWS continues to rapidly grow, we seek a Sr. Sales Leader to own driving adoption of Amazon Web Services within our Energy vertical." That's basically the first sentence. But we already used that in responsibilities. Might be okay to have About the role as a brief summary.
Qualifications: Basic Qualifications: 10+ years of technology sales experience; Experience in sales team management. Preferred Qualifications: Bachelor's degree or equivalent.
We could also include "business savvy and sales leadership background" as a qualification (maybe from description). But that's more like a skill. We'll put under Qualifications.
Thus Qualifications section: