Principal, Strategy & BD, AWS Corporate Strategy & Business Development
for headings. Use - for lists. Use
for prose.
We need to parse the description and extract relevant content.
Sections:
- About the role: likely the introductory paragraph(s) describing role. Should be prose.
- Responsibilities: list of duties.
- Requirements: maybe basic qualifications? Or "Key job responsibilities" is responsibilities. "Basic Qualifications" and "Preferred Qualifications" could be Requirements and Qualifications? The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills? Actually they list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role: description of role, mission, etc.
- Responsibilities: bullet list under "Key job responsibilities" and also some responsibilities in prose earlier.
- Requirements: maybe "Basic Qualifications" (7+ years etc.) and maybe also "Preferred Qualifications"? But they separate Requirements and Qualifications. Could treat Requirements as basic qualifications (must-have) and Qualifications as preferred qualifications (nice-to-have). Or vice versa. We'll decide: Requirements = Basic Qualifications. Qualifications = Preferred Qualifications.
- Skills: maybe list of skills like communication, analytical, technical, strategic thinker, etc. Could extract from "The Ideal Candidate" and "Communication & Writing". Could be a list.
- Benefits: description of benefits (health insurance, 401k matching, paid time off, parental leave, etc.) plus mention of sign-on payments and RSUs.
- Pay: salary ranges per location.
- Schedule: travel expectations (25% typical, up to 75% during peak), willingness to travel, work outside normal hours, weekends.
We must not include sections with placeholder or vague like "commensurate with experience". We have actual numbers for pay, travel percentages.
We must not include boilerplate like EEO, accommodation link, etc. Remove those.
We must preserve all substantive info; do not invent or summarize away detail. So we need to keep specifics: e.g., "7+ years of developing, negotiating and executing business agreements experience", etc. Also "Bachelor's degree". Also "MBA". Also "Experience as a founder or executive focused on related segments, or as a practice leader or business unit owner". Also "Experience selling to Fortune 1000 or Global 2000 organizations". Also "7+ years of working with Data & AI related technologies...". Also "7+ years of working with Business Application Technologies...".
We need to list these as items under Requirements and Qualifications.
We need to ensure we don't repeat content unnecessarily.
Let's extract sections.
First, introductory paragraphs:
"AWS Corporate Strategy & Business Development – North America Emerging Companies, Supplier & Vendor Portfolio AWS is seeking a Corporate Strategy and Business Development leader to join our team with a focus on AWSI Deep Engagements across our North America emerging company customers within Amazon's Supplier & Vendor portfolio. This role will drive holistic strategies across Amazon's business with high-potential emerging partners and suppliers, working at the intersection of AWS and broader Amazon. This is a unique opportunity to join a centralized corporate team that manages strategic partnerships across all of Amazon with an AWS lens. The companies we work with are among Amazon's most promising emerging suppliers and vendors, and this role will help them drive technology transformation via AWS tools, technology, and partners. AWS and Amazon are on the forefront of the AI revolution with partners and the companies building the future of supply chain, commerce, and vendor innovation. We are seeking a person who can continuously (and effectively) walk the line between thought leader and executor, every day. The person will be responsible for assessing inbound requests, independently managing opportunities end-to-end (commonly the most complex challenges in never-been-done-before deals), and seeing complex and high-impact partnerships through to completion. An in-depth knowledge of how emerging companies operate within Amazon's Supplier & Vendor ecosystem, how they engage across Amazon, and what Amazon's strategy is (or could be) with these types of companies is important. The person will need a strong commercial aptitude and be able to quickly identify best-in-class partnerships that are valuable and high-impact for Amazon, Amazon Web Services (AWS), and our customers. You'll also manage executive relationships and negotiate partnership deals that are unconventional, need a centralized advocate, and/or have broader implications to AWS and other Amazon business units that are not immediately obvious. This includes non-standard deal construction, complex accounting procedures, and deal negotiations that require creative problem-solving and deep commercial expertise. This role will interact closely with internal AWS and Amazon leaders from various disciplines, requiring confidence and credibility when engaging with the most senior leadership at both AWS and Amazon. This key role will be highly visible at senior levels of the organization and work on some of our most vexing challenges. You will need to work collaboratively with internal management teams to understand relative advantages and risks, if/when major features should be included to existing roadmaps, consolidation, and adoption. You'll at times need to be comfortable moving forward without a clear path, almost always with high degrees of ambiguity."
Then "Communication & Writing" paragraph: "This role demands exceptional written and oral communication skills. You will regularly author strategy documents, build executive-level presentations, and communicate complex partnership narratives to senior leaders. Effective communication (written and verbal) at the executive level is not a nice-to-have; it is core to the role."
Then "Travel & Availability": "This role requires willingness to travel within North America, sometimes with little notice. While travel may reach 75% during peak deal cycles, the typical expectation is approximately 25%, depending on engagement cadence. While we strive for a healthy work-life balance, the highly visible nature of this role and the types of deals we work on mean it is not unusual to work well outside of normal hours, including weekends."
Then "The Ideal Candidate": paragraph about analytical, technical, strategic thinker, etc.
Then "Key job responsibilities": bullet list (we need to capture each bullet). Let's extract:
- Identify, evaluate, and manage strategic partnership opportunities with North America emerging companies across Amazon's Supplier & Vendor portfolio, driving technology transformation through AWS tools, technology, and partners.
- Independently manage complex, end-to-end deal cycles including non-standard deal construction, creative accounting procedures, and unconventional partnership structures with no established playbook.
- Engage with senior leadership at AWS and Amazon, presenting partnership strategies spanning multiple business units including ASCS, Amazon Ads, and Amazon Stores.
- Negotiate high-impact partnership agreements requiring a centralized advocate, including co-selling and co-innovation opportunities with suppliers and vendors to Amazon.
- Author strategy documents, executive-level presentations, and written narratives articulating complex partnership opportunities, risks, and recommendations.
- Assess inbound requests from emerging suppliers and vendors, prioritize by strategic value and multi-BU potential, and determine engagement models across lead sharing, co-selling, and co-innovation.
- Collaborate cross-functionally across AWS and Amazon to evaluate advantages, risks, roadmap implications, and adoption strategies.
- Travel within North America (typically 25%, up to 75% during peak periods), sometimes with limited notice.
- Navigate ambiguity with evolving priorities and first-of-their-kind deal structures involving high-growth emerging companies.
Then "A day in the life": prose but maybe not needed as separate section; could be part of About the role or Responsibilities. But we can incorporate into About the role? The instruction: include a section only when posting has real specific content. The "A day in the life" is prose describing typical activities. Could be part of About the role or Responsibilities. Since we already have About the role covering role description, we could add that prose there. But we must not duplicate. We'll keep About the role as the initial description plus maybe the "A day in the life" paragraph.
Then "About The Team": includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These are more about company culture; could be considered Benefits? But we already have Benefits section for compensation/benefits. The "About The Team" is more about culture; maybe we could treat as part of About the role? But the instruction says we should not create sections unless there is real specific content. The "About The Team" has content but not exactly matching our predefined headings. We could incorporate relevant parts into Benefits (like work-life balance) or maybe into a separate section like "About the team" but not allowed headings. Since only allowed headings are those listed, we should not add extra headings. So we need to fold that content into existing sections where appropriate: e.g., work-life balance into Benefits or Schedule? Actually work-life balance is a benefit/culture; we could put under Benefits. The "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth" could be considered part of Benefits or maybe Qualifications? But they are not qualifications. Probably best to incorporate them into Benefits section as part of overall benefits/culture. However we must not invent headings; we can just add paragraphs under Benefits.
But we must preserve all substantive info; we can include them as
under Benefits.
Now Basic Qualifications list:
- 7+ years of developing, negotiating and executing business agreements experience
- 7+ years of professional or military experience
- 7+ years of working with Core Cloud Technology Services, including, but not limited to Compute, Edge, Hybrid, Security, and/or Networking experience
- 7+ years of Go-To-Market, Business Development, Sales, or Consulting experience
- Bachelor's degree
Preferred Qualifications:
- MBA
- Experience as a founder or executive focused on related segments, or as a practice leader or business unit owner
- Experience selling to Fortune 1000 or Global 2000 organizations
- 7+ years of working with Data & AI related technologies, including, but not limited to, AI/ML, GenAI, Analytics, Database, and/or Storage experience
- 7+ 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
Now Skills: we can extract from "The Ideal Candidate" and "Communication & Writing". The Ideal Candidate paragraph: "We are seeking an analytical, technical, and strategic thinker who is passionate and relentless. The ideal candidate enjoys solving complex problems where there is no clearly defined path to success, and isn't frustrated by a lack of clarity when defining how to execute. This individual must be able to work effectively with cross-functional teams and thrives in a fast-paced setting that is constantly evolving and isn't dissuaded when they hear "no" or frustrated by shifting priorities. Experience working with emerging and high-growth companies, particularly within supplier, vendor, or marketplace ecosystems, is highly valued. Finally, as our deals are atypical, we require a leader who is comfortable defining goals that align to the right business outcomes, and is exceptionally comfortable driving the right outcomes with little guidance."
Communication & Writing: exceptional written and oral communication skills, authoring strategy documents, building executive-level presentations, communicating complex partnership narratives to senior leaders.
Thus skills list: analytical thinking, technical aptitude, strategic thinking, passion, relentless, problem-solving, comfort with ambiguity, cross-functional collaboration, fast-paced adaptability, resilience to "no", handling shifting priorities, experience with emerging/high-growth companies in supplier/vendor/marketplace, goal definition, driving outcomes with little guidance, exceptional written and oral communication, authoring strategy documents, building executive-level presentations, communicating complex partnership narratives.
We can make a bullet list.
Now Benefits: we have paragraph: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on
for prose. We need to parse the description and extract relevant content. Sections: - About the role: likely the introductory paragraph(s) describing role. Should be prose. - Responsibilities: list of duties. - Requirements: maybe basic qualifications? Or "Key job responsibilities" is responsibilities. "Basic Qualifications" and "Preferred Qualifications" could be Requirements and Qualifications? The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills? Actually they list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: description of role, mission, etc. - Responsibilities: bullet list under "Key job responsibilities" and also some responsibilities in prose earlier. - Requirements: maybe "Basic Qualifications" (7+ years etc.) and maybe also "Preferred Qualifications"? But they separate Requirements and Qualifications. Could treat Requirements as basic qualifications (must-have) and Qualifications as preferred qualifications (nice-to-have). Or vice versa. We'll decide: Requirements = Basic Qualifications. Qualifications = Preferred Qualifications. - Skills: maybe list of skills like communication, analytical, technical, strategic thinker, etc. Could extract from "The Ideal Candidate" and "Communication & Writing". Could be a list. - Benefits: description of benefits (health insurance, 401k matching, paid time off, parental leave, etc.) plus mention of sign-on payments and RSUs. - Pay: salary ranges per location. - Schedule: travel expectations (25% typical, up to 75% during peak), willingness to travel, work outside normal hours, weekends. We must not include sections with placeholder or vague like "commensurate with experience". We have actual numbers for pay, travel percentages. We must not include boilerplate like EEO, accommodation link, etc. Remove those. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep specifics: e.g., "7+ years of developing, negotiating and executing business agreements experience", etc. Also "Bachelor's degree". Also "MBA". Also "Experience as a founder or executive focused on related segments, or as a practice leader or business unit owner". Also "Experience selling to Fortune 1000 or Global 2000 organizations". Also "7+ years of working with Data & AI related technologies...". Also "7+ years of working with Business Application Technologies...". We need to list these as items under Requirements and Qualifications. We need to ensure we don't repeat content unnecessarily. Let's extract sections. First, introductory paragraphs: "AWS Corporate Strategy & Business Development – North America Emerging Companies, Supplier & Vendor Portfolio AWS is seeking a Corporate Strategy and Business Development leader to join our team with a focus on AWSI Deep Engagements across our North America emerging company customers within Amazon's Supplier & Vendor portfolio. This role will drive holistic strategies across Amazon's business with high-potential emerging partners and suppliers, working at the intersection of AWS and broader Amazon. This is a unique opportunity to join a centralized corporate team that manages strategic partnerships across all of Amazon with an AWS lens. The companies we work with are among Amazon's most promising emerging suppliers and vendors, and this role will help them drive technology transformation via AWS tools, technology, and partners. AWS and Amazon are on the forefront of the AI revolution with partners and the companies building the future of supply chain, commerce, and vendor innovation. We are seeking a person who can continuously (and effectively) walk the line between thought leader and executor, every day. The person will be responsible for assessing inbound requests, independently managing opportunities end-to-end (commonly the most complex challenges in never-been-done-before deals), and seeing complex and high-impact partnerships through to completion. An in-depth knowledge of how emerging companies operate within Amazon's Supplier & Vendor ecosystem, how they engage across Amazon, and what Amazon's strategy is (or could be) with these types of companies is important. The person will need a strong commercial aptitude and be able to quickly identify best-in-class partnerships that are valuable and high-impact for Amazon, Amazon Web Services (AWS), and our customers. You'll also manage executive relationships and negotiate partnership deals that are unconventional, need a centralized advocate, and/or have broader implications to AWS and other Amazon business units that are not immediately obvious. This includes non-standard deal construction, complex accounting procedures, and deal negotiations that require creative problem-solving and deep commercial expertise. This role will interact closely with internal AWS and Amazon leaders from various disciplines, requiring confidence and credibility when engaging with the most senior leadership at both AWS and Amazon. This key role will be highly visible at senior levels of the organization and work on some of our most vexing challenges. You will need to work collaboratively with internal management teams to understand relative advantages and risks, if/when major features should be included to existing roadmaps, consolidation, and adoption. You'll at times need to be comfortable moving forward without a clear path, almost always with high degrees of ambiguity." Then "Communication & Writing" paragraph: "This role demands exceptional written and oral communication skills. You will regularly author strategy documents, build executive-level presentations, and communicate complex partnership narratives to senior leaders. Effective communication (written and verbal) at the executive level is not a nice-to-have; it is core to the role." Then "Travel & Availability": "This role requires willingness to travel within North America, sometimes with little notice. While travel may reach 75% during peak deal cycles, the typical expectation is approximately 25%, depending on engagement cadence. While we strive for a healthy work-life balance, the highly visible nature of this role and the types of deals we work on mean it is not unusual to work well outside of normal hours, including weekends." Then "The Ideal Candidate": paragraph about analytical, technical, strategic thinker, etc. Then "Key job responsibilities": bullet list (we need to capture each bullet). Let's extract: - Identify, evaluate, and manage strategic partnership opportunities with North America emerging companies across Amazon's Supplier & Vendor portfolio, driving technology transformation through AWS tools, technology, and partners. - Independently manage complex, end-to-end deal cycles including non-standard deal construction, creative accounting procedures, and unconventional partnership structures with no established playbook. - Engage with senior leadership at AWS and Amazon, presenting partnership strategies spanning multiple business units including ASCS, Amazon Ads, and Amazon Stores. - Negotiate high-impact partnership agreements requiring a centralized advocate, including co-selling and co-innovation opportunities with suppliers and vendors to Amazon. - Author strategy documents, executive-level presentations, and written narratives articulating complex partnership opportunities, risks, and recommendations. - Assess inbound requests from emerging suppliers and vendors, prioritize by strategic value and multi-BU potential, and determine engagement models across lead sharing, co-selling, and co-innovation. - Collaborate cross-functionally across AWS and Amazon to evaluate advantages, risks, roadmap implications, and adoption strategies. - Travel within North America (typically 25%, up to 75% during peak periods), sometimes with limited notice. - Navigate ambiguity with evolving priorities and first-of-their-kind deal structures involving high-growth emerging companies. Then "A day in the life": prose but maybe not needed as separate section; could be part of About the role or Responsibilities. But we can incorporate into About the role? The instruction: include a section only when posting has real specific content. The "A day in the life" is prose describing typical activities. Could be part of About the role or Responsibilities. Since we already have About the role covering role description, we could add that prose there. But we must not duplicate. We'll keep About the role as the initial description plus maybe the "A day in the life" paragraph. Then "About The Team": includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These are more about company culture; could be considered Benefits? But we already have Benefits section for compensation/benefits. The "About The Team" is more about culture; maybe we could treat as part of About the role? But the instruction says we should not create sections unless there is real specific content. The "About The Team" has content but not exactly matching our predefined headings. We could incorporate relevant parts into Benefits (like work-life balance) or maybe into a separate section like "About the team" but not allowed headings. Since only allowed headings are those listed, we should not add extra headings. So we need to fold that content into existing sections where appropriate: e.g., work-life balance into Benefits or Schedule? Actually work-life balance is a benefit/culture; we could put under Benefits. The "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth" could be considered part of Benefits or maybe Qualifications? But they are not qualifications. Probably best to incorporate them into Benefits section as part of overall benefits/culture. However we must not invent headings; we can just add paragraphs under Benefits. But we must preserve all substantive info; we can include them as
under Benefits. Now Basic Qualifications list: - 7+ years of developing, negotiating and executing business agreements experience - 7+ years of professional or military experience - 7+ years of working with Core Cloud Technology Services, including, but not limited to Compute, Edge, Hybrid, Security, and/or Networking experience - 7+ years of Go-To-Market, Business Development, Sales, or Consulting experience - Bachelor's degree Preferred Qualifications: - MBA - Experience as a founder or executive focused on related segments, or as a practice leader or business unit owner - Experience selling to Fortune 1000 or Global 2000 organizations - 7+ years of working with Data & AI related technologies, including, but not limited to, AI/ML, GenAI, Analytics, Database, and/or Storage experience - 7+ 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 Now Skills: we can extract from "The Ideal Candidate" and "Communication & Writing". The Ideal Candidate paragraph: "We are seeking an analytical, technical, and strategic thinker who is passionate and relentless. The ideal candidate enjoys solving complex problems where there is no clearly defined path to success, and isn't frustrated by a lack of clarity when defining how to execute. This individual must be able to work effectively with cross-functional teams and thrives in a fast-paced setting that is constantly evolving and isn't dissuaded when they hear "no" or frustrated by shifting priorities. Experience working with emerging and high-growth companies, particularly within supplier, vendor, or marketplace ecosystems, is highly valued. Finally, as our deals are atypical, we require a leader who is comfortable defining goals that align to the right business outcomes, and is exceptionally comfortable driving the right outcomes with little guidance." Communication & Writing: exceptional written and oral communication skills, authoring strategy documents, building executive-level presentations, communicating complex partnership narratives to senior leaders. Thus skills list: analytical thinking, technical aptitude, strategic thinking, passion, relentless, problem-solving, comfort with ambiguity, cross-functional collaboration, fast-paced adaptability, resilience to "no", handling shifting priorities, experience with emerging/high-growth companies in supplier/vendor/marketplace, goal definition, driving outcomes with little guidance, exceptional written and oral communication, authoring strategy documents, building executive-level presentations, communicating complex partnership narratives. We can make a bullet list. Now Benefits: we have paragraph: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on