Technology
Shapes how digital products look and work
Every tap, menu and error message in a digital product has been designed. A UI/UX designer works out how that product should behave, what it should show and how somebody moves through it. User experience (UX) covers the whole journey; user interface (UI) covers the screens, controls, type, colour and visual detail through which it happens.
A screen turns policy and technology into small, unavoidable moments. If a rail ticket cannot be changed, the designer decides when to explain the rule. They choose what alternative to offer and make clear what will happen after a tap on “continue”. Strong UI/UX work begins with behaviour, not decoration. Noticing the hesitation before a click matters alongside visual judgement and curiosity about unexpected use.
Job titles overlap. Many technology companies use product designer for somebody covering both UI and UX. Larger organisations may separate interaction design, visual design and user research. Design degrees are common but not compulsory. Employers care most about the portfolio. They want more than polished screens. You must explain the problem, your choices and what changed after testing.
| When | Lowest 10% earn under | A typical earner | Top 10% earn over |
|---|---|---|---|
| On graduating | £21,000 | £28,000 | £40,000 |
| 1 year in | £23,000 | £32,000 | £46,000 |
| 2 years in | £26,000 | £37,000 | £54,000 |
| 3 years in | £28,000 | £42,000 | £62,000 |
| 4 years in | £31,000 | £47,000 | £70,000 |
| 5 years in | £34,000 | £52,000 | £78,000 |
| 6 years in | £36,000 | £56,000 | £85,000 |
| 7 years in | £38,000 | £60,000 | £92,000 |
| 8 years in | £40,000 | £64,000 | £98,000 |
| 9 years in | £42,000 | £67,000 | £104,000 |
| 10 years in | £44,000 | £70,000 | £110,000 |
A well-designed product lets somebody transfer money, book an appointment or find the right train. They do not have to think about the screen itself. The improvement may be one clearer sentence or one fewer step, but it can save thousands of people time and uncertainty. There is quiet satisfaction in making something feel simple when you know how much thought it required.
This is not creativity for its own sake. Every decision has limits. You consider what the user needs, what the technology can do and what the business can afford. You also consider what people with different abilities can access. Those constraints turn design into a practical puzzle. Taste and imagination still matter, but the strongest idea works for real people rather than only looking impressive.
Designers work with customers, product managers, engineers, researchers, writers and marketing. You learn how people behave and how software is built. You also see why sensible business decisions can create strange experiences. That breadth can lead towards research, shared design standards, product management or leadership. The role rewards people who enjoy joining several kinds of thinking into one answer.
People are less likely to challenge a database structure than the colour of a button. Feedback can arrive as personal preference, a senior leader’s passing thought or five contradictory requests from five different teams. You need to listen without becoming defensive, identify the real concern underneath the suggested fix and use evidence where possible. Even then, the final decision will not always be the one you believe is best.
Most jobs are not spent inventing beautiful new apps from scratch. You will work inside existing design rules, ageing technology and legal requirements. Decisions made years before you arrived also matter. An elegant journey may fail because it ignores an error, a small screen or somebody using a keyboard instead of a mouse. Much of the craft is improving an imperfect product within its real limits.
Your design still has to survive engineering estimates and changing priorities. More details appear while it is being built. Features may be simplified, delayed or made slightly differently. If you disappear after handing over the screens, small compromises can build into a poor experience. The job requires patience and a close relationship with engineers. Design quality is decided in the final product, not in the design file.
Usually 3–4 years
Graphic and interaction design courses supply direct practice, while psychology and computer science can lead in through research or technology. The subject matters less once an employer opens the portfolio. Build case studies that let the reader follow a problem through early sketches, rejected choices and changes made after testing. A set of immaculate final screens without that trail makes it difficult to tell whether you designed the experience or merely decorated it.
Usually 0–2 years’ experience
Early tasks tend to be contained parts of an existing product, completed with a more experienced designer’s support. You might prepare interview notes, map a simple journey and create screens using the company’s design rules. Progress shows in careful decisions and an ability to improve them without treating feedback as a personal attack.
Usually 2–5 years’ experience
A whole feature can now belong to you. You take it from an unclear problem through research, alternative journeys and test versions to work with engineers. Responsibility expands from a set of screens to the whole experience. That includes errors and awkward situations missing from an ideal journey.
Usually 5–8 years’ experience
You’re trusted with larger journeys and problems that have no obvious solution. You’ll bring evidence into product strategy, spot consequences beyond the immediate screen and help less experienced designers develop. Your work is judged not only by its craft but by whether it improves the product and helps the team make better decisions.
Usually 8–12 years’ experience
At this level, several teams may contribute to one journey that no team owns outright. You create coherence across those boundaries, raise quality standards and tackle systemic problems. A lead often coordinates designers in a particular area; a principal usually remains an individual contributor whose judgement travels widely through the organisation.
Usually 12+ years’ experience
Design quality can no longer depend on your personal review of every screen. You shape hiring, critique, research access, design systems and the place of user experience in senior decisions. The challenge is building an organisation that notices poor journeys early, while giving its designers enough autonomy to solve them well.
Builds strong foundations in typography, composition and colour, including how visual choices guide attention. Graduates often arrive with polished craft, then need to develop user research, product thinking and comfort with technical constraints.
Teach research methods, testing and how people move through products and services. This is the broadest match for the whole role because visual, behavioural and technical questions meet in the same projects. Graduates must still learn how commercial priorities and an existing design system narrow the alternatives they can explore.
Help you see how memory, expectation, language and social context shape a user’s actions. That makes research findings less superficial and assumptions about an “average user” easier to challenge. The missing craft is visual and interactive: type, order of information and interface behaviour need repeated practice even when your understanding of people is strong.
Fine art and other studio subjects bring experience making and revising visual work. English and history sharpen interpretation and storytelling. Their graduates may initially think in images or linear narratives, while product design requires interaction choices that change with the user’s action. Research practice and familiarity with technical limits are also weaker areas.
Help you understand how digital products are built and what makes an interaction difficult to create. This knowledge makes work with engineers easier. You will normally need separate practice in visual design and research. What is easy to build should inform the design without controlling it.
Business, architecture and marketing contribute commercial purpose, spatial thinking and audience knowledge. Each can illuminate why a service exists and how people encounter it. The gap is joining those insights to a testable interaction, clear visual hierarchy and evidence from actual users, rather than relying on strategy or taste alone.
Hover a subject to see why it helpsTap a subject to see why it helps
08:45 – 10:00Frame the journey before drawing
Product data, support messages and a test all show people leaving your travel app while changing a return ticket. They do not explain why. At the team check-in, an engineer adds a crucial rule. Some fares can be changed, while others must be refunded and bought again. You resist opening the design tool until that awkward path is understood.
10:00 – 11:15Watch someone use it
You and a researcher speak to two customers who recently tried to change a journey. One cannot tell whether pressing “continue” will charge them immediately; the other keeps returning to the first screen to check the original ticket. You ask them to talk through what they expected without rescuing them. The most useful moments are often the uncomfortable pauses.
11:15 – 12:15Untangle the journey
You map the current steps, customers’ questions and the rules the system must follow. The button problem is really an information problem. People need to compare the old journey, the new journey and the price difference before they feel safe continuing. You agree with the product manager on what the first improvement should achieve.
12:15 – 13:00Sketch before polishing
You draw several rough versions of the flow. One is compact but hides too much; another explains everything and feels like completing a tax return. You show the options to another designer, combine the strongest parts and discard a visually attractive idea that makes the decision harder.
13:00 – 13:45Lunch
Bento box.
13:45 – 15:15Build the prototype
You turn the sketches into a clickable prototype using the company’s components. You write clearer labels, add the state where no alternative trains are available and check what happens on a small phone. An AI design tool produces several plausible layouts quickly; deciding which one actually solves the problem remains your job.
15:15 – 16:00Design critique
You present the work to other designers. They challenge whether the price difference is prominent enough and point out that the confirmation relies on colour to communicate meaning. You explain the research, take notes and change the hierarchy. Critique is useful when everyone is trying to improve the work rather than prove who has the best taste.
16:00 – 17:00Work with engineering
An engineer walks through the test design with you screen by screen. One interaction would require the app to know a fare before the booking system can provide it. You redesign that moment together. You describe the important behaviours and errors, but leave room for the engineer to suggest a simpler way to build it.
17:00 – 18:00Let the awkward cases in
You test the revised journey using only a keyboard. A screen reader reveals that one label makes no sense without its visual setting. As you rewrite it, the engineer loads a real booking made from two tickets with separate change fees. The tidy comparison becomes unreadable on a small screen. You sketch a grouped version and leave both options open for testing. You finish with fewer polished screens but a more honest account of the journey.
+5 hours compared with the average UK job