Principal Solutions Architect, HCLS

At Amazon Web Services (AWS), we are seeking a Principal Healthcare & Life Sciences (HCLS) Solutions Architect to join our HCLS organization within AWS Industries. In this role, you will define and drive our strategy for global HCLS customers and partners, serving as a trusted strategic advisor to some of the world's largest healthcare and life sciences organizations. You will lead the development of long-term technology strategies that address complex, often undefined business challenges — helping customers understand how cloud adoption can fundamentally transform their business outcomes and competitive position.

As a Principal Solutions Architect, you will operate as both a technical authority and a strategic influencer — connecting technology vision with measurable, long-term business value for healthcare and life sciences organizations. You will bring exceptional technical depth, executive-level business acumen, and the ability to shape technology strategy at the highest levels, engaging C-suite leaders, business decision makers, and senior technical executives to influence the direction of enterprise-scale cloud transformations.

You will architect solutions to the most significantly complex challenges in HCLS — decomposing intricate, multi-system problems into elegant, scalable designs that become reference architectures for the broader SA community. You will drive the creation of new architectural patterns and industry-specific methodologies (spanning Artificial Intelligence, Machine Learning, Generative AI, data platforms, and regulated workloads), and you will influence the product roadmaps of AWS service teams by translating deep customer insight into clear engineering requirements. In close partnership with account management, professional services, support, product teams, and the AWS partner ecosystem, you will own the strategy for building broad, lasting AWS adoption within your most strategic HCLS enterprise customers.

Key job responsibilities
This role drives the success of AWS's most complex and strategic Healthcare and Life Sciences engagements. As a Principal Solutions Architect, you will own end-to-end solution programs — from strategy through architecture through customer realization — delivering measurable, long-term business impact. You will operate with complete independence, applying high judgment to determine where to focus your efforts for the greatest organizational and customer impact.

A core responsibility is defining the technical and strategic direction for large-scale HCLS transformations, including AI/ML and Generative AI programs, data modernization, and regulated cloud migrations. You will develop reusable reference architectures, methodologies, and thought leadership content — whitepapers, frameworks, and prescriptive guidance — that scale your impact across the SA community and the broader HCLS market.

You will serve as a strategic advisor to your customers' senior leadership, building trust at the executive level and influencing their long-term technology and business strategy. You will identify emerging customer needs before they are fully articulated, ask the questions customers haven't asked themselves, and lead the consensus-building required to align large, complex organizations around a path forward.

This role is a significant force multiplier within the SA organization. You will develop and lead programs to scale best practices across teams, perform Principal SA Technical Promotion Assessments, shepherd the tech promo process, and actively mentor and grow the HCLS SA community. You will contribute to your organization's strategic planning, identifying capability gaps, influencing hiring decisions, and partnering with leaders to shape the long-term direction of the team.

A day in the life
Your morning opens with a call with a global health system's CTO — you're advising on a multi-year cloud transformation roadmap and pushing back on a proposed architecture that will create long-term constraints. Mid-morning, you're leading an internal working group to define a new HCLS Generative AI reference architecture that three account teams will deliver to separate customers next quarter. After lunch, you join a product team's product review, translating patterns you've observed across a dozen customer engagements into a concise set of requirements that could shape the next major service release. You spend the late afternoon mentoring two SAs on an upcoming promotion assessment — walking through how to apply the "Moving to Principal" criteria rigorously and fairly. Between meetings, you're adding to a whitepaper that will be published at re:Invent, and fielding a Slack thread where SAs across three segments are debating a regulatory architecture question only you've navigated at this scale. No two days look the same.