Why pre-screen senior designers before the portfolio review
A portfolio at this level shows outcomes without the arguments behind them: why that layout, what was rejected, what the stakeholder wanted instead. That reasoning is the difference between a senior designer and a productive one. Designers worth hiring can walk through a decision and a rejection without defensiveness. A short screen asks for both, before anyone spends an hour reviewing files.
What actually matters when screening Senior Designer candidates
- 01
Portfolio
Ask them to walk through three case studies showing their own contribution: brand identity systems, campaign artwork, or product UI, with the business problem and outcome named.
- 02
Craft and rationale
Probe typographic and grid decisions, colour contrast to WCAG AA, print prep (bleeds, CMYK, spot inks), and how they maintain component libraries in Figma.
- 03
Feedback and iteration
Test how they handle a marketing director rejecting a direction late; look for critique rituals, version control, and evidence of killing their favourite concept.
- 04
Working with the brief
Judge how they interrogate a vague brief: budget, channel specs, deadlines, stakeholder sign-off chain, and how they brief junior designers or external illustrators.
Pre-screening questions to ask Senior Designer candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Work that shipped
3 questions01What is the most challenging design project you have worked on?
Listen forA real constraint such as a difficult brief or a technical limit, with the design response explained.
Challenges described as deadlines or difficult clients, with no design problem identified.
02Do you have experience with digital and web design?
Listen forDigital work delivered with implementation constraints understood, not designs handed over as images.
Designs produced with no regard for how they would be built, or no engagement with developers.
03Can you discuss your experience across print and digital work?
Listen forThe differing constraints understood, including colour management, resolution and production limits in print.
Both claimed equally with no distinction, or print production requirements not understood.
Decisions with reasoning
3 questions04What is your process for starting a new design project?
Listen forThe problem and audience established before any visual work, with the brief interrogated first.
Process starting from visual exploration, or briefs accepted without clarifying questions.
05Do you have experience designing across different platforms and screen sizes?
Listen forDesigns that work at the extremes, with behaviour at awkward intermediate sizes considered.
Designs produced at two fixed widths, or platform conventions ignored for visual consistency.
06Do you have experience designing for accessibility?
Listen forContrast, type size and focus states considered during design rather than corrected after an audit.
Accessibility treated as a compliance step, or contrast decided by appearance alone.
Develops other designers
3 questions07Do you have experience leading or mentoring other designers?
Listen forFeedback given that teaches the reasoning, with named designers who improved under them.
Junior work redone rather than critiqued, or no designer they developed.
08How do you handle feedback and criticism of your designs?
Listen forFeedback separated into taste and problem, with the underlying concern addressed rather than the note.
Feedback described as interference, or every note implemented without judgement.
09Can you describe your experience working with teams across functions?
Listen forEngineering and commercial constraints treated as inputs, with a design changed because of them.
Other functions described as obstacles, or no design changed by a technical constraint.
Standard held
3 questions10How do you incorporate a company's brand identity into your work?
Listen forBrand understood as a system with rules, and extended coherently rather than reinterpreted each time.
Brand treated as a colour palette, or personal style applied over an established identity.
11Do you have experience creating design guidelines and maintaining consistency?
Listen forGuidelines others actually used, with governance for how new work is checked against them.
Guidelines produced and ignored, or consistency maintained only by them reviewing everything.
12How do you measure whether a design was successful?
Listen forOutcome measures such as conversion, comprehension or task success, agreed before the work began.
Success judged by internal approval or awards, with no user or business outcome measured.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Shows depth beyond pretty screens: original files, before and after states, and measurable outcomes such as conversion lift or rebrand rollout.
Craft and rationale
25%5Explains kerning, type scale, and file setup choices in production terms, and defends each decision against the brief rather than taste.
Feedback and iteration
25%5Treats feedback as input, separates subjective preference from brief conflict, and shows concrete iterations that improved on the original route.
Working with the brief
15%5Writes back a sharpened brief with questions and constraints, then delegates and reviews junior work without redoing it themselves.
A portfolio shows the outcome, not the argument that got there. A one-way video screen asks about work that was rejected.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async, alongside a portfolio. Enough to establish shipped work, test their reasoning, and check leadership and brand judgement.
What should I ask for alongside the screen?
A portfolio with a note on what was theirs in each piece. Senior work is usually collaborative, and the useful detail is which decisions they made rather than which files they touched.
Evaluating answers
What is the strongest signal when screening this role?
Work that was rejected and what they did. Senior designers describe the reasoning on both sides. Anyone whose work was always accepted has either not pushed or is not telling you.
How do I judge whether they can lead?
Ask how they give feedback to a junior designer. Real answers describe teaching the reasoning rather than fixing the file. Anyone who redoes the work is producing rather than developing.
























