Business Development Manager, AWS Cloud Intelligence , AWS Cloud Intelligence

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description. Key parts: - Description: "Join a team of cloud experts focused on uncovering and articulating advantages for AWS Customers! The AWS Cloud Intelligence team is a specialty services organization that provides cloud compete expertise globally. We are subject matter experts (SMEs) covering top and emerging competitors, key domains, and industry segments. Cloud Intelligence enables field teams to help their customers quickly by removing both business and technical blockers in the sales cycle. We advise account teams and their customers through at scale content, gather and analyze insights surrounding comparable cloud providers, and highlight product and position gaps that our customers are experiencing to continuously improve AWS’ overall value proposition. In addition to on-demand self-service resources, the CI team provides targeted support for specific competitive opportunities through one-to-one customer engagements. This team hires SAs and BDMs who are SMEs in one or more public clouds to advise AWS field teams on the best strategies to develop compelling business cases to support customers co-existing and partnering with competing public cloud services. As a Cloud Intelligence Field BDM, you will be a strategic partner to the AWS field sales team. You will help customers understand why AWS is the best cloud partner for their business. You will coach sales teams on how to amplify AWS strengths and create differentiation strategies. As a strategic partner to sales and external customers, you will identify emerging signals and best practices, to serve the broader organization. This position blends business and technology skillsets. Cloud Intelligence Field BDMs drive complex engagements and interact with executive audiences. They also have technical competence that enables them to analyze AWS and other cloud providers. Candidates must have the capability to craft and convey compelling value propositions, and to communicate concepts and stories effectively. We are looking for experience in one or more of the following: market or competitive intelligence, sales, business value engineering, sales enablement, sales coaching, and customer-facing technology sales experience. The ability to successfully differentiate cloud services in competitive market segments is key." - "Key job responsibilities" list bullet points: - Develop scalable competitive strategies to enable winning key strategic deals. - Support, coach, and develop large deal closing capability. - Be the go-to resource for an AWS field sales segment and sales leadership for AWS differentiation. - Leverage excellent communication skills to articulate the business value of AWS value propositions, working backwards from our customers strategic objectives. - Demonstrate the ability to earn trust with and influence C-level executives in customer organizations and within AWS. - Support strategic, in-person workshops (this position will require travel). - Develop and share cloud adoption trends and blockers across the cloud ecosystem. - Enable and upskill field teams through development of field-friendly content, and delivery of trainings. - Track signals and identify opportunities, in order to provide Cloud Intelligence with insight to improve offerings. - Influence internal stakeholders on market realities, with the objective to further differentiate AWS’s value. - "About The Team" paragraph: description of AWS, diverse experiences, work/life balance, inclusive team culture, mentorship & career growth, equal opportunity employer, etc. This is boilerplate? It's about team culture; but we need to decide if we include as "About the role" maybe. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing description). Responsibilities (list). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills (maybe list of capabilities). Benefits (benefits described). Pay (salary ranges). Schedule (maybe travel requirement? Not explicit schedule; but we have "Support strategic, in-person workshops (this position will require travel)." That's not schedule but travel. No explicit schedule like full-time, etc. So we may omit Schedule if no concrete schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated: comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. So Benefits section is valid. Pay: salary ranges listed for multiple locations. So Pay section is valid. Schedule: not given; we should not create Schedule section. Now we need to extract substantive info for each section. About the role: Should summarize the role description (first paragraphs). Must not repeat job title. Provide prose in

. Could be multiple paragraphs? Probably one

with the description. Responsibilities:

• each bullet. Requirements: Basic Qualifications list. They are many bullet-like statements each starting with "5+ years of ...". We need to preserve all substantive info; we can list each as
• . Should we combine? Probably each as separate list item. Qualifications: Preferred Qualifications list. Also list each as
• . Skills: Could be derived from capabilities: "capability to craft and convey compelling value propositions, and to communicate concepts and stories effectively." Also "experience in one or more of the following: market or competitive intelligence, sales, business value engineering, sales enablement, sales coaching, and customer-facing technology sales experience." Also "ability to successfully differentiate cloud services in competitive market segments". Also "technical competence that enables them to analyze AWS and other cloud providers". Also "experience explaining complex technical concepts to various business and technical audiences", "experience presenting to both technical and non-technical executive audiences". Also "experience leading complex, multi-year initiatives". Also "experience managing programs across cross functional teams". Also "experience selling enterprise software or cloud-based applications". Also "experience developing strategies that influence leadership decisions at the organizational level". Also "experience working with Core Cloud Technology Services..." etc. Actually many of those are in Basic Qualifications. But Skills section could capture the skill-based requirements not just years. However we already have Requirements (basic qualifications) and Qualifications (preferred). The instruction says we can have Skills section; we need to decide if we have specific skill content not covered elsewhere. The posting includes "Candidates must have the capability to craft and convey compelling value propositions, and to communicate concepts and stories effectively." That's a skill. Also "ability to successfully differentiate cloud services in competitive market segments". Also "technical competence that enables them to analyze AWS and other cloud providers". Also "experience explaining complex technical concepts to various business and technical audiences". Also "experience presenting to both technical and non-technical executive audiences". Also "experience leading complex, multi-year initiatives". Also "experience managing programs across cross functional teams". Also "experience selling enterprise software or cloud-based applications". Also "experience developing strategies that influence leadership decisions at the organizational level". Also "experience working with Core Cloud Technology Services..." etc. Many of those are in Basic Qualifications but they are phrased as experience. Could still be considered skills. However to avoid duplication, maybe we put Skills as a short list of those capability statements not captured by years. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one? But they ask for headings list; we can include both if they have content. We'll include Requirements (basic qualifications) and Qualifications (preferred). Skills maybe we can omit if thin. But we have some skill statements not captured by years: "capability to craft and convey compelling value propositions, and to communicate concepts and stories effectively." "ability to successfully differentiate cloud services in competitive market segments." "technical competence that enables them to analyze AWS and other cloud providers." Those are skills. Could be a Skills section. Benefits: list of benefits: 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 maybe "sign-on payments and restricted stock units (RSUs)" mentioned earlier under compensation. That's part of Pay? Actually they said "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation, could be in Pay section. We'll include in Pay. Pay: salary ranges per location. We need to preserve all substantive info; we can list each location with range. Could be a
  with each location. Schedule: none, so omit. Now we need to strip boilerplate: remove EEO, equal-opportunity, scam-warning, duplicated lines, application instructions, cookie/navigation/legal. Also remove "About The Team" section's generic AWS praise? It's about team culture but might be considered boilerplate? It's not exactly boilerplate; it's about AWS culture, diversity, etc. Might be considered generic but still substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About The Team" includes diversity, work/life balance, inclusive culture, mentorship, equal opportunity employer statement. Those are EEO/equal-opportunity boilerplate. So we should remove that entire "About The Team" block. Also remove the equal opportunity employer statements later. Also remove the Los Angeles County etc. Also remove the accommodation links. Also remove the "Company - Amazon Web Services, Inc. Job ID: A10539321". Also remove the "Basic Qualifications" heading? We'll keep the content but not the heading as we will use our own headings. Thus we keep: - Description (role overview) - Key job responsibilities - Basic Qualifications (as Requirements) - Preferred Qualifications (as Qualifications) - Skills (maybe from capability statements) - Benefits - Pay Now we need to format. Let's extract the description prose: The first paragraph(s) before "Key job responsibilities". Let's copy: "Join a team of cloud experts focused on uncovering and articulating advantages for AWS Customers! The AWS Cloud Intelligence team is a specialty services organization that provides cloud compete expertise globally. We are subject matter experts (SMEs) covering top and emerging competitors, key domains, and industry segments. Cloud Intelligence enables field teams to help their customers quickly by removing both business and technical blockers in the sales cycle. We advise account teams and their customers through at scale content, gather and analyze insights surrounding comparable cloud providers, and highlight product and position gaps that our customers are experiencing to continuously improve AWS’ overall value proposition. In addition to on-demand self-service resources, the CI team provides targeted support for specific competitive opportunities through one-to-one customer engagements. This team hires SAs and BDMs who are SMEs in one or more public clouds to advise AWS field teams on the best strategies to develop compelling business cases to support customers co-existing and partnering with competing public cloud services. As a Cloud Intelligence Field BDM, you will be a strategic partner to the AWS field sales team. You will help customers understand why AWS is the best cloud partner for their business. You will coach sales teams on how to amplify AWS strengths and create differentiation strategies. As a strategic partner to sales and external customers, you will identify emerging signals and best practices, to serve the broader organization. This position blends business and technology skillsets. Cloud Intelligence Field BDMs drive complex engagements and interact with executive audiences. They also have technical competence that enables them to analyze AWS and other cloud providers. Candidates must have the capability to craft and convey compelling value propositions, and to communicate concepts and stories effectively. We are looking for experience in one or more of the following: market or competitive intelligence, sales, business value engineering, sales enablement, sales coaching, and customer-facing technology sales experience. The ability to successfully differentiate cloud services in competitive market segments is key." We can keep that as About the role. Now Responsibilities: list the bullet points under "Key job responsibilities". We'll copy each. Now Requirements (Basic Qualifications): list each bullet: - 5+ years of developing, negotiating and executing business agreements experience - 5+ years of professional or military experience - 5+ years of working with Core