Auto Apply to hundreds of jobs in a few hours

Español

日本語

Product Designer skills: what to learn first, and what can wait

Tools change every few years, but the way a good designer frames a problem doesn't. Get fluent in Figma and flows first, because that's what a recruiter can check in a minute. Then build the research, systems and product judgement that make a team trust you with the messy features.

688 open jobs

Step one

Gets you the interview

Figma, properlyAuto layout, components with variants, shared styles and a file another designer can open without a tour. Hiring managers open your files, and a mess of detached frames tells them how your handoffs will go.

User flows and edge statesDraw the empty state, the error, the loading screen and the second-time visit, not just the happy path. Most junior portfolios skip these, so showing them is an easy way to look like you've shipped before.

Clickable prototypesA prototype in Figma or ProtoPie that someone can tap through on a phone makes a case study feel real. It's also the thing you'll test with users, so learn to build one fast and rough.

Visual fundamentalsType scale, spacing, grids and contrast. You don't need a signature style, but screens that look off will get you screened out before anyone reads your reasoning.

Step two

Gets you the offer

Running a usability testWrite a short script, recruit a handful of people, run the session over Zoom or in Maze, and turn what you saw into a ranked list of fixes. Being able to describe one test you ran, and what it changed, carries a whole interview loop.

Working inside a design systemTeams want someone who reaches for the existing button before drawing a new one, and who knows when a new pattern is worth proposing. Study a public system like Material Design or Polaris to learn the vocabulary: tokens, variants, documentation.

Accessibility standardsKnow WCAG well enough to check contrast, focus order, tap target size and screen reader labels on your own work. Engineers notice when a designer catches these before QA does.

Engineering handoffRedlines are mostly gone, but specs aren't. Annotate interactions, name components the way the codebase does, and use Dev Mode so a front-end engineer can build your screen without a follow-up meeting.

Step three

Gets you promoted

Reading product dataPull a funnel in Amplitude or Mixpanel, read an A/B test result, and say what you'd change because of it. Senior designers argue with evidence, and this is where the evidence lives.

Shaping the problem before the solutionSenior designers get pulled into roadmap talks before a ticket exists. Writing a one-page problem brief with the PM, including what you won't solve, is how you move from producing screens to deciding which ones get made.

Leading critiqueRunning a design review where people give useful feedback, and pushing a decision to closure, is a big part of the staff and lead roles. Practise by offering to run your team's weekly crit.

Owning a system component end to endPropose a new pattern, get it through review, document it and see it adopted across teams. That kind of work reaches every screen, which is what promotion committees want to see.

Certificates worth your time

Certificate	Best for	Effort	Worth it?
NN/g UX Certification	Working designers who want structured training in research and interaction design	a handful of full-day courses plus an exam after each	Well respected and the courses are good, but it's costly. Worth it if your employer pays; a strong case study still counts for more.
Google UX Design Professional Certificate	Career changers who need structure and a first set of projects	several months of evenings at your own pace	Fine for learning the basics, weak as a hiring signal on its own. Replace its template projects with real work before you apply.
IAAP Certified Professional in Accessibility Core Competencies (CPACC)	Designers on teams that build for government, healthcare or education	a few weekends of study before the exam	A real edge where accessibility is a contract requirement. Elsewhere, knowing WCAG in practice matters more than the letters.

Course content, prices and exam rules change, so check the provider's own site before you sign up.

Put it on your resume like this

Weak

Worked on the design system and made components in Figma.

Strong

Built 40 Figma components with variants and tokens for a shared design system adopted by 6 product teams, cutting new-screen design time from 3 days to 1.

Questions people ask

Should I learn Figma or Sketch?

Figma. It's what you'll see named in most product design postings, and its multiplayer files are how teams actually work. If a job uses Sketch, the concepts carry over in an afternoon.

How much research skill do I need if my company has UX researchers?

Enough to run a quick usability test and read a research report critically. Researchers handle the big studies, but you'll still test your own prototypes between their projects.

Do I need to learn to code?

You don't need to ship code. Knowing how HTML, CSS and a component library fit together makes your specs match what engineers can build, and it helps you spot a hard-to-build design early.

What skill do new product designers most often lack?

Scoping. They design the ideal version and have nothing ready when the sprint gets cut. Practise drawing a small first release next to the full idea, so you're the one proposing the trade-off.

Got step one? Start applying. HeroApply matches you to roles that fit.

Start your trial