Career & Jobs
Design Interview Red Flags Look for the Pattern, Not a Magic Number
One extra conversation is not automatically unreasonable, and one short exercise is not automatically fair. Ask what each stage is meant to prove, what it costs you, and what the company is willing to show in return.
The short read
Ask before doing
Get the complete process, expected effort, evaluation criteria, and work-ownership terms before investing.
Judge the pattern
Unclear scope, repeated unpaid work, changing expectations, and weak reciprocity matter more than one rigid round count.
Offer an alternative
Use an existing case study or a narrower exercise when it can answer the same hiring question with less candidate burden.
Read the process as a system
An interview process is trying to reduce uncertainty for both sides. The company may want to understand craft, problem framing, collaboration, communication, or how you respond to constraints. You need evidence about the role, manager, team, decision authority, workload, and whether the organization can evaluate design responsibly.
A portfolio conversation, take-home exercise, and live working session can each answer a different question—or repeat the same test while shifting more cost to the candidate. The red flag is often not the format. It is a process that cannot explain what it still needs to learn.
Useful question
What uncertainty remains after my portfolio review, and how will this next stage help you resolve it?
Ask before investing
You are allowed to understand the commitment before agreeing to it. Clear questions are not hostility; they help both sides plan.
| Stages | What remains in the process, who attends each stage, and what decision will each one support? |
|---|---|
| Time | What effort is expected, what is the deadline, and may I timebox the work? |
| Evaluation | Which capabilities are being assessed, and what does a useful response demonstrate? |
| Work ownership | Is this a hypothetical or retired problem, and how will my materials be handled after the interview? |
| Access | What information, tools, and accommodations are available so the exercise measures the intended skill? |
Notice the answer and the manner of the answer. A team may have a demanding process and still be transparent, flexible, and respectful. A seemingly simple process can reveal risk when basic questions are treated as disloyalty.
Evaluate a take-home by relevance, scope, and risk
Is the prompt relevant?
The task should test work the role actually performs. A polished consumer app redesign may tell little about a role centered on complex internal workflows.
Can the scope fit the timebox?
A small flow, critique, prioritization exercise, or research plan can be bounded. A full discovery-to-prototype case study usually cannot.
Could the company use the result?
A current business problem, production-ready deliverables, or transfer of rights deserves closer questioning. Prefer hypothetical, retired, or clearly protected material.
Will the team discuss the work?
A conversation can reveal reasoning and let you test the team's feedback culture. Silent collection of a polished artifact provides less value to the candidate.
A live exercise should reveal collaboration, not reward performance theater
A live session can show how someone asks questions, scopes ambiguity, responds to information, and includes collaborators. It becomes less useful when the candidate is expected to perform instant visual polish, guess hidden criteria, or work without the tools and access the role normally provides.
Ask what the interviewers want to observe and whether you may think aloud, take notes, use your normal tools, or pause to organize. The exercise should measure the capability the team names—not comfort with an artificial stage.
Notice repeated signals, not isolated awkwardness
Patterns worth investigating
- The process expands after you agree
- Different interviewers describe different roles
- The exercise has no stated evaluation criteria
- The prompt resembles current company work
- Accessibility requests are resisted or ignored
- Candidates receive urgency but no timeline
- The team asks for evidence but shares little
- Feedback is promised and repeatedly withheld
One scheduling mistake can be ordinary. Several mismatches can reveal weak ownership, an undecided role, or a culture that externalizes the cost of uncertainty. Ask for clarification before treating your interpretation as proof.
Clarify, reshape, or decline
Clarify
Ask for the expected effort, decision criteria, remaining stages, and how the materials will be used.
Reshape
Offer a timeboxed response, an existing case-study walkthrough, or a discussion of how you would approach the problem instead of completing the full artifact.
Decline
When the cost, ambiguity, ownership risk, or pattern of behavior exceeds the value of continuing, withdraw briefly and professionally. You do not need to prosecute the company in your email.
If you want a quick way to organize the signals before deciding, use the Interview Red Flag Calculator. Treat the result as a conversation prompt, not a verdict.
Look for reciprocal evidence
A strong process does not only extract proof from candidates. It gives candidates access to the future manager, realistic examples of the work, clear success criteria, time for questions, and honest information about the team's constraints.
The goal is not the shortest possible interview. It is enough relevant evidence for both sides to make a decision without unnecessary labor, hidden tests, or avoidable risk.
QuestionsAnswers
Questions, answered.
A few practical details before you keep going
Share this resource
Written by
Nikki KippleProduct Designer & Design Instructor
Designer, educator, founder of The Crit. I've spent years teaching interaction design and reviewing hundreds of student portfolios. Good feedback shouldn't require being enrolled in my class — so I built a tool that gives it to everyone. Connect on LinkedIn →
Too close to your own work?
Send one screen, case study, or URL. We'll show what's working, what's getting skipped, and what to fix next.