Who Is a UI/UX Designer: Responsibilities and How to Start
Basics3 minInnovialabs editorial team
In short
A UI/UX designer shapes how a product works for the user (UX) and how it looks (UI), from user flows and prototypes to ready-to-build mockups. To start, you need interface design fundamentals, solid Figma skills and a portfolio that explains 2–3 problems rather than a gallery of pretty screens.
The short answer
UX (user experience) is about how easy a product is to use: is the path to the goal clear, are there unnecessary steps, where do people get lost. UI (user interface) is the visual layer: grids, typography, color, components, button states.
A UI/UX designer covers both: they understand the user's and the business's problem, design a solution and turn it into mockups that developers can build. Large companies sometimes split the roles, but most job postings expect both.
What the daily work looks like
- Understanding the task: what the business wants, who the users are, what scenarios they have.
- Running or using research: interviews, competitor analysis, analytics data, support feedback.
- Designing structure: user flows, screen maps, wireframes.
- Prototyping and testing ideas with users or within the team.
- Producing final mockups with every state covered: loading, error, empty screen, long text.
- Maintaining the design system: components, styles and rules for using them.
- Supporting development: answering questions, reviewing the implementation, adjusting designs.
Working with developers and PMs
Designers rarely work alone. A typical set of relationships:
| With whom | What you align on |
|---|---|
| Product manager | goals, priorities, metrics, scope |
| Developers | feasibility, timelines, component behavior, responsiveness |
| QA | expected interface behavior, edge cases |
| Analysts | user behavior data, experiment results |
A good designer talks to developers before the final mockups, not after. That is the moment to learn that a solution would take disproportionate effort and to find a simpler option. Handoff files should answer questions in advance: spacing, states, behavior on small screens.
What a junior designer needs to know
Fundamentals:
- composition, grids, typography, color and contrast;
- UX basics: usability heuristics, user flows, information architecture;
- common interface patterns for web and mobile platforms;
- accessibility basics: contrast, target sizes, clear labels.
Tools:
- Figma, the industry standard: auto layout, components, variants, prototyping;
- a basic understanding of HTML and CSS, not to write markup but to speak the same language as developers.
Working habits:
- explaining decisions through the user's problem rather than "it looks nicer";
- accepting critique and iteration calmly;
- asking questions until the task is clear.
How to build a first portfolio
The most common beginner mistake is a portfolio of beautiful screens without context. Hiring managers want to see how you think.
- Pick 2–3 problems: a redesign of a real service, a study project or a task for a business you know.
- For each, describe the problem, users, constraints, options considered, the result and why you chose it.
- Show intermediate steps: flows, wireframes, prototype.
- Include the mobile version and interface states, not only the "perfect" screen.
- Trim the text to what matters: a case study should be readable in a few minutes.
A concept redesign of a well-known app is fine, but label it honestly as a concept and explain which problem you were solving.