# Product / UX designer

> Decides how a piece of software behaves for the person using it — screen by screen, state by state — and proves the decision with evidence.

Page: https://flyvolo.ai/en/careers/product-designer
Impact index: 52/100 · confidence Medium confidence · assessed 2026-09-10
This is not a probability of losing a job.

## Scope

Written for product, UX and UI designers on software teams. Design research as a separate role, brand and marketing design, and game design differ.

## Tasks

### Producing screens and components

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: Design tools now generate screens from a prompt and a design system, and code-generation tools skip the mockup entirely by producing a working interface. The pixel-production hours that filled a junior designer's week are the clearest casualty on a product team.
- What this does NOT establish: Pixel production was the paid apprenticeship. Removing it does not just remove junior jobs; it removes how anyone becomes the senior designer the same team still needs.
- Records:
  - 2026-03-01 · Constraint · Figma reported that it began enforcing AI credit limits across all its seats in March 2026, so generating designs and prototypes with Figma Make and its other AI features now draws on metered credits — https://flyvolo.ai/en/changes/ev-20260301-product-designer-3 (source: https://www.sec.gov/Archives/edgar/data/1579878/000162828026053348/fig-20260630.htm)
  - 2024-07-02 · Constraint · Figma rolled back its Make Designs prompt-to-UI feature soon after launch when 'weather app' prompts produced screens closely resembling Apple's, citing unvetted new components; relaunched Sept 2024 — https://flyvolo.ai/en/changes/ev-20240702-product-designer-1 (source: https://www.figma.com/blog/inside-figma-a-retrospective-on-make-designs/)

### Defining the right problem

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: This rests on observing real people using real software and on organisational judgement about what the business can and will change. It is the input to everything downstream, and generating polished screens for the wrong problem is now cheaper and therefore more common — which raises the value of getting the problem right.
- What this does NOT establish: Defining the problem is usually shared with product management, and on small teams it is not the designer who wins that argument. Being valuable is not the same as being the one who decides.
- Records:
  - 2025-02-10 · Constraint · The UK government's AI Playbook says choosing where to use AI must be led by user needs and pain points, not by what the technology can do, found through user research — https://flyvolo.ai/en/changes/ev-20250210-product-designer-6 (source: https://www.gov.uk/government/publications/ai-playbook-for-the-uk-government/artificial-intelligence-playbook-for-the-uk-government-html)

### Research and usability testing

- Direction: Being augmented
- Basis: evidenced (verified records attached)
- Why: Transcription, synthesis of interview notes and analysis of session recordings are much faster with assistance, and synthetic 'users' are being marketed as a substitute. The substitute is weak where it matters: it cannot reproduce the surprise of a real person doing something no one anticipated, which is the finding research exists to produce.
- What this does NOT establish: Research is the first budget cut in most downturns, regardless of whether synthetic users are any good. Its exposure is commercial before it is technical.
- Records:
  - 2026-03-16 · Pilot · UK government designers piloted GOV.UK Chat with over 10,000 users and 99 remote usability tests, added clarifying questions, and found streaming answers meant redesigning safety guardrails — https://flyvolo.ai/en/changes/ev-20260316-product-designer-5 (source: https://insidegovuk.blog.gov.uk/2026/03/16/5-things-we-learned-testing-gov-uk-chat-an-ai-assistant-for-government/)
  - 2026-02-12 · Constraint · Canada's government design guidance requires AI help tools on Canada.ca to be labelled as AI and to cite an authoritative source in every answer, bans human names, and asks for early user testing — https://flyvolo.ai/en/changes/ev-20260209-product-designer-4 (source: https://design.canada.ca/guidance/ai/design-guidance.html)
  - 2025-02-17 · Constraint · A Nature Machine Intelligence study with 3,200 participants found that language models used in place of human participants, including in user testing, misportray and flatten identity groups — https://flyvolo.ai/en/changes/ev-20250217-product-designer-7 (source: https://www.nature.com/articles/s42256-025-00986-z)

### Getting the team to agree

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: Design decisions in software are negotiated, not decreed. The designer's leverage comes from evidence and from credibility built over previous decisions, both of which are personal. Tools produce more options to argue about; they do not settle the argument.
- What this does NOT establish: Alignment work grows with team size and disappears with the team. It protects the designer who is already trusted, not the role's headcount.
- Records:
  - 2026-05-14 · Constraint · Figma reported paid customers up 54% year on year to about 690,000 and new Pro team conversions up over 150%, attributing seat expansion to design's growing importance and adoption of its AI products — https://flyvolo.ai/en/changes/ev-20260515-product-designer-2 (source: https://www.sec.gov/Archives/edgar/data/1579878/000162828026035087/q126pressrelease.htm)

### Designing for non-deterministic products

- Direction: New task
- Basis: evidenced (verified records attached)
- Why: A large share of new software has a model in the loop, and designing how it fails, how it explains itself and how the user stays in control is an unsolved craft. Teams are hiring designers specifically for it, and the skill is scarce because almost no one has done it for long.
- What this does NOT establish: Scarcity here is temporary by construction — almost no one has done it for long because it is new, and that gap closes as everyone gets the same few years of practice.
- Records:
  - 2026-03-16 · Pilot · UK government designers piloted GOV.UK Chat with over 10,000 users and 99 remote usability tests, added clarifying questions, and found streaming answers meant redesigning safety guardrails — https://flyvolo.ai/en/changes/ev-20260316-product-designer-5 (source: https://insidegovuk.blog.gov.uk/2026/03/16/5-things-we-learned-testing-gov-uk-chat-an-ai-assistant-for-government/)
  - 2026-02-12 · Constraint · Canada's government design guidance requires AI help tools on Canada.ca to be labelled as AI and to cite an authoritative source in every answer, bans human names, and asks for early user testing — https://flyvolo.ai/en/changes/ev-20260209-product-designer-4 (source: https://design.canada.ca/guidance/ai/design-guidance.html)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt