Senior Graphic Designer interview questions and practice.
Takes the lead on complex design projects, sets visual direction, reviews junior work and manages brand consistency across outputs. An interviewer hiring a Senior Graphic Designer is not testing whether you know what the job is. They are trying to establish whether you design from evidence and can be argued with, or whether you present taste and defend it.
No card for the taster. Full interviews are paid one at a time. Nothing renews.
Last reviewed
What interviewers for Senior Graphic Designer actually ask
Three questions from the bank below, each scored against one competency. The follow-up is what separates a prepared answer from a memorised one.
Take me through a project where research changed what you built.
You are asked to design something and there is no time for research. What do you do?
What is the hardest interaction problem you have solved?
What they are really assessing
That gets scored against 7 competencies: user research & problem framing, design craft & visual quality, interaction design & usability, collaboration with product & engineering, critique, feedback & stakeholder management, design systems, tooling & process and design impact & measurement. Each one is assessed from the specifics in your answers, which is why "we improved the process" scores lower than a sentence with a number, a date and a decision in it.
At senior level the questions get harder because they are testing judgement, not knowledge. Expect them to push hardest on push on a complex problem solved end to end, influence on product strategy, raising team quality, and a failed design honestly analysed.
User research & problem framing
Understands users and their problems before designing: plans and runs interviews, usability tests and analytics review, synthesises findings and reframes the brief around the real problem.
- Weak
- Designs from the brief or personal taste; cannot describe a research method used or a finding that changed the design.
- Adequate
- Describes research methods used (interviews, usability tests, analytics), how findings were synthesised and one design change driven by them.
- Strong
- Describes a project where research reframed the problem, the method and sample, the specific finding, the design change and the measured effect on task success, conversion or support tickets.
Design craft & visual quality
Produces high-quality work in their discipline (UI, visual, graphic, motion): hierarchy, typography, layout, colour, interaction detail, consistency with systems and attention to edge states.
- Weak
- Portfolio is described in adjectives ('clean', 'modern'); cannot explain a typographic or layout decision or how edge states were handled.
- Adequate
- Explains key design decisions on a piece of work (hierarchy, type, spacing) and how it fits a design system, with awareness of empty, error and loading states.
- Strong
- Talks through a piece with the decisions and rejected alternatives, the system constraints, edge and accessibility states, and critique received and applied; work shows consistent quality across the portfolio.
Interaction design & usability
Designs flows that users complete: information architecture, task flows, states and feedback, accessibility (WCAG) and responsive behaviour, validated through testing rather than assumed.
- Weak
- Describes screens rather than flows; cannot explain a usability problem found in testing or an accessibility consideration.
- Adequate
- Describes mapping a flow, testing it with users, fixing a usability issue found, and basic accessibility practices.
- Strong
- Describes a flow redesigned after testing with the specific failure observed, the fix and the improvement in completion or error rates, plus accessibility work (contrast, keyboard, screen readers) done and verified.
Collaboration with product & engineering
Works effectively with product managers and developers: contributes to scoping, hands over specs and assets cleanly, negotiates trade-offs when constraints bite and checks the built result.
- Weak
- Hands designs over and moves on; describes developers as not implementing designs properly; no example of a trade-off negotiated.
- Adequate
- Describes handover practices (specs, components, prototypes), regular check-ins with developers and one trade-off made under a technical constraint.
- Strong
- Describes a project where a constraint forced a redesign, how they worked with engineering to find the best option, how they did design QA on the build, and how the collaboration process improved afterwards.
Critique, feedback & stakeholder management
Presents work with rationale, seeks and gives critique constructively, separates taste from evidence, and manages subjective stakeholder feedback without diluting the design.
- Weak
- Takes feedback personally or accepts all changes; cannot describe how they present rationale or push back with evidence.
- Adequate
- Describes presenting rationale tied to user goals, handling a stakeholder's subjective request by exploring the underlying concern, and running critique sessions.
- Strong
- Describes a senior stakeholder disagreement, how they surfaced the real concern, what evidence or test settled it, and the result; describes changing their own design after critique with a specific example.
Design systems, tooling & process
Works systematically: uses and contributes to design systems, keeps files and components organised, manages versions and documents decisions so others can build on the work.
- Weak
- Files are ad hoc; cannot describe a component library or how consistency is maintained across a product.
- Adequate
- Describes using a design system and tools (Figma components, variants, libraries) and contributing a component with documentation.
- Strong
- Describes building or improving a design system, the adoption problem solved, the efficiency or consistency gain with evidence, and how governance and contribution work.
Design impact & measurement
Connects design work to outcomes: defines success metrics with product, measures after launch, iterates on evidence and can say what a design changed for users and the business.
- Weak
- Cannot cite any outcome for their work beyond stakeholder approval; success is 'it shipped'.
- Adequate
- Cites a metric that moved after a design change (conversion, task time, satisfaction) and how it was measured.
- Strong
- Describes defining metrics before designing, the result with figures, an iteration driven by the data, and a design that did not work and what they learned.
10 questions you should expect
What a strong answer contains, not a model answer to memorise. A memorised answer falls apart on the first follow-up, and there is always a follow-up.
Take me through a project where research changed what you built.
Scored against: User research & problem framingA strong answer contains: The original assumption, the method and how many people, the specific finding that broke the assumption, and what shipped instead. Best answers name a finding that was inconvenient for the roadmap.
And then they askHow many people did you actually speak to, and what would you do with half the time?
You are asked to design something and there is no time for research. What do you do?
Scored against: User research & problem framingA strong answer contains: Use what exists (support tickets, session recordings, sales calls, existing analytics, five hallway tests), then state the assumptions explicitly in the design so they can be checked later. Not refusing, and not pretending it is evidence-based.
And then they askHow do you make the assumptions visible so someone can challenge them?
What is the hardest interaction problem you have solved?
Scored against: Interaction design & usabilityA strong answer contains: The specific constraint (state, error handling, progressive disclosure, an input people always get wrong), the options they tried, how they tested it, and the trade-off they accepted. Not a redesign of a landing page.
And then they askWhat did you try first that did not work?
How do you handle the unhappy paths: errors, empty states, slow connections?
Scored against: Interaction design & usabilityA strong answer contains: That they design them at all, and early rather than as an afterthought. Specific examples: the first-run empty state, a partial failure, a form that loses data. This is the fastest way to distinguish a product designer from a visual one.
And then they askShow me an empty state you designed and what it was doing.
Pick a screen from your portfolio. Why is it laid out that way?
Scored against: Design craft & visual qualityA strong answer contains: Reasons rather than preference: hierarchy driven by the user's task, type scale and spacing from a system, contrast and touch targets meeting accessibility thresholds, and what they removed. "It felt balanced" scores low.
And then they askWhat did you take out of this screen, and who wanted it there?
An engineer says your design is too expensive to build. What happens next?
Scored against: Collaboration with product & engineeringA strong answer contains: Find out which part and why, separate the essential behaviour from the visual expression, offer a cheaper version that keeps the user outcome, and know when to argue for the expensive one. Includes an example of both.
And then they askTell me about a time you accepted a worse design, and one where you did not.
How early do engineers see your work?
Scored against: Collaboration with product & engineeringA strong answer contains: Early and rough, with a reason: feasibility, edge cases and effort surface sooner. Candidates who hand over finished files at the end are describing rework they will not admit to.
And then they askWhat has an engineer told you at the sketch stage that saved you a week?
How do you handle a senior stakeholder who wants a change you think is wrong?
Scored against: Critique, feedback & stakeholder managementA strong answer contains: Get to the problem underneath the requested solution, bring evidence rather than opinion, offer a test where one is possible, and accept the decision gracefully when it goes against them. Includes a case where they were wrong.
And then they askTell me about a time you pushed back and it turned out they were right.
What is your relationship with the design system: user, contributor, or owner?
Scored against: Design systems, tooling & processA strong answer contains: An honest position, plus a specific contribution or a considered exception: the component they added, the pattern they deliberately broke and why, how they kept it in sync with what engineering actually built.
And then they askWhen is it right to break the system?
How do you know your design worked?
Scored against: Design impact & measurementA strong answer contains: A named metric or usability measure with a before and after, or an honest "nobody measured it and here is what I would set up now". Designers who have never looked past launch are common; those who have are not.
And then they askWhat would you have measured if you could have measured anything?
Reading the questions is the easy half. Try answering three of them out loud, to someone who follows up.
Try 5 minutes freeWhat your 30 minutes covers
The same shape as a real first-round interview, pitched at senior Senior Graphic Designer and scored throughout.
Warm-up, then Motivation & fit
Build rapport, settle nerves, and get a short walk-through of your background. Why this role, why this employer, and what you are actually looking for.
Your experience
Two or three real situations from your CV in depth: context, what you did, what happened, what you would change.
Pitched at senior scope: senior designer: owns complex, cross-team problems and sets quality and process standards; leads research and design strategy for a product line.
Role-specific questions
The core competencies and domain knowledge for the role, with follow-ups on anything vague.
Drawn from this role's domain: planning and running user interviews and usability tests, synthesising research into insights and design principles and information architecture and task flow design, and the rest of the competency model.
Your questions, then Wrap-up
Your questions for the interviewer, and yes, they are assessed. Next steps and a clean finish.
What changes with seniority
The questions barely change between levels. What changes is the answer they will accept.
| Junior | Mid | Senior | |
|---|---|---|---|
| Scope of ownership | Owns defined screens, features or campaign assets end to end with review; runs simple usability tests. | Owns a product area or brand stream: research, design and iteration with measurable outcomes; contributes to the design system. | Senior designer: owns complex, cross-team problems and sets quality and process standards; leads research and design strategy for a product line. |
| Tolerance for ambiguity | Handles routine design problems; escalates unclear requirements with options. | Frames ambiguous problems, proposes research and design approaches, and negotiates scope with product. | Works from business goals with no brief; defines the problem and the approach. |
| People leadership | No direct reports; collaborates with developers directly on their features. | Mentors juniors and leads critique sessions. | Leads designers on projects, coaches craft and runs critique culture. |
| Who they deal with | Product manager, developers, design lead, marketing requesters. | Product managers, engineering leads, marketing, customer support for insight, senior stakeholders reviewing work. | Heads of product and engineering, executives, external agencies or researchers. |
Where candidates lose this interview
A portfolio of final screens
Beautiful end states with no problem, no constraint and no discarded option tell the interviewer nothing about how you think. Every case study needs the brief, what you tried, what you rejected and why: the messy middle is the part being assessed.
Taste presented as reasoning
"It felt cleaner", "it's more modern", "I wanted it to breathe". Design leads probe these immediately. Tie every visual decision to hierarchy, the user's task, accessibility or the system, and the answer becomes defensible.
No unhappy paths anywhere
Portfolios full of populated, successful, wide-screen states signal a designer who has not shipped. Empty states, errors, loading, permissions and small screens are where most of the real work lives.
Research as a slide rather than a decision
Candidates describe interviews and surveys, then show a design that owes nothing to them. What is scored is the finding that changed the design, ideally an inconvenient one.
Never having lost an argument
A designer who has always been right is either very junior or not collaborating. Have a case where you pushed back and were overruled, and one where you pushed back and were wrong.
What your report would say
Every competency above scored from your own answers, the sentence that cost you quoted back, and your weakest answers rewritten the way a strong Senior Graphic Designer would have said them.
Take me through a project where research changed what you built.
- The original assumption, the method and how many people, the specific finding that broke the assumption, and what shipped instead. Best answers name a finding that was inconvenient for the roadmap
The format, not a result. Scores on your report come from what you actually said.
Is the AI interviewer realistic? See a full sample report