Six question sets for hiring a UI designer: core craft, the portfolio walkthrough, design systems and states, handoff, accessibility, and a 1-to-5 scorecard. Every question comes with why it is worth asking and what a strong answer sounds like. Download as DOCX.
The first UI designer I ever interviewed showed me the most beautiful portfolio I had seen that year, and I hired them almost on the spot. Six weeks later we had gorgeous screens that our engineer could not build, no error states anywhere, and a phone layout that nobody had drawn. The portfolio was real. My interview was not.
The problem is that a UI portfolio is designed to be persuasive, and a founder without a design background has no defense against a persuasive portfolio. So you have to stop judging pictures and start judging reasoning: why this hierarchy, what was rejected, which states exist, what changed between the file and the live product. Those answers are legible to anyone.
At FirstHR we build for small businesses that hire without an HR department, where the founder is usually the only interviewer in the room. This page gives you 36 interviewer questions across six sets, each with why it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard you can fill in the same day.
TL;DR
Interview a UI designer on six things: visual craft, reasoning, systems and states, handoff to engineering, accessibility and responsive judgment, and how they take feedback. The strongest single question is what do you decide first on a new screen, layout, type, or color, because the order tells you whether they build structure or decorate it. Score all seven areas from 1 to 5 the same day, on written evidence.
What to Assess in a UI Designer
A UI designer owns the surface of your product: layout, typography, color, components, states, and the system that keeps them consistent as the product grows. The interview should test six areas, and only one of them is the part you can see in a portfolio.
That imbalance is why UI hires go wrong. The visual craft is on display from the first slide, while systems thinking, handoff quality, accessibility, and the ability to take a blunt note from a founder are all invisible until you ask about them directly. Every one of them costs you money when it is missing.
Visual craft
Hierarchy, type, spacing
Whether the candidate builds structure or decorates it. Ask what they decide first on a new screen and how they set a type scale and a spacing unit.
Systems thinking
Components and states
Whether the work survives a growing product: reusable components, every state designed, and naming another person can work inside.
Handoff
Can engineering build it?
The gap between a beautiful file and a shipped screen. Specs, states, responsive behavior, and availability for the questions that follow.
Accessibility
Contrast, keyboard, labels
Factual questions with right answers. Contrast ratios, visible focus states, and heading structure separate practice from vocabulary.
Feedback and ownership
How they take a note
You will give feedback in plain language, not design language. How the candidate receives it decides whether the hire works past month three.
Scorecard
Score, do not guess
A seven-area rubric scored 1 to 5 with written evidence, so the decision rests on the interview rather than on the best-looking portfolio.
Weight these to the job you have. If this person will be your only designer, range and self-direction matter more than depth in any one area. If they are joining an existing product and an engineer, systems and handoff carry the most weight.
UI, UX, or Product Designer?
UI is the visual and interactive surface, UX is the reasoning and structure underneath it, and product design usually covers both plus the business trade-offs. Interviewing for one and hiring for the other is the most expensive mistake in this process, so settle the question before you write a single question.
Role
Owns
Hire this one when
UI designer
Visual language, layout, typography, components, states, design system
Flows work but the product looks unfinished or inconsistent
UX designer
Problem framing, flows, information structure, prototypes, usability testing
Customers cannot finish tasks, or you keep guessing what to build
UI/UX designer
Both, at a level suited to a smaller product
You need one person covering the whole product experience
Product designer
UI plus UX plus roadmap and business trade-offs
You want one senior person owning the product end to end
Most small businesses need the hybrid, which is why the combined UI/UX role is so common at this size. If the gap you actually have is research and flows rather than surface, run the UX designer question sets instead of these.
Say the split out loud in the interview and ask which side the candidate is genuinely stronger in. Honest designers answer in a sentence. The ones who claim equal depth in both are usually stronger in neither. If the posting is not written yet, start from the UI designer job description templates and build the question set from the duties you list there.
Which Question Set Should You Use?
Use the core set with every candidate, then add the sets that match the scope of the job and the round you are in. Most small businesses run the core questions in round one, the portfolio walkthrough in round two, and handoff plus systems in round three with an engineer present.
Set 1: Core Questions
Every candidate
Eight questions on craft, process, and self-awareness, each with why it is worth asking and what a strong answer sounds like. Use it in the first conversation.
Set 2: Portfolio Walkthrough
The real interview
Seven prompts that make a candidate explain decisions rather than show pictures: the brief, their own contribution, the rejected alternative, and what shipped.
Set 3: Systems and States
Product roles
Seven questions on reusable components, error and empty states, naming, system rules, and theming. Weight this heavily for a product that keeps growing.
Set 4: Handoff and Collaboration
With your engineer
Seven questions on specs, working with engineering under a deadline, presenting to non-designers, and resolving conflicting direction without a design manager.
Set 5: Accessibility and Responsive
The skipped set
Seven questions on contrast, keyboard operation, screen readers, phone layouts, and working inside a brand somebody else built.
Set 6: Scorecard and Red Flags
Score, do not guess
A seven-area rubric scored 1 to 5 with space for evidence, plus a nine-item red-flag checklist. Use it with every set above.
Match the Set to the Round
First conversation with anyone: Core Questions. Second round, the deepest hour of the process: Portfolio Walkthrough. A product that keeps growing: Systems and States. Round with your engineer: Handoff and Collaboration. Any product customers actually use: Accessibility and Responsive. Running through all of them and deciding: the Scorecard, which works with every set above. Add general behavioral questions only where they earn their place, since the sets here already cover most of that ground.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Download all six as a single Word document, or copy the sets you need one at a time. Every question lists why it is worth asking and what a strong answer sounds like, and the last file is the scoring rubric with a red-flag checklist.
Download All 6 UI Designer Question Sets
Five question sets plus a 1-to-5 scorecard and red-flag checklist. All in one DOCX.
Set 1: Core UI Designer Questions
Eight questions on craft, process, and self-awareness for every candidate. Roughly 30 minutes with follow-ups, and the answers are legible whether or not you have a design background.
Core UI Designer Interview Questions
CORE UI DESIGNER INTERVIEW QUESTIONS
Candidate: __
Role and level: __
Interviewer: __
Date: _
HOW TO USE THIS SET
Ask every candidate for this job the same core questions, in the same order, and
write the answers down as you go. Eight questions is roughly 30 minutes with
follow-ups. Each question below lists why it is worth asking and what a strong
answer sounds like, so you can judge interface craft without being a designer
yourself.
QUESTIONS
1. Describe the interface you are proudest of. What made it good?
Why ask: It reveals what the candidate thinks quality means before you tell
them what you value.
Strong answer: Talks about clarity, hierarchy, and how easily people got
through the screen. Weak answers only describe how it looked.
2. Walk me through how you turn a rough requirement into a finished screen.
Why ask: A UI designer at a small company rarely gets a clean spec, so the
process from vague request to shipped screen is the job.
Strong answer: Asks questions first, sketches structure before styling,
checks the existing components, and shows work early rather than at the end.
3. What do you decide first on a new screen: layout, type, or color?
Why ask: The order tells you whether the candidate designs structure or
decorates it.
Strong answer: Structure and hierarchy first, type scale second, color last
and sparingly. Someone who opens with color choices is usually styling.
4. How do you set a type scale and a spacing system on a new product?
Why ask: Type and spacing are where amateur interfaces fall apart, and both
are checkable claims.
Strong answer: Names a base size, a small set of steps, and a spacing unit
they hold to. Vague answers about what feels right are a warning sign.
5. Show me a screen you would redesign today. What would you change and why?
Why ask: It tests self-criticism and whether the candidate can separate a
design decision from their ego.
Strong answer: Names a specific decision, the reason it was wrong, and what
they learned. Candidates who cannot name one are rarely reflective.
6. How do you know a design is finished?
Why ask: Unfinished interface work is the most common cost at a small
company, because states nobody designed get invented by an engineer.
Strong answer: Mentions all the states, responsive behavior, contrast checks,
and a handoff another person can build from without asking.
7. Tell me about a time you disagreed with feedback on a design.
Why ask: You will give this person feedback that is not expressed in design
language, and how they receive it decides whether the hire works.
Strong answer: Argues the case with reasoning or evidence, then commits to
the decision. Silent compliance and open resistance are both problems.
8. What are you slower at than you would like to be?
Why ask: An honest gap tells you what to cover with the rest of the team or
with a contractor.
Strong answer: A specific, credible gap such as motion, illustration, or
research, with what they do about it. Nobody is strong at everything.
NOTES
[Write down the exact examples and any follow-up answers here.]
Set 2: Portfolio and Screen Walkthrough
Seven prompts that make a candidate explain decisions rather than show pictures. Pick the two pieces closest to your product and spend the time there.
Portfolio and Screen Walkthrough Questions
UI DESIGNER PORTFOLIO WALKTHROUGH
Candidate: __
Projects reviewed: __
Date: _
HOW TO USE THIS SET
The portfolio walkthrough is the real interview for any UI role. Pick the two
pieces closest to what you are hiring for, not the two the candidate leads with,
and spend 30 to 40 minutes on those. You are listening for decisions and reasons,
not admiring the pictures.
QUESTIONS
1. What was the brief, and who was the audience for this screen?
Why ask: A designer who cannot restate the problem was probably handed
finished decisions.
Strong answer: Describes the user, the business goal, and the constraint
(deadline, platform, existing brand) in one clear paragraph.
2. Which parts of this did you personally design?
Why ask: Portfolios routinely include team and agency work with no credit
split.
Strong answer: Draws a clean line between their work and everyone else, and
volunteers it rather than waiting to be asked.
3. Why this layout and this hierarchy rather than another one?
Why ask: Hierarchy is the core skill in interface design and it is invisible
until you ask.
Strong answer: Explains what the user must see first, second, and third, and
how the layout enforces that order.
4. Show me an alternative you rejected. Why did you drop it?
Why ask: Real design work leaves rejected versions behind. An absence of them
suggests a single pass with no exploration.
Strong answer: Has the alternative to hand and gives a concrete reason it
lost, ideally from feedback or testing rather than taste.
5. Did this ship? What changed between your file and the live version?
Why ask: The gap between the portfolio image and the shipped product is where
you learn how the candidate works with engineers.
Strong answer: Knows exactly what changed and why, and does not blame
engineering for the difference.
6. What happened after it launched?
Why ask: It separates designers who follow their work into production from
those who hand off and move on.
Strong answer: Cites something measured (task completion, support tickets,
signups) or at least an honest account of the feedback that came back.
7. Open the live product on your phone and talk me through it.
Why ask: It is the fastest way to test responsive judgment and to see whether
the polished image survives contact with a real device.
Strong answer: Comfortable doing it, explains the small-screen decisions, and
points out weaknesses before you do.
NOTES
[Record which pieces you reviewed and the strongest and weakest answers.]
Set 3: Design System, Components, and States
Seven questions on reusable components, error and empty states, naming, when to break the system, and theming. Weight this set heavily for a product that keeps growing.
Design System, Components, and States Questions
UI DESIGNER: DESIGN SYSTEM, COMPONENTS, AND STATES
Candidate: __
Date: _
HOW TO USE THIS SET
This is the set that separates a UI designer from someone who makes attractive
mockups. Ask it of every candidate who will own screens in a product that keeps
growing. If your product is one marketing page, weight this set lower.
QUESTIONS
1. What goes into a component before you would call it reusable?
Why ask: Reuse is what keeps an interface consistent once more than one
person touches it.
Strong answer: Talks about variants, sizes, states, spacing rules, and naming
that someone else can find. Not just a saved copy of a button.
2. Which states do you design for a form field, and which get forgotten?
Why ask: Missing states are the number one source of rework, because an
engineer will invent whatever is not in the file.
Strong answer: Lists default, hover, focus, filled, disabled, error, and the
error message itself, plus loading where it applies.
3. How do you design the empty state of a screen?
Why ask: Empty states are the first thing a new customer sees, and most
candidates have never thought about them.
Strong answer: Treats it as onboarding: explains what goes here, why it
matters, and gives one clear action.
4. How do you keep a design system consistent as the product grows?
Why ask: Consistency decays fast at a small company where speed wins.
Strong answer: Describes a rule for when to extend an existing component
versus create a new one, and some form of periodic cleanup.
5. When is it right to break the system?
Why ask: A designer who never breaks the rules produces rigid products, and
one who always breaks them produces chaos.
Strong answer: Gives a specific case, a marketing surface or a rare flow,
and says how the exception was contained.
6. How do you name layers, components, and files so someone else can work in
them?
Why ask: File hygiene is invisible in a portfolio and expensive when it is
missing.
Strong answer: Has an actual convention and can describe it in a sentence.
Offer to open a real file if the candidate is willing.
7. How do you handle dark mode or theming, if the product needs it?
Why ask: Theming is a structural decision, not a color swap, and getting it
wrong late is costly.
Strong answer: Talks about semantic tokens and roles rather than picking
darker colors screen by screen.
NOTES
[Record how the candidate described states, naming, and system rules.]
Set 4: Handoff, Collaboration, and Tooling
Seven questions on specs, working with engineering under a deadline, presenting to people who are not designers, and resolving conflicting direction without a design manager in the middle.
Handoff, Collaboration, and Tooling Questions
UI DESIGNER: HANDOFF, COLLABORATION, AND TOOLING
Candidate: __
Date: _
HOW TO USE THIS SET
At a small company the UI designer sits between the founder, the engineers, and
whoever owns the brand. This set tests whether their work arrives in a form other
people can use. Ask it in the round where the engineer or the founder is present.
QUESTIONS
1. What does a good handoff to an engineer include, from your side?
Why ask: Handoff quality decides how much of your engineering time is spent
guessing.
Strong answer: Specs for spacing and type, every state, responsive behavior,
asset export, and a note on edge cases. Then availability for questions.
2. An engineer says your design cannot be built in the time available. What do
you do?
Why ask: It happens constantly at a small company and the response tells you
whether the person is a partner or an obstacle.
Strong answer: Asks what specifically is expensive, then proposes a simpler
version that keeps the important part. Never simply insists.
3. How do you present work to someone who is not a designer?
Why ask: Your founders and salespeople are the audience for design reviews,
not other designers.
Strong answer: Frames the problem first, shows the work second, and asks for
decisions rather than opinions on color.
4. Two stakeholders give you opposite direction. How do you resolve it?
Why ask: With no design manager in the middle, the designer has to resolve
this themselves.
Strong answer: Gets both in the same conversation, restates the goal, and
pushes for one named decision maker.
5. What tools do you work in, and how deep do you go in each?
Why ask: Tool claims are cheap and easy to verify in a working session.
Strong answer: Specific about the main design tool, prototyping, and any
handoff or version practice. Honest about what they only touch occasionally.
6. How much front end code can you read or write?
Why ask: Not a requirement, but it changes how much translation your team has
to do.
Strong answer: An honest range, from none to comfortable in the browser. Both
are fine; a bluff that collapses later is not.
7. Tell me about a project that went badly. What was your part in it?
Why ask: Ownership is the single best predictor of how the person behaves in
month six.
Strong answer: Names their own contribution to the problem without
performing guilt, and describes what they do differently now.
NOTES
[Record the handoff description in the candidate’s own words.]
Set 5: Accessibility, Responsive, and Brand
Seven questions with checkable answers: contrast ratios, keyboard operation, screen readers, phone layouts, and extending a brand somebody else built.
Accessibility, Responsive, and Brand Questions
UI DESIGNER: ACCESSIBILITY, RESPONSIVE, AND BRAND
Candidate: __
Date: _
HOW TO USE THIS SET
These three areas get skipped in most interview lists and each one turns into a
bill later: an inaccessible product, a broken phone layout, or a brand that drifts
in every new screen. Six to seven questions, 20 minutes.
QUESTIONS
1. How do you check color contrast, and what ratio do you target?
Why ask: It is a factual question with a right answer, so it separates real
practice from vocabulary.
Strong answer: Names a contrast checker and a ratio target for body text, and
treats it as a constraint on the palette rather than a final audit.
2. Can someone use your interface with a keyboard alone?
Why ask: Keyboard operation is the most common accessibility failure in
interfaces designed purely visually.
Strong answer: Designs a visible focus state, thinks about tab order, and
does not rely on hover to reveal anything important.
3. How do you design for people using a screen reader?
Why ask: A designer who has never considered it will ship structures that
cannot be read aloud in a sensible order.
Strong answer: Talks about heading structure, meaningful labels on controls,
and alternative text, and knows where the engineer takes over.
4. Walk me through how you take a desktop layout down to a phone.
Why ask: Small business products are used on phones far more than founders
expect.
Strong answer: Describes what gets prioritized, what collapses, and what
changes shape, plus touch target sizes. Not simply narrower columns.
5. How do you work inside an existing brand you did not create?
Why ask: Most UI hires inherit a brand and have to extend it rather than
replace it.
Strong answer: Learns the rules first, extends them consistently, and raises
gaps rather than quietly inventing new colors and type.
6. What would you do if our brand colors fail contrast requirements?
Why ask: It is a real conflict that comes up in almost every small business
product.
Strong answer: Keeps the brand for large display uses, introduces an
accessible variant for interface text, and documents the rule.
7. Which of our screens would you fix first, and why that one?
Why ask: It tests judgment on your actual product and shows whether the
candidate prepared.
Strong answer: Picks a high-traffic or high-friction screen, gives a reason
tied to users or revenue, and does not simply say it looks dated.
NOTES
[Record the accessibility answers verbatim; they are easy to verify later.]
Set 6: Scorecard and Red Flags
A seven-area rubric scored 1 to 5 with space for written evidence, plus a nine-item red-flag checklist. The asset most interview-question lists leave out.
UI Designer Scorecard and Red Flags
UI DESIGNER INTERVIEW SCORECARD
Candidate: __
Interviewer: __
Date: _
Score each area from 1 (poor) to 5 (excellent) and write one line of evidence
from the interview. Fill this in the same day, before you discuss the candidate
Fit for the scope of this job Score: [ 1 2 3 4 5 ]
Evidence: __
SUMMARY
Total score: ______ / 35
Recommendation: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Strongest evidence: __
Biggest concern: __
Interviewer signature: __
RED FLAGS
•Cannot explain a single decision, only describe what was made.
•Portfolio contains no work that shipped, or the candidate does not know what
changed between the file and the live product.
•Talks about color and trends but never about hierarchy or states.
•Has never designed an error state, an empty state, or a loading state.
•Cannot say which parts of a team project were personally theirs.
•Describes engineers as the reason designs get ruined.
•No answer at all on contrast, keyboard use, or small screens.
•Dismisses your brand or your existing product in the first ten minutes.
•Will not open a working file or talk through one on screen.
INTERVIEWER REMINDER
If more than one person interviews, everyone scores independently before the
group talks. Discuss the written evidence first, then the gaps. This keeps one
strong impression from deciding the hire on its own.
Running the Portfolio Walkthrough
Run the walkthrough on your terms, not the candidate's. Pick the two pieces closest to what you are hiring for, ignore the showreel, and spend 30 to 40 minutes on those two. A rehearsed presentation tells you almost nothing; an unrehearsed conversation about two specific screens tells you almost everything.
The sequence that works is the same every time: what was the brief, which parts did you personally design, why this hierarchy, what did you reject, did it ship, and what changed before it did. Then ask what happened after launch. Six questions, one project, and you will know more than an hour of general conversation would give you.
Ask this
Because
What was the brief and who was it for?
A designer who cannot restate the problem was handed finished decisions
Which parts did you personally design?
Team and agency work appears in portfolios with no credit split
Why this hierarchy rather than another?
Hierarchy is the core skill and it is invisible until you ask
Show me the version you rejected
Real design leaves alternatives behind; one pass means no exploration
Did it ship, and what changed?
The gap between the file and the live product is where handoff shows
Open it on your phone now
The fastest test of responsive judgment and of a polished image
Close the walkthrough by asking which screen of yours they would fix first and why that one. Candidates who prepared will have looked at your product. The reason they give tells you whether they think in terms of users and revenue or in terms of taste.
Judging Interface Craft Without a Design Background
You do not need to be a designer to score this interview, but you do need to change what you are grading. Grade the reasoning and the facts, both of which are legible to anyone, and treat the visuals as the least reliable signal in the room.
Reasoning is testable with one follow-up: why. Ask it twice on the same screen and a strong candidate keeps going deeper, while a weak one runs out of answers by the second round and retreats to what looked better. Facts are even easier, because contrast ratios, form field states, and touch target sizes have right answers you can look up afterward.
Signals of real craft
Decides structure and hierarchy before color
Names a type scale and a spacing unit and holds to them
Designs error, empty, loading, and disabled states
Signals of reasoning
Explains why, not only what, on every screen
Has a rejected alternative and a reason it lost
Knows what changed between the file and the live product
Signals of rigor
Checks contrast as a constraint, not an afterthought
Designs a visible focus state and keyboard order
Opens the work on a phone without being prompted
Warning signs
Only talks about trends, tools, and color
Cannot separate personal work from team work
Blames engineering for every compromise
If you can bring in one design-literate person for a single round, do it, even a friend who works as a designer elsewhere. One outside opinion on one candidate calibrates your own scoring for every candidate after that, and it costs you an hour.
Design Exercises and Paid Test Projects
A short exercise is genuinely useful, but it has to be paid, tightly scoped, and never real production work. Two to four hours is the ceiling for a small business, and anything beyond that reads as free labor and quietly removes the strongest candidates from your pipeline.
In most cases a live working session beats a take-home. Give the candidate one of your existing screens, 60 to 90 minutes, and ask them to improve it while talking through the decisions. You learn more from watching someone reason out loud under mild pressure than from a polished file delivered three days later by an unknown number of people.
Pay for the Exercise, and Say So Up Front
Agree the fee in writing before the candidate starts, give every candidate for the same job the same brief, and confirm in writing that you will not use the output in your product unless you hire them. An unpaid multi-day exercise costs you the candidates who have other offers, which is exactly the group you are trying to reach. If the work you are asking for would be billable from a freelancer, it is billable from a candidate. Where the exercise involves a contractor rather than an employee, keep the classification distinction clean from the start. This is general information, not legal advice.
Accessibility Questions Worth Asking
Accessibility questions are the most useful part of a UI interview for a non-designer, because they have right answers. A candidate either names a contrast ratio target or does not, either designs a visible focus state or does not, and you can check the claim afterward in ten minutes.
Ask four: how do you check color contrast and what ratio do you target, can someone use your interface with a keyboard alone, how do you design for a screen reader, and what would you do if our brand colors fail contrast. The fourth is the one that separates real practice from vocabulary, because it forces a trade-off rather than a definition.
The Department of Justice publishes guidance on web accessibility under the ADA that is worth reading before you write the job description, because it shapes what you are entitled to expect from the role. A designer who treats contrast as a constraint on the palette rather than as an audit at the end will save you an expensive retrofit later.
Fair, Legal, and Structured Interviewing
A good interview is fair, legal, and structured, and the three reinforce each other. Asking the same job-related questions of everyone keeps you compliant, reduces bias, and produces better hires at the same time. Design hiring drifts unstructured more than most, because a strong portfolio pulls the conversation wherever the candidate wants it to go.
Ask about the work, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that probe them create legal risk even when they are asked as small talk. Keep away from age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. Design interviews have their own version of this trap, because portfolios and personal sites often reveal graduation years, personal projects, and religious or political work. Judge the interface decisions, not the biography attached to them. You may ask whether the candidate can perform the essential functions of the job and whether they are authorized to work in the United States. This is general information, not legal advice.
Same core questions, same order
A structured interview, where every candidate answers the same core questions and is scored on the same rubric, predicts on-the-job performance far better than an open conversation, and it is also the simplest protection against a decision built on rapport. Design hiring drifts unstructured more than most, because a strong portfolio pulls the conversation wherever the candidate wants it to go. Fix the core set in advance, keep the portfolio walkthrough for the sections designed for it, and ask the same closing questions of everyone. The six sets on this page are built so you can run the whole process from a written script.
Score independently, then discuss
When a founder, an engineer, and a marketer all sit in on the interview, have each of them score the rubric alone before anyone speaks. Design work invites strong opinions, and the loudest opinion in the room otherwise sets the tone for everyone else. Compare the written evidence first, then talk about the gaps between the scores, which is where the useful conversation is. A seven-area rubric filled in independently turns a debate about taste into a comparison of evidence, and it gives you something to look back at when the second and third candidates blur together.
Interview for the job you actually have
A first design hire at a company with no designer and a senior UI designer joining an existing design team are different interviews. If this person will be your only designer, weight range, self-direction, and comfort working without review, and ask what they would want from you in month one. If they are joining an engineer and an existing product, weight systems thinking and handoff. Be explicit about what the role must produce in the first 90 days and build the question set around that, rather than interviewing for a large-company specialist you do not need.
Same Questions, Same Rubric, Better Hires
A structured interview, where every candidate answers the same core questions and is scored against a consistent rubric, predicts on-the-job performance far more reliably than an open conversation. Asking the same job-related questions of everyone also keeps you inside the EEOC rules against basing a decision on protected characteristics. Structure is both the fairer approach and the more effective one.
Portfolios and personal sites carry more incidental personal information than a resume does: graduation years, personal projects, political and religious work. Judge the interface decisions and leave the biography attached to them out of the scoring. A list of questions employers cannot ask is worth reading before the first interview. This is general information, not legal advice.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Score seven areas from 1 to 5 the same day, with one line of written evidence under each. Filling in a rubric a week later, from memory, after three candidates have blurred together, is the same as not scoring at all.
Scoring area
What a 5 looks like
Visual craft
Structure and hierarchy first, a named type scale and spacing unit
Reasoning
Explains why on every screen and has the rejected alternative to hand
Systems thinking
Components with variants and states, and a naming convention
Handoff and collaboration
Specs, states, responsive notes, and stays available for questions
Accessibility and responsive
Contrast targets, focus states, and real phone layout decisions
Feedback and ownership
Argues the case, then commits, and owns their part when it went badly
Fit for this job
Honest about range and about what they would need in month one
The biggest red flag is a candidate who describes what they made but never why. Ask twice on a different piece before you conclude, because interview nerves are real, but a designer who does not reason out loud will not survive your feedback either. The full red-flag checklist ships with the scorecard, and the general interview red flags guide covers the ones that are not specific to design.
UI Designer Pay
Federal survey data puts the median for the occupation that covers UI designers at $104,000 a year, but the band around it is unusually wide, so the national median is a poor anchor for a small business. Benchmark to your market and to the scope of the job you are actually filling.
Median $104,000 a Year (BLS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), web and digital interface designers, the occupation that covers UI, UX, and interaction designers, had a median annual wage of $104,000. The lowest 10 percent earned under $53,750 and the highest 10 percent over $201,550, with quartiles at $73,290 and $158,820.
Occupation (BLS, May 2025)
10th percentile
Median
90th percentile
Web and digital interface designers
$53,750
$104,000
$201,550
Graphic designers
$39,520
$62,960
$104,910
Most small businesses land nearer the lower quartile than the median, particularly for a first design hire who is not expected to lead a team. Use salary benchmarking against your own market rather than the national figure, and check whether your state requires a pay range in the posting under pay transparency law.
A freelancer or agency is billed by project, by phase, or by hour and only while working, which fits a business with irregular design volume better than a salary plus benefits and overhead. If you go that route, the ownership and licensing questions in the sets above matter more, not less.
Interviewing a UI Designer Without an HR Department
At a company with a design team, a UI candidate is reviewed by people who can read a file and spot a broken type scale in ten seconds. At a small business, the founder usually runs the interview alone, between everything else, with no way to check the claims being made. Here is how to close that gap.
You are judging design craft without being a designer
At a company with a design team, a UI candidate is reviewed by people who can read a file and spot a broken type scale in ten seconds. At a small business, the founder is usually the only interviewer, and the honest worry is being sold a beautiful portfolio by someone who cannot ship. The fix is to stop judging the pictures and start judging the reasoning: ask why this hierarchy, what was rejected, which states exist, what changed before launch. Those answers are legible to anyone, and the sets on this page are written so you can score them without a design background.
One designer covers what three people cover elsewhere
Your first UI hire will probably also touch the marketing site, the pitch deck, the app icon, and whatever the sales team needs by Friday. Interview for that reality instead of for a narrow product specialist. Ask which formats they have personally shipped and which they have not, how they decide what to do first when three people ask at once, and how comfortable they are with nobody senior reviewing their work. Honest range beats claimed range, and the candidate who admits a gap is usually the one who will tell you the truth in month six as well.
The interview is the easy part; the hire is where it gets real
Once you choose someone, the work turns into hiring them properly: a clear written offer, the new hire paperwork, an intellectual property and confidentiality assignment so the company owns the design output, tool and brand access on day one, and a structured first 90 days. FirstHR handles that people side for a small business: send the offer for e-signature, run the onboarding workflow and the paperwork, and keep the signed documents and the interview scorecards on the employee profile. Applicant tracking is coming soon to FirstHR, so pair it with your current sourcing tools for now.
Keep the completed evaluation forms from every candidate, not only the one you hire. When the role opens again in a year, or when someone asks how the decision was made, that written record is the only version of the interview that still exists.
From Interview to Onboarding
The interview is the easy part. Once you choose a candidate, the work becomes hiring them properly: a written offer letter, the new hire paperwork, an intellectual property assignment before any work starts, and tool and brand access on day one so the first screens come back on brand.
Fix the question set first
Choose the sets that match the scope of the job and ask the same core questions of every candidate, so the comparison is between answers rather than impressions.
Score the same day
Fill in the seven-area rubric with written evidence before you discuss the candidate, independently if more than one person sat in on the interview.
Send the offer in writing
Confirm the level, the pay range, the reporting line, and the exempt or non-exempt classification based on actual duties, then collect the signature electronically.
Own the output and the record
Have the designer sign an intellectual property and confidentiality assignment before work starts, and keep the scorecards, offer, and paperwork in one place.
Classification is worth a moment of care here. Whether a designer is exempt from overtime depends on actual duties rather than on the job title, and the Department of Labor sets out the tests in its professional exemption fact sheet. Get it wrong and the correction comes with back pay attached. This is general information, not legal advice.
FirstHR connects the offer, the paperwork, the e-signatures, and the onboarding workflow in one place, and keeps the signed documents and the interview scorecards on the employee profile, so a small business can run the whole hiring-to-onboarding path from one system. Applicant tracking is coming soon to FirstHR, so pair it with whatever you use to source candidates today. More hiring templates live in the hiring templates library.
Give the new designer a 30-60-90 day plan with one visible piece of work in the first month. A designer whose first month produces nothing anyone can see loses confidence fast, and so does everyone around them. Applicant tracking is coming soon to FirstHR, and until it launches the scorecards from this page are your hiring record.
Key Takeaways
Assess a UI designer on six things: visual craft, reasoning, systems and states, handoff, accessibility, and how they take feedback.
Judge the reasoning rather than the pictures, because a portfolio is built to persuade and reasoning is legible to anyone.
Run the portfolio walkthrough on the two pieces closest to your product and ask what shipped and what changed before it did.
Accessibility questions have right answers, which makes them the most useful part of the interview for a non-designer.
Federal survey data puts the median for web and digital interface designers at $104,000 a year (BLS, May 2025).
Score seven areas from 1 to 5 the same day with written evidence, independently if more than one person interviewed.
Frequently Asked Questions
What questions should I ask a UI designer in an interview?
Ask questions that force the candidate to explain decisions rather than show pictures. The six that do the most work are: what do you decide first on a new screen, layout, type, or color; walk me through how you turn a rough requirement into a finished screen; which states do you design for a form field; what does a good handoff to an engineer include from your side; how do you check color contrast and what ratio do you target; and show me an alternative you rejected and why you dropped it. Each of those has a checkable answer, so you can score it without a design background. Add a portfolio walkthrough on the two pieces closest to your product, and close with a question about feedback, because you will be giving plenty of it in plain language rather than design language.
How do I evaluate a UI designer if I am not a designer myself?
Judge the reasoning, not the visuals. A founder cannot reliably tell a good type scale from a bad one, but anyone can tell whether a candidate explains why a screen is arranged the way it is, what they rejected, and what changed before launch. Three questions do most of the work: why this hierarchy rather than another, which parts did you personally design, and what happened after it shipped. Then check the facts that have right answers, such as the contrast ratio they target, the states they design for a form field, and whether their live work holds up when you open it on your phone in front of them. Write a score for each area the same day, on evidence, and bring in an engineer or a design-literate advisor for one round if you can.
What is the difference between a UI designer and a UX designer?
A UI designer owns the visual and interactive surface: layout, typography, color, components, states, and the design system that keeps them consistent. A UX designer owns the reasoning underneath it: problem framing, user flows, information structure, prototypes, and usability testing. In practice the two overlap heavily and most small businesses hire one hybrid person rather than both. The diagnostic is simple. If customers cannot finish a task or you keep guessing what to build, the gap is UX. If the flows work but the product looks unfinished and inconsistent next to competitors, the gap is UI. A product designer covers both plus the business trade-offs, and usually costs more. Decide which gap you have before you write a single interview question, because interviewing for one and hiring for the other is the most expensive mistake in the process.
Should I give a UI designer a design test or take-home exercise?
A short exercise is useful, but it has to be paid, scoped, and never real production work. Two to four hours is the ceiling for a small business, and anything larger reads as free labor and quietly filters out the strongest candidates, who have other offers. A better option in most cases is a paid working session of 60 to 90 minutes where the candidate improves an existing screen of yours while talking through the decisions. You learn more from watching someone reason out loud than from a polished file delivered three days later, and it costs the candidate less. Whichever you choose, give every candidate the same brief, agree the fee in writing before they start, and confirm that you are not using the output in the product unless you hire them.
What are red flags in a UI designer interview?
The biggest one is a candidate who can describe what they made but never why. Ask twice with a different piece before you conclude, because nerves are real, but a designer who does not reason out loud will not survive your feedback either. Other warning signs: a portfolio with nothing that shipped, or no knowledge of what changed between the file and the live product; talking about trends, tools, and color but never hierarchy or states; never having designed an error state, an empty state, or a loading state; no answer at all on contrast, keyboard use, or small screens; refusing to open or discuss a working file; and describing engineers as the reason designs get ruined. Any one of those is a conversation. Three of them is a decision.
How much does a UI designer cost to hire?
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), web and digital interface designers, the federal occupation that covers UI, UX, and interaction designers, had a median annual wage of $104,000. The lowest 10 percent earned under $53,750 and the highest 10 percent over $201,550, with quartiles at $73,290 and $158,820. That band is wide because it covers everything from a junior designer at a small company to a senior product designer at a technology firm, so anchor to your market and to the scope you actually need rather than to the national median. A contractor or agency is billed by project or by hour and only while working, which fits a small business with irregular design volume better than a salary plus benefits and overhead. Many states now require a pay range in the job posting.
How many interview rounds does a UI designer hire need?
Three rounds are enough for almost any small business. Round one is a short screen on level, scope, and pay expectations, which prevents everyone from spending hours on a mismatch. Round two is the portfolio walkthrough, the deepest hour of the whole process, where you take the two pieces closest to your situation and ask about decisions rather than visuals. Round three is a working session with whoever the designer will sit beside, usually the founder and an engineer, covering handoff, collaboration, and a real screen from your product. Score the rubric after each round while the answers are fresh rather than at the end. Adding a fourth round rarely changes the decision and frequently loses the candidate to a company that moved faster.
Who owns the design work a new UI designer produces?
For an employee, work created within the scope of employment generally belongs to the employer, but you should still have a signed intellectual property and confidentiality assignment on file rather than relying on that default. For a contractor or freelancer, the default often runs the other way, and ownership has to be assigned in the written agreement before any work starts. Settle three things in that agreement: who owns the finished designs, who owns the working source files, and what fonts, icons, and stock assets were used and under which license, because an unlicensed font in your product is a bill you receive later. Raise all of it during the interview rather than after the offer. This is general information, not legal advice; have an employment attorney review your agreements.
