Questions to Ask a Designer in an Interview
Questions to ask a designer in an interview, written for the person doing the hiring, whether the seat is for a graphic designer, a brand or web designer, or a UX designer on a product team. The list opens with the basics every candidate expects (a portfolio piece, design process, criticism, tools and taste), then goes deeper by subject: the portfolio, process, craft and tools, teamwork, and fit. The process group closes with what to ask a UX designer in particular (flows, usability tests, prototypes), and craft and tools closes with interview questions to ask graphic designers about logos, print and image licenses. The guide covers how to structure the hour, which questions suit which kind of designer, and how to press without interrogating.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The basics
Walk me through a project you are proud of. What was the brief, and what did you actually do?
Why ask it
The word "actually" is doing the work. Strong candidates separate their own contribution from the team's without being prompted. If every sentence starts with "we", ask which two decisions were theirs alone.
How would you describe your design process, from the brief to the final handoff?
Why ask it
Most candidates have a tidy version ready: research, sketch, refine, deliver. Let them finish, then ask where their last project broke that order. How they work when the schedule gets in the way is the process you would be hiring.
How do you handle criticism of your work? Tell me about feedback you disagreed with and how it ended.
Why ask it
Everyone says they welcome feedback, so the story is the part to listen to. You are hoping for one case where they changed their mind and one where they held their position with evidence. If every story ends with them proved right, ask for one that did not.
Which design tools do you work in every day, and which did you pick up most recently?
Why ask it
The list matters less than it looks, because a capable designer can usually learn a new program on the job. The recent one tells you more: ask what made them learn it and what they stopped using as a result. If the role truly depends on one program, say so and ask to see a file made in it.
Which brand, product or piece of design do you admire, and what makes it good?
Why ask it
The pick shows their taste and the explanation shows whether they can take a design apart. "It's just so clean" is thin. Pointing at one decision, like how a label copes with a long product name or how an error message is worded, is the answer of someone who looks closely.
What brought you into design: a degree, teaching yourself, or a sideways move from another job?
Why ask it
An easy one for the first minutes, and no route is the right one. Listen for what they had to teach themselves along the way. A former teacher, coder or shop assistant usually carries something a design course does not cover, so ask what it is.
Portfolio
Before there was a design, what was the problem? Put it in a sentence that does not mention a screen or a layout.
Why ask it
Some designers start from a layout and work backwards to a justification. "The old page looked dated" describes a design, not a problem. "Customers kept phoning to ask when their order would arrive" is the kind of sentence you are hoping for.
Who else worked on this, and what did each of them own?
Why ask it
This catches inflated portfolios politely. Someone who can name the writer, the developer and the account lead, and say what each contributed, has worked in a real team. Vagueness about everyone else is worth a second question, since it can mean they worked alone or are claiming too much.
What constraints was this piece made under: time, budget, brand rules, an existing codebase?
Why ask it
A three-day turnaround and a three-month project produce different work from the same person. Once you know which this was, ask which constraint they would have lifted first if they could, and what that would have bought.
Show me something that did not work out. What happened?
Why ask it
Often the most revealing ten minutes of the interview. Hope for a specific account of why it failed and a lesson that changed later work. Blaming the client entirely, or claiming that nothing has ever failed, tells you how the next failure will be handled.
How do you measure whether a design succeeded once it is out in the world?
Why ask it
It is easy to hand work over and never look back, so any follow-up counts in their favor: a sales figure, fewer support tickets, a reprint order, one afternoon watching someone use it. Ask what the number was before as well as after. For print and brand work, the fair version is how they found out what the client or the audience made of it.
If you could reopen one project in this portfolio, what would you change?
Why ask it
Designers who still look hard at their old work will have an answer ready. A change that goes back to an early decision, such as the wrong audience or a layout that never suited the real content, shows more understanding than wanting another pass at the colors.
How did you decide what went into this portfolio and what stayed out?
Why ask it
Choosing and ordering the work is itself a design job, and you are looking at the result. Ask what the first piece is there to say. "It's everything I've done" means nobody edited, and editing is a large part of what you are hiring.
Is there work you are not able to show, and can you describe it without naming the client?
Why ask it
Plenty of good work sits under a confidentiality agreement, so a gap in the portfolio is not a warning by itself. Hearing the problem and their part in it, with the details held back, shows how they would treat your unreleased work too. Be wary if they offer to show it anyway.
Which piece in here is closest to the work you want to do next?
Why ask it
If they point at the brand identity and the role is mostly campaign resizing and slide decks, say so now. Hearing it in the interview is kinder than finding out in the second month, and some candidates will want the job anyway.
Process
What do you need to know before you start designing anything?
Why ask it
Audience, goal, deadline, who signs off, what already exists: each one they ask for saves you a wasted round later. Happily starting from a one-line brief sounds easygoing, but it means the brief gets designed as written, mistakes included.
How do you get to know the people a piece of work is for?
Why ask it
Sitting in on a sales call, reading reviews, watching someone use the thing, standing in the shop: any first-hand contact counts. If all they have ever had is a persona document written by another team, ask how much they trusted it.
What do you do when there is no research and no time to get any?
Why ask it
The honest answer involves stand-ins: support logs, sales calls, analytics, five minutes with anyone who talks to customers. "I would insist on research" is a fine principle, so ask what happened the last time the answer was no.
Tell me about a time you were handed a solution instead of a problem. What did you do?
Why ask it
"Just make the logo bigger" or "add a pop-up" lands on most designers' desks sooner or later, and the reply shows how they work without authority. Refusing and silently complying are the two easy answers. The middle path is asking what the request is meant to fix, or building it while gathering evidence for an alternative.
How many directions do you explore before committing to one, and how do you choose?
Why ask it
Ask to see the options that lost on a real project, and why they lost. If only the winner survives in memory or in the files, the first idea was probably polished and sent, which is a habit deadlines encourage.
When have numbers or test results made you change a design you liked?
Why ask it
This checks whether evidence can beat their own taste. Ask what the result was, how large the test or sample was, and whether they still think the old version looked better. It is fine if they do.
Tell me about a time what the business wanted and what the audience needed pulled apart. Where did you land?
Why ask it
There is no clean answer, which is why it is worth asking. Siding with the audience every time wears out a designer's welcome, and siding with the business every time is taking orders. The part to dwell on is the trade they proposed and who they had to persuade.
How do you estimate how long a piece of design work will take?
Why ask it
Estimates are usually wrong, so ask how far out the last one was and what it left out. Review rounds and waiting for sign-off are the usual culprits, and hearing that they now add time for both is the mark of a lesson learned on a real job.
How do you handle several projects with deadlines in the same week?
Why ask it
Working late is not a method. The answer to hope for involves saying early which job will slip and letting whoever owns the priorities decide. Quietly choosing on your behalf feels helpful and will sometimes be the wrong choice.
Tell me about a deadline you were not going to make. What did you cut?
Why ask it
Knowing what to cut is a different skill from being thorough. In the good version of this story the cut was the thing that mattered least to the audience, it was made while there was still time to act, and the team was told. Cutting sleep does not count.
How do you know when to stop working on a design?
Why ask it
Perfectionism and carelessness both show up here. The answer you want is a stopping rule that sits outside their own taste: it passed a review, the open questions are answered, or the date they agreed to has arrived. "When I'm happy with it" deserves a follow-up about the last time they never were.
Pick one flow from your portfolio and take me through every screen a first-time user sees. Where do people give up?
Why ask it
A UX designer should know the path as well as the screens, including the dull steps such as sign-up and confirmation. Knowing where people abandon it, and how that was found out, separates someone who designed a flow from someone who drew its best screen.
Tell me about the last usability test you ran yourself. Who took part, and what did you ask them to do?
Why ask it
Details are hard to fake here: how participants were found, the task they were set, the moment someone got stuck. Five colleagues at their desks is a fair answer from a small company. If testing was always another team's job, ask what they did with the findings.
How do you decide whether an idea needs a paper sketch, a rough wireframe or a clickable prototype?
Why ask it
The cheapest thing that answers the open question is usually the right one. A polished prototype for everything spends days where an hour would do, and never building one skips the problems only a working model shows. Ask what the last prototype was built to find out.
How do you divide decisions with a product manager: who settles what gets built, and who settles how it works?
Why ask it
Titles and team habits vary so much that the answer mostly describes their last company. That is still useful, because you can hold it against your own setup. The story to hope for is a disagreement argued out with evidence, with neither side simply handing down requirements.
Which screen size do you design for first, and what happens to the layout on the others?
Why ask it
Starting with the phone forces a decision about what matters most, while starting wide can leave the small screen as one long stacked column. Either order works if they can show the same page at two or three widths. A portfolio of desktop screens alone is worth a question.
Craft and tools
How do you keep up with design trends, and which current one are you steering clear of?
Why ask it
The first half gets a list of newsletters and feeds, which tells you little. The trend they are avoiding is the real question: naming a fashionable look they declined to use, and why it would not have suited the job, shows taste with reasons behind it. Chasing every trend and sneering at all of them are both poor signs.
Where do you look for ideas outside of other designers' work?
Why ask it
A feed of other people's portfolios tends to produce work that looks like the feed. Old signage, architecture, supermarket shelves abroad, games, film titles: any real outside interest will do. Ask where the last one turned up in a project.
What is something you use every week that is badly designed, and how would you fix it?
Why ask it
It works as a small live critique that nobody can rehearse. The best answers ask who the thing is for before fixing it, and guess at the constraint that caused the flaw. Assuming the people who made it were careless is a less promising start.
How do you choose typefaces and color for a project? Talk me through the last time.
Why ask it
Fundamentals show here. You want reasons from outside personal preference: legibility at the size it will be read, contrast, what the brand already owns, how it prints or renders, what the font license allows. "It felt right" needs a follow-up.
Tell me about a time the accessible choice and the better-looking choice were not the same. Which won?
Why ask it
Anyone can say accessibility matters, so ask for the instance: a contrast ratio that dulled the brand color, a tap target that crowded the layout, type that had to grow. If your work must meet a legal or contractual accessibility standard, name it and ask what they have built to it, because the requirement differs by country and sector.
How have you worked with a design system, and when did you deliberately break it?
Why ask it
Both halves matter. Never departing from the system can mean assembling components without judging them, and departing constantly leaves work nobody else can maintain. For the time they did break it, ask how they decided and who they told.
Tell me about working inside brand guidelines you did not write. Where did they run out?
Why ask it
Guidelines never cover every case: the tiny app icon, the trade-show banner, the partner logo that clashes. What a designer does at the point where the rules stop, and whether they told whoever owns the brand, says more about their judgment than any on-brand layout.
How comfortable are you with motion, illustration, writing copy or code, and where do you hand over to a specialist?
Why ask it
Small teams need range and large ones need depth, so there is no right answer, only one that matches the role. For each skill they claim, ask for the last finished project that needed it. "I have dabbled" and "I delivered it" are different answers.
How do you set up and name your files so that someone else can pick them up?
Why ask it
On a video call, ask them to share a working file instead of describing one. Named layers, tidy components and clear versions mean a colleague can cover for them. A folder of files called final, final 2 and really final means you inherit a puzzle every time they take a week off.
What do you check before your work goes to a client, a developer or a printer?
Why ask it
Spelling, alignment, export sizes, image rights, bleed and color mode for print: people who have been burned keep a list. Ask what mistake put the first item on it. Most designers have a story about a typo that went out, and it is a good sign when they tell it.
How do you use AI tools in your work, and where do you not trust them?
Why ask it
No answer is right everywhere, but theirs has to fit your own rules, so say what those are: policies on generated images, client confidentiality and who owns the output differ between employers and contracts. Then ask which portfolio pieces involved these tools and which parts were done by hand.
Show me a logo or identity you designed. How does it hold up at the size of an app icon, in a single color and on a dark background?
Why ask it
A mark that only works large and in full color is half finished. Ask to see the awkward versions, such as the one-color stamp or the tiny browser icon, and whether they were planned from the start or patched in when the client asked.
How much of your work has gone to print, and how close did you get to the printer: paper choice, proofs, a press check?
Why ask it
Screen-only designers can be excellent, but if this job ends in packaging, signage or a brochure, hands-on print experience saves expensive reprints. A candidate who has stood at a press can tell you what a proof showed that the screen had hidden.
How do you take one campaign idea across a billboard, a square social post and a narrow web banner without redesigning it each time?
Why ask it
Much of a graphic designer's week is adaptation, so the method matters more than the hero image. Good answers begin by fixing which elements stay put and which may move. Ask which format broke the idea, and what they dropped to make it fit.
Where do your photographs, illustrations and fonts come from, and how do you keep track of what each license allows?
Why ask it
You are listening for a habit: a record of sources, licenses saved with the project, a query raised before using anything doubtful. License terms vary by library and by contract, so describe how your company handles them and ask how that compares with what they are used to.
Have you built templates for people who are not designers, such as slide decks, social posts or reports? What did they do to them?
Why ask it
Templates are where a brand lives day to day, in the hands of colleagues with no training. The second half is the telling one: a designer who went back, saw the stretched logos and simplified the template has learned something a showpiece never teaches.
If we hired you for a single project, what would we get at the end: which file formats, and the editable source files or only the finished artwork?
Why ask it
Mostly a question to ask a graphic designer you are engaging as a freelancer or through a studio. Who owns the artwork and whether working files are included depend on the contract and on copyright rules that differ by country, so agree it in writing before the work begins.
Teamwork
How do you work with the writers, developers and marketers around you, and when do you bring each one in?
Why ask it
Timing is the tell. Handing a writer a finished layout full of placeholder text means the word count was decided before anyone wrote a word. Asking for real copy and a developer's opinion at the sketch stage is the habit of someone who has made things with other people.
How do you hand work to developers, and what do they usually come back to you about?
Why ask it
What comes back is the useful part of the answer. People who work closely with developers can list the repeat queries, such as empty screens, error messages, loading and text that runs long, and have usually started specifying those up front. For print or packaging, ask the same about the printer.
When a developer says your design cannot be built in the time available, what do you do next?
Why ask it
Curiosity is the good sign: asking which part is expensive usually turns up a cheaper version that keeps what matters. Going over the developer's head and silently dropping the idea are the two answers to worry about.
How do you present work to people who do not speak design?
Why ask it
The answer is its own demonstration, so notice how they explain it to you. If the reasons are words like clean, modern and intuitive, a finance director will not follow them either. Starting from what the work is meant to achieve, before any talk of how it looks, is the better order.
What do you do with feedback like "make it pop" or "I'll know it when I see it"?
Why ask it
Every designer gets this, so a blank look would be strange. The skilled response translates it: asking what the person wants noticed first, or showing two rough versions and asking which is nearer. Guessing and producing another full round is the expensive way.
What do you do when a stakeholder starts redesigning your work in the review?
Why ask it
"Move that up, make this one green" is a familiar way for a review to go off course. Useful responses take the suggestion back to the goal (what should the reader notice first?) or offer two options to choose between. Nodding along and then ignoring it, or resentfully doing exactly as told, both store up trouble.
How many rounds of revision are normal for you, and what do you do when they will not stop?
Why ask it
Endless rounds usually mean nobody agreed at the start who approves or what done looks like. An answer that goes back and settles that is worth more than patience. With a freelance or agency designer, ask how they write it into the agreement.
Tell me about a client or stakeholder you found hard to work with. What did you try?
Why ask it
Pay attention to how the person is described. Contempt for a client's taste tends to reappear as contempt for colleagues. The stronger story works out what the difficult person was afraid of, such as a boss to answer to or a launch they could not afford to miss.
How do you critique another designer's work?
Why ask it
Good critics ask what the designer was trying to do before saying anything about the result. If the answer is a list of things they would have done differently, that is preference with a senior title, and junior colleagues tend to stop showing unfinished work to people like that.
How do you stay in step with a team that is remote or spread across time zones?
Why ask it
Find out what they write down. Annotated files, recorded decisions and a short written rationale carry design work across time zones, while a habit of settling everything on a call does not. Skip this one if your team shares a room.
Have you directed or mentored other designers? What was hard about it?
Why ask it
For a senior or lead role. The usual struggle is leaving someone else's work alone, and candidates who admit to redoing a junior's file at midnight at least know the trap. For a junior hire, turn it around and ask who taught them the most.
Fit and growth
What drew you to this role, and what do you know about our product or brand so far?
Why ask it
You are checking whether they looked. Having tried the product, visited the shop or noticed that the website and the packaging do not match means they have already begun thinking like your designer. A general love of design could be said to any employer.
If you joined tomorrow, what is the first thing about our website, product or brand you would want to change?
Why ask it
Treat it as a view of how they think, not as a free audit, and keep it to a few minutes. The best replies name what they cannot know from outside, such as your data and constraints, and still commit to an opinion. Pure flattery is a non-answer.
Have you worked in-house, at an agency or freelance, and what would you miss in a move to our setup?
Why ask it
An agency means many clients and quick turnover, in-house means one brand for years, and freelance means choosing your own work. Someone crossing over should know what they are giving up. If they cannot name anything, they may not have pictured the job yet.
What kind of team do you do your best work in?
Why ask it
Compare the answer honestly against the team you actually have. Someone used to a research partner and a weekly critique may find it lonely as your only designer, however good the portfolio is. Describe the real setup and ask how they would manage without the part that is missing.
What are you better at than most designers you have worked with?
Why ask it
The usual strengths question, phrased so that "I'm a perfectionist" will not fit. A useful answer is narrow: fast, clean production files, naming things, calming a nervous client, type at small sizes. Check it against the portfolio, and against the gap on your own team.
Which part of the craft are you weakest at right now?
Why ask it
Motion, typography, writing, research: naming a real one and saying what they do about it, whether that is a course or leaning on a colleague, makes someone easier to manage. A strength dressed up as a weakness is an evasion. Say which gaps your team can cover so that the honest answer feels safe.
What kind of design work would you rather not do?
Why ask it
Everyone has one: banner resizes, slide decks, endless production fixes. If it makes up a third of this job, both of you need to hear that today. A plain answer is a candidate being straight with you, and "I love all of it" is a candidate being polite.
How do you like to receive feedback: written or live, on early sketches or near the end?
Why ask it
Cheap to ask and immediately useful if you hire them. A preference for written notes in advance, or for hearing the problem without a suggested fix, has usually been learned from a review process that hurt. Ask what that process was.
What is the last thing you learned that changed how you work?
Why ask it
Curiosity shows in what changed, not in what was read. "I now write the copy before I draw anything" is a change you could watch them make, and a list of courses is not. Ask who or what prompted it.
Where do you want your career to go: deeper into the craft, or toward leading a team?
Why ask it
Both are legitimate, and the point is whether you have that path to offer. If your company only promotes designers into management, someone who wants to stay hands-on should hear that before accepting, not at their second review.
What do you want to be better at in a year, and what would you need from us?
Why ask it
What they ask for tells you what keeping them will cost: a training budget, time with a senior designer, a kind of project you may not have. If there is no ask at all, prompt once, since some people think it rude to request anything before an offer.
What do you want to ask us about how design gets done here?
Why ask it
Access to customers, who signs off, whether developers build what was drawn: whatever they ask about is usually what went wrong at the last job. Answer honestly, including the unflattering parts, because they will know the truth within a month anyway.
Running a designer interview
Practical guidance for the conversation itself
Structure the hour
Before the hour: choose about ten
The list is longer than any interview. Take two or three of the basics, three or four from the portfolio group and two from each group that matters most for this role, then write them down so every candidate gets the same ones. Answers are far easier to compare when the questions matched.
Portfolio walkthrough, about half the hour
One project, in depth, chosen by them. Interrupt for decisions instead of waiting until the end: why this and not that, what you tried first, who disagreed. Depth on one project beats a tour of six.
Situational questions, about twenty minutes
The stakeholder, deadline, revision and handoff questions above. These are about how they behave under constraint, which is much of the job and rarely visible in a portfolio.
Their questions, the last ten minutes
Protect this time even if the walkthrough runs long. What they ask about, whether it is process, access to customers or how developers treat the designs, tells you what they have been missing and whether you can provide it.
Match the questions to the designer
- Graphic or brand designer: start with the logo, print, campaign and licensing questions that close Craft and tools, then lean on the typeface and color, brand guidelines, file setup and final-check questions, and ask to see one piece in its printed or finished form.
- Product or UX designer: start with the flow, usability test, prototype and product manager questions that close Process, then lean on the problem, research, design system, accessibility and developer handoff questions, and ask what happened to the numbers after launch.
- Junior designer: welcome school and self-started projects, drop the mentoring and business trade-off questions, and weigh how they take a suggestion in the room above polish.
- Senior or lead designer: spend longer on stakeholders, critique, scope cuts and mentoring, and ask what they decided not to do.
- Freelancer or contractor: add the estimating, revision rounds, file handover and final deliverables questions, and ask how they like to be briefed.
How to press without interrogating
- When they describe a decision, ask what the alternative was and why it lost.
- When they say the team decided, ask what they personally argued for.
- When they mention research, ask how many people and what surprised them.
- When a screen looks finished, ask what it shows when something goes wrong or there is nothing to show yet.
- When they cite a metric, ask what it was before and who measured it.
- If an answer stays abstract twice, ask for a single specific instance instead of rephrasing.
Common mistakes by interviewers
Judging the visuals and calling it a judgment of the designer
Polish is partly a function of how much time and freedom the last employer allowed. Ask what constraints the work was made under before you read the craft as the ceiling of their ability.
Asking for a design philosophy
It tends to produce a rehearsed abstraction. The same information comes out of asking how they decided one specific thing, and that version is much harder to prepare in advance.
Unpaid take-home exercises on real problems
Candidates with other options often decline these, so you end up filtering for spare time more than skill, and asking for free work on a live problem can look like collecting ideas. If you need to see them work, use a short paid exercise or a live session on a problem you have already solved. Rules on unpaid trial work differ by country, so check what applies where you hire.
Leaving non-designers off the panel
The developers, writers and marketers who will work with them daily notice different things. Give one of them a slot and a specific question to own.
Drifting into personal questions
Small talk about age, family plans, health or where someone is from can stray into ground that employment law restricts, and what is restricted differs by country and state. Keep the questions on the work and check the rules where you hire.