SaaS Designers: What They Do, Skills, and How to Become One
What a SaaS designer does, the skills the role needs, how it differs from other product design jobs, and how to become one — grounded in real product examples.
SaaS designers are the people who turn dense, multi-user business software into products people can actually use. It is a specialised corner of product design: the work is less about pixel-perfect marketing pages and more about dashboards, data tables, settings, onboarding, and the flows that get a whole team to value. If you have ever wondered what a SaaS designer does, what skills the role demands, how it differs from a general UX or web designer, or how to become one, this guide walks through it — grounded in how real SaaS products are designed in production.
Whether you are hiring a SaaS designer, moving into the role, or trying to understand where you fit on a product team, the sections below cover the role, its skills, its day-to-day, the different flavours of SaaS design jobs, and a realistic path into the work.
What is a SaaS designer?
A SaaS designer is a product designer who specialises in software-as-a-service products — recurring, multi-user, often data-heavy tools that teams use to do their work. The role spans research, information architecture, user flows, interaction design, and interface design, all aimed at one outcome: helping users reach value quickly and keep reaching it across thousands of sessions. Where a marketing or web designer is judged on first impressions, a SaaS designer is judged on whether the product still feels obvious on the user’s hundredth visit.
SaaS designer vs UX designer vs product designer
The titles overlap, and at many companies they describe the same person. The distinction is one of focus. A UX designer concentrates on research, flows, and usability; a UI designer on the visual interface; a product designer typically owns both plus the connection to product strategy. A SaaS designer is a product designer whose specialism is SaaS — fluent in the patterns business software lives in (dashboards, tables, permissions, onboarding) and in designing for a recurring, multi-seat relationship rather than a one-time visit.
What does a SaaS designer do?
Day to day, a SaaS designer moves between research, structure, and craft. The mix varies by company and seniority, but the core work is consistent.
Research and understand the users
SaaS products serve multiple roles — admins, daily users, viewers, billing owners. A SaaS designer figures out who uses the product, the jobs each role is trying to do, and where they get stuck today, through interviews, support data, and product analytics.
Design flows and information architecture
Before drawing screens, a SaaS designer structures the product and its key journeys: sign-up, onboarding, the core recurring task, administration. Strong information architecture is what lets a dense product grow without becoming a maze.
Design data-dense interfaces
Dashboards, tables, forms, settings, and empty states are the bread and butter of SaaS design. The craft is taming complexity — progressive disclosure, scannable layouts, sane defaults — so the product feels calm even when it manages a lot.
Prototype, test, and iterate
A SaaS designer builds flows at low and high fidelity, tests them with real users, and refines based on where people hesitate. Because the product keeps growing, the work is continuous rather than a one-off project.
Maintain a design system
SaaS products are large, so consistency is survival. SaaS designers build and tend design systems — shared components, patterns, and rules — that keep a sprawling product coherent and let teams ship faster.
Collaborate with product and engineering
Design does not happen in isolation. A SaaS designer works with product managers on priorities and with engineers on what is feasible, often owning the connection between user needs and what actually ships.
Skills a SaaS designer needs
The role rewards a specific blend of craft, systems thinking, and product sense. The skills that matter most include:
- Information architecture: structuring dense, multi-feature products so users can find and understand everything.
- Interaction and UI design: designing dashboards, tables, forms, and settings that stay clear under real data loads.
- User research: interviewing users, reading analytics, and turning messy signals into clear design decisions.
- Design systems: building and maintaining reusable components and patterns that keep large products consistent.
- Prototyping: bringing flows to life in tools like Figma to test ideas before engineering builds them.
- Product and business sense: understanding activation, retention, and expansion so design choices map to outcomes that matter.
- Collaboration and communication: working fluently with PMs and engineers, and explaining the reasoning behind design decisions.
Types of SaaS design roles
"SaaS designer" is an umbrella. On a real team the work is often split across more specific roles:
- Product designer (SaaS): owns end-to-end design of features and flows, from research to shipped interface.
- UX designer: focuses on research, flows, and usability of the SaaS product.
- UI / visual designer: focuses on the interface, design system, and visual craft.
- UX researcher: specialises in understanding users and validating designs with evidence.
- Design systems designer: builds and maintains the shared component library the whole product is built on.
- Growth designer: focuses on onboarding, activation, and conversion surfaces that drive adoption.
How to become a SaaS designer
There is no single path, but a realistic route into SaaS design looks like this:
- Learn the fundamentals: information architecture, interaction design, visual design, and a working knowledge of how SaaS products are built.
- Get fluent in the tools: Figma for design and prototyping, plus familiarity with design systems and handoff to engineering.
- Study real products relentlessly: take apart how leading SaaS tools handle onboarding, dashboards, tables, and settings — pattern recognition is the core skill.
- Build SaaS-specific work: design a realistic dashboard, a settings flow, or an onboarding journey for your portfolio, not just pretty landing pages.
- Show your thinking: a SaaS design portfolio is judged on reasoning — the problem, the constraints, the flow decisions — more than on polished screens alone.
- Get reps: internships, junior roles, freelance projects, or redesigns of existing tools all build the judgment the role depends on.
Where SaaS designers find inspiration
The fastest way to grow as a SaaS designer is to study how leading products solve real problems in production — not in mockups, but in shipped interfaces. Seeing how many products handle onboarding, empty states, dashboards, data tables, and settings side by side is how patterns become instinct. That is exactly why curated libraries of real SaaS screens exist: they turn scattered observation into a reference you can study deliberately.
Frequently asked questions
What is a SaaS designer?
A SaaS designer is a product designer who specialises in software-as-a-service products — recurring, multi-user, often data-heavy tools. The role spans research, information architecture, flows, and interface design, all aimed at helping users reach value quickly and keep reaching it across many sessions.
What does a SaaS designer do?
A SaaS designer researches users, designs flows and information architecture, crafts data-dense interfaces like dashboards and settings, prototypes and tests with real users, maintains a design system, and collaborates with product and engineering to ship features that help teams get value from the product.
What skills does a SaaS designer need?
Core skills include information architecture, interaction and UI design for dense interfaces, user research, design systems, prototyping in tools like Figma, product and business sense around activation and retention, and strong collaboration with PMs and engineers.
How do you become a SaaS designer?
Learn product design fundamentals, get fluent in Figma and design systems, study how real SaaS products solve common patterns, and build SaaS-specific portfolio work — a dashboard, an onboarding flow, a settings redesign — that shows your reasoning. Then get reps through junior roles, freelance, or internships.
What is the difference between a SaaS designer and a product designer?
A product designer designs digital products broadly; a SaaS designer is a product designer whose specialism is SaaS. They are fluent in the patterns business software lives in — dashboards, tables, permissions, onboarding — and in designing for a recurring, multi-user relationship rather than a one-time visit.
Study real SaaS design in the SaaSUI library
Every skill above sharpens fastest against real products. Browse hand-picked screens — onboarding, dashboards, data tables, settings, and empty states — from real SaaS applications in the SaaSUI.Design library to build the pattern recognition that separates good SaaS designers from great ones.

Interested in sponsoring SaaSUI.Design? Learn about sponsorship options →











