Questions to Ask a Designer
Questions for a conversation with a working designer, whether over coffee, in a portfolio review, or on a mentoring call. They cover how they got in, how decisions get made on real projects, how the work is judged, and what the career looks like from the inside. A run in the middle is for anyone working out what questions to ask a UX designer or a UI designer in particular: research, testing, and the states of a screen nobody draws.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
How did you get into design, and what was your first paid work?
Why ask it
Routes in vary widely: art school, a self-taught switch, or drifting over from an adjacent role. The first paid job tells you what portfolio was enough at the time, which is the practical part for anyone trying to enter now.
What are you working on at the moment, and what stage is it at?
Why ask it
Grounds the conversation in something live rather than a finished case study. Designers talk more freely about a project mid-flight, including the parts that are not working yet.
Walk me through how a project starts for you. What do you do in the first week?
Why ask it
The answer separates designers who begin with the problem from those who begin in the tool. Look for research, constraints and existing patterns before anything visual appears.
How do you decide when something is finished?
Why ask it
Most designers have a private stopping rule: a deadline, a review, or the point where changes stop improving anything. It is one of the harder skills to learn and rarely discussed openly.
How do you know whether a design worked after it shipped?
Why ask it
Concrete answers name a metric, a support ticket volume, or a follow-up study. Answers about how the work was received usually mean nobody measures outcomes, which is common and worth knowing.
How much of your work is reusing existing patterns rather than making something new?
Why ask it
In a mature product most of the decisions are already fixed by a design system, and the skill becomes knowing when breaking it is worth the argument. Ask what they last added to the shared library and who had to sign it off.
How do you hand work over to the people who build it?
Why ask it
Ask what the handover physically consists of: a file, a written spec, a shared call, or a week sitting next to an engineer. Whatever gets lost between the design and the shipped screen is decided at this step.
Where does accessibility come into your process, and who checks it?
Why ask it
A useful answer names a point in the timeline and a person. If nobody tests contrast, focus order or a screen reader before release, you have learned what the team's stated commitments amount to.
What do you do when the brief is vague and nobody will decide?
Why ask it
Designers spend more time chasing decisions than drawing. Listen for the specific tactic: writing the decision down and circulating it, presenting two options with a recommendation, or naming a date after which they choose themselves.
How do you present work to someone senior who already has a solution in mind?
Why ask it
An executive opinion arrives with the brief more often than designers admit. Ask what they showed and in what order, because sequencing is usually what carries these rooms rather than the strength of the argument.
What was the last thing you were asked to change that you disagreed with, and what happened?
Why ask it
This is where you learn how much authority the role actually carries. Notice whether they escalated, found evidence, or simply made the change, and what the disagreement cost them.
How much access do you get to the people who use what you make?
Why ask it
Direct access is the difference between designing from evidence and designing from a brief. Many designers have less of it than their process diagrams suggest, and the honest answer is informative.
What do a UX designer and a UI designer each do where you work, or is it one job?
Why ask it
The titles mean different things from one company to the next, and plenty of teams fold both into a single product designer. Their answer tells you which half of your other questions they can speak to from experience.
Where does a UX designer's job stop and a researcher's or product manager's begin on your team?
Why ask it
Ask who writes the interview guide, who sits in the sessions, and who has the last word on what gets built. The borders are drawn by whoever was hired first, so no two teams give the same answer.
What did your last round of user research change in the design?
Why ask it
A strong answer names one finding and the flow that moved because of it. If nothing moved, ask what the research was for, because sometimes it is run to confirm a decision already made.
How do you test a flow before anyone builds it?
Why ask it
Expect a method and a scale: a clickable prototype in front of a handful of people, a paper sketch, a colleague from another team. Follow up with what counted as the flow failing.
Which state of a screen gets forgotten most often: empty, loading, or error?
Why ask it
A mockup shows the screen with tidy data in it, and a real account rarely looks like that. UI designers tend to have a story about one that shipped undrawn and what they sketch first now.
What is the smallest interface detail you have argued for, and did it matter?
Why ask it
It might be a button's pressed state, eight pixels of spacing, or how long a menu takes to open. The story shows how a UI designer weighs polish against the cost of an engineer's afternoon.
How do you check an interface on a real device and not only in the design file?
Why ask it
Type size, tap targets and color behave differently on a small phone held outdoors than on a large monitor. Ask what they last changed after seeing their own work on hardware.
What happens to your layouts with long text, a larger font setting, or another language?
Why ask it
Translated labels often run longer than the original, and some readers turn the text size up. A designer who has been caught by this once usually has a test string they paste into every button.
Which part of your work would surprise someone who thinks the job is making things look good?
Why ask it
Answers usually involve writing, documentation, meetings, or reconciling constraints from three teams. It gives a realistic picture of where the hours actually go.
How do you handle a critique that lands badly?
Why ask it
Ask about a specific occasion rather than their general attitude. What matters is how they separate a bad delivery from a valid point, since that skill is what makes senior designers useful in a room.
What is in your toolkit now that was not there two years ago?
Why ask it
Tools and workflows change quickly in this field. What they have adopted, and what they tried and abandoned, tells you more about where the craft is moving than a general question about trends.
Have you worked in-house, at an agency, and freelance? How did they differ?
Why ask it
The trade-offs are concrete: variety against depth, stability against rate, whose problem the deadline is. Someone who has done more than one can compare them in a way that job descriptions cannot.
How does someone get promoted where you work, and what did you have to show?
Why ask it
Design ladders are often vague above mid-level. Ask what evidence was expected and who decided, because the answer reveals whether progression is defined or negotiated case by case.
What in your portfolio actually got you hired, as far as you know?
Why ask it
Usually one or two pieces do the work, and often not the ones the designer is proudest of. Ask what interviewers asked about, which is the closest thing to direct feedback on a portfolio you will get.
What is the worst project you have taken, and would you take it again?
Why ask it
Answers involve a client who would not decide, a rate too low to justify the work, or a brief that changed weekly. The second half separates a bad experience from a lesson about what to decline.
If you were starting now, what would you do differently?
Why ask it
Common answers involve specializing earlier, learning to write, or building relationships instead of polishing work. It is a better closing question than asking for advice, because it is grounded in something they actually regret.
What does a normal day actually look like, hour to hour?
Why ask it
Most people are surprised by how little of it is designing. If the honest answer is three hours of calls and two hours in a file, that is worth knowing before you choose the career.
How much of your week is designing versus talking about design?
Why ask it
The ratio shifts sharply with seniority, and people rarely mention that when giving career advice. Ask what they gave up as the meetings grew and whether they wanted the trade.
Which part of the job did nobody warn you about?
Why ask it
Usually one of three things: the amount of persuasion, the amount of writing, or how much work never ships. Whichever they name is a gap in how design is taught.
Where do you go when you are stuck on something visual?
Why ask it
Expect specifics: a shelf of books, a folder of saved work, going for a walk, or starting again at a smaller size. This is practical, immediately borrowable, and rarely written down anywhere.
How do you get to a decision when there is no data and everyone has an opinion?
Why ask it
This is the actual condition of most design work. Listen for a mechanism, a bet framed narrowly, a decision-maker named in advance, rather than an appeal to good taste.
Is there anything in your portfolio you would not put there now?
Why ask it
Designers are usually candid about this, and the reasons teach you a lot: work that photographs well but failed, work that was mostly someone else's, work that no longer represents them.
How do you decide whether to take a job or a project?
Why ask it
Listen for criteria, not just enthusiasm: who the decision-maker will be, whether there is a real problem, whether they will get to see the work used. These criteria are usually built from a bad experience.
How did you learn to talk about money, whether pricing or a raise?
Why ask it
Nobody is taught this and most designers learned it badly first. Expect a specific mistake with a number attached, which is more instructive than any general advice on the subject.
Who taught you the most, and what did they do differently?
Why ask it
Naming a person forces something specific: how they critiqued, how they showed unfinished work, how they handled being wrong. Generic answers about mentorship carry nothing you can use.
What do people early in their careers overrate, and what do they underrate?
Why ask it
The pairing is what makes this productive. Common answers overrate tools and trends and underrate writing, follow-through, and asking about constraints, but hearing their version tells you what they see going wrong around them.
Which of your skills have stayed valuable, and which have become obsolete?
Why ask it
This is the closest thing to a forecast you can get without asking for predictions. The skills they name as durable are usually about judgement, communication, or typography rather than software.
If I want to get better at this, what am I probably not doing?
Why ask it
Better than asking for general advice, because it invites them to look at you rather than the field. Bring work if you can, since the answer improves enormously when they have something to point at.
Getting a useful answer from a designer
Practical guidance for the conversation itself
How to run the conversation
Ask about one project, in order
Pick something they have shipped and walk through it from brief to launch. A single project traced end to end surfaces constraints, disagreements and compromises that no question about process will reach.
Look at the work before you meet
Spend ten minutes on their portfolio and bring one specific observation. Designers answer detailed questions about their own work far more generously than general ones about the field.
Ask what got cut
Case studies show the version that shipped. The interesting material is what was in the second round and why it did not survive, which is where the real decision-making lives.
Asking a UX designer or a UI designer
Find out early which side of the work fills their week, since the title alone will not tell you. With a UX designer, lean on the questions about research, testing and who decides what gets built. With a UI designer, lean on the ones about screen states, real devices and the details they fought for.
What to avoid
Asking for free work
A conversation about their career is not an opening to request a critique of your project or logo ideas. If you want a portfolio review, ask for it directly and expect to pay or to wait for a slot.
Asking which tool they use and stopping there
Tool answers are the least durable part of the conversation and are usually public anyway. Ask how they decide something is finished instead.
Treating one discipline as all of design
A product designer, a brand designer and an industrial designer share a job title and little else. Ask which parts of their answer are specific to their own field.