A graphic designer interview is usually built around your portfolio, but the questions underneath it are about judgment: why you chose that typeface, how you arrived at that layout, who the work was for, and what the client actually asked for. Expect to walk through two or three projects in detail — a logo, a packaging or display piece, a web layout — and to explain the brief, the audience research, the concepts you rejected, and the feedback rounds.
Technical questions cover the unglamorous half of the job: preparing digital files for printing, color modes, bleeds and trim, resolution, font licensing and outlining, and delivering logo systems in the formats a client will actually need. Interviewers also probe how you take direction — conferring with clients or a supervisor, interpreting vague feedback, pushing back on a request that would weaken the design, and managing several projects with competing deadlines.
Prepare by rehearsing each portfolio piece as a short story with a problem, a constraint, and a measurable outcome. Bring at least one project that went badly and what you changed. Know your own file-prep checklist well enough to recite it. Have questions ready about how briefs come in, who approves work, and whether the role is print-heavy, digital-heavy, or both.
1. Walk me through one project in your portfolio from the initial brief to the final delivered files.
What they're testing
Whether you work from a brief and constraints or just make attractive things, and whether you understand the full production chain.
A strong answer
State the client, the commercial goal, and the constraints (budget, print method, existing brand assets). Describe the audience research, the concepts you developed, which one was selected and why, and how feedback shaped it. End with what you delivered — press-ready files, logo formats, a spec sheet — and how the piece performed or was used.
Common failure mode: Narrating visual choices only ('I liked this blue') with no brief, no audience, and no mention of what was actually handed off.
Likely follow-up: Which concept did the client reject, and were they right?
2. How do you run a first conversation with a client to determine the layout and direction of a project?
What they're testing
Active listening and the ability to extract a usable brief from a non-designer.
A strong answer
Describe the questions you ask: what the piece must accomplish, who sees it and where, what has been tried before, what they think is off-limits, deadline, and format. Explain how you play back what you heard in writing so there's a shared reference. Mention getting examples of what they like and, more usefully, what they dislike.
Common failure mode: Saying you 'just ask what they want' and treating the client's stated solution as the brief instead of digging for the underlying goal.
Likely follow-up: What do you do when the client can't articulate what they want?
3. Describe how you research the target audience before you start designing.
What they're testing
Whether design decisions are grounded in who will see the work.
A strong answer
Explain the sources you use — client sales data, competitor work, existing customer feedback, where the piece will physically appear. Give a concrete case where research changed a decision, like enlarging type for an older audience or simplifying a display because viewers pass it at a distance.
Common failure mode: Treating audience research as a formality and jumping straight to aesthetic preference.
Likely follow-up: Tell me about a time your assumption about the audience was wrong.
Reading answers isn't rehearsing them.
Run these exact questions with a voice AI interviewer and get scored on your real answers — the first five minutes are free.
4. How do you choose a typeface and type size for a project?
What they're testing
Typography fundamentals and the ability to justify choices out loud.
A strong answer
Tie the choice to legibility at the actual reproduction size, tone and brand fit, the length and hierarchy of the copy, licensing and cost, and whether the family has the weights you need. Give an example where you rejected a first choice because it broke down at small sizes or lacked the necessary characters.
Common failure mode: Naming favorite typefaces with no reasoning about legibility, hierarchy, or licensing.
Likely follow-up: How do you build hierarchy when the client insists everything is important?
5. Walk me through your process for preparing digital files for printing.
What they're testing
Production competence — the thing that costs real money when it goes wrong.
A strong answer
Describe a checklist: correct color mode and any spot colors, resolution of placed images, bleed and safe margins, trim and fold marks, overprint and knockout, fonts outlined or embedded, links packaged, and a proof review against the printer's spec. Mention confirming requirements with the printer before building, not after.
Common failure mode: Saying 'I export a PDF' with no mention of bleed, color, resolution, or talking to the printer.
Likely follow-up: A printer says your file has a transparency issue. What now?
6. Tell me about a time a print or production job came back wrong. What happened?
What they're testing
Accountability and whether you built a process fix afterward.
A strong answer
Give a specific error — a color shift, a mistrim, a low-resolution image that got through. Say who caught it, what it cost in time, how you resolved it with the client and printer, and the concrete step you added to your prepress checklist afterward.
Common failure mode: Blaming the printer or the client entirely, or claiming it has never happened.
Likely follow-up: What's on your pre-release check now that wasn't before?
7. A client says the logo you designed 'doesn't feel right' but can't explain why. What do you do?
What they're testing
Social perceptiveness and skill at converting vague feedback into actionable direction.
A strong answer
Explain that you ask diagnostic questions rather than immediately redesigning: is it the mark, the type, the color, the weight? Show comparisons and let them react to options. Reference the original brief and the audience to reframe the discussion around goals. Then propose a small number of targeted revisions rather than starting over.
Common failure mode: Either defending the work rigidly or immediately producing ten new versions, which trains the client to give vague feedback.
Likely follow-up: How many revision rounds do you build into a logo project?
8. How do you handle a request that you believe will make the design worse?
What they're testing
Whether you can advocate for craft without being difficult to work with.
A strong answer
Describe stating the specific consequence in the client's terms — legibility at size, printing cost, brand inconsistency — and offering an alternative that addresses their underlying concern. Note that if they still want it after being informed, it's their brand and you execute it well. Give a real example of each outcome.
Common failure mode: Framing it as a fight to win, or capitulating instantly without ever stating the risk.
Likely follow-up: Give an example where you lost that argument and it turned out fine.
9. Describe how you develop a logo system, including what you deliver to the client.
What they're testing
Depth on a core deliverable and understanding of how logos live after handoff.
A strong answer
Cover research and competitive audit, sketching and concept exploration, refinement in vector, testing at small size and in one color, and reversal on dark backgrounds. Deliverables: vector masters, raster exports at needed sizes, horizontal and stacked lockups, one-color and reversed versions, clear-space and minimum-size rules, and color specs for print and screen.
Common failure mode: Stopping at 'I present three options' with no mention of testing, variants, or usage guidance.
Likely follow-up: How do you test whether a mark works at favicon size?
10. You have three projects due the same week and a client adds a rush request. How do you handle it?
What they're testing
Organizing, planning, and prioritizing work under competing deadlines.
A strong answer
Describe assessing true deadlines versus stated ones, identifying which stages have hard dependencies like a print run, and going to the supervisor or client with options rather than a flat no — reduced scope, later delivery on a lower-priority item, or a simpler execution. Emphasize communicating early rather than silently slipping.
Common failure mode: Saying you'd just work late, with no triage, no negotiation, and no one informed.
Likely follow-up: Who do you go to first when something has to slip?
11. How do you determine the size and arrangement of images and copy on a layout?
What they're testing
Layout principles and whether you can articulate composition decisions.
A strong answer
Talk about establishing hierarchy from the communication goal, using a grid, controlling reading order, balancing image weight against text, and leaving deliberate white space. Mention the physical context — a shelf display versus a page versus a screen — and how it changes scale decisions. Give a concrete example.
Common failure mode: Vague talk about 'balance' and 'flow' with no reference to hierarchy, grid, or context.
Likely follow-up: What do you do when the copy runs far longer than the space allows?
12. How do you approach designing for both print and web when the same brand assets have to work in each?
What they're testing
Cross-medium fluency, a frequent gap in otherwise strong portfolios.
A strong answer
Cover color mode differences and how you manage expectations about screen versus press color, resolution and vector versus raster, type sizes that read on screen versus in hand, and accessibility considerations like contrast. Describe maintaining a single source of brand assets so the two don't drift apart.
Common failure mode: Treating the two as identical, or admitting to only ever working in one medium without showing how you'd learn the other.
Likely follow-up: How do you brief a developer on a layout you designed?
13. Tell me about a time you received harsh critique on your work. How did you respond?
What they're testing
Ego management and coachability, which predict day-to-day workability.
A strong answer
Pick a real instance, describe the criticism plainly without softening it, say what part of it was valid, what you changed, and what you kept and why. Show that you separated the work from yourself and asked follow-up questions to understand the objection.
Common failure mode: Choosing an example where the critic was obviously wrong, so the story becomes self-congratulation.
Likely follow-up: How do you give critique to another designer?
14. How do you review a final layout before it goes out, and what do you look for?
What they're testing
Attention to detail and whether you have a repeatable QA habit.
A strong answer
Describe a two-pass approach: a content pass for copy accuracy, names, dates, contact details, and legal marks, then a production pass for alignment, widows and orphans, image resolution, color, and bleed. Mention printing it out or viewing at actual size, and getting a second pair of eyes on copy.
Common failure mode: Relying entirely on the client to catch copy errors and having no personal checklist.
Likely follow-up: What error have you personally missed most often?
15. Describe a project where you had to work within an existing brand system rather than create something new.
What they're testing
Discipline and willingness to serve a brand over personal style.
A strong answer
Name the constraints — set palette, type family, logo rules, tone — and show where you found room to solve the problem creatively inside them. Explain how you handled a case where the guidelines didn't cover the situation, and who you consulted before extending the system.
Common failure mode: Describing brand guidelines as a creative prison, which signals you'll be difficult on in-house or agency work.
Likely follow-up: What did you do when the guidelines contradicted the medium?
16. What software do you use day to day, and how do you keep your skills current?
What they're testing
Technical baseline plus active learning, given how fast tooling shifts.
A strong answer
Name the categories you're strong in — vector, raster, layout, prototyping, motion or 3D if relevant — and be honest about depth. Describe how you learn: side projects, following production changes from printers, tutorials tied to real jobs, and picking up a new tool because a project demanded it. Give a recent example.
Common failure mode: Listing every application ever installed with no evidence of depth, or having learned nothing new in years.
Likely follow-up: What's the last tool or technique you taught yourself, and why?
17. Tell me about a concept you loved that the client killed. How did you handle it?
What they're testing
Professional detachment and understanding that the work serves a commercial need.
A strong answer
Describe the concept and why you believed in it, the case you made, and the reason it was rejected. Show that you delivered the chosen direction at full quality rather than sulking, and note anything you learned about pitching — like presenting fewer, better-argued options or tying concepts back to the brief.
Common failure mode: Using the story to prove the client had bad taste, revealing that you underinvested in the surviving direction.
Likely follow-up: How do you present concepts so the strongest one wins?
18. How do you write and present the rationale for your work?
What they're testing
Speaking and writing skill — the top-rated skills for this role and the difference between a designer who gets buy-in and one who doesn't.
A strong answer
Explain that you open with the problem and the audience, then show how each major choice serves that, avoiding jargon. Mention keeping presentations short, giving the client a clear decision to make, and following with written notes so the reasoning survives the meeting.
Common failure mode: Presenting work silently and letting stakeholders react to surface aesthetics with no framing.
Likely follow-up: How do you present to a room that includes non-designers and executives?
19. Show me a piece of work you'd redo. What's wrong with it?
What they're testing
Self-critique and current standards versus past output.
A strong answer
Name a real weakness — muddy hierarchy, a typeface that didn't hold up, a layout that ignored where the piece was actually seen. Explain what you understand now that you didn't then and how it changed subsequent work.
Common failure mode: Picking a piece that's actually fine, or blaming the client's constraints instead of the design decisions you controlled.
Likely follow-up: What habit did you change as a result?
20. Why do you want this role, and what kind of work do you want to be doing more of?
What they're testing
Motivation and fit with the actual mix of work — packaging, displays, logos, web, or print collateral.
A strong answer
Connect specifics about the team's output to the kind of problems you want to solve, and be honest about the areas you want to grow in. Name the medium or category you're strongest in and one you want more reps in, framed as something the role would give you.
Common failure mode: Generic enthusiasm for 'creative work' that could apply to any studio, or a wish list that doesn't match the role's actual output.
Likely follow-up: Which part of this role would you find least interesting?