Senior Business Development Manager, Business Development, AWS Enterprise Support

We need to output HTML fragment with sections: headings

for sections like 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. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. Must not create sections with placeholder text. We need to parse the description: It includes a lot of description about role, responsibilities, qualifications, etc. We need to extract sections. We have: - Description (intro) about AWS Applied AI Solutions organization, vision, etc. This could be "About the role" maybe. - "Key job responsibilities" list bullet points. - "About The Team" includes subsections: Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. These are more about company culture; could be considered part of "About the role" or separate sections? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Likely we have: - About the role: introductory paragraph(s) describing role, vision, etc. - Responsibilities: the bullet list under "Key job responsibilities". - Requirements: maybe "Basic Qualifications" list. - Qualifications: maybe "Preferred Qualifications". - Skills: maybe not explicitly listed; but we could infer from qualifications? However we should not create a Skills section unless there is explicit content. The posting does not have a separate "Skills" heading; but we could treat some of the qualifications as skills? The instruction: only include a section when posting has real, specific content for it. There's no explicit Skills section, but we could combine skills into Qualifications? Probably better to not create Skills section if not explicit. - Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also "Learn more about our benefits at ...". So we have benefits content. - Pay: The posting includes salary ranges for various locations: "The base salary range for this position is listed below. ... USA, CA, San Diego - 147,900.00 - 200,100.00 USD annually" etc. So we have pay info. - Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section. Thus we will output sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, basic qualifications, preferred qualifications, benefits details, pay ranges. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About The Team" subsections? Those are not part of the standard headings but contain substantive info about culture. Should we include them? They are not under the allowed headings but they are substantive. The instruction says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to map content to those headings. The "About The Team" content could be considered part of "About the role" or maybe we could create a separate section like "About the team" but not in the list. Safer to incorporate that content into About the role section (since it's about team culture). However we must preserve all substantive info; we can include it in About the role as prose. We must not repeat the job title as a heading. The job title is "Premium Support BDM" maybe. Not included. We must not put Job ID/requisition numbers as headings; we can drop them. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, the Los Angeles County applicants text, the accommodation link, the "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also the "Amazon is an equal opportunity employer..." etc. Also the "Our inclusive culture empowers Amazonians..." etc. Also the "If you have a disability..." etc. Also the "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also the "Company - Amazon Web Services, Inc." line. Also the "Job ID: A10512660". Also the "Description" heading maybe? We can ignore. We need to keep the substantive content: the introductory paragraphs about AWS Applied AI Solutions organization, vision, etc. The "As Premium Support BDM, you will be part of the Enterprise Support organization..." paragraph describing role. Also the bullet list under "Key job responsibilities". Also the "About The Team" subsections (Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth). Also the "Basic Qualifications" list. Also the "Preferred Qualifications" list. Also the benefits paragraph. Also the pay ranges. We need to format as HTML fragment. Let's extract and rewrite. First, About the role: combine the initial description paragraphs (starting from "Description As part of the AWS Applied AI Solutions organization...") and the paragraph starting with "As Premium Support BDM, you will be part of the Enterprise Support organization..." plus maybe the "About The Team" subsections? But we could also treat "About The Team" as part of About the role. However the "About The Team" includes headings like Diverse Experiences, Why AWS, etc. Those are not lists but could be turned into

  paragraphs. We'll keep them as prose. We need to ensure we don't lose any bullet points. Let's extract bullet points for responsibilities: - Engage customers, partners, and field teams to deeply understand and measure customer value and pain points in adoption of Enterprise Support Services (Enterprise Support, Enterprise On-Ramp, Migration Services, plus other new products launched throughout the year) - Analyze drivers of Enterprise Support Services adoption and identify levers for improvement - Identify, design and execute controlled experiments in driving Enterprise Support Services adoption - Review and analyze Enterprise Support Services pricing and costing, ensuring savings are passed on to our customers - Quantify impact of Enterprise Support Services adoption on AWS Platform adoption, estimate the ROI of Support investments in accelerating AWS platform adoption - Develop and refine sales collateral, reference cases and value proofs for customers and partners - Drive commercial innovation in Support, e.g. differentiated support offerings per customer segment. - In conjunction with Field Enablement, create Support related training programs and material for the field team so that they can properly articulate the Support value proposition - Work with stakeholders across Commercial/Public Sales, Premium Support, and Enterprise - Prepare and present business reviews to the senior Sales and BD management team - Drive Enterprise Support Services deals end to end with Sales Now Basic Qualifications list (each line starts with bullet? Actually they are separate lines but each is a qualification). Let's capture: - 5+ years of developing, negotiating and executing business agreements experience - 5+ years of professional or military experience - 5+ years of working with Core Cloud Technology Services, including, but not limited to Compute, Edge, Hybrid, Security, and/or Networking experience - 5+ years of working with Business Application Technologies, including, but not limited to End User Compute (EUC), Supply Chain, Contact Center as a Service, Consumer Data Applications, Encrypted Communications, and/or Communication Developer Services experience - 5+ years of Go-To-Market, Business Development, Sales, or Consulting experience - 5+ years of in program management, workforce strategy development, or metrics-driven decision making experience - Bachelor's degree - Experience developing strategies that influence leadership decisions at the organizational level - Experience managing programs across cross functional teams, building processes and coordinating release schedules - Experience selling enterprise software or cloud-based applications - Experience explaining complex technical concepts to various business and technical audiences - Experience presenting to both technical and non-technical executive audiences - Experience leading complex, multi-year initiatives that may be cross-functional and/or span business and technology Preferred Qualifications list: - 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 identifying, negotiating, and executing complex legal agreements - Experience designing, implementing, and scaling workforce development programs across large-scale operations, 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 Benefits paragraph: "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 and restricted stock units (RSUs)." Also "Final compensation will be determined based on factors including experience, qualifications, and location." Also "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Actually that sentence appears before the pay ranges. We'll include that as part of Pay section maybe. Pay: list of ranges per location: - USA, CA, San Diego - 147,900.00 - 200,100.00 USD annually - USA, GA, Atlanta - 147,900.00 - 200,100.00 USD annually - USA, NY, New York - 162,700.00 - 220,200.00 USD annually - USA, OR, Portland - 147,900.00 - 200,100.00 USD annually - USA, TX, Austin - 147,900.00 - 200,100.00 USD annually - USA, TX, Dallas - 147,900.00 - 200,100.00 USD annually - USA, VA, Herndon - 147,900.00 - 200,100.00 USD annually - USA, WA, Bellevue - 147,900.00 - 200,100.00 USD annually We should preserve all. Now we need to strip out boilerplate: The "About The Team" subheadings (Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth) are not boilerplate; they are substantive. We'll keep them as prose under About the role maybe. We also need to remove the "Los Angeles County applicants:" paragraph, the EEO statement, the accommodation link, the "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner.", the