User Experience Designer III, AI at Work

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID. Must not include boilerplate like EEO, accommodation, etc. Must preserve all substantive info. We need to parse the description. Sections: - About the role: The description starts with "Description We are looking for a Senior UX Designer...". That's about the role. Could be "About the role" heading. - Responsibilities: "Key job responsibilities" list. - A day in the life: Could be part of responsibilities or separate? Might be considered responsibilities but we can include as part of responsibilities or separate "A day in the life" not a required heading. Probably better to include under Responsibilities. - About The Team: Could be "About the Team" maybe not a required heading but could be part of About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. "About the Team" is not in list, so we should not create a heading for it. We could incorporate its content into About the role or maybe omit? But we must preserve ALL substantive information. So we need to include that info somewhere. Could put under About the role as a paragraph. - Basic Qualifications: That's Requirements or Qualifications? The list includes Basic Qualifications and Preferred Qualifications. So we can have Requirements (maybe Basic Qualifications) and Qualifications (Preferred Qualifications). Or we could combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements and Qualifications separate. We'll put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. - Skills: There's a list of skills/experience like motion design, micro-interactions, front-end technologies etc. Also "Experience with AWS services, cloud infrastructure, or AI/security product domains", "Familiarity with the AWS Design System (Cloudscape) or similar enterprise design systems", etc. Those could go under Skills. - 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 mention sign-on payments and RSUs. So we have benefits content. - Pay: The base salary range: "USA, TX, Austin - 137,800.00 - 186,400.00 USD annually" and "USA, WA, Seattle - 137,800.00 - 186,400.00 USD annually". So we have pay info. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. We must not include boilerplate like EEO, accommodation, etc. Also must not include duplicated lines. Also must not include application instructions. Also must not include Job ID. We need to preserve all substantive information: that includes the description paragraphs, responsibilities list, day in the life, about the team, basic qualifications, preferred qualifications, skills, benefits, pay. We need to format as semantic HTML: use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include or tags, no markdown fences. We need to decide how to split content. Let's outline:

  About the role

  We are looking for a Senior UX Designer to be the single-threaded owner (STO) of the user experience for a brand-new AI-native application launching to both Amazon internal customers and external AWS customers. This is a high-impact, high-autonomy role on a small, fast-moving team where you will be the voice of the customer and the primary driver of design quality. You will own the experience from concept through production — ensuring that what we build is not only functional, but genuinely loved by the people who use it. This product is AI and agent-native from the ground up — not a bolt-on AI feature to an existing service. You will define what it means to interact with intelligent agents, design trust and transparency into AI-driven workflows, and create experiences that make complex AI capabilities feel intuitive and empowering for enterprise customers. You will be the single designer responsible for the end-to-end experience — from first-run onboarding through daily power-user workflows — across both internal Amazon users and external AWS customers. This is not a role where you'll receive a fully scoped brief and execute against it. You'll operate in ambiguity, define the problem space, and chart the design direction. You'll wear many hats — researcher, interaction designer, visual designer, prototyper, and storyteller — and you'll thrive doing it.

  Maybe also include About The Team paragraph here: "Our team is focused on creating meaningful, intuitive experiences that customers rely on. We operate in a collaborative environment where designers, product managers, engineers, and researchers work closely together to solve problems that span multiple systems and touchpoints. We value clarity of thought, inclusive perspectives, and a commitment to craft. As we look ahead, we are investing in new ways to leverage AI capabilities and scale our design impact. This is an opportunity to shape both what we build and how we build it." We could add that as another paragraph under About the role.

  Responsibilities

  • Lead end-to-end design from problem framing and discovery through delivery, iteration, and post-launch refinement, ensuring solutions address real customer needs across complex product surfaces.
  • Establish and maintain interaction and visual design standards that ensure coherence across multiple product areas, creating patterns that are maintainable and scalable over time.
  • Collaborate with product managers, engineers, and data scientists to align cross-functional partners around a shared design direction, balancing customer needs against technical constraints and business priorities.
  • Conduct and apply user research to inform design decisions, map full customer journeys to identify friction and opportunities, and use data signals to validate and iterate on shipped experiences.
  • Evaluate when and how to integrate generative AI tools into the design workflow, accelerating prototyping and exploration while maintaining high craft standards where human judgment is essential.
  • A day in the life: You might start your morning reviewing research findings with your team, then move into a design critique where you present interaction concepts for a complex workflow spanning multiple systems. After lunch, you could partner with engineering to work through edge cases and technical constraints, followed by a strategy session where you advocate for a design direction with product leadership. Throughout it all, you are mentoring other designers, shaping how the team approaches problems, and pushing for solutions that serve customers over the long term.
  But note: "A day in the life" is prose, not a list item? Could be a paragraph. But we can keep as list item for simplicity. However instruction: Use
  • for any list of duties/requirements/benefits. The day in the life is not a list but a narrative; we could put as

    . But we could also treat as a list item; but better to follow instruction: only use

    • for lists. So we should put day in the life as a

      after the list. Thus:

      Responsibilities

      • Lead end-to-end design from problem framing and discovery through delivery, iteration, and post-launch refinement, ensuring solutions address real customer needs across complex product surfaces.
      • Establish and maintain interaction and visual design standards that ensure coherence across multiple product areas, creating patterns that are maintainable and scalable over time.
      • Collaborate with product managers, engineers, and data scientists to align cross-functional partners around a shared design direction, balancing customer needs against technical constraints and business priorities.
      • Conduct and apply user research to inform design decisions, map full customer journeys to identify friction and opportunities, and use data signals to validate and iterate on shipped experiences.
      • Evaluate when and how to integrate generative AI tools into the design workflow, accelerating prototyping and exploration while maintaining high craft standards where human judgment is essential.

      A day in the life: You might start your morning reviewing research findings with your team, then move into a design critique where you present interaction concepts for a complex workflow spanning multiple systems. After lunch, you could partner with engineering to work through edge cases and technical constraints, followed by a strategy session where you advocate for a design direction with product leadership. Throughout it all, you are mentoring other designers, shaping how the team approaches problems, and pushing for solutions that serve customers over the long term.

      Now Requirements (Basic Qualifications):

      Requirements

      • 7+ years of design experience
      But also maybe include "Experience working on 0-to-1 products or early-stage product teams, ideally taking a product from concept to GA launch" is under Preferred Qualifications? Actually that is listed under Preferred Qualifications. So Requirements only have basic qualification. Now Qualifications (Preferred Qualifications):

      Qualifications

      • Experience working with engineering and product teams to define a product and bring it to market
      • Experience designing AI-native or agent-based products — particularly generative AI, conversational AI, autonomous agents, or ML-powered workflows launched to external customers
      • Experience launching AI products at AWS or a major cloud provider to external enterprise customers
      • Experience working on 0-to-1 products or early-stage product teams, ideally taking a product from concept to GA launch
      • Comfort operating in highly ambiguous environments with minimal direction
      • Experience with AWS services, cloud infrastructure, or AI/security product domains
      • Familiarity with the AWS Design System (Cloudscape) or similar enterprise design systems
      • Deep understanding of the unique UX challenges of AI — trust, explainability, error handling, progressive disclosure of AI confidence, and human-in-the-loop patterns
      • Experience designing for dual-audience products (internal + external customers)
      • Experience working on small, cross-functional teams where speed and ownership are valued over process
      • Experience with motion design, micro-interactions, or front-end technologies (HTML/CSS/JS) is a plus
      Now Skills: Could be separate section but we already covered many skills in Qualifications. However there may be overlapping. The instruction says prefer a few substantive sections over many thin ones. We could merge Skills into Qualifications or maybe keep Skills for technical skills like motion design, front-end tech, AWS Design System, etc. But we already have those in Qualifications. To avoid duplication, we could treat Qualifications as both preferred qualifications and skills. But we need to follow headings list: Skills is an option. If we put skills, we must not duplicate content. We could split: Qualifications for experience/background, Skills for specific abilities. Let's see. Preferred Qualifications list includes many items that are skills/experience. Could be considered qualifications. The Skills heading could be used for things like "Experience with motion design, micro-interactions, or front-end technologies (HTML/CSS/JS) is a plus", "Familiarity with the AWS Design System (Cloudscape) or similar enterprise design systems", "Experience with AWS services, cloud infrastructure, or AI/security product domains". But those are already in Preferred Qualifications. To avoid duplication, we could not have a separate Skills section; we can incorporate those into Qualifications. The instruction says prefer a few substantive sections over many thin ones. So better to not create Skills if its content overlaps heavily. We'll omit Skills section.