UI UX designer job description
The title fuses two jobs the market used to keep apart, and that fusion is why so many of these hires disappoint. One of them is interface craft. The other is finding out what people actually do and rebuilding the flow around it. Plenty of designers are strong at one and adequate at the other, and the advert almost never says which one the company is short of. Here is a description you can post, and how to work out which candidate is in front of you.
The job description
We are looking for a designer who works from evidence and ships. You will own flows end to end, from understanding the problem through to the details engineering needs, and you will still be around after release.
What you will own
- End-to-end flows for the areas you take on, rather than screens in isolation
- Talking to users directly, at whatever scale the question deserves
- The interface itself: hierarchy, states, content, and behaviour at the edges
- Working inside the design system, and arguing for a change to it when the pattern genuinely does not fit
- The handover, and the decisions that surface mid-build
What the job needs
- Shipped work in a product with real users and real constraints
- The ability to run a usability session without leading the participant to the answer
- Enough understanding of the build to know which requests are expensive
Signals we weight heavily
- You have removed steps from a flow
- You can show the error and empty states of something you shipped
- You have changed a design because a user did something you did not expect
What a UI UX designer is actually accountable for
Screens are the deliverable. The outcome is that people finish what they came to do, that support hears about it less often, and that engineering can build the thing without inventing half of it.
- Fewer steps between somebody starting and finishing, with evidence that it got shorter
- The states nobody enjoys designing: empty, loading, error, permission refused
- A decision defended to somebody senior who wants it changed, and reversed when their argument turns out to be better
- A handover engineering can build without a week of clarifying questions
- Knowing what happened to the design after release
Four ways a UI/UX designer hire looks right and is not
Every one of these passes a resume screen. Ladders eye-tracking study timed the average initial scan at just 7.4 seconds, which is long enough to check the four signals below and not long enough to check anything that would contradict them.
Looks right
A beautiful portfolio of concept work
Concept work is unconstrained: no legacy component, no edge case, no engineer explaining that the interaction is a fortnight of work. It is genuine evidence of craft and taste, and no evidence at all of the compromises that decide whether shipped software is any good. Ask for a screen they are not proud of and the constraint that produced it.
Looks right
A portfolio built mostly on redesigns
The most common case study format and the hardest to attribute. Redesigns are frequently unshipped, self-initiated, and presented without a before-number because there never was one. Ask what the metric was beforehand, who measured it, and which parts of the redesign actually reached users.
Looks right
UI and UX in the same title
The market fused two jobs into one keyword. A strong interface designer may never have run a usability session. A strong researcher may hand over a flow diagram and expect somebody else to make it look convincing. The portfolios can look similar, so decide which gap you are filling before the advert goes out.
Looks right
Deep tool skill: component libraries, variants, a design system on the resume
System and tool fluency is visible, demonstrable and quickly learned, which is why most interviews spend their time there. What actually decides the hire is whether the designer can hold a decision in front of a founder who wants the button moved, and change their mind when the argument against them is the better one.
What to ask for evidence of instead
Four questions, and what the answer actually tells you. Take these into your own process whether or not you ever talk to us.
- Show me a flow you simplified. How many steps disappeared, and what broke as a result?
- What it tells you: The second half is the real question. Every simplification costs something, usually an edge case or a power user, and designers who have shipped can name the trade-off they accepted and who complained.
- Walk me through the empty state, the error state and the loading state of something you shipped.
- What it tells you: The fastest way to establish whether the portfolio work ever reached production. Concept work never has these. Shipped work always does, because somebody had to decide what the screen says when the request fails.
- Tell me about a design you shipped that did not work. How did you find out?
- What it tells you: Whether they see anything at all after handover. A designer who has never received bad news about a design either did not ship it or was never shown the numbers, and both are worth knowing before you hire.
- Which of your designs did engineering push back on, and how did it end?
- What it tells you: Whether build cost is treated as an input or as somebody else problem. Ask for one case where they changed the design and one where they held the line. A designer who always concedes and one who never does are the same failure in opposite directions.
How Continuity1 runs this funnel
The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.
- 1 in 3
- Shortlisted candidates you meet who become the hire
- Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.
- Continuity1 tracked engagements
- ~3
- Interviews your team sits in, per hire
- Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.
- Ashby talent-trends report
- 1 in 9
- Accepted offers that ghost before joining
- Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.
- nasscom community
- 95%
- Offers that close inside your stated band
- 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.
- Continuity1 tracked engagements
Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.
You review a scored shortlist and make the calls. The filtering never lands on your calendar.
Questions teams ask
Are we hiring for UI or for UX?
Look at what is failing. If people cannot find or complete things and nobody knows why, you need research and flow work. If the product works and looks unconvincing beside the alternative, you need interface craft. One title covers both, so the advert has to name the failure you are fixing or you will interview the wrong half of the market.
Portfolio review or a design exercise?
A portfolio walkthrough done properly beats an exercise almost every time, because you can ask about constraints, disagreements and what shipped. If you do run an exercise, keep it short, use a problem you have already solved, and pay for anything that takes real time.
Should the designer do research, or do we need a researcher?
Below a certain size the designer does the research, and the risk is that it quietly stops happening under delivery pressure. Ask how many users they spoke to in their last six months and who those users were. The number is often zero, it is not always their fault, and it still tells you which habit you are hiring.
In-house designer or an agency?
An agency is good at a defined project with an end date. A product that changes every week needs somebody who accumulates context about your users, sits in the trade-off conversations and stays with what shipped. If your problem is one launch, use the agency. If your problem is a product, hire.
Related