Sr. UX Designer

We need to output HTML fragment with sections: About the role (maybe not needed if content is description?), Responsibilities, Requirements (maybe combine Required Qualifications?), Skills? Benefits, Pay, Schedule. Must include only sections with real specific content. Remove boilerplate, navigation, EEO, etc. Also remove application instructions, duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. We need to preserve all substantive information. Let's parse the posting: - Title: Senior UX Designer Job Description (but we don't repeat title as heading) - Opening paragraph: "We are seeking a Senior UX Product Designer to help shape the next generation of AI-powered experiences across our product ecosystem. In this role, you will work at the intersection of user experience, product strategy, and applied AI, translating complex model capabilities into intuitive, trustworthy, and high-impact workflows. You will define how humans collaborate with AI—designing the interactions, feedback loops, transparency moments, and control surfaces that make AI feel both powerful and reliable. You will partner closely with product management, product engineering, and data science to build experiences that balance innovation with responsible AI practices. This role is ideal for a designer who thrives in ambiguity, understands the unique behaviors and constraints of AI systems, and can convert them into clear, user-centered solutions." That's about the role. Could be "About the role" section. - Then "Key Responsibilities" with bullet list. - Then "Required Qualifications" with bullet list. - Then "Preferred Qualifications" bullet list. - Then "This posting is for proactive recruitment purposes..." (maybe not needed; it's boilerplate? It's about usage; could be considered metadata but not essential; we can drop as it's not substantive? Might be considered minor metadata; we can fold into a short p or drop. Probably drop. - Then "What’s in it For You?" with sub-bullets: Hybrid Work Model, Flexibility & Work-Life Balance, Career Development and Growth, Industry Competitive Benefits, Culture, Social Impact, Making a Real-World Impact. Those are benefits. So we can create Benefits section summarizing those bullet points. - Then "Our use of AI within the recruitment process" paragraph: maybe not needed? It's about recruitment AI usage; could be considered boilerplate? Might be considered relevant but not a benefit; maybe we can include as a short note under About the role? Probably drop as it's not substantive about job. - Then "In the United States, Thomson Reuters offers a comprehensive benefits package..." This repeats benefits details; we already have benefits; we can incorporate details into Benefits section. But we must not duplicate. We'll combine. - Then "Thomson Reuters complies with local laws that require upfront disclosure of the expected pay range for a position. The base compensation range varies across locations. For any eligible US locations, unless otherwise noted, the base compensation range for this role is $102,200 USD - $189,800 USD. For Ontario, Canada, the base compensation range for this role is $105,000 CAD - $155,000 CAD. Base pay is positioned within the range based on several factors including an individual’s knowledge, skills and experience with consideration given to internal equity. Base pay is one part of a comprehensive Total Reward program which also includes flexible and supportive benefits and other wellbeing programs. This role may also be eligible for an Annual Bonus based on a combination of enterprise and individual performance." That's Pay section. - Then "About Us" paragraph describing company. Could be About the role? Actually it's about company; could be included as About the role or maybe a separate About Us section but not required. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (maybe combine opening paragraph and About Us?). But About Us is more about company; still could be considered About the role? Probably we keep About the role as the initial description; we could also add a short About Us paragraph but not required. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine About the role and About Us into About the role? Might be okay. - Then EEO statement etc: drop. - Then accommodation contact etc: drop. Thus sections: About the role, Responsibilities, Requirements (maybe combine Required and Preferred Qualifications? Could have Requirements and Preferred Qualifications separate? The instruction lists Requirements, Qualifications, Skills as possible headings. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications or Skills. But we have both; we could have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (preferred). Let's decide: Use Requirements for required qualifications, and Qualifications for preferred qualifications. Or Skills for preferred? The list includes Skills as a possible heading; but we have preferred qualifications that include abilities etc. Could treat as Skills. However we have both required and preferred; we can have two sections: Requirements (required) and Qualifications (preferred). That seems fine. - Benefits: combine bullet points from "What’s in it For You?" and the later benefits paragraph. - Pay: compensation range and bonus. - Schedule: Not explicitly mentioned; there is hybrid work model, flexible work arrangements, work from anywhere up to 8 weeks per year. That's schedule/flexibility. Could be considered Schedule section. The instruction says include Schedule only if posting actually states them. It does mention hybrid work model, flexible work arrangements, work from anywhere up to 8 weeks per year. So we can create Schedule section with those details. We must not include sections with filler like "commensurate with experience". We have real specifics. Now produce HTML fragment: use

for each section heading. Use

• for lists. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must not include markdown code fences. Let's craft. Sections:

  About the role

  We are seeking a Senior UX Product Designer to help shape the next generation of AI-powered experiences across our product ecosystem. In this role, you will work at the intersection of user experience, product strategy, and applied AI, translating complex model capabilities into intuitive, trustworthy, and high-impact workflows. You will define how humans collaborate with AI—designing the interactions, feedback loops, transparency moments, and control surfaces that make AI feel both powerful and reliable. You will partner closely with product management, product engineering, and data science to build experiences that balance innovation with responsible AI practices. This role is ideal for a designer who thrives in ambiguity, understands the unique behaviors and constraints of AI systems, and can convert them into clear, user-centered solutions.

  Thomson Reuters informs the way forward by bringing together the trusted content and technology that people and organizations need to make the right decisions. We serve professionals across legal, tax, accounting, compliance, government, and media. Our products combine highly specialized software and insights to empower professionals with the data, intelligence, and solutions needed to make informed decisions, and to help institutions in their pursuit of justice, truth, and transparency. Reuters, part of Thomson Reuters, is a world leading provider of trusted journalism and news. We are powered by the talents of 26,000 employees across more than 70 countries, where everyone has a chance to contribute and grow professionally in flexible work environments. At a time when objectivity, accuracy, fairness, and transparency are under attack, we consider it our duty to pursue them.

  That combines About the role and About Us.

  Responsibilities

  • Lead the end-to-end design of AI-powered features, including agentic workflows, generative interactions, and human-in-the-loop systems
  • Translate model behaviors, data inputs, and system limitations into coherent UX patterns that drive user trust and product adoption.
  • Prototype with real AI/LLM models to evaluate user prompts, improve model responses, and inform product direction.
  • Map and design collaboration patterns between users and AI—defining when AI acts autonomously, when humans take control, and how handoffs occur.
  • Create clear interaction flows that incorporate transparency moments, safety guardrails, override options, and recovery states.
  • Partner with data science and engineering to shape model requirements, evaluate performance constraints, and align system behaviors with user needs.
  • Partner with UX Research to run usability testing and AI-specific validation studies to understand user mental models, trust factors, and interaction expectations.
  • Leverage qualitative and quantitative data to run evaluative studies for AI features (e.g., prompt/response quality, hallucination risk, trust sign)
  • Contribute to internal design standards for AI patterns, prompt design guidelines, evaluation criteria, and UX quality benchmarks.
  • Collaborate with product and research teams to identify new opportunities where AI can meaningfully improve outcomes for users.
  • Communicate design decisions with clarity, influence senior stakeholders, and guide teams through ambiguous or evolving problem spaces.
  • Leverage AI tooling and internal content standards to deliver clear, concise, brand aligned product experiences.
  • Design accessible solutions and collaborate with the Accessibility team to ensure WCAG 2.1 AA compliance, using AI checks alongside expert review.

  Requirements

  • 6+ years of professional product design experience with a strong portfolio demonstrating end-to-end ownership of complex workflows.
  • Experience designing with AI or LLM technologies, including prompt design, generative UX, and evaluating model output quality.
  • Strong interaction design skills with the ability to simplify ambiguous AI behaviors into predictable, user-centered experiences.
  • Familiarity with model behaviors and limitations—hallucinations, confidence levels, deterministic vs. probabilistic output, and data quality impacts.
  • Ability to prototype using tools such as Figma, Python notebooks, model sandboxes, or no-code AI orchestration tools.
  • Hands-on experience planning and executing end-to-end user research—defining objectives, recruiting participants, moderating studies (interviews, usability tests, surveys, concept/validation), synthesizing insights, and translating findings into roadmap and design decisions.
  • Deep systems-thinking skills and comfort designing across multiple layers: UI, data inputs, model constraints, and operational workflows.
  • Experience collaborating with product management, product engineering, data science, product analytics, user research, content design, accessibility, UX engineering in high-velocity, cross-functional teams.
  • Strong communication and storytelling skills—able to influence decisions and articulate the “why” behind design choices.
  • Commitment to responsible AI principles, including transparency, fairness, and user empowerment.
  • A growth mindset, comfort navigating ambiguity, and an enthusiasm for experimenting with emerging technologies.

  Qualifications

  • Ability to design intuitive search, drafting, and review workflows—especially those involving complex knowledge structures or trust-critical decision moments.
  • Comfort working with model-evaluation tooling, analytics dashboards, and prompt or version-management systems to understand and refine AI behavior.
  • Strength in shaping information architecture for large-scale content ecosystems, including clear citation patterns, confidence signals, and quality indicators.
  • Familiarity with domain-heavy environments—such as newsroom tooling, legal research, tax and compliance, risk and fraud, or financial analysis—and the ability to translate complexity into usable experiences.
  • Experience shipping zero-to-one products, iterating rapidly through ambiguity to test hypotheses, derisk bets, and accelerate product market fit.

  Benefits

  • Hybrid Work Model: flexible hybrid working environment for office-based roles while delivering a seamless experience that is digitally and physically connected.
  • Flexibility & Work-Life Balance: Flex My Way policies to help manage personal