.jpg)
What does a UX designer actually do?
A UX designer's job is to understand why people struggle with a product and translate that into better decisions: flows, structures, interactions. You work at the intersection of user needs and business goals, and the tricky part is keeping both in balance at the same time.
Here's something a lot of beginners miss: UX is not just about making things look clean or "intuitive." It's about constantly asking why something isn't working, then finding evidence to back your answer. Research, testing, iteration. That loop never really stops.
You'll spend time doing user interviews, mapping flows, sketching wireframes, building prototypes, running usability tests. But just as much time (maybe more) goes into explaining your decisions to product managers and developers who have their own constraints and priorities. Communication is genuinely half the job.
Do you need a degree?
No. A design, psychology, HCI, or communication background helps, but it's not a gate. What hiring managers actually look at is your portfolio: evidence that you can identify a problem, work through it, and make reasonable decisions along the way.
If you're switching careers, your previous background is an asset, not a liability. Healthcare, fintech, SaaS, e-commerce. These industries want UX designers who actually understand their domain. Someone coming from nursing or banking brings context that most new designers simply don't have.
How long does it take?
Be skeptical of bootcamps selling "job-ready in 12 weeks." The realistic timeline:
- 3 to 6 months to understand the fundamentals and build your first real project
- 6 to 12 months to have a portfolio that can get you interviews
- 1 to 2 years to land a junior role and start becoming genuinely competent in it
The speed depends on how much time you put in weekly and, critically, how quickly you move from consuming content to actually shipping work.
Skills you need in 2026
Hard skills:
- User research: interviews, surveys, usability testing
- Wireframing and prototyping (low to high fidelity)
- Interaction design basics
- Figma (non-negotiable; it's the industry standard)
- Basic understanding of how front-end development works. You don't need to code, but knowing what's technically feasible makes you a better collaborator.
Soft skills:
- Presenting design decisions with clear rationale
- Listening to feedback without taking it personally
- Aligning with teams that have different goals than you
And one thing that doesn't get said enough: English.
Most UX resources, tools, research, and job opportunities are in English. Nielsen Norman Group, Figma documentation, conference talks, industry reports. All English. If your English is weak, your ceiling as a UX designer is lower than it needs to be. It's worth treating it as a core skill, not an optional extra.
The AI question
AI has changed the workflow. Not eliminated the role, but genuinely changed it.
Designers who use AI tools to speed up research synthesis, generate early concepts, or prototype faster are more productive than those who don't. Tools like NotebookLM for organizing research, Cursor or Lovable for building functional prototypes without deep coding. These are becoming part of the standard toolkit.
But here's what hasn't changed: AI can't do user empathy. It can't sit in a research session and catch the moment when a person says one thing but means another. It can't weigh the tension between what users want and what the business needs. That judgment is still yours.
The designers who struggle with AI are the ones who try to use it to skip thinking. The ones who thrive use it to think faster. If you want to understand what good AI product design actually looks like, check out the UX for AI chatbots guide on SubUX.
Tools to learn
Start with Figma. Everything else can wait until you actually need it.
Once you're comfortable:
- FigJam or Miro for workshops and mapping
- Maze or Lyssna for unmoderated testing
- Notion for documenting research
- Framer or Webflow for prototypes that look like real products
One worth adding now: some basic comfort with vibe coding. Using AI tools to push a prototype live so stakeholders can actually interact with it. It's not required, but it closes the gap between design and reality in a way that impresses people.
Learning: courses vs. self-study
Both work. What doesn't work is learning in circles without ever shipping anything.
If you need structure and accountability, a good course or bootcamp can make sense. Look for programs with real portfolio projects and mentorship, not just video lessons. The Google UX Design Certificate on Coursera is a solid foundation for beginners. Interaction Design Foundation is consistently useful for going deeper on specific topics.
If you're self-directed, use job listings as your curriculum. Read 20 to 30 actual UX designer job postings in the market you want to work in. They'll tell you exactly what skills are expected, what tools to know, and what level of experience different companies are looking for.
The trap for self-learners: spending months on tutorials without building anything reviewable. At some point you have to put work out there.
Building your portfolio
Three case studies done properly beat ten shallow ones every time.
Each case study needs to answer: What was the problem? What did you do and why? What did you learn from the result? The "why" part is what most portfolios miss, and it's the part that actually tells a hiring manager whether you can think.
Keep your sketches, early iterations, and research notes. The messy middle of a design process is more interesting to reviewers than the polished final screen.
One thing I've learned from doing this a long time: the designers who progress fastest are the ones who constantly draw conclusions from their work. Not just "this test failed" but "this test failed because we assumed X, and the research showed Y, so next time I'd do Z differently." That reflection habit compounds over time.
A note on fake redesigns: Recreating Amazon or Netflix is fine as practice. But try to have at least one project where you talked to real users, even just five people. That changes how you think about design in a way that tutorial projects don't.
The fundamentals that never change
As you build your skills, it helps to have solid references to come back to. Things like typography hierarchy, content hierarchy and scanning patterns, and understanding form design are not exciting topics, but they're what separates designers who produce work that actually works from those who produce work that just looks right.
Accessibility is part of this too. Knowing things like color contrast requirements and focus states isn't optional if you're working on real products. Most junior designers skip this, which is a mistake.
The job market right now
Honest picture: it's more competitive than it was two or three years ago. AI tooling has increased application volume across the board, and the average time-to-hire for UX roles is running 40 to 60 days. Remote roles are fewer than in the 2021 to 2022 peak, and your location matters more again.
What actually helps:
Pick a niche
Healthcare UX, fintech, AI product design, accessibility. A focus makes your portfolio readable and your value proposition clear. Generalists are harder to hire for specific roles.
Show your process, not just your output
Because AI tools make polished mockups easy, everyone's work looks good. The differentiator is your reasoning.
Build connections before you need them
Applying cold to 100 job listings rarely works. Being known in design communities (Slack groups, LinkedIn, local meetups) converts much better. Start before you're actively job hunting.
What's genuinely different in 2026
AI fluency is expected
Not deep technical knowledge, but comfort using AI tools in your workflow. Expect interview questions about it.
The portfolio bar has risen
Polished visuals are table stakes. What stands out is evidence of research, iteration, and clear thinking.
Systems thinking matters more
Products are more complex, and UX designers who understand design systems, component logic, and how their decisions affect the whole product (not just a single screen) are more valuable than those who design in isolation.
User empathy is still the job
The fundamentals don't change. You need to genuinely care about the people who will use what you're designing, their actual frustrations, not the ones you imagine for them. That's what separates designers who produce good work from designers who produce correct-looking work.
Where to start today
- Read about UX fundamentals: what the design process looks like, Nielsen's heuristics, basic research methods
- Get into Figma. There are free courses and tutorials; start building anything
- Pick a real (or realistic) problem and work through it from research to prototype
- Document the process as you go. That documentation becomes your first case study
- Build in public: write about what you're learning, share work-in-progress
The path into UX is still very much open. It just rewards people who do the work, the research, the reflection, the willingness to be wrong and adjust, over those who just learn the tools.
Want to go deeper on specific topics? Check out the SubUX guides library: practical, research-backed UX references for designers at every level.
