UI/UX Designer

The resume exists to get the portfolio opened

For most roles the resume is the artefact that decides whether you get an interview. In design it is a doorway. A hiring manager reads it for about twenty seconds, looking for a reason to click the portfolio link, and everything after that is decided by the work.

This changes where the effort goes. A beautifully typeset resume with a weak portfolio fails. A plain resume with three strong case studies does not. If you are dividing your time between them, the split should be heavily toward the work.

Two things do belong on the resume: the portfolio link, visible and working, and enough context about each role that the reader knows what kind of designer you have been.

The title has been unbundled

UI/UX Designer as a single title is increasingly a small-company arrangement. Larger organisations have split the work, and knowing the split matters because the interviews differ.

Product designers own a problem end to end: research, interaction, interface, and often some responsibility for whether the thing worked. UX researchers run studies and do not usually ship interfaces. UI or visual designers own the surface, the design system, and craft. UX writers own the words, which at many companies changes outcomes more than the layout does.

A posting that asks for all of these at once is either a small company where you will genuinely do all of it, which can be excellent early in a career, or a company that has not thought about what it needs. The tell is whether they name a design team you would join.

Decide which you want to be doing in three years, because portfolios built for one read as thin to the others.

Case studies, and the mistake almost everyone makes

The standard portfolio case study runs: here was the brief, here is my process, here are wireframes, here is the final screen. It is a chronology, and chronologies are boring to read and reveal little.

What a hiring manager is trying to learn is how you think when the problem resists. So structure around the decision rather than the timeline.

State the problem and, importantly, who said it was a problem. Show what you found that changed your understanding, because a designer who learned nothing during discovery did not do discovery. Show at least two directions you considered and say why one lost. Then show the outcome, including whatever did not work.

Three case studies at that depth beat eight walkthroughs. If you only have one project with that story in it, present one and say so.

Show the rejected work

The single most useful thing you can add to a portfolio is the option you did not ship, alongside the reason.

Finished screens all look competent. They demonstrate craft, which is table stakes at interview, and they hide the judgment, which is what separates candidates. A designer who shows three approaches and explains why the middle one lost on accessibility grounds and the elegant one lost because engineering estimated six weeks has demonstrated something no polished final screen can.

This also protects you from the most awkward interview moment in design hiring, where someone asks why you did the obvious-looking thing and you have to reconstruct a reason on the spot.

Constraints are more interesting than freedom

Portfolios full of unconstrained concept work, app redesigns nobody asked for, speculative rebrands of large companies, are common and they land poorly with hiring managers.

The reason is that real design work is mostly negotiation with constraints. A legacy system that cannot change. A design system you did not choose. An engineering team with two weeks. A legal requirement that ruins your layout. A stakeholder who wants their feature on the homepage.

Work that shows you navigated those is more valuable than work that shows what you would do with no limits, because the job is the former every day.

If your portfolio is mostly student or speculative work, add one piece with real constraints even if it is small. Redesign something for a local business with an actual budget and an actual owner who disagrees with you.

Accessibility is a hiring signal now

Accessibility used to be a specialism. At a growing number of employers it is a baseline expectation, driven partly by legislation in several markets and partly by organisations that have been sued.

For candidates this is an opportunity, because most portfolios still ignore it entirely. A case study that mentions contrast ratios, keyboard navigation, focus states, or how a component behaves with a screen reader stands out immediately, and it signals a designer who thinks about the whole audience rather than the ideal user on the newest phone.

You do not need to be an expert. Knowing the standard your market works to, being able to name the failures you found in an existing product, and having fixed one of them is enough to be ahead of most applicants.

It is also a good interview question to ask them. How the team handles accessibility tells you a lot about whether design has influence at that company or is decoration applied at the end.

Working with engineers, and how it gets tested

Interviewers ask about the engineering relationship because it is where design roles most often fail in practice.

The answer they are wary of describes handing off finished designs and being frustrated when the build differs. That describes someone who works in a vacuum and treats implementation as somebody else's compromise.

The answer that lands describes involving engineers before the design is finished, because they know what is cheap and what is expensive, and adjusting a design to be half the effort for ninety percent of the value is a design skill rather than a concession.

Concrete evidence helps. Whether you have worked in a shared design system, whether you have written or reviewed component specifications, whether you have sat in refinement sessions. Designers who have done these get treated as collaborators rather than as a service function, and the difference shows up in seniority.

The take-home, and what to do about unpaid work

Most design processes include an exercise, and they range from a two-hour focused task to a multi-day project that looks a lot like free work.

Judge them by scope and specificity. A tight exercise on a generic problem is a reasonable test. A multi-day brief on a real problem the company currently has, with no compensation, is something else, and you are entitled to say so or to decline.

For the reasonable ones, the winning approach is the same as the case study advice. Do not present a polished final screen. Present the problem as you understood it, the assumptions you had to make because the brief was thin, two directions, and what you would test first. Candidates who arrive with one immaculate mockup and no reasoning consistently lose to candidates with rougher work and a clear argument.

Time-box it and say what you spent. "This is four hours of work; here is what I would do with another day" is a professional answer and reads as someone who manages scope.

What separates the top of the band

We do not print salary figures, because a number from New York means nothing in Toronto, Bangalore or Nairobi.

The structural pattern in design compensation is that craft gets you in and influence moves you up. Designers who are excellent at the surface but not involved in what gets built sit lower than designers whose work changes the decision about what to build, at the same title and the same years.

The moves that reprice you: from an agency or studio to in-house product work, from an internal tool to the product a company sells, from a local company to a multinational in the same city, and acquiring the research skills that let you argue from evidence rather than from taste.

Design systems work is worth naming separately. Designers who have built and maintained one are scarce relative to demand, and it is a durable specialism rather than a fashion.

For what the role pays where you live, our salary calculator takes your city and your years of experience.

Do this before your next application

Open your portfolio and look at your strongest case study. If it does not contain an option you rejected and the reason, add that before you send anything else. It is the fastest single improvement available to most designers, and it takes an afternoon.

Our job search builder searches every board you trust at once, and the ATS scanner shows what a filter reads first.