Principal Healthcare Solutions Architect, AI Solutions
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. Must preserve all substantive info, no boilerplate, no EEO, etc. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary ranges for various locations, and benefits description. So we can include Pay section with salary ranges? It says "The base salary range for this position is listed below." Then lists multiple city ranges. So we have pay info. Benefits: description of benefits. So we can include Benefits section. Schedule: not mentioned except travel ~30% of the time. That's not schedule per se; schedule could be travel expectation. Might be considered schedule? The instruction: include Schedule section only if posting actually states them. It mentions travel ~30% of the time. That's not a schedule like full-time/part-time, but could be considered schedule? Probably not; we should not create Schedule section unless explicit schedule like "full-time", "part-time", "shift". Travel is not schedule. So omit Schedule.
We need sections: About the role (maybe from description), Responsibilities (Key job responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe from responsibilities? Could combine? But we need to follow instruction: use headings for those categories if content exists. We have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. Skills maybe from responsibilities like presentations, whiteboarding, etc. Could create Skills section from bullet points like "Experience communicating across technical and non-technical audiences", "Knowledge of presentations and whiteboarding skills". Might be okay.
We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all bullet points from responsibilities, basic qualifications, preferred qualifications, benefits, pay ranges, travel, team description, etc.
We must remove boilerplate: EEO, equal opportunity, scam warning, legal, navigation, cookie, duplicated lines, application instructions. Also remove "About The Team" sections like "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Those are boilerplate? They are generic AWS culture statements; likely considered boilerplate to remove. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" sections might be considered boilerplate but they are part of job description. However they are generic AWS marketing; but they might be considered not substantive? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About The Team" sections are substantive? They describe culture, but they are generic across many AWS jobs. Might be considered boilerplate. Safer to remove them? The instruction only mentions specific boilerplate types; not explicitly culture. But to be safe, we could keep them as they are part of description. However they might be considered filler. I'd lean to keep them because they are part of the job posting and not explicitly excluded. But the instruction says "Prefer a few substantive sections over many thin ones." So we could combine them into a short paragraph under About the role maybe.
We need to output only HTML fragment, no markdown fences.
Let's structure:
About the role
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.
Responsibilities
- 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
Requirements
- 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
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
Skills
Strong technical presentation and whiteboarding abilities; ability to communicate complex concepts to both technical and non-technical audiences, including C-level executives; experience building proofs of concept and reference architectures; familiarity with healthcare industry trends and regulations; skill in collaborating with cross‑functional teams (BD, sales, marketing, product) to drive go‑to‑market strategies.
But we must not invent detail. The Skills section we created includes some inference. Might be considered summarizing. Better to omit Skills section if not explicitly listed. The posting does not have a separate "Skills" heading; we could combine skills into Responsibilities or Qualifications. The instruction: use headings for sections if posting has real, specific content for it. There's no explicit Skills section, so we should not create one. So we omit Skills. We have Benefits and Pay sections. Benefits: The posting includes: "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." We should preserve that. Pay: The posting includes base salary ranges for multiple locations. We should include that. We need to format Pay as maybe awith list? Could use
- for each location. But the instruction: Use
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but it's a list of ranges. Could still use
- . Might be okay. Or just
with the ranges separated by commas. Safer to use
. We must not include Job ID or requisition numbers. We must not include boilerplate like "Amazon is an equal opportunity employer..." etc. Remove that. We must not include "Los Angeles County applicants:" etc. That's legal boilerplate; remove. We must not include "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction; remove. We must not include "Learn more about our benefits at https://..." maybe that's okay as it's part of benefits description; but it's a link; we can keep as part of benefits paragraph. We must not include "Our inclusive culture empowers Amazonians..." that's boilerplate; remove. We must not include "If you have a disability and need a workplace accommodation..." that's accommodation info; maybe considered boilerplate; remove. We must not include "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc; remove. We must not include "Our inclusive culture empowers Amazonians to deliver the best results for our customers." remove. We must not include "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. We must not include "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." That's substantive pay info; keep. We must not include "Amazon also offers comprehensive benefits including ..." keep. We must not include "Learn more about our benefits at https://amazon.jobs/en/benefits." keep as part of benefits. Now produce HTML. Let's craft:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
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. Learn more about our benefits at https://amazon.jobs/en/benefits.
Pay
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.
- 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 - $182,800.00 - $247,300.00 USD annually
- USA, NY, New York - $20
- . Might be okay. Or just
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but it's a list of ranges. Could still use