Sr Partner Solution Architect, US Consulting Partners
Amazon Web Services (AWS) · San Francisco, CA · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove application instructions. Keep substantive info.
We need to parse description.
Content:
- Description: This position is part of the AWS Specialist and Partner Organization (ASP). In this role, you will be responsible for the technical management and enablement of selected AWS Partner Network Consulting Partners located in the US. You will have the opportunity to own the technical strategy and execution plan for how your partners will develop their business practices and grow. As the right candidate, you are a leader who draws upon your experience with developing partners, joint technical business planning, opportunity identification, oversight and development of new lines of business, industry practices and APN Competencies, go-to-market solution development, relationship building, and working in both a direct and matrix operating structure.
- Key job responsibilities (list): You will need to collaborate effectively with internal stakeholders, partner development managers, partner core team leaders, be results driven, and have proven experience in developing a network of partners with deep capabilities and high-delivery quality. This role is partner facing, which includes interacting and building relationships with consulting partners' senior stakeholders, consultants and AWS customers. You will be responsible for earning the trust of the partner’s technical leaders, guiding the partner’s growth, transformation of their technology practices on the AWS Platform, and the creation of packaged offerings along with partner resources. You should be comfortable in managing a broad portfolio of partners from early stage cloud native, traditional large system integrators, value added resellers, and specialist providers. Some travel is required in order to interface and build relationships with your partners as required, this is less than 20% in most cases.
- Diverse Experiences (maybe not needed as a section; it's more encouragement to apply; could be omitted or maybe part of About the role? It's not a formal section; we can ignore as it's not a heading.)
- About The Team: description.
- Basic Qualifications: list.
- Preferred Qualifications: list.
- Benefits: mention comprehensive benefits including health insurance etc. Also mention sign-on payments and RSUs, base salary range for location (multiple locations). Also mention 401(k) matching, paid time off, parental leave.
- Pay: base salary ranges listed for various locations. Also mention sign-on payments and RSUs.
- Schedule: travel less than 20% maybe considered schedule? Not exactly schedule but could be considered schedule (travel requirement). The instruction: include Schedule section only if posting actually states them. It mentions "Some travel is required ... less than 20%". That's schedule/travel info. So we can include Schedule section with that.
- Skills: maybe we can extract from responsibilities/qualifications: experience communicating across technical and non-technical audiences, etc. But we have Qualifications sections; we could put Skills as separate if there is explicit skill list. The posting includes "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients" etc. That's more qualification. We could put under Qualifications or Skills. Since we have both Qualifications and Skills headings allowed, we need to decide. The posting includes Basic Qualifications and Preferred Qualifications; we could map those to Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- About the role: could be the initial description paragraph (the first paragraph). Could also include About The Team? Actually About The Team is separate but could be part of About the role? Might be better to have About the role (role description) and About The Team maybe as part of About the role or separate? Since we have only those headings, we could put About the role covering both the role description and team description. Or we could have About the role and maybe not include About The Team separately. The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide if we have content for About the role. Yes we have description of role. So we will output
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove application instructions. Keep substantive info.
We need to parse description.
Content:
- Description: This position is part of the AWS Specialist and Partner Organization (ASP). In this role, you will be responsible for the technical management and enablement of selected AWS Partner Network Consulting Partners located in the US. You will have the opportunity to own the technical strategy and execution plan for how your partners will develop their business practices and grow. As the right candidate, you are a leader who draws upon your experience with developing partners, joint technical business planning, opportunity identification, oversight and development of new lines of business, industry practices and APN Competencies, go-to-market solution development, relationship building, and working in both a direct and matrix operating structure.
- Key job responsibilities (list): You will need to collaborate effectively with internal stakeholders, partner development managers, partner core team leaders, be results driven, and have proven experience in developing a network of partners with deep capabilities and high-delivery quality. This role is partner facing, which includes interacting and building relationships with consulting partners' senior stakeholders, consultants and AWS customers. You will be responsible for earning the trust of the partner’s technical leaders, guiding the partner’s growth, transformation of their technology practices on the AWS Platform, and the creation of packaged offerings along with partner resources. You should be comfortable in managing a broad portfolio of partners from early stage cloud native, traditional large system integrators, value added resellers, and specialist providers. Some travel is required in order to interface and build relationships with your partners as required, this is less than 20% in most cases.
- Diverse Experiences (maybe not needed as a section; it's more encouragement to apply; could be omitted or maybe part of About the role? It's not a formal section; we can ignore as it's not a heading.)
- About The Team: description.
- Basic Qualifications: list.
- Preferred Qualifications: list.
- Benefits: mention comprehensive benefits including health insurance etc. Also mention sign-on payments and RSUs, base salary range for location (multiple locations). Also mention 401(k) matching, paid time off, parental leave.
- Pay: base salary ranges listed for various locations. Also mention sign-on payments and RSUs.
- Schedule: travel less than 20% maybe considered schedule? Not exactly schedule but could be considered schedule (travel requirement). The instruction: include Schedule section only if posting actually states them. It mentions "Some travel is required ... less than 20%". That's schedule/travel info. So we can include Schedule section with that.
- Skills: maybe we can extract from responsibilities/qualifications: experience communicating across technical and non-technical audiences, etc. But we have Qualifications sections; we could put Skills as separate if there is explicit skill list. The posting includes "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients" etc. That's more qualification. We could put under Qualifications or Skills. Since we have both Qualifications and Skills headings allowed, we need to decide. The posting includes Basic Qualifications and Preferred Qualifications; we could map those to Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- About the role: could be the initial description paragraph (the first paragraph). Could also include About The Team? Actually About The Team is separate but could be part of About the role? Might be better to have About the role (role description) and About The Team maybe as part of About the role or separate? Since we have only those headings, we could put About the role covering both the role description and team description. Or we could have About the role and maybe not include About The Team separately. The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide if we have content for About the role. Yes we have description of role. So we will output About the role
with paragraphs.
- Responsibilities: we have Key job responsibilities paragraph(s). We'll output Responsibilities
with - items.
- Requirements: could be Basic Qualifications? Or maybe Requirements is for mandatory qualifications. We'll put Basic Qualifications under Requirements.
- Qualifications: could be Preferred Qualifications.
- Skills: maybe we can extract skill-specific items like "Experience communicating across technical and non-technical audiences", "Experience building complex software systems", etc. But those are already in qualifications. Might be redundant. However we could still create Skills section if there is explicit skill list. The posting includes "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients" (under Basic Qualifications). Also "Experience building complex software systems that have been successfully delivered to customers, or experience in computer architecture" (under Preferred). Also "Experience architecting/operating solutions built on AWS", "Experience with cloud, server or infrastructure technologies and business models", "Experience presenting to executives, IT Management, and developers.", "Experience with technical consulting and/or architecture engagements with large-scale customers or enterprises." Those are skills/experience. So we could put them under Skills. But we already have Qualifications sections. To avoid duplication, we could treat Basic and Preferred as Qualifications (maybe split into Requirements and Qualifications). Then Skills could be omitted if no distinct skill list beyond qualifications. However the instruction says prefer a few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one? But we have headings for both; we can use them if we have content. Let's assign:
- Requirements: Basic Qualifications (mandatory).
- Qualifications: Preferred Qualifications (preferred).
- Skills: maybe we can extract a list of skills like "Technical consulting", "Architecture", "Partner development", "Go-to-market solution development", "Relationship building", "Executive communication". But those are already covered. To avoid thin sections, maybe we omit Skills if not distinct. However the instruction says include a section ONLY when posting has real, specific content for it. If we don't have a distinct skill list beyond qualifications, we could omit Skills. But we need to decide.
We also have Benefits, Pay, Schedule.
Benefits: mention comprehensive benefits including health insurance etc., sign-on payments and RSUs, 401(k) matching, paid time off, parental leave. Also link to benefits page.
Pay: base salary ranges for locations, plus sign-on payments and RSUs.
Schedule: travel less than 20%.
Now we need to strip boilerplate: remove EEO, legal, diversity encouragement, Los Angeles County stuff, San Francisco Fair Chance, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10500319". Also remove "Diverse Experiences" paragraph (encouragement). Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe we can keep mention of benefits but not the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits info; it's a URL. Should we keep it? It's not boilerplate; it's a reference. Might be considered part of benefits. However it's a link to external page; it's still substantive. We could keep it as part of benefits paragraph. But the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not those. So we can keep.
But we need to be careful not to include navigation etc.
Now produce HTML.
Structure:
About the role
... (combined role description and team description maybe)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
...
Pay
...
Schedule
...
We need to ensure we don't repeat content.
Let's extract each.
About the role: combine first paragraph and About The Team paragraph.
First paragraph: "This position is part of the AWS Specialist and Partner Organization (ASP). In this role, you will be responsible for the technical management and enablement of selected AWS Partner Network Consulting Partners located in the US. You will have the opportunity to own the technical strategy and execution plan for how your partners will develop their business practices and grow. As the right candidate, you are a leader who draws upon your experience with developing partners, joint technical business planning, opportunity identification, oversight and development of new lines of business, industry practices and APN Competencies, go-to-market solution development, relationship building, and working in both a direct and matrix operating structure."
About The Team paragraph: "The US Consulting Partner (USCP) team drives the technical strategy and execution for our largest and most strategic partners to scale their growth. As a strategic contributor, you'll work at the intersection of partner and customer needs, ensuring the technical perspective of partners and customers shapes how we engage. The team leads technical enablement initiatives, owns technical relationships with the partner, and provides operational support across the partner ecosystem. Your role will be instrumental in advancing USCP’s mission to make AWS partners more successful through technical innovation and excellence."
We can combine into one or two paragraphs. Probably two paragraphs.
Responsibilities: from "Key job responsibilities" paragraph(s). Let's break into bullet points.
Original: "You will need to collaborate effectively with internal stakeholders, partner development managers, partner core team leaders, be results driven, and have proven experience in developing a network of partners with deep capabilities and high-delivery quality. This role is partner facing, which includes interacting and building relationships with consulting partners' senior stakeholders, consultants and AWS customers. You will be responsible for earning the trust of the partner’s technical leaders, guiding the partner’s growth, transformation of their technology practices on the AWS Platform, and the creation of packaged offerings along with partner resources. You should be comfortable in managing a broad portfolio of partners from early stage cloud native, traditional large system integrators, value added resellers, and specialist providers. Some travel is required in order to interface and build relationships with your partners as required, this is less than 20% in most cases."
We can split into bullets:
- Collaborate effectively with internal stakeholders, partner development managers, partner core team leaders; be results driven; have proven experience developing a network of partners with deep capabilities and high-delivery quality.
- Interact and build relationships with consulting partners' senior stakeholders, consultants, and AWS customers (partner-facing role).
- Earn the trust of partners' technical leaders; guide partner growth; transform technology practices on AWS Platform; create packaged offerings and partner resources.
- Manage a broad portfolio of partners ranging from early-stage cloud native, traditional large system integrators, value-added resellers, to specialist providers.
- Travel required to interface and build relationships with partners (<20% of time).
We should keep the travel note maybe in Schedule section instead. But it's also a responsibility. However we have Schedule section for travel; we could move travel note there. But responsibilities bullet could omit travel and mention schedule separately. However the responsibility includes travel; we could keep it in responsibilities and also schedule? Might duplicate. Better to put travel in Schedule section only. So responsibilities bullets exclude travel line.
Thus responsibilities bullets:
- Collaborate effectively with internal stakeholders, partner development managers, partner core team
About the role
... (combined role description and team description maybe)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
...
Pay
...
Schedule
...
We need to ensure we don't repeat content. Let's extract each. About the role: combine first paragraph and About The Team paragraph. First paragraph: "This position is part of the AWS Specialist and Partner Organization (ASP). In this role, you will be responsible for the technical management and enablement of selected AWS Partner Network Consulting Partners located in the US. You will have the opportunity to own the technical strategy and execution plan for how your partners will develop their business practices and grow. As the right candidate, you are a leader who draws upon your experience with developing partners, joint technical business planning, opportunity identification, oversight and development of new lines of business, industry practices and APN Competencies, go-to-market solution development, relationship building, and working in both a direct and matrix operating structure." About The Team paragraph: "The US Consulting Partner (USCP) team drives the technical strategy and execution for our largest and most strategic partners to scale their growth. As a strategic contributor, you'll work at the intersection of partner and customer needs, ensuring the technical perspective of partners and customers shapes how we engage. The team leads technical enablement initiatives, owns technical relationships with the partner, and provides operational support across the partner ecosystem. Your role will be instrumental in advancing USCP’s mission to make AWS partners more successful through technical innovation and excellence." We can combine into one or two paragraphs. Probably two paragraphs. Responsibilities: from "Key job responsibilities" paragraph(s). Let's break into bullet points. Original: "You will need to collaborate effectively with internal stakeholders, partner development managers, partner core team leaders, be results driven, and have proven experience in developing a network of partners with deep capabilities and high-delivery quality. This role is partner facing, which includes interacting and building relationships with consulting partners' senior stakeholders, consultants and AWS customers. You will be responsible for earning the trust of the partner’s technical leaders, guiding the partner’s growth, transformation of their technology practices on the AWS Platform, and the creation of packaged offerings along with partner resources. You should be comfortable in managing a broad portfolio of partners from early stage cloud native, traditional large system integrators, value added resellers, and specialist providers. Some travel is required in order to interface and build relationships with your partners as required, this is less than 20% in most cases." We can split into bullets: - Collaborate effectively with internal stakeholders, partner development managers, partner core team leaders; be results driven; have proven experience developing a network of partners with deep capabilities and high-delivery quality. - Interact and build relationships with consulting partners' senior stakeholders, consultants, and AWS customers (partner-facing role). - Earn the trust of partners' technical leaders; guide partner growth; transform technology practices on AWS Platform; create packaged offerings and partner resources. - Manage a broad portfolio of partners ranging from early-stage cloud native, traditional large system integrators, value-added resellers, to specialist providers. - Travel required to interface and build relationships with partners (<20% of time). We should keep the travel note maybe in Schedule section instead. But it's also a responsibility. However we have Schedule section for travel; we could move travel note there. But responsibilities bullet could omit travel and mention schedule separately. However the responsibility includes travel; we could keep it in responsibilities and also schedule? Might duplicate. Better to put travel in Schedule section only. So responsibilities bullets exclude travel line. Thus responsibilities bullets: - Collaborate effectively with internal stakeholders, partner development managers, partner core team