Principal Product Designer, AWS Applied AI Solutions
Posted Updated
Description
Do you want your design work to decide what gets built, rather than describe it afterward?
Amazon builds artificial intelligence systems that scientists and clinicians use to discover new medicines and run clinical trials. Better software here has an unusually direct consequence: therapies reach patients sooner, and scientists spend their time on science.
You will own the end-to-end user experience point of view across that portfolio — from regulated clinical research through computational drug discovery — defining how a scientist works alongside an artificial intelligence teammate rather than operating a tool and proving it with working prototypes that become the specification engineering leverages to build.
Key job responsibilities
Own and defend the user experience point of view across the portfolio, working as a peer to product management, applied science, engineering and architecture rather than downstream of finished requirements.
Define the interaction model for software that acts on a person's behalf — how it shows its evidence, where the person keeps control, what it does when it is wrong, and how work is handed back.
Direct and build high-fidelity working prototypes, and use them as the shared specification that product and engineering develop against.
Mentor and develop other designers across the portfolio through mentoring and shared patterns.
A day in the life
You spend a morning with a computational biologist. She tells you the product output looks plausible and she does not trust it. This is the most consequential thing anyone will say all quarter, and the rest of your week goes into turning it into something the product does differently.
Later that week you present one working flow and three open questions to leadership, arguing that products built separately should reach a customer as one. How that lands decides what gets funded.
Another day you review a prototype of a pattern you specified.
About the team
Life Sciences, within AWS Applied AI Solutions, supports AI products for drug discovery and clinical research. Small team, large surface. Arguments are settled by building and inspecting: prototypes are the primary artifact and the engineering handoff. Regulators shape the products and how research is run, and design has carried much of the product direction, making the role load-bearing, not advisory. UX is horizontal: you succeed when a partner team ships your work. The systems behave like a capable colleague, not a tool, knowing when to act, when to ask, and how to show their work.
Amazon builds artificial intelligence systems that scientists and clinicians use to discover new medicines and run clinical trials. Better software here has an unusually direct consequence: therapies reach patients sooner, and scientists spend their time on science.
You will own the end-to-end user experience point of view across that portfolio — from regulated clinical research through computational drug discovery — defining how a scientist works alongside an artificial intelligence teammate rather than operating a tool and proving it with working prototypes that become the specification engineering leverages to build.
Key job responsibilities
Own and defend the user experience point of view across the portfolio, working as a peer to product management, applied science, engineering and architecture rather than downstream of finished requirements.
Define the interaction model for software that acts on a person's behalf — how it shows its evidence, where the person keeps control, what it does when it is wrong, and how work is handed back.
Direct and build high-fidelity working prototypes, and use them as the shared specification that product and engineering develop against.
Mentor and develop other designers across the portfolio through mentoring and shared patterns.
A day in the life
You spend a morning with a computational biologist. She tells you the product output looks plausible and she does not trust it. This is the most consequential thing anyone will say all quarter, and the rest of your week goes into turning it into something the product does differently.
Later that week you present one working flow and three open questions to leadership, arguing that products built separately should reach a customer as one. How that lands decides what gets funded.
Another day you review a prototype of a pattern you specified.
About the team
Life Sciences, within AWS Applied AI Solutions, supports AI products for drug discovery and clinical research. Small team, large surface. Arguments are settled by building and inspecting: prototypes are the primary artifact and the engineering handoff. Regulators shape the products and how research is run, and design has carried much of the product direction, making the role load-bearing, not advisory. UX is horizontal: you succeed when a partner team ships your work. The systems behave like a capable colleague, not a tool, knowing when to act, when to ask, and how to show their work.
