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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Description paragraph: "As an Analytics sales specialist ..." includes responsibilities, tasks.
- "Key job responsibilities" bullet list: Drive revenue..., Meet or exceed..., Develop and execute..., Develop working backwards..., Create & articulate..., Accelerate..., Maintain..., Work with partners..., Develop long-term..., Ensure..., Expect moderate travel.
- "About The Team" paragraph: description of team.
- "Basic Qualifications": 7+ years B2B or enterprise sales with focus on hunting new business experience; 10+ years of technology sales experience.
- "Preferred Qualifications": Master's degree in business, data science, public administration, finance, engineering, human resources, or related field, or PMP certificate; Experience interpreting data and making business recommendations; Experience designing, implementing, and scaling upskilling, apprenticeship, or workforce development programs across large-scale operations or corporate environments, including forecasting workforce needs and leveraging analytics to drive program decisions; Experience interpreting data and making business recommendations across leadership and cross-functional teams; Experience using analytical tools for workforce metrics and reporting.
- Then there is EEO boilerplate etc to remove.
- Then Los Angeles County applicants paragraph: job duties for this position include: work safely and cooperatively..., adhere to standards..., communicate effectively..., follow all federal...; Criminal history may have a direct...; Pursuant to the Los Angeles County Fair Chance Ordinance...; Pursuant to the San Francisco Fair Chance Ordinance...; Our inclusive culture...; If you have a disability...; If the country/region you’re applying in isn’t listed...; 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 health insurance..., 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits. USA, CA, San Francisco - 187,000.00 - 252,900.00 USD annually USA, MA, Boston - 170,000.00 - 230,000.00 USD annually USA, NJ, Jersey City - 187,000.00 - 252,900.00 USD annually USA, NY, New York - 187,000.00 - 252,900.00 USD annually Company - Amazon Web Services, Inc. Job ID: A10543753
We need to extract Pay and Benefits sections if present. Pay: base salary ranges listed for multiple locations. Benefits: health insurance etc. So we can include Pay and Benefits sections.
Schedule: not mentioned (no schedule info). So omit.
Skills: maybe not explicit; but we could infer from responsibilities? The instruction: include a section ONLY when posting has real, specific content for it. There's no explicit "Skills" heading. Could we create Skills from responsibilities? Probably not; better to omit if no explicit skills list. However we could include "Skills" if we infer from responsibilities? The rule says: "Prefer a few substantive sections over many thin ones." It doesn't forbid inferring, but says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we create Skills section, we need to have specific content. We could list skills like "strategic sales leadership, technical and business acumen, engaging C-suite, translating technical solutions, building consensus, developing value propositions, strategic analysis, enterprise sales, technical solution development". Those are mentioned in the description. So we could create a Skills section with those items as list. That seems acceptable as they are specific content.
Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine into Qualifications section with subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Qualifications can contain both basic and preferred.
Requirements: maybe we could separate basic qualifications as Requirements? But we have Qualifications heading; we could put both basic and preferred there. Requirements maybe for things like "must have" etc. But we can just put all qualifications under Qualifications. Or we could split: Requirements = basic qualifications, Qualifications = preferred? But the instruction says use those headings as appropriate. It's okay to have both Requirements and Qualifications if content exists. Let's see: Basic Qualifications are explicit requirements. Preferred Qualifications are preferred. So we can have Requirements (basic) and Qualifications (preferred). That seems logical.
Thus sections:
- About the role: maybe the initial description paragraph (the first paragraph) and maybe "About The Team"? Actually "About The Team" is about team, not role. Could be part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the initial description under About the role. Also maybe include "About The Team" under About the role? Could be separate but we don't have a heading for team. Could incorporate into About the role as additional paragraph.
- Responsibilities: the "Key job responsibilities" list.
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: derived from description (strategic sales leadership, technical and business acumen, etc.)
- Benefits: health insurance etc.
- Pay: salary ranges.
- Schedule: none, omit.
We must not include boilerplate like EEO, accommodation, etc. Also remove Los Angeles County applicants paragraph? That includes job duties (work safely etc.) which is substantive? It's about workplace safety and compliance; could be considered part of responsibilities? But it's more about general employment conditions. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Los Angeles County paragraph includes legal stuff (Fair Chance Ordinance) and accommodation info; that seems like legal/EEO boilerplate. Also includes "work safely and cooperatively..." which is generic. Likely considered boilerplate. So we should drop that entire paragraph.
Also remove "Our inclusive culture empowers Amazonians..." etc. That's also boilerplate.
Remove "If you have a disability..." accommodation line.
Remove "If the country/region you’re applying in isn’t listed..." etc.
Remove "Learn more about our benefits at ..." maybe we keep benefits description but not the link? The instruction: remove boilerplate, but benefits description is substantive. The link maybe considered boilerplate? Could keep but it's a link; maybe okay. Safer to keep benefits description without the link? The link is part of benefits info; but it's a URL. Might be okay to keep. However it's not boilerplate; it's a reference. I'd keep it.
Now compile HTML.
Structure:
About the role
As an Analytics sales specialist in this rapidly expanding field, you'll drive growth by helping customers leverage emerging technologies that directly impact their AI and technical capabilities to create business success. You will work backwards from customer goals and you'll create strategic plans that align AWS solutions with their desired outcomes. You will educate customers on "art of the possible" success stories and AWS enablers including Amazon Redshift, a managed petabyte-scale data warehouse for fast SQL analytics; Amazon Athena, for serverless SQL queries directly on S3 data; Amazon EMR, a managed big data platform for Spark, Hive, and Presto workloads; AWS Glue, a managed ETL service for data preparation and transformation; AWS Lake Formation, for simplified data lake creation and management; AWS SageMaker Studio, a unified IDE for end-to-end machine learning workflows; Amazon Kinesis and MSK for real-time data streaming and processing; and Amazon OpenSearch, a managed search and analytics engine. You'll help customers understand how this analytics foundation enables them to build and deploy AI/ML solutions using Amazon Bedrock, Amazon SageMaker, and other AWS AI services to drive business transformation. Then you will work with a specialized solution architect to craft a solution spanning these solutions as well as selected partner products and manage the sales process including evaluation, pricing, objection handling, navigating competitive pressures, proofs of concept and construction of a supporting business case. The ideal candidate combines strategic sales leadership with deep technical and business acumen. You will collaborate across AWS teams, including sales representatives, solutions architects, product managers, professional services, and partners to drive customer success. You should have experience engaging confidently with both C-suite executives and technical stakeholders, demonstrating the ability to translate complex technical solutions into clear business value. Your background should reflect success in building consensus across organizations, developing compelling value propositions, and navigating technical and business challenges. Experience in strategic analysis, enterprise sales, and technical solution development is essential, as you'll need to understand both the technical architecture and business implications of modern data and AI solutions.
About The Team The Amazon Specialist Sales team positions AWS as the best place to move customer workloads into the cloud. As part of a single-threaded sales team focusing on Financial Services customers you will be responsible for working with strategic customers and their existing account teams to qualify and pursue sales opportunities for enterprise application workloads and datacenter migration projects. You will engage with our segment sales, solutions architects, partner, and professional services organizations to drive highly complex opportunities to closure. These opportunities will include migrating Data Warehouses and building Data Foundations for AI. We pride ourselves on thinking big, delivering exceptional results for our customers, and working across AWS as #OneTeam.
Then Responsibilities:
Responsibilities
- Drive revenue and market share in a defined territory.
- Meet or exceed annual revenue targets.
- Develop and execute against a comprehensive account/territory plan.
- Develop working backwards analytics visions including business case and financial justification, potentially gleaned from earnings reports.
- Create & articulate compelling value propositions around AWS analytics services.
- Accelerate customer adoption of Amazon analytics services.
- Maintain a robust sales pipeline leveraging sales force automation tools and best practices.
- Work with partners to extend reach & drive adoption.
- Develop long-term strategic relationships with key accounts.
- Ensure customer satisfaction.
- Expect moderate travel.
Requirements (Basic Qualifications):
Requirements
- 7+ years of B2B or enterprise sales with a focus on hunting new business experience.
- 10+ years of technology sales experience.
Qualifications (Preferred Qualifications):
Qualifications
- Master's degree in business, data science, public administration, finance, engineering, human resources, or related field, or PMP certificate.
- Experience interpreting data and making business recommendations.
- Experience designing, implementing, and scaling upskilling, apprenticeship, or workforce development programs across large-scale operations or corporate environments, including forecasting workforce needs and leveraging analytics to drive program decisions.
- Experience interpreting data and making business recommendations across leadership and cross-functional teams.
- Experience using analytical tools for workforce metrics and reporting.
Skills:
We need to list skills derived: strategic sales leadership, deep technical and business acumen, engaging C-suite executives and technical stakeholders, translating complex technical solutions into clear business value, building consensus across organizations, developing compelling value propositions, navigating technical and business challenges, strategic analysis, enterprise sales, technical solution development, understanding technical architecture and business implications of modern data and AI solutions.
Let's make list.
Skills
- Strategic sales leadership