How to Actually Run an Interview With A Graphic Designer
You have a role to fill and you're trying to figure out how to talk to someone who spends their days making things look good. I've sat on both sides of this table more times than I care to count, and most of the people asking how to do an interview with a graphic designer are doing it wrong from the start. The biggest mistake I see is treating it like a trivia test. Asking someone to name the difference between kerning and tracking doesn't tell you anything about whether they can ship work on time under pressure. It tells you they've read a design glossary. That's not the same thing.
What to Actually Do During an Interview With A Graphic Designer
Here's the framework that works. Start with their portfolio, but don't just look at the shiny final images. Pick three pieces and ask them to walk you through one specifically. I want to know which piece they chose, why they chose it, what the constraints were, who made the decisions, and what they would change if they had another week. The answer to that last question is the most useful data point in the entire conversation. People who say "I'd do nothing differently" are either lying or haven't reflected on their work enough to give an honest answer. I've seen it happen repeatedly. After the portfolio review, give them a live exercise. Not a timed test worth 40 percent of their grade like some bootcamp nonsense. A realistic scenario with a clear brief and a reasonable deadline — two to three days, done outside the interview itself. Something like redesigning a single landing page section or creating a set of social assets for a product launch with specific brand guidelines.
They should submit a Figma file or a link, not a PDF of static images. Static images hide everything that matters: layer organization, component usage, naming conventions, how they handled edge cases and responsive states. A real design file shows you how they think, not just what they produced.
Get the Full Details
The Problem With the Traditional Portfolio Review
Most people assume that a beautiful portfolio equals a good hire. It doesn't. I once hired a designer whose portfolio looked absolutely stellar — editorial layouts, branding systems, motion work. First week on the job, I learned she had never used Auto Layout in Figma, her layers were named "Rectangle 47 copy 12," and every project was built in Photoshop despite the team running a Figma-based workflow. She was a skilled compositor who had copied everything by hand because that's what she'd always done. I spent three weeks retraining her on tools that should have been baseline. That cost the team real money and delayed two product launches. The fix was simple on the back end: requiring a live file walk-through during the interview process. The second candidate I interviewed that month opened her Figma file and I knew within five minutes she was going to be functional on day one. Her portfolio looked less impressive than the first woman's, honestly. But her file structure was clean, she used components correctly, and she'd thought about design systems. So when you're doing an interview with a graphic designer, ask them to share their screen and open a recent project file. Watch how they navigate it. This alone filters out half the candidates who only know how to produce pretty pictures in isolation.
What to Ask Beyond the Portfolio
The questions that actually matter fall into three buckets: process, collaboration, and constraints. For process, ask about a time their design got cut or changed after their boss or a stakeholder saw it. How did they handle the feedback? What did they learn? Designers who can't articulate a revision story either haven't had revisions or they don't process them well. Both are red flags depending on your workplace culture. For collaboration, ask who they handed work off to and what that handoff looked like. A designer who only works in a vacuum and then "sends files" is not a team player. You want someone who talks to engineers, writes specs, and cares about implementation.
For constraints, ask about a project where the brief was vague or contradictory. The best designers thrive in ambiguity because that's what real work looks like. The ones who crumble are usually fine — they're just better suited for agencies with tight creative direction than product teams.
Red Flags and Green Flags
Watch for the candidate who only uses the word "I" when describing team projects. Design is rarely a solo sport. If they say "I designed the whole thing" for every project, either they were the only designer at a tiny startup, or they're misrepresenting what happened. Dig into this. Ask follow-up questions about what the PM did, what the copywriter contributed, what the engineer pushed back on. Green flag: someone who references real conversations with other roles. "The engineer said the animation wasn't feasible so we simplified it to a fade." That's the sound of a person who ships work, not a person who makes art and hopes it gets built. Another green flag is asking you questions about the team structure, the tool stack, and the review process. Candidates who don't ask anything are either disinterested or performing for the interview without thinking about whether the role is right for them. Either outcome is costly.
How Long This Should Take
A proper interview with a graphic designer takes about an hour for the live session, plus two to three days for the take-home exercise. Don't complain about the time investment. A bad hire costs you six to twelve months of lost productivity and potentially damaged product quality. The exercise pays for itself if it prevents one mis-hire. If you're short on time, cut the portfolio presentation down to 20 minutes and spend the remaining 40 on a live design critique of their file. Pull up a component on screen and ask them to explain how it works, how it connects to the rest of the system, and what happens at breakpoint transitions. This takes less effort than grading a take-home and reveals more truth.
When This Process Doesn't Work
Be honest about the limits of this approach. The live file review doesn't tell you how someone works under acute deadline pressure. It doesn't show you their attitude in a Slack channel or how they react when a stakeholder asks for "just one more revision." Those things reveal themselves over the first 30 days on the job, and there's no shortcut around that. The take-home exercise also has a bias toward candidates who have spare time. Some of the best designers I've met were between contracts and had a week to pour into a spec exercise. Others had full-time jobs and needed to complete it in evenings. The quality of output from the exhausted candidate was often worse, not because they lacked skill but because they lacked bandwidth. I learned to weight the file quality and decision-making over polish in those situations. And if you're hiring for a very specialized role — say, someone who needs deep motion design or 3D skills — a general design exercise won't test the right things. Build a specialized task for that. Nothing wrong with that.
The point is just that an interview with a graphic designer is never a perfect predictor. It's a filter, and like any filter, it lets some things through and catches others. The goal isn't perfection. It's better odds than flipping a coin and hoping for the best.
