Principal Healthcare Solutions Architect, AI Solutions
About the role
withcontaining the description. Then "Key job responsibilities" list: bullet points. We'll put
Responsibilities
with- each bullet.
Then "About The Team" includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more about company culture; could be considered part of "About the role" or maybe separate sections like "About the team". The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About The Team" could be part of "About the role" or maybe "Qualifications"? Probably better to include under "About the role" as additional description. But we must not create sections with filler. We can include "About the role" covering initial description and maybe team info.
Then "Basic Qualifications" and "Preferred Qualifications". Those map to Requirements and Qualifications? Usually Basic Qualifications = Requirements, Preferred Qualifications = Qualifications or Skills. We'll treat Basic Qualifications as Requirements (
Requirements
) and Preferred Qualifications as Qualifications (Qualifications
) or Skills. The instruction includes Skills heading separate. We could put Preferred Qualifications under Skills. But we have both Requirements and Qualifications headings. Let's decide: Requirements = Basic Qualifications. Qualifications = Preferred Qualifications. Skills maybe not needed if covered. But we could also extract skills from Preferred Qualifications (knowledge of large scale automation, etc.) as Skills. However we have limited headings; we can include Skills if we have specific skill list. The Preferred Qualifications list includes knowledge items and experience items. Those could be considered Skills. We could put them under Skills. But we also have Qualifications heading; maybe we put Preferred Qualifications under Qualifications. Then Skills could be omitted if no specific skill list beyond that. But we have knowledge items that are skills. Let's decide: Use Requirements for Basic Qualifications, Qualifications for Preferred Qualifications, and maybe Skills omitted. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one? But headings are prescribed; we can include both if they have content. Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have Benefits section. Pay: Salary ranges listed for various locations. So we have Pay section. Schedule: Travel ~30% of the time mentioned. That's schedule/travel. So we can include Schedule section with that. We must not include boilerplate like EEO, etc. Remove those. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from description, responsibilities, qualifications, benefits, pay, schedule. We need to format as HTML fragment: only tags, no or . Usefor headings,
- for lists,
for prose. We need to ensure we don't create empty sections. Let's extract content. Description (About the role): Paragraphs: "At Amazon Web Services (AWS), we are seeking a Healthcare Solutions Architect to join our Applied AI Solutions (AAIS) Go to Market (GTM) organization. In this role, you will help shape and deliver on our GTM strategy for global healthcare customers and partners. As a solutions architect, you will be at the forefront of helping customers succeed using AWS technologies, linking technology with measurable business value for healthcare and life sciences organizations. As part of the AWS Applied AI Solutions organization, we have a vision to provide business applications, leveraging Amazon's unique experience and expertise, that are used by millions of companies worldwide to manage day-to-day operations. We blend vision with curiosity and Amazon's real-world experience to build opinionated, turnkey solutions. In this role, you will work closely with Business Development, Sales Specialists, and Product leadership to develop, accelerate, and sell current and new healthcare products. You will engage directly with customers to understand their business challenges, design and propose technical solutions, and guide successful implementation. By establishing and growing business and technical relationships with customers and internal stakeholders, you will drive customer adoption and value realization of AWS solutions in the healthcare and life sciences industry. You will use this knowledge to work with the Product organization to develop new features and capabilities and influence the product roadmap." That's the description. We could also include "About The Team" content: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is also substantive. Should we include under About the role? Probably yes, as it's about the team and culture. We'll incorporate those paragraphs into the About the role section after the initial description, maybe as separate
elements. But we must not create filler. Those paragraphs are substantive. Let's capture them: "Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." "Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." "Inclusive Team Culture AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do." "Mentorship & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional." "Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve." We'll include these as separate
under About the role. Now Responsibilities: bullet points under "Key job responsibilities". Let's list them: - Work with Business Development (BD) and Sales leaders to lead technical engagement with customers to understand requirements, propose solutions, and address technical concerns - Build and deliver technical presentations, demonstrations, and proofs of concept to showcase AWS capabilities to Healthcare customers - Partner with Sales, Business Development, and Marketing teams to develop and execute go-to-market strategies for healthcare solutions - Collaborate with Product teams to develop new features, products, and services that delight healthcare customers, providing technical expertise and customer feedback - Capture and share best practices and technical knowledge within the AWS solutions architect community - Develop customer-facing technical content such as reference architectures, whitepapers, and implementation guides for healthcare use cases - Stay current on industry trends, regulations, and emerging technologies in the healthcare and life sciences space - Travel ~30% of the time to support customer engagements Note: Travel is also schedule; but we can keep it in responsibilities and also maybe schedule. But we should not duplicate? The instruction says preserve ALL substantive information; we can include travel in responsibilities and also schedule section? Might be duplicate but okay. However we might want to avoid duplication; but it's okay to have same info in two places? Might be considered redundant but not prohibited. However better to keep travel under Schedule section, and maybe remove from responsibilities to avoid duplication. But responsibilities list includes travel; we could keep it there and also have schedule section referencing travel. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered unnecessary. I'd keep travel in responsibilities and also include schedule section with travel detail. But to avoid duplication, maybe we keep travel only under Schedule and remove from responsibilities. However the responsibilities bullet list includes travel; if we remove it, we lose that detail from responsibilities. But we could keep it in responsibilities and also schedule; it's still preserved. I'd keep both. Now Requirements (Basic Qualifications): - 12+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - Bachelor's degree in computer science, engineering, mathematics or equivalent - Experience developing technology solutions and evangelising end-to-end technology roadmaps that guide IT transformations toward cloud computing - Experience communicating across technical and non-technical audiences and at C-level, including training, workshops, publications Now Qualifications (Preferred Qualifications): - Knowledge of large scale automation and workflow management or equivalent - Knowledge of distributed systems design and implementation or equivalent - Knowledge of database design and implementation or equivalent - Knowledge of presentations and whiteboarding skills with a high degree of comfort speaking with internal and external executives, IT management, and developers - Experience architecting, migrating, transforming or modernizing customer requirements to the cloud We could also treat the last as experience. Now Skills: maybe we could extract specific skills from Preferred Qualifications: large scale automation, workflow management, distributed systems design, database design, presentations, whiteboarding, speaking with executives, architecting, migrating, transforming, modernizing customer requirements to cloud. But we already have them under Qualifications. Could also create Skills section with those items. But to avoid thin sections, maybe we combine Preferred Qualifications into Skills and omit Qualifications. However we have both headings; we can include both if they have content. Let's decide to put Preferred Qualifications under Qualifications, and Skills maybe omitted or we could put some specific skills like "presentations and whiteboarding skills" etc. But we already have them. Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we should have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Skills could be omitted if we consider Qualifications covers it. Now Benefits: list: - Sign-on payments and restricted stock units (RSUs) - 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 - Parental leave We could also mention "Learn more about our benefits at https://amazon.jobs/en/benefits." but that's a link; we can include as part of description. Now Pay: Salary ranges per location: - USA, CA, San Francisco - 210,200.00 - 284,300.00 USD annually - USA, IL, Chicago - 182,800.00 - 247,300.00 USD annually - USA, MA, Boston - 18
- for lists,