UI vs UX design: what each one actually means for UK beginners
Updated on August 03, 20266 minutes read
Imagine you open a food delivery app in Manchester on a wet Tuesday, tap three times, and your curry is on its way without a single moment of confusion. The reason it felt that easy is that two different jobs quietly did their work: UX design decided what should happen and in what order, and UI design decided how every button, colour and label looked while it happened. People lump them together as "UX UI design", but they answer different questions, and understanding the split is the first thing that makes the field click.
What is UI and UX in design?
UX stands for user experience. It's the thinking behind how a product works end to end — the flow, the logic, the moments where someone might get stuck. A UX designer maps out the journey, sketches rough wireframes, and tests them with real people before anyone worries about how pretty it is.
UI stands for user interface. It's everything a person actually sees and touches: the typography, the spacing, the colour of a "Pay now" button, the little animation when a form submits. A UI designer turns the skeleton the UX work produced into something that looks polished and behaves consistently.
Here's a concrete example. Say a small letting agency in Leeds wants an online booking tool for property viewings. The UX designer works out that a tenant needs to pick a property, choose a time slot, and confirm — and that showing available slots before asking for a phone number reduces drop-off. The UI designer then decides the calendar is a clean grid, the selected slot turns deep purple, and the confirm button sits where a thumb naturally rests. Same screen, two kinds of thinking.
Most job adverts in the UK ask for both, which is why the combined "UX/UI designer" title is so common. On smaller teams you'll do the lot. At larger companies — think a bank in London or a retailer in Edinburgh — the roles sometimes split into dedicated UX researchers and UI designers.
A quick side-by-side
| UX design | UI design | |
|---|---|---|
| Core question | Does this work and make sense? | Does this look right and feel consistent? |
| Typical output | User flows, wireframes, research findings | Visual mockups, style guides, prototypes |
| Main tools | Figma, FigJam, Maze, user interviews | Figma, colour and type systems, component libraries |
| Mindset | Problem-solving, empathy, testing | Craft, detail, visual consistency |
| Good first sign | You ask "why is this confusing?" | You notice misaligned buttons everywhere |
Is UI/UX design an IT job?
Sort of, and it's a fair question to ask. UX/UI design sits in the tech world and you'll work alongside developers, product managers and data people every day. But it isn't a traditional IT support or systems job. You're not fixing servers or managing networks. You're closer to product and design, using research and visual craft to shape digital products.
That matters for how you learn it. You don't need a computer science degree, and you don't need to be a strong coder. A common worry among career changers is whether the role demands programming — the honest answer is covered in our piece on whether UX/UI design requires coding. Short version: a basic grasp of how the web is built helps you talk to developers and design things that are actually buildable, but you won't spend your days writing code.
Is UI/UX design well paid?
Pay is one of the reasons the field pulls in so many career changers. In the UK, a junior UX/UI designer typically starts on a respectable graduate-level salary, and it climbs steadily with a strong portfolio and a couple of years of shipped work. Mid-level and senior designers in cities like London, Bristol and Manchester earn comfortably above the national median, and specialists — UX researchers, design systems leads, product designers — sit higher still.
A few things push earnings up faster than others. A portfolio that shows real problem-solving beats a folder of pretty screens every time. Fluency in Figma is close to essential now, since most UK teams have standardised on it. And a track record of working with developers and product managers signals you can operate on a real team, not just in a design bubble.
One honest caveat. "Well paid" assumes you can prove you can do the work. The salary follows the skills and the evidence, not the job title, so how you learn and what you build during that time matters a great deal.
Can I learn UX in 3 months?
Yes — with a realistic definition of "learn". Three months of focused, structured study is enough to grasp the core methods, get properly comfortable in Figma, and produce two or three portfolio projects that show you understand the process. That's the level a UK employer expects from a junior candidate: not a decade of experience, but clear evidence you can research a problem, sketch solutions, test them and hand off a tidy interface.
What you can't do in three months is fake experience. The people who land roles fastest treat those months as a full-time apprenticeship in the craft. They redesign real products, get feedback, iterate, and write up their thinking so a hiring manager can follow the decisions. Structure helps enormously here, which is why a guided programme tends to beat piecing together free tutorials on your own.
If you want the full breakdown of what fits into a twelve-week plan, our UX/UI design bootcamp is built around exactly that timeline, with mentor feedback on the projects that go into your portfolio. If your schedule is unpredictable, the self-paced UX/UI route covers the same ground while you keep working.
A rough three-month shape
In the first stretch you learn the UX fundamentals — research, user flows, wireframing — and start speaking the language of the field. The middle stretch is where UI craft comes in: type, colour, layout, and building components in Figma. The final stretch is portfolio time, turning your best work into case studies that explain why you made each choice. That last part is what actually gets interviews.
Where UK beginners tend to trip up
Two mistakes crop up again and again. The first is jumping straight to visuals and skipping the messy research part — the result is a beautiful interface that solves the wrong problem. The second is building a portfolio of unbriefed "concept" redesigns with no reasoning attached. Hiring managers in the UK want to see how you think, not just that you own Figma.
Choosing a starting point is easier once you know which of these appeals to you more. If you love figuring out why something's confusing, UX will pull you in. If you can't stop noticing wonky spacing, UI is your natural home. Either way, the combined skill set is what most UK job adverts actually want.
UI and UX are two halves of the same job: one makes a product work, the other makes it look and feel right, and beginners are expected to handle both. If you're weighing up a switch, the clearest next step is to compare the guided and self-paced options and their timelines on the Code Labs Academy course overview and pick the one that fits your life.
