Sr Partner Solution Architect, US Consulting Partners

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 content. We need to parse the job description. Key parts: - 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." That's prose for About the role. - "Key job responsibilities" then bullet list? Actually after that: "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." That's responsibilities. - "Diverse Experiences" paragraph about encouraging candidates. - "About The Team" paragraph. - Basic Qualifications list: bullet points? Actually they are sentences: "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients 7+ years of design/ implementation/ consulting experience of large-scale, enterprise applications 3+ years of experience working with multi-national partners/customers in support of technology sales 5+ years building out proven relationships with partners/suppliers leading to increased sales opportunities". That's a run-on list; we can split into

items. - Preferred Qualifications list: multiple sentences. - Then EEO boilerplate etc to remove. - Los Angeles County applicants paragraph (legal) - remove. - San Francisco Fair Chance etc - remove. - Inclusive culture paragraph - remove? It's boilerplate EEO; remove. - Accommodation link - remove. - If country/region not listed - remove. - 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 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. Then location salary ranges: USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually etc. So we have Pay info: salary ranges per location. Also Benefits info: health insurance etc. Schedule: not mentioned (some travel less than 20% but not schedule). So we should not create Schedule section. We need sections: About the role (maybe "About the role" heading), Responsibilities, About the Team could be separate? Could be "About the Team" as a section heading. Basic Qualifications, Preferred Qualifications (maybe combine as Requirements/Qualifications). Benefits, Pay. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include. Potential sections: - About the role (prose from first paragraph) - Responsibilities (prose from "Key job responsibilities" paragraph) - About the Team (prose from "About The Team") - Basic Qualifications (list) - Preferred Qualifications (list) - Benefits (list of benefits) - Pay (list of salary ranges per location) We should not include "Diverse Experiences" as separate section? It's a paragraph encouraging candidates; could be part of About the role or maybe a separate section "Diverse Experiences". But the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "Diverse Experiences" paragraph is substantive (encouraging candidates). Could be its own section. However typical headings list does not include "Diverse Experiences". The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "Diverse Experiences" or "About The Team". But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. But they say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. However we can also use other headings if needed? The instruction: "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; but we could also use other headings if they fit? Safer to stick to those headings. So we need to map content to those headings. We have: - About the role: fits first paragraph. - Responsibilities: fits "Key job responsibilities" paragraph. - Requirements: could combine Basic Qualifications? Or Requirements could be basic qualifications. - Qualifications: could be Preferred Qualifications. - Skills: maybe not present; we could omit. - Benefits: benefits paragraph. - Pay: salary ranges. - Schedule: not present; omit. We should not create empty sections. Thus we will output:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  • ...
  ...
  We need to preserve all substantive information; do not invent or summarize away detail. We need to split the Basic Qualifications sentences into separate list items. Basic Qualifications text: "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients 7+ years of design/ implementation/ consulting experience of large-scale, enterprise applications 3+ years of experience working with multi-national partners/customers in support of technology sales 5+ years building out proven relationships with partners/suppliers leading to increased sales opportunities" We need to parse into items: - Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients - 7+ years of design/implementation/consulting experience of large-scale, enterprise applications - 3+ years of experience working with multi-national partners/customers in support of technology sales - 5+ years building out proven relationships with partners/suppliers leading to increased sales opportunities We'll keep as is. Preferred Qualifications text: "Experience building complex software systems that have been successfully delivered to customers, or experience in computer architecture 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." We need to split into items: - Experience building complex software systems that have been successfully delivered to customers, or experience in computer architecture - 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 Note there is a period after developers; we keep. Benefits text: "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." We can make list items: - 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 earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation; could be included in Pay section? It mentions sign-on payments and RSUs. We'll include in Pay. Pay section: includes base salary ranges per location and sign-on payments and RSUs. We need to list: - Sign-on payments and restricted stock units (RSUs) as part of Amazon package. - Base salary range for this position varies by location: - USA, CA, San Francisco - $176,600.00 - $239,000.00 USD annually - USA, NY, New York - $169,000.00 - $228,600.00 USD annually - USA, TX, Dallas - $153,600.00 - $207,800.00 USD annually - USA, TX, Houston - $153,600.00 - $207,800.00 USD annually We should preserve the exact numbers and formatting. We also have sentence: "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 factors including experience, qualifications, and location." We'll incorporate. Now we need to ensure we don't include boilerplate like EEO, legal, etc. We also need to include "About The Team" paragraph. Where does it fit? Could be part of About the role? But we have About the role already. Could we add another section "About the Team"? Not in the example headings but we could treat as "About the role" includes team description? However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could incorporate the About The Team paragraph into About the role section (maybe as additional prose). That would preserve all info. Thus About the role section will contain two paragraphs: first paragraph about role, second about team. We need to keep them as separate

  tags or combine? Could be two

  inside the section. Now we need to ensure we don't repeat job title. Now