The short answer
Creative and design interviews for UX, UI, copywriting, art direction and production roles test your process as much as your portfolio: user research, iteration, handling feedback and collaboration with developers and stakeholders. Expect portfolio walkthroughs told in STAR form and scenarios like conflicting stakeholder feedback. Show rationale and measured impact, not just visuals.
Key takeaways
- Interviewers judge your process and reasoning, not only the final visuals.
- Walk through case studies as stories, from research insight to iteration to outcome.
- Show how you handle critique and conflicting stakeholder feedback without ego.
- Mention measurable impact, such as task success, conversion or accessibility results.
- Dismissing developers or feedback, and aesthetics without a user problem, are red flags.
Focus areas
- User-centered design and research
- Design process and problem-solving
- Collaboration and stakeholder management
- Feedback reception and growth mindset
- Portfolio and case study quality
- Measuring design impact
- Balancing creativity with constraints
Scenarios you may get
- Stakeholder wants bright colors but data shows muted performs better
- Scope creep mid-sprint with 5 new feature requests
- Accessibility requirements conflict with visual direction
- Design challenge with 2-hour deadline
- 8 stakeholders with different feedback to synthesize
- Portfolio has beautiful work but limited process documentation
What interviewers look for
- User research insights driving design
- Multiple iterations with clear rationale
- Collaboration examples with conflict resolution
- Measurable impact or outcomes
- Honest about constraints and adaptations
Red flags
- Aesthetic-first design without user problem backing
- Dismissive of developer or product input
- Defensive about feedback from stakeholders
- Shallow portfolio with no process shown
- Cannot cite any data on design impact
- Prefers working alone, resists collaboration
Terms to know
- user research
- user journey
- wireframe
- prototype
- design system
- usability testing
- A/B testing
- accessibility
- WCAG
- task success rate
Roles
ux-designer
Creative and design interviews, for UX and UI designers, copywriters, art directors and creative production roles, are about how you get to good work, not just the work itself. The interviewer wants to hear how user research shaped your direction, why you made each decision, how you handled critique and how you worked with developers, product managers and clients.
In Offermic, the creative interviewer plays a Creative Director at a digital agency: user-focused, collaborative and interested in process clarity and measurable impact.
What do design interviewers look for?
- Research-driven design. Insights from users that changed your direction.
- Iteration with rationale. What changed between versions and why.
- Collaboration, including how you resolved disagreements.
- Measured impact: task success, conversion, engagement, accessibility.
- Honesty about constraints and how you adapted.
Strong candidates walk through projects step by step, talk positively about engineers, show how their thinking evolved after feedback and admit mistakes.
How is a design interview structured?
Offermic’s creative profile weights a session roughly like this:
| Question type | Share in Offermic’s creative profile | Example |
|---|---|---|
| Behavioral | About 40% | “Tell me about defending a design decision to a stakeholder.” |
| Scenario | About 30% | “Eight stakeholders gave you conflicting feedback.” |
| Situational | About 20% | “Accessibility rules clash with the brand’s visual direction.” |
| Closing | About 10% | Your questions |
The profile does not run live design exercises and avoids critiquing competitors’ designs or proprietary design systems.
Common design interview questions
- “Walk me through your research phase for a project. What did you learn that changed your direction?”
- “Tell me about defending a design decision to a stakeholder who disagreed.” See persuading someone.
- “Describe a project where you iterated multiple times. What drove each iteration?”
- “Give me an example of collaborating with a developer through technical constraints.” See collaboration example.
- “Walk me through handling design feedback in a critique. How do you separate ego from feedback?” See handling negative feedback.
Scenarios to rehearse: a stakeholder who wants bright colors when data favors a muted palette, mid-sprint scope creep, accessibility requirements that conflict with visual direction, a two-hour design deadline and synthesizing feedback from eight stakeholders.
How to answer design questions
Use the STAR method as a case-study walkthrough: the problem (Situation), your role (Task), research, decisions and iterations (Action), and outcome (Result). Put the weight on the reasoning behind decisions.
Two references help you speak precisely. Nielsen Norman Group defines usability as a quality attribute that assesses how easy user interfaces are to use. The W3C develops the Web Content Accessibility Guidelines (WCAG) with the goal of a single shared standard for web content accessibility, so naming the WCAG level you designed to is a concrete, credible detail.
Situation
Example answer (product designer, fintech app): many new users abandoned onboarding at the identity verification step, and the product team wanted a full redesign.
Task
I led the design work and had one sprint to find the cause before committing to a redesign.
Action
I watched session recordings and ran five quick usability tests, which showed that users did not understand why we needed their ID and stopped when the camera opened. Instead of a full redesign, I added a short explanation screen, a progress indicator and an option to finish later, and checked contrast and screen-reader labels against WCAG AA. I reviewed the build with the developer twice before release.
Result
Completion of that step rose noticeably in the following month, and support tickets about verification dropped. The explanation-first pattern became part of our design system.
Worked scenario: eight stakeholders, eight opinions
Question: “After a design review, you receive conflicting feedback from eight stakeholders. How do you move forward?” A SPAR answer:
- Situation: Some feedback is about user needs, some about personal taste, and some contradicts other comments. Trying to satisfy everyone will produce a worse design.
- Proposal: Sort the feedback against the project goals and the user research, and get one decision maker to confirm priorities.
- Action: Group comments into themes, mark each as supported by research, a business constraint or a preference, and share the summary. Agree with the product owner which issues to address, test the most contested question with a few users, and explain the reasoning back to stakeholders.
- Result: A focused revision, stakeholders who can see their input was considered, and a design that still serves the user.
Red flags that sink design answers
- Beautiful work with no user problem behind it.
- Talking down about developers or product managers.
- Getting defensive when the interviewer questions a decision.
- A portfolio that shows only final screens, no process.
- No evidence of impact, not even qualitative.
- Preferring to work alone.
Metrics and terms worth knowing
| Metric | What it shows |
|---|---|
| Task success rate | Share of users who complete a task in testing |
| Time on task | How long a task takes |
| Conversion rate | Share of users who complete a target action |
| Error rate | How often users make mistakes in a flow |
| Accessibility score | Conformance with WCAG criteria |
| Design system adoption | How widely shared components are used |
How to prepare for a design interview
- Choose two or three case studies that show different strengths, such as research, systems and stakeholder work.
- Rehearse each walkthrough aloud in about five minutes, then practice going deeper on one decision.
- Prepare a critique story where feedback changed your design.
- Ask about the design team’s size, research practice and how design is involved in roadmap decisions.
Related roles and pages
Role bank: UX designer. Related hubs: marketing and tech. Also useful: presentation you gave.
Questions people also ask
How long should a portfolio walkthrough be?
For one case study, aim for about five minutes, covering the problem, research, key decisions, iterations and the result. Be ready to go deeper on any step.
What if I don't have metrics for my design work?
Use what you have, such as usability test findings, qualitative feedback, adoption or support ticket changes, and say what you would measure next time.
Does Offermic include live design exercises?
No. The creative interviewer asks about your process and decisions in conversation. Practice whiteboard or take-home exercises separately if your target role uses them.
Sources
- WCAG 2 Overview, W3C Web Accessibility Initiative
- Usability 101: Introduction to Usability, Nielsen Norman Group
Written byCan Garip, Founder
Can Garip is the founder and developer of this app. He builds the AI mock interview product and writes its interview preparation guides.
Drafted with AI assistance, then edited and fact-checked by the author.

Say it out loud before the real thing
Answer this question to an AI interviewer and get a 0–100 score with a rewritten answer in the same structure.