Principal Sales Specialist, Analytics, US-FSI Technical Sales Specialists
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and inside we can have - for basic and preferred? Might need to differentiate? Could just list all qualifications together. But we need to preserve all substantive info; we can separate basic and preferred as separate
maybe with a note. But we must not invent headings like "Basic Qualifications". However we can keep them as plain text inside - maybe prefix with "Basic:". But better to keep as separate
with a preceding indicating basic vs preferred. That is acceptable.
- Requirements: Not explicitly present; but we could treat qualifications as requirements. However there is a "Key job responsibilities" which is responsibilities. There's no explicit "Requirements". Could we create a Requirements section from the qualifications? The instruction says use headings only if posting has real specific content for it. There's no explicit "Requirements" heading, but we could infer that qualifications are requirements. However we already have Qualifications section; maybe we don't need Requirements. The list of possible headings includes Requirements but we can omit if not present.
- About the role: we have initial description paragraph. So we can have About the role.
- Responsibilities: we have "Key job responsibilities" list.
- About The Team: could be part of About the role or separate? Could be a separate section "About the team". But not in the list of headings; but we could incorporate into About the role or maybe treat as part of About the role. The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit About the team. So we could embed team info within About the role or maybe as a separate section but not in allowed headings? It 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a heading like About the team. Instead we can incorporate that paragraph into About the role or Responsibilities. Probably About the role is appropriate to include role description and team context.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now craft HTML.
We'll start with About the role
then
containing the description paragraph(s) including the initial description, the technology list, the ideal candidate paragraph, and the About The Team paragraph.
We need to preserve all substantive info; we must not omit details like specific technologies, etc.
Let's extract the description text:
"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."
Then About The Team paragraph:
"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."
We'll combine.
Now Responsibilities: list from "Key job 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.
We need to keep each as
- .
Now Qualifications: Basic Qualifications and Preferred Qualifications.
Basic Qualifications:
- 7+ years of B2B or enterprise sales with a 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
Note there is duplicate "Experience interpreting data and making business recommendations" appears twice; we should keep both as separate items? Might be redundant but we must preserve all substantive info; we can keep both.
Now Benefits: paragraph:
"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 (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."
We should keep that.
Now Pay: we have multiple location salary ranges:
- 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
We need to present them. Could be a
- each.
Now ensure we removed boilerplate: EEO, equal opportunity, legal, scam warning, etc. Also removed "
- maybe with a note. But we must not invent headings like "Basic Qualifications". However we can keep them as plain text inside
- maybe prefix with "Basic:". But better to keep as separate
- with a preceding
- .
Now Qualifications: Basic Qualifications and Preferred Qualifications.
Basic Qualifications:
- 7+ years of B2B or enterprise sales with a 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
Note there is duplicate "Experience interpreting data and making business recommendations" appears twice; we should keep both as separate items? Might be redundant but we must preserve all substantive info; we can keep both.
Now Benefits: paragraph:
"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 (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."
We should keep that.
Now Pay: we have multiple location salary ranges:
- 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
We need to present them. Could be a
- each. Now ensure we removed boilerplate: EEO, equal opportunity, legal, scam warning, etc. Also removed "
indicating basic vs preferred. That is acceptable. - Requirements: Not explicitly present; but we could treat qualifications as requirements. However there is a "Key job responsibilities" which is responsibilities. There's no explicit "Requirements". Could we create a Requirements section from the qualifications? The instruction says use headings only if posting has real specific content for it. There's no explicit "Requirements" heading, but we could infer that qualifications are requirements. However we already have Qualifications section; maybe we don't need Requirements. The list of possible headings includes Requirements but we can omit if not present. - About the role: we have initial description paragraph. So we can have About the role. - Responsibilities: we have "Key job responsibilities" list. - About The Team: could be part of About the role or separate? Could be a separate section "About the team". But not in the list of headings; but we could incorporate into About the role or maybe treat as part of About the role. The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit About the team. So we could embed team info within About the role or maybe as a separate section but not in allowed headings? It 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? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a heading like About the team. Instead we can incorporate that paragraph into About the role or Responsibilities. Probably About the role is appropriate to include role description and team context. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with
About the role
thencontaining the description paragraph(s) including the initial description, the technology list, the ideal candidate paragraph, and the About The Team paragraph. We need to preserve all substantive info; we must not omit details like specific technologies, etc. Let's extract the description text: "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." Then About The Team paragraph: "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." We'll combine. Now Responsibilities: list from "Key job 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. We need to keep each as
- .
Now Qualifications: Basic Qualifications and Preferred Qualifications.
Basic Qualifications:
- 7+ years of B2B or enterprise sales with a 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
Note there is duplicate "Experience interpreting data and making business recommendations" appears twice; we should keep both as separate items? Might be redundant but we must preserve all substantive info; we can keep both.
Now Benefits: paragraph:
"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 (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."
We should keep that.
Now Pay: we have multiple location salary ranges:
- 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
We need to present them. Could be a