TL;DR
- Learn exactly three tools: Figma for wireframing and prototyping, Maze or UXtweak for usability testing, and FigJam or Miro for ideation. This is the minimum necessary toolkit for entry-level UX roles.
- Figma appears on the majority of entry-level UX job descriptions and is non-negotiable in 2026. Start here rather than Sketch or Adobe XD.
- Run one usability test with five participants using Maze or UXtweak. One documented test in your case study signals user-thinking methodology to hiring managers.
- Show your ideation process in FigJam or Miro before you wireframe. A 30-minute affinity map or user journey diagram proves you know how design decisions get made in teams.
- The vehicle that makes all three visible is a single portfolio case study. One strong case study showing design, research, and collaboration beats five polished Figma mockups with no research.
What UX designers actually use on the job
According to BrainStation's guide to what tools UX designers use, 88% of UX designers begin with pen and paper, and 72% also incorporate digital tools. Those two numbers together tell you something useful: the workflow isn't "pick a tool and live in it." It's a sequence - sketch first, then move into software at specific stages.
That sequence maps to three distinct categories. Not ten. Not forty. Three.
The design category covers wireframing and prototyping - turning rough ideas into something a test participant can actually click through. The research category covers usability testing - structured sessions where you watch real people interact with your prototype and capture what breaks. The collaboration category covers ideation - the whiteboard sessions, affinity mapping, and user journey work that happens before a single frame is drawn.
Understanding these as three separate jobs is what most career changers miss. They assume "UX tools" means design software, full stop. Hiring managers screen for all three categories because the job requires all three.
Design tools (the wireframing and prototyping layer)
Design tools are where you build the thing - wireframes at low fidelity, then high-fidelity mockups, then clickable prototypes a test participant can navigate. If you don't have design-tool work in your portfolio, a hiring manager can't assess whether you can execute. Figma is the dominant player in 2026, and it's where you start - not Sketch, not Adobe XD.
Research tools (the user-testing layer)
Research tools run structured usability tests - task flows, click maps, and think-aloud recordings that tell you where your design fails. Maze and UXtweak are the two most accessible to career changers, both with free tiers that support early-stage portfolio work. This category is distinct from design tools, not an add-on. You use research tools after your prototype exists, with real participants, to gather evidence that your design actually works.
Collaboration tools (the ideation layer)
FigJam and Miro are where teams make design decisions before wireframing starts - user journey mapping, affinity diagrams, stakeholder workshops, and concept voting sessions. These aren't design software. They're digital whiteboards that create an artifact showing your process, not just your output. That process artifact is what a hiring manager reads as evidence of collaborative design thinking.
Why the tools-first approach gets career changers stuck
I've watched hundreds of career transitions through MentorCruise. The successful ones follow a pattern: they start with internal clarity (what do I actually want from a UX role?), move to skill mapping (which three tools and which case study will demonstrate I can do this?), and only then go external - applications, networking, interviews. Most career changers start with step three and wonder why they're stuck.
The tools-first failure mode looks like this: three months learning Figma features, two months on a Maze tutorial, six weeks on a Miro course. Tool knowledge accumulates. No portfolio case study ships. And a Figma certificate from a course platform tells a hiring manager nothing about whether you can solve a user problem.
As UX Playbook's senior designer hiring guide puts it: "Hiring managers are looking for business problem solvers who happen to use design as their tool." The tools are the medium, not the message. A portfolio case study is the artifact that demonstrates you can use design to solve a problem - and it's the only artifact that gets you to a first interview.
We see this anxiety in applications every week. One designer wrote to us: "I was recently laid off and do not feel particularly confident about my UX research portfolio." That's not a tool-knowledge problem. It's a portfolio evidence problem. The two are related but not identical. Learning Maze doesn't produce a case study. Running one usability test does.
The reframe: stop asking "which tools should I learn?" and start asking "what do I need to build, and which three tools will produce that artifact?"
The three-slot toolkit
Three slots, each with a distinct job. That's the whole framework. Slot 1 is design (Figma) - where you build the prototype. Slot 2 is research (Maze or UXtweak) - where you test whether it works. Slot 3 is collaboration (FigJam or Miro) - where you show the process that led to the prototype. A portfolio case study without all three slots has a gap that every hiring manager can see.
Before you choose within each slot, the comparison below maps what you're committing to:
| Slot | Role | Primary pick | Free/budget alternative | Why this slot matters for hiring |
|---|---|---|---|---|
| Design | Wireframing and prototyping | Figma | Figma free tier (same tool, limited projects) | Appears on the majority of entry-level UX job descriptions |
| Research | Usability testing | Maze | UXtweak (free tier available) | Shows you understand user thinking, not just mockup execution |
| Collaboration | Ideation and workshop facilitation | FigJam | Miro (free tier, 3 boards) | Shows you know how design decisions get made in teams |
You can demonstrate all three slots without spending money before your first role.
Slot 1 - Figma (the design layer)
Figma is non-negotiable for career changers in 2026. Not fashionable opinion - a hiring-signal fact. Figma appears on the majority of entry-level UX job descriptions across sources including Medium's Design Bootcamp, BrainStation's career guides, and recruiting platforms covering the UX space. You can learn Figma from scratch on the free tier and ship a complete case study prototype without paying anything.
Sketch is not the answer. It's macOS-only, has no free tier, and new-user adoption is declining as Figma has become the standard. Adobe XD entered maintenance mode in 2023, per Designshack's comparison of Sketch, Figma, and Adobe XD - no new features, no active development roadmap. Learning either tool before your first role is optimizing for a shrinking slice of job descriptions.
The honest Figma limitation: the free tier caps you at 3 draft files. For a first case study - one prototype file and two documentation files - that's enough. Paid plans start at $15/month per editor as of 2026. Don't pay before you've landed your first role.
Slot 2 - Maze or UXtweak (the research layer)
Maze runs unmoderated usability sessions where participants attempt a task flow in your Figma prototype while the software captures click paths, task completion rates, and time-on-task data. BrainStation's data shows teams typically combine Maze or Lookback for research alongside Figma as their core design platform. UXtweak's free tier is a legitimate alternative, particularly if you need to run more sessions before committing to a paid plan.
Why one documented test matters to a hiring manager: it proves you can close the loop between "I designed something" and "I know whether it works." A Figma-only portfolio shows design execution. A portfolio with one Maze test - five participants, three documented findings - shows user-thinking methodology. Those are different signals to a hiring team.
The honest caveat: setting up a Maze test properly and recruiting five participants takes time. That's real. But "five colleagues or friends who haven't seen your design" is a legitimate first test. You don't need a research panel to produce something readable.
Slot 3 - FigJam or Miro (the collaboration layer)
FigJam is the natural pairing with Figma - same ecosystem, automatic linking between files, and hiring managers who already use Figma will recognize a FigJam artifact without explanation. Miro is the more established stand-alone option, with wider adoption outside pure design teams - product managers, UX researchers, and business analysts all use it, which means your ideation artifact reads as cross-functional.
The hiring signal: showing an affinity map or user journey diagram in your case study proves you know design decisions are made collaboratively. A Figma prototype alone implies you built something. An affinity map plus a prototype implies you ran a process first. Miro's free tier supports 3 boards; FigJam's free tier is sufficient for one case study. Either works for your first portfolio project.
What to build with these three tools
The case study is the output that makes all three tool slots count. Figma without a research layer is design execution only. Maze results without a prototype are evidence without a product. FigJam artifacts without both are process theater. The portfolio case study is what stitches all three into a hiring signal - one artifact showing design, research, and collaboration working together on a real user problem.
Here's the build order:
-
Pick a real user problem you can observe. Don't invent scenarios. Find something in your own life or network - a friction point someone experiences regularly. "My colleague can't figure out how to use our internal expenses form" is a better starting problem than "I'll design a fitness app" because you can observe the real failure.
-
Use Figma to wireframe your solution. Build 10-15 screens at low fidelity first, then take one core flow to a clickable prototype. Clickable means a test participant can navigate from a starting screen to a completion screen without guidance. One prototype flow is enough.
-
Run a usability test with five participants using Maze or UXtweak. Five participants is enough to surface the most common failure patterns in a design - this is a widely used professional standard, not a shortcut. Recruit from colleagues, friends, or community members who haven't seen your design. Each session runs 10-20 minutes. You're capturing where participants get stuck, where they click when lost, and what they say out loud. Document your three most important findings.
-
Document your ideation process in FigJam or Miro before you wireframe. Even a 30-minute session produces something hireable: an affinity map from five brief user conversations, a current-state user journey showing pain points, or a concept sketch session with rough directions. Any of these shows you ran a design process, not just a design execution.
One person in our applications put it directly: "its not possible without any mentor, so i want someone to help me make projects to make a stronger portfolio and guide me to land a job." That instinct is right. The case study is the thing - the tools are how you make it. When you're ready to build your UX portfolio, this four-step sequence is the build order that makes all three tools legible to a hiring manager.
What tools you don't need to learn yet
Every tool on this list is used by working UX professionals. I'm not saying they're bad tools. I'm saying none of them help you ship the case study that gets you hired - which is the only output that matters right now.
- Sketch - macOS-only, no free tier, declining new-user adoption. Not the starting point for a career changer without Apple hardware and income.
- Adobe XD - entered maintenance mode in 2023, per Designshack's comparison guide. No new features in active development. Learning a tool with no development roadmap is a poor return on your time.
- InVision - largely replaced by Figma-native prototyping. The reason InVision existed (shared clickable prototypes) is now a built-in Figma feature. Learning it separately is redundant.
- Principle and Framer - advanced prototyping tools for micro-interactions and production-level animations. Senior-level workflow additions. Rarely appear in entry-level job descriptions.
- Axure RP - enterprise documentation tool for heavily annotated specs. Used at large organizations with formal spec processes. Not a beginner portfolio tool.
The filter: if a tool doesn't help you ship the case study, it's not a first-job priority. Add it when a specific role or team asks for it.
Tools, mentors, and next steps
I mentioned the transition formula earlier - most career changers go straight to the external step (tools, certifications, applications) before doing the internal work (what UX role am I targeting?) and the skill mapping (which three tools and which case study will demonstrate I can do this?). The sequence matters because "which tools should I learn?" doesn't have one universal right answer. It has a right answer for your target role and your specific case study.
The career changers who move fastest are the ones who run that sequence with someone who has been on the other side of UX hiring - a working UX designer or researcher who has screened portfolios and knows what gets a case study into the yes pile.
At MentorCruise, we have 6,700+ mentors across design disciplines, and we accept fewer than 5% of mentor applicants. A UX mentor who has hired for design roles can work through the toolkit-selection question with you, review your Maze test results to confirm they're framed the way a hiring manager reads them, and tell you whether your Figma prototype tells a user story or just shows screens.
If you're ready to build your UX portfolio with that kind of accountability, find a UX mentor who has screened design portfolios and knows what entry-level hiring managers are actually looking for.
FAQs
Do I really need all three tools, or just Figma?
Yes, you need all three. A Figma-only portfolio shows design execution but not user research methodology or collaborative process. Each slot signals a different competency: Figma shows you can build a prototype, Maze or UXtweak shows you can close the loop between design and user evidence, and FigJam or Miro shows you understand that design decisions are made with other people. A portfolio missing any one slot leaves a competency question unanswered for every hiring manager who reads it.
Figma's free tier has limitations - should I pay for a subscription before I get my first UX job?
No. The free tier supports 3 draft files - enough for a first case study with one prototype flow and supporting documentation. You don't need a paid plan until you have client work or team collaboration that exceeds the free limit. Figma paid plans start at $15/month per editor as of 2026. Don't pay before you land your first role. The free tier covers everything you need to build a hireable first case study.
What if the company I'm applying to uses Sketch, Adobe XD, or a different tool?
Once you understand UX thinking, switching tools takes days. The mental model transfers: wireframing logic, prototype architecture, and design system thinking are consistent across Figma, Sketch, and similar platforms. Figma and Sketch share most of the same mental model - the core wireframing and prototyping logic transfers. If a job posting specifies a tool you don't know, a week of deliberate practice in that tool covers the gap. Don't optimize your learning for a tool you haven't been asked about yet.
How long does it take to learn Figma well enough to include it in a portfolio?
2-4 weeks of deliberate practice. Two weeks gets you to wireframe level - basic frames, navigation flows, component reuse. Four weeks gets you to a presentable prototype with a consistent visual system and a completed flow a test participant can navigate without guidance. The key is building your actual case study prototype rather than following tutorials for their own sake. Tutorials teach features; the prototype is where the skills compound into something hireable.
