Six question sets for hiring any kind of designer: core questions, the portfolio walkthrough, discipline add-ons for graphic, product, interior and industrial work, freelance terms, and a scorecard. Every question comes with why it is worth asking. Download as DOCX.
The word designer covers at least six different jobs, and the most common mistake I see small businesses make is interviewing for all of them at once. A brand designer, a product designer, and an interior designer share a portfolio format and almost nothing else. Which one you are hiring decides what a good answer even sounds like.
At FirstHR, we build for owners who make this hire themselves, usually without a design background and without an HR department to structure the process. That combination is why designer interviews so often collapse into whether the portfolio looks nice, which is the least reliable signal available to you.
This page gives you six question sets covering any design discipline, each question paired with why it is worth asking and what a strong answer sounds like, plus a scorecard so the decision rests on written evidence rather than on whose taste won the room. The matching designer job description templates cover the posting side.
TL;DR
Interview a designer in four layers: core craft and process questions that apply to any discipline, a portfolio walkthrough where the candidate explains decisions rather than showing pictures, discipline add-ons for graphic, product, interior or industrial work, and feedback handling. Ask the same questions of every candidate, then score seven areas from 1 to 5 independently before anyone discusses.
Decide What Designer Means Here First
Before you write a question, define the discipline, the seniority, and whether this is an employee or a project engagement. Those three answers determine roughly half of your question list, and getting them wrong produces a shortlist of candidates who are each wrong for the role in a different way.
The reason this matters more at a small business is that you probably only get one designer. At a larger company a mis-scoped hire lands inside a team that absorbs the gap. When the designer is your only designer, a graphic specialist who cannot do product work, or a product designer who has never prepared a print file, becomes a permanent hole in your capability.
Write down what the person must produce in their first 90 days before you interview anyone. Then build the question set backward from that list. If the honest answer is that you need range across several formats, interview for range explicitly rather than hoping a specialist will stretch.
Which Kind of Designer Are You Hiring?
Each design discipline demands a different test, even though the interview format looks the same. The guide below maps the six kinds of design hire a small business actually makes, and what each interview has to establish beyond the core questions everyone gets asked.
Graphic and brand
Marketing, print, social
The most common small business design hire. Test volume, brand consistency, and production correctness: bleed, color mode, resolution, and templates other people can use.
UI, UX, and product
Apps and digital products
Test research, flows, prototypes, design systems, and developer handoff. Judged by whether people can finish a task, not by how the screens photograph.
Interior and spatial
Spaces and interiors
Test space planning, material durability, budget tracking, contractor coordination, and awareness of local codes and any state licensing that applies.
Industrial and technical
Products and CAD
Test manufacturability, tolerances, drawing revision control, and the prototype-to-production loop. A design you cannot build at your cost is worse than none.
Generalist first hire
Your only designer
Test range across formats, self-direction, and prioritization. With no senior designer to review the work, breadth and judgment matter more than depth.
Freelance or contract
Project-scoped work
Test scope, revision rounds, availability, asset licensing, and who owns the finished work. Settle ownership in writing before anything starts.
Range across formats, self-direction, prioritization
Freelance or contract
Scope, revision rounds, availability, ownership of the work
If your role sits between two of these, pick the primary discipline for the core interview and add the second block as a secondary set. A candidate strong in the primary and adequate in the secondary is a better bet than one who is average at both. For narrower roles we have dedicated sets for graphic designers and UX designers.
Which Question Set Should You Use?
Every candidate gets the core set and the portfolio walkthrough. After that, add the discipline block that matches the role, the feedback set if this person will work closely with you, and the freelance set if the engagement is a project rather than a hire. The scorecard is used with all of them.
Core Questions
Every candidate
Eight questions that apply to any designer: opening a thin brief, self-assessed strengths, a direction that failed, brand consistency, file organization, estimating, tools and handoff.
Portfolio Walkthrough
The real interview
Seven prompts that make the candidate explain decisions rather than show visuals: the brief, their specific contribution, why these choices, what they cut, and how it performed.
Discipline Add-Ons
Pick one block
Extra questions for graphic and brand, UI and product, interior, industrial and CAD, and the generalist first design hire. Add the block that matches your role.
Feedback and Revisions
Where hires fail
Six questions on disagreeing with feedback, revision rounds, presenting to a non-designer, conflicting direction, and missed deadlines. The set most lists skip.
Freelance and Contract
Project engagements
Six questions on ownership, asset licensing, scoping and pricing, availability, source-file handover, plus a classification reminder before the engagement starts.
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 Hire
Any designer, any discipline: Core Questions plus Portfolio Walkthrough. A specialist role: add the matching Discipline block. Your only designer: add the generalist block and weight range heavily. A project rather than a hire: add Freelance and Contract, and settle ownership before work starts. Every candidate, always: the Scorecard and Red Flags. When in doubt, start with Core plus Portfolio and add one block.
6 Free Question Sets to Download
Download all six as a single Word document or copy individual sets. Each question lists why it is worth asking, what a strong answer sounds like, and what a weak answer sounds like, with space for notes. Fill in the candidate details and use them as they are.
Download All 6 Designer Question Sets
Core, portfolio, discipline add-ons, feedback, freelance, and a scorecard with red flags. All in one DOCX.
Set 1: Core Designer Questions (Any Discipline)
Eight questions to ask every designer regardless of discipline: opening a thin brief, honest self-assessment, a direction that failed, brand consistency, file organization, estimating, tools and handoff. Start here.
Core Designer Questions (Any Discipline)
DESIGNER INTERVIEW: CORE QUESTIONS FOR ANY DISCIPLINE
Candidate: __
Role / discipline: __
Interviewer: __
Date: __
Use this set for every designer you interview, whatever the discipline.
Ask the same questions of every candidate for the same role so the
comparison is fair.
1. Walk me through how you start a project when the brief is thin.
Why ask: Small businesses rarely hand over a polished brief. This is the
single best predictor of whether a designer will need constant hand-holding.
Strong answer: Describes a repeatable opening move. Asks who the audience is,
what the piece has to accomplish, where it will appear, what the deadline and
budget are, and what has been tried before. Says they write the brief back to
you for confirmation before designing.
Weak answer: Starts designing immediately, or says they need a complete brief
before they can begin anything.
2. Which parts of this role are you strongest in, and which would you
need to grow into?
Why ask: Design titles are inconsistent across companies. This question
separates the candidate who has done your exact work from the one whose title
merely matched.
Strong answer: Names specific strengths tied to real projects and is candid
about gaps. A designer who says they are strong on brand systems but light on
motion is telling you something useful and true.
Weak answer: Claims equal expertise in everything, or cannot name a single
area they are still developing.
3. Show me a project where the first direction did not work. What
did you change and why?
Why ask: Design is iteration. You are testing whether the candidate can
diagnose a failing direction rather than defend it.
Strong answer: Explains what signal told them it was not working (a
stakeholder reaction, a usability problem, a print constraint, a metric), what
they changed, and what the change did. Owns the misstep without drama.
Weak answer: Says the client just did not get it, or cannot recall a project
that changed direction.
4. How do you keep work consistent with an existing brand or style?
Why ask: Most design hires at a small business inherit a brand rather than
invent one. Consistency is a bigger part of the job than originality.
Strong answer: Talks about working from a style guide or component library,
building one where it does not exist, and knowing when a deliberate exception
is justified. Mentions checking type, color, and spacing against a reference.
Weak answer: Treats every project as a fresh creative statement, or has never
worked inside a defined brand.
5. What does your file and asset organization look like?
Why ask: Unglamorous and highly predictive. Whoever inherits these files after
the designer leaves will either thank you or curse you.
Strong answer: Named layers, versioned files, an organized source folder, and
exported assets in the formats the rest of the team needs. A strong candidate
has an actual convention and can describe it.
Weak answer: Cannot describe any system, or says the files live only on their
personal machine.
6. How do you estimate how long a piece of work will take?
Why ask: A designer who cannot estimate will quietly wreck every launch date
you set.
Strong answer: Breaks the work into stages, quotes a range rather than a
single number, states the assumptions the estimate depends on, and flags early
when an estimate is slipping.
Weak answer: Gives a confident single number for any work described, or
refuses to estimate at all.
7. What tools do you work in, and how do you hand work off to
whoever uses it next?
Why ask: Handoff is where design work most often breaks down at a small
company, because there is no one in the middle to catch mistakes.
Strong answer: Names the tools honestly, describes exporting print-ready or
developer-ready files, and asks what the receiving side needs. Willingness to
learn your existing tool matters more than any specific software.
Weak answer: Names tools but cannot describe what happens after the design is
approved.
8. Tell me about a project you are proud of that nobody praised.
Why ask: Filters for intrinsic standards. It also surfaces the unglamorous
production work that keeps a small business running.
Strong answer: Picks something practical, a template system, a cleanup, a
process fix, and explains the value it created. Shows the candidate cares
about outcomes and not only about portfolio pieces.
Weak answer: Only has award-shaped answers, or reframes the question into
another showcase project.
NOTES
[Capture specific examples, named projects, and red flags here.]
Set 2: Portfolio Walkthrough Questions
Seven prompts that turn a slideshow into an interview. They make the candidate explain the brief, their specific contribution, the reasoning behind each choice, and what they would change now.
Portfolio Walkthrough Questions
DESIGNER INTERVIEW: PORTFOLIO WALKTHROUGH
Candidate: __
Piece under review: __
Interviewer: __
Date: __
Pick two pieces yourself rather than letting the candidate choose both.
Choose the one closest to your actual work, and one you do not understand.
Ask the candidate to talk you through decisions, not visuals.
1. What was the brief, and who was the audience?
Why ask: A designer who cannot restate the problem was probably executing
someone else instructions rather than solving anything.
Strong answer: States the goal, the audience, the constraints, and the success
measure in plain language before mentioning a single design choice.
Weak answer: Jumps straight to the visual treatment.
2. What was your specific contribution to this piece?
Why ask: Portfolios routinely include team and agency work. You need to know
what this person actually did.
Strong answer: Precise about their own scope and generous about the rest of
the team. Says which screens, which assets, which stage they owned.
Weak answer: Uses only the word we, or claims sole credit for work that
obviously required a team.
3. Why this typeface, this palette, and this layout?
Why ask: This is the fastest test of whether choices were reasoned or copied
from a trend.
Strong answer: Ties each choice back to the audience, the medium, and the
brand. Legibility at the real viewing distance, contrast, print constraints,
and hierarchy all count as reasons.
Weak answer: Because it looked good, or because a reference site used it.
4. What did you have to cut, and what would you change now?
Why ask: Real projects involve trade-offs and hindsight. Absence of both
suggests a portfolio built for display rather than shipped work.
Strong answer: Names a concrete trade-off (scope, budget, timeline, technical
limit) and one honest improvement they would make with more time.
Weak answer: Says they would change nothing.
5. How did this piece perform, or how did you know it worked?
Why ask: Connects design to business outcomes, which is the whole reason a
small business is paying for it.
Strong answer: Cites a result where one exists (response rate, conversion,
sales, fewer support questions) and is honest where it was never measured.
Weak answer: Assumes it worked because it was approved.
6. Show me something in progress, or a piece you would not normally show.
Why ask: A polished portfolio hides the working process. Sketches, wireframes,
and rejected directions show how the candidate thinks.
Strong answer: Happy to show messy work and can narrate why one direction won.
Weak answer: Has nothing beyond finished pieces, or refuses.
7. Which piece here is closest to the work we need done?
Why ask: Tests self-assessment and how carefully the candidate read your role.
Strong answer: Picks a genuinely close piece and explains the transfer
honestly, including what would be different at your company.
Weak answer: Claims everything transfers, or picks the flashiest piece
regardless of fit.
NOTES
[Note which decisions the candidate could explain and which they could not.]
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Separate blocks for graphic and brand, UI and product, interior and spatial, industrial and CAD, and the generalist first design hire. Add the one that matches your role and ignore the rest.
Add the block that matches the role to the core set. Ignore the rest.
GRAPHIC, BRAND, AND MARKETING DESIGN
•How do you adapt one campaign concept across social, email, and print?
•What do you check before sending a file to a printer?
•How do you build a brand system someone else can use without you?
•Describe a time you had to design with almost no budget for assets.
Why ask: This role lives on volume, consistency, and production correctness.
Strong answer: Mentions bleed, color mode, resolution, and file formats without
prompting, and describes templates that let non-designers stay on brand.
UI, UX, AND PRODUCT DESIGN
•Walk me through a flow you designed. Where did users get stuck?
•How do you decide what to research versus what to just build and test?
•How do you keep a design system consistent as the product grows?
•What does a good handoff to an engineer look like from your side?
Why ask: Product design is judged by whether people can complete a task, not by
how the screens look in a case study.
Strong answer: Talks about specific research methods, usability observation, and
states in a design system, including error and empty states.
INTERIOR AND SPATIAL DESIGN
•Walk me through how you plan a space against a fixed budget.
•How do you select materials for durability rather than for photographs?
•How do you coordinate with contractors and handle site changes?
•What licensing or code requirements apply to your work in this state?
Why ask: Interior work is constrained by budgets, codes, and trades, and a
candidate who ignores those constraints will cost you money.
Strong answer: Talks about budget tracking, lead times, substitutions, and
knows which drawings and permissions are required locally.
INDUSTRIAL, TECHNICAL, AND CAD DESIGN
•How do you design for the manufacturing method we actually use?
•Walk me through a tolerance or material decision you got wrong.
•How do you manage drawing revisions so the shop builds the right version?
•What does your prototyping loop look like?
Why ask: An attractive design that cannot be manufactured at your cost is worse
than no design at all.
Strong answer: Speaks fluently about constraints, revision control, and
prototype-to-production steps rather than about aesthetics.
GENERALIST FIRST DESIGN HIRE
•Which of these formats have you personally shipped, and which have you not?
•How do you decide what to work on when three people ask you at once?
•What would you want from us in your first month to be effective?
•How comfortable are you being the only designer in the company?
Why ask: A first design hire has no senior designer to review the work, so
self-direction and range matter more than depth in any one format.
Strong answer: Honest about range, comfortable prioritizing, and asks about
brand assets, approvals, and who the final decision maker is.
NOTES
[Record which discipline block you used and the answers that stood out.]
Set 4: Feedback, Revisions, and Stakeholder Questions
Six questions on disagreeing with feedback, revision rounds, presenting to a non-designer, conflicting direction, and missed deadlines. This is the set most interview lists skip and the one that predicts most failures.
Feedback, Revisions, and Stakeholder Questions
DESIGNER INTERVIEW: FEEDBACK, REVISIONS, AND STAKEHOLDERS
Candidate: __
Interviewer: __
Date: __
This is the set most interview lists skip, and it is where design hires most
often fail at a small business. Craft rarely ends the relationship. Feedback
handling usually does.
1. Tell me about feedback you disagreed with. What did you do?
Why ask: You will give this designer feedback that is vague, contradictory, or
simply wrong. How they respond determines whether the working relationship
survives.
Strong answer: Asks what problem the feedback is pointing at, offers an
alternative that solves it, and executes the decision once it is made. Argues
about the goal, not about taste.
Weak answer: Either caves instantly on everything or treats every note as an
attack on their expertise.
2. How do you handle a request to make the logo bigger?
Why ask: A deliberately clichéd prompt that reveals whether the candidate
translates blunt feedback into a real problem.
Strong answer: Reads it as a visibility or hierarchy concern, proposes options
that solve it, and shows rather than argues.
Weak answer: Mocks the request, or resizes without asking what it is for.
3. What does your revision process look like?
Why ask: Endless revision rounds are the most common way design work blows a
budget at a small company.
Strong answer: Consolidates feedback from all stakeholders into one round,
confirms it in writing, defines how many rounds are included, and flags when a
request is new scope rather than a revision.
Weak answer: Accepts unlimited piecemeal changes, or has never thought about
rounds at all.
4. How do you present work to a non-designer?
Why ask: At a small business the approver is the owner, not a design director.
A designer who cannot explain their work will be overruled constantly.
Strong answer: Restates the brief, presents the work against the goal, explains
the reasoning in plain language, and asks specific questions rather than
whether the client likes it.
Weak answer: Presents visuals with no framing, or uses jargon as a shield.
5. Two people give you conflicting direction. What now?
Why ask: Small teams have unclear decision rights, and this happens in week one.
Strong answer: Surfaces the conflict immediately, asks who owns the decision,
and does not quietly pick a side or average the two.
Weak answer: Tries to satisfy both, or waits silently for the conflict to
resolve itself.
6. Describe a project that went past deadline. What happened?
Why ask: Tests communication under pressure more than it tests planning.
Strong answer: Explains the cause, when they raised the flag, and what they
changed afterward. Early warning matters more than a perfect record.
Weak answer: Has never missed a deadline, or blames everyone else.
NOTES
[Watch for defensiveness, and for eagerness to please with no point of view.]
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Six questions plus a classification reminder for project engagements: ownership of the finished work, asset licensing, scoping and pricing, availability, and source-file handover at the end.
Freelance and Contract Designer Questions
DESIGNER INTERVIEW: FREELANCE AND CONTRACT
Candidate: __
Project / scope: __
Date: __
Use alongside the core and portfolio sets when the engagement is a project
rather than a hire. Settle ownership and scope before work begins, not after.
1. Who owns the finished work, and what do you keep?
Why ask: This is the question small businesses forget to ask, and the one that
costs them later. Copyright in work by an independent contractor does not
transfer automatically.
Strong answer: Expects to sign a written assignment, is clear about what
stays theirs (fonts, stock, personal tooling), and raises licensing for any
third-party assets used.
Weak answer: Assumes payment alone transfers ownership, or resists putting
ownership in writing.
2. What are your licensing terms on fonts, stock, and illustrations?
Why ask: A commercial license you do not hold is a bill that arrives later.
Strong answer: Names the sources, states what licenses cover, and tells you
which assets you would need to license in your own name.
Weak answer: Cannot say where assets came from.
3. How do you scope and price a project like this one?
Why ask: Tests whether the engagement will stay inside a budget you can plan.
Strong answer: Breaks the project into deliverables, defines revision rounds,
states what triggers additional cost, and asks clarifying questions before
quoting anything.
Weak answer: Quotes a number instantly with no questions, or refuses to
estimate at all.
4. What is your availability and turnaround, and who else are you serving?
Why ask: A freelance designer with five other clients may be excellent and
still unable to hit your launch.
Strong answer: Honest about capacity, states realistic turnaround, and explains
how they handle urgent requests and time away.
Weak answer: Claims unlimited availability.
5. What happens to source files at the end of the engagement?
Why ask: Editable source files, not just exported images, are what let the next
person continue the work.
Strong answer: Hands over organized, editable source files as standard, and
says so without being asked.
Weak answer: Delivers flattened exports only, or charges extra for source
files without disclosing that up front.
6. How do you prefer to work with a client who has no design background?
Why ask: You will be the approver, and the working style has to fit yours.
Strong answer: Describes a check-in rhythm, shows work early rather than only
at the end, and adapts to your tools and pace.
Weak answer: Disappears until the deadline and reveals a finished product.
CLASSIFICATION REMINDER
Whether a designer is a contractor or an employee is determined by the actual
working relationship, not by the label on the agreement. Set hours, supplied
equipment, ongoing supervision, and open-ended work all point toward employee
status. Decide this before the engagement starts.
NOTES
[Record scope, rounds, ownership terms, and availability agreed verbally.]
Set 6: Designer Scorecard and Red Flags
A seven-area rubric scored 1 to 5 with space for written evidence, plus a nine-item red-flag checklist. Score right after the interview, independently, before anyone compares notes.
Designer Interview Scorecard and Red Flags
DESIGNER INTERVIEW SCORECARD
Candidate: __
Role / discipline: __
Interviewer: __
Date: __
Score each area from 1 (poor) to 5 (excellent) immediately after the
interview, while it is fresh. Write evidence from the conversation, not a
general impression. If more than one person interviews, everyone scores
Fit for this discipline and stage Score: [ 1 2 3 4 5 ]
Evidence: __
RED FLAGS CHECKLIST
[ ] Cannot explain why any specific design decision was made
[ ] Uses only we when describing portfolio work, and cannot isolate their part
[ ] Portfolio pieces are all concepts, never anything that shipped
[ ] Dismissive about feedback, clients, or previous employers
[ ] No system for files, versions, or handoff
[ ] Refuses to discuss ownership of work or licensing of assets
[ ] Claims equal expertise in every discipline you name
[ ] Estimates instantly with no clarifying questions
[ ] Portfolio quality is wildly inconsistent between pieces
SUMMARY
Total score: ______ / 35
Overall recommendation: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Strongest evidence for: __
Strongest evidence against: __
Interviewer signature: __
Keep every completed scorecard with the rest of the hiring record for this
role. Consistent, written evidence is what makes a decision defensible later.
Running the Portfolio Walkthrough
The portfolio walkthrough is the real interview, and it goes wrong in one predictable way: the candidate presents, you nod, and nobody learns anything. Fix that by picking the pieces yourself and asking about decisions rather than visuals.
Choose two pieces. Take the one closest to the work you actually need done, so you can judge transfer rather than potential. Then take one you do not understand at all, because explaining an unfamiliar project to a non-expert is exactly what this person will do for you every week.
You pick the pieces
Choose the piece closest to your real work
Choose one you do not understand
Do not let the candidate curate both
Ask for decisions
Why this typeface, palette, and layout
What was cut, and why
What they would change now
Isolate their contribution
Which screens or assets they personally made
Which stage they owned
Watch for we with no specifics
Ask for the messy version
Sketches, wireframes, rejected directions
Work in progress, not only finished pieces
How one direction won over another
The single most useful follow-up is a plain why. Ask it about the typeface, the palette, the layout, and the thing they cut. A strong designer has a reason ready every time, tied to the audience or the medium. A weaker one runs out of reasons by the third question and falls back on what looked good.
Judging Design Skill Without a Design Background
You do not need to grade the craft to run this interview well. You need to tell a reasoned decision from a decorated one, and that is a skill any owner already has in their own domain. The pattern is consistent across the three questions below.
Walk me through how you start a project when the brief is thin.
Why ask it: Small businesses rarely hand over a polished brief, so this predicts how much hand-holding the designer will need.
Strong answer: Describes a repeatable opening move: asks who the audience is, what the piece must accomplish, where it appears, the deadline and budget, and what was tried before. Writes the brief back to you for confirmation before designing anything.
Weak answer: Opens the design tool immediately, or refuses to start until someone hands over a complete brief.
Why this typeface, this palette, and this layout?
Why ask it: It is the fastest test of whether the choices in a portfolio were reasoned or copied from whatever was trending that year.
Strong answer: Ties each choice to the audience, the medium, and the brand. Legibility at the real viewing distance, contrast, print constraints, and hierarchy all count as reasons.
Weak answer: Because it looked good, or because a reference site used it. No connection to the audience or the medium.
Tell me about feedback you disagreed with. What did you do?
Why ask it: You will give vague or contradictory feedback at some point. The response decides whether the working relationship survives it.
Strong answer: Asks what problem the feedback is pointing at, proposes an alternative that solves that problem, and executes cleanly once the decision is made. Argues about the goal, not about taste.
Weak answer: Caves instantly on every note, or treats each piece of feedback as an attack on their expertise.
Two extra signals are worth as much as the answers. First, isolate contribution: portfolios routinely include agency and team work, so ask which screens or assets the candidate personally made. Second, call two references who worked with them directly, and ask specifically about deadlines and how they took feedback rather than about strengths in general.
Structure Beats Instinct, Especially on Taste
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation. Asking the same job-related questions of everyone also keeps you inside the EEOC rules against basing decisions on protected characteristics. Design interviews drift more than most, because a portfolio conversation follows whatever the candidate chose to show, so structure matters here more than average.
Design Exercises and Paid Test Projects
A short paid exercise tells you more than any additional conversation, but only if you pay for it and scope it tightly. Spec work, meaning a full design produced on the promise of possible payment, filters out your strongest candidates first, because experienced designers decline it on principle.
Keep the exercise to two or three hours, write a real brief with a stated goal and audience, and use a realistic but non-live problem so nobody suspects you are harvesting free work. State the fee up front and confirm you will not use the output commercially. Then judge the process as much as the output.
Element
What good looks like
Scope
Two to three hours, one deliverable, written brief
Payment
A stated flat fee agreed before the candidate starts
Problem
Realistic but not a live job you are about to run
Usage
Explicit promise that you will not use the output
What you judge
Questions asked about the brief, reasoning, and execution
Follow-up
A 20-minute walkthrough of their choices, not just the file
Ask candidates to send the questions they had about the brief along with the work. Those questions often separate the shortlist better than the deliverable does, because they show whether the designer interrogates a problem before solving it. If the portfolio and references are already strong, an exercise is optional.
Ownership, Licensing, and Classification
Design hiring carries an intellectual property question that most roles do not, and it has to be settled before work begins. Work created by an employee within the scope of employment is a work made for hire that belongs to the company automatically. Work by an independent contractor does not transfer without a signed written agreement.
The U.S. Copyright Office is clear that only certain categories of specially commissioned work can be treated as work made for hire, and even then a written agreement is required. Paying an invoice does not by itself transfer copyright, which surprises a lot of owners the first time they try to hand a logo file to a new agency.
Settle Ownership Before Work Starts, Not After
Ask every contract designer three questions before the engagement begins: who owns the finished work, what do you keep, and where did the fonts, stock images, and illustrations come from. Third-party assets carry their own commercial licenses that may not transfer with the design. Getting a signed assignment and a licensing list up front costs one email. Getting it afterward, from a designer who has already been paid, can cost considerably more. This is general information, not legal advice.
Classification is the second question. Whether a designer is an employee or a contractor depends on the actual working relationship rather than the label on the agreement, and set hours, supplied equipment, and open-ended work all point toward employee status.
Consideration
Employee designer
Contract designer
You direct hours, tools, and process
Company owns the output automatically
Needs a signed assignment to transfer copyright
Covered by FLSA overtime rules unless exempt
Scoped to a defined project with an end date
For employees, the creative professional exemption is decided case by case. The Department of Labor requires a salary or fee at or above the standard level of $684 per week ($35,568 a year) plus a primary duty requiring invention, imagination, originality, or talent. Designers doing routine production work to a set formula are generally non-exempt. Check your state rules too, since some are stricter.
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 interviews need the discipline more than most, because taste feels like evidence and is not.
Ask about the work, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing hiring decisions on protected characteristics, and questions that probe them create legal risk even when they feel like friendly rapport. Do not ask about age, race, religion, national origin, sex, pregnancy or family plans, disability, or genetic information. Design interviews have their own traps: asking when someone graduated from art school is an age question, and asking about the personal work on a candidate portfolio can drift into religion or family. Keep every question tied to the work the role requires. This is general information, not legal advice.
Same questions, same order, every candidate
A structured interview, where every candidate answers the same questions scored against the same rubric, predicts on-the-job performance far better than a free-flowing conversation, and it reduces the chance the decision rests on rapport rather than evidence. Design interviews drift more than most, because a portfolio conversation naturally follows whatever the candidate chose to show. Fix that by picking the portfolio pieces yourself and keeping the same core questions for everyone. The sets on this page are built to be asked in the same order every time.
Never ask for free work
Spec work, meaning a full design produced on the promise of possible payment, filters out the strongest candidates first, because experienced designers decline it. If you need to see how someone works, pay for a short, tightly scoped exercise and say up front what you will pay, how long it should take, and that you will not use the output. Two hours of paid work with a clear brief tells you more than a week of unpaid speculation, and it costs you far less than a bad hire.
Score independently, then discuss
When several people review a designer, have each score the rubric on their own before anyone talks. Design opinions are especially prone to anchoring: one confident voice saying the work looks dated will pull an entire room. Compare written evidence first, then discuss the gaps. A simple 1-to-5 rubric per area, filled in separately, turns a taste argument into a structured decision, which matters most when the owner is also the person with the strongest aesthetic opinions in the room.
Watch the design-specific traps in small talk. Asking when someone graduated from art school is an age question, and asking about the personal work in a portfolio can drift toward religion, family, or national origin without anyone intending it. Keep to job-related questions. This is general information, not legal advice.
Red Flags and Scoring the Interview
Score the rubric immediately after each interview, while the answers are still fresh, and rate the same seven areas for every candidate. The red flags below are the patterns worth weighting heavily, because each one predicts a specific kind of failure after the hire.
Cannot explain a single decision
The candidate can describe what they made but not why. Ask twice with a different piece before concluding, because nerves are real, but a designer who never reasons out loud will not survive your feedback.
Everything is a concept
A portfolio with no work that shipped often means work that never survived a client, a printer, or an engineer. Ask which pieces went live and what changed between the portfolio version and the real one.
Dismissive about past clients
A candidate who describes every previous employer as the problem is telling you how they will describe you. Listen for shared ownership of what went wrong.
Resists any talk of ownership
A designer who will not discuss who owns the finished work, or where fonts and stock assets came from, is creating a bill you will receive later. Settle this before work begins.
Scoring area
What a 5 looks like
Craft and visual quality
Consistent quality across pieces, appropriate to the medium
Process and problem framing
Repeatable opening move; restates the brief before designing
Portfolio depth
Explains decisions, trade-offs, and what they would change
Feedback and revisions
Argues about the goal, not taste; defines revision rounds
Communication
Explains reasoning plainly to someone with no design training
Reliability and handoff
Estimates in ranges, flags slippage early, organized files
Fit for discipline and stage
Has shipped work close to yours, at your scale
If more than one person interviews, everyone scores independently before the group talks. Design opinions anchor faster than most: one confident voice calling the work dated will pull an entire room. Compare written evidence first, then discuss the gaps, and feed the scores into a clean interview feedback step. Reference checks close the loop.
Designer Pay by Discipline
Designer pay varies more by discipline than by almost any other factor, which is why a single number for designer is not useful. Use federal data as a baseline, then adjust for your local market, the seniority you need, and whether the role is full-time or contract.
Median Pay Ranges From $62,960 to $104,000 by Discipline
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), median annual wages were $62,960 for graphic designers, $67,190 for interior designers, $83,910 for commercial and industrial designers, and $104,000 for web and digital interface designers. Within graphic design alone the spread is wide: the lowest 10 percent earned under $39,520 and the highest 10 percent over $104,910.
Design occupation
Median annual wage
Median hourly
Graphic designers
$62,960
$30.27
Interior designers
$67,190
$32.31
Commercial and industrial designers
$83,910
$40.34
Web and digital interface designers
$104,000
$50.00
Two practical notes. A freelance or contract designer is billed by project or hour and only when working, which suits businesses whose design volume is irregular. And if you post a range, check whether your state or city requires it, since pay transparency rules now cover a meaningful share of the country.
Interviewing a Designer Without an HR Department
A large company runs designers through a coordinated panel with a design director grading craft and a recruiter managing scorecards. At a small business the owner does all of it, usually without a design background, between everything else. That reality is where the avoidable mistakes live.
You are hiring a designer without being a designer yourself
Most owners making this hire cannot grade craft the way a design director would, and they know it, which is why so many designer interviews collapse into whether the portfolio looks nice. You do not need to grade the craft. You need to tell a reasoned decision from a decorated one. Every core question in these sets comes with a note on why it is worth asking and what a strong answer sounds like, so you can listen for specificity, honest trade-offs, and a repeatable process rather than trusting your own eye. Pair that with two references who worked with the candidate directly.
The word designer is doing too much work in your job posting
A brand designer, a product designer, and an interior designer are three different professions that happen to share a portfolio format. Interviewing all of them with one generic question list produces a shortlist of people who are each wrong for the role in a different way. Decide the discipline first, then add the matching block from the discipline set to the core questions. If you genuinely need range because this is your only designer, interview for range explicitly: ask which formats they have personally shipped and which they have not, and treat an honest no as a good sign rather than a gap.
The interview ends and the ownership question is still open
Design work carries an intellectual property question that most hires do not. Work created by an employee inside the scope of their job belongs to the company automatically, but work by an independent contractor does not transfer without a signed written agreement, and fonts, stock photography, and illustrations carry their own licenses. Settle this before work begins rather than after. FirstHR handles that people-side sequence for a small business: send the offer and the IP assignment for e-signature, run the new hire paperwork and onboarding workflow, and keep the signed documents on the employee profile. FirstHR is an onboarding and HR platform, not a design tool or a project management system, so pair it with those. Applicant tracking is coming soon to FirstHR.
The habit that fixes most of this is unglamorous: write the questions before the first interview, ask the same ones every time, and score in writing within ten minutes of the candidate leaving. A single founder running that process well beats an unstructured panel, and it costs nothing but the discipline to keep to it. Applicant tracking is coming soon to FirstHR.
From Interview to Onboarding
The interview is step one. Once you pick a designer, the work shifts to hiring cleanly: a written offer that states the discipline and the classification, an IP and confidentiality agreement signed before work begins, and tool and brand access ready on day one.
Send the offer
Confirm the discipline, the scope, the pay, and the exempt or non-exempt classification in writing, based on the actual duties rather than the title.
Sign the IP assignment
Have the designer sign an intellectual property and confidentiality assignment before work starts, so the company owns the brand and design output.
Hand over brand and tools
Design tool access, the brand library, fonts and their licenses, and a named approver, so the first pieces come back on brand.
Store the hiring record
Keep the scorecards, the signed offer, the IP assignment, and the classification basis together and easy to find later.
A designer ramps on context rather than on process: the brand library, the font licenses, the approval path, and who has final say. Give them that in the first week and the first pieces come back usable. An onboarding template keeps the sequence from depending on memory, and the standard new hire paperwork runs alongside it.
FirstHR connects the offer, the IP assignment, e-signatures, the paperwork, and the onboarding workflow in one place, and stores the signed documents and the hiring record on the employee profile, so a small business can run interview to onboarded from one system. FirstHR is an onboarding and HR platform, not a design tool or a project management system, so pair it with those. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Decide the design discipline before you write a single question, because it determines what a good answer even sounds like.
Give every candidate the same core set and portfolio walkthrough, then add only the discipline block that matches the role.
Run the portfolio walkthrough yourself: pick the pieces, and ask why each decision was made rather than asking to see more work.
Test feedback and revision handling explicitly, since that is where small business design hires fail more often than on craft.
Settle ownership and asset licensing in writing before work begins; a contractor keeps copyright without a signed assignment.
Score seven areas from 1 to 5 with written evidence right after the interview, independently, before anyone compares notes.
What questions should I ask when interviewing a designer?
Ask questions that test process, judgment, and collaboration, not just taste. The core set that works for any discipline is: how do you start when the brief is thin, which parts of this role are you strongest in and which would you grow into, show me a project where the first direction failed, how do you keep work consistent with an existing brand, what does your file organization look like, how do you estimate timelines, and how do you hand work off to whoever uses it next. Then add a portfolio walkthrough where you pick the pieces and ask why each decision was made. Finish with feedback and revision questions, which is where small business design hires most often fail. Every question on this page includes why it is worth asking and what a strong answer sounds like.
How do I judge design skill if I am not a designer?
You do not need to grade craft; you need to tell a reasoned decision from a decorated one. Ask why for every visible choice and listen for answers that connect to the audience, the medium, and the brand rather than to trends. Strong candidates describe trade-offs, name what they cut and why, and are honest about what they would change now. Weak candidates describe what they made without ever explaining why. Three practical shortcuts help: pick the portfolio pieces yourself rather than letting the candidate curate, ask what their specific contribution was on team projects, and check two references who worked with them directly. If you want more confidence, run a short paid exercise scoped to two hours rather than judging on conversation alone.
What should I ask during a design portfolio review?
Ask about decisions, not visuals. Start with what the brief was and who the audience was, then ask what the candidate personally contributed, since portfolios routinely include agency and team work. Ask why this typeface, this palette, and this layout, which is the fastest test of whether choices were reasoned or copied. Ask what had to be cut and what they would change now, because a candidate who would change nothing is showing you a display piece rather than shipped work. Ask how the piece performed or how they knew it worked. Finally, ask for something in progress, since sketches and rejected directions reveal thinking that a polished case study hides. Choose the pieces yourself: one close to your actual work, and one you do not understand.
Should I ask a designer to do a test project?
Yes, if you pay for it and scope it tightly. Never ask for spec work, meaning a full design produced on the promise of possible payment, because experienced designers decline it and you filter out your strongest candidates first. A good exercise is two to three hours, has a written brief with a clear goal, uses a realistic but non-live problem, and comes with a stated fee and a promise that you will not use the output commercially. Judge the exercise on process as much as output: ask the candidate to send their questions about the brief along with the work, since the questions often tell you more than the deliverable. For many small business roles, a paid exercise is optional if the portfolio plus references are already strong.
Who owns the design work a contractor produces for my business?
Under U.S. copyright law, work created by an employee within the scope of employment is a work made for hire owned by the employer, but work created by an independent contractor stays with the contractor unless there is a signed written agreement transferring it, and only certain categories of commissioned work qualify as work made for hire at all. In practice that means you need a written assignment signed before work begins, not an invoice afterward. Fonts, stock photography, and illustrations carry their own licenses that may not transfer with the design. Ask every contract designer who owns the finished work, what they keep, and where third-party assets came from. See the U.S. Copyright Office guidance on works made for hire, and treat this as general information rather than legal advice.
Is a designer exempt or non-exempt under the FLSA?
It depends on actual duties and pay, not on the job title. The creative professional exemption under the Fair Labor Standards Act applies when an employee is paid on a salary or fee basis at or above the standard salary level, currently 684 dollars per week or 35,568 dollars a year, and their primary duty requires invention, imagination, originality, or talent in a recognized artistic field. The Department of Labor says this must be decided case by case. Designers doing routine production work to a set formula are generally non-exempt and owed overtime, while designers exercising genuine creative judgment may qualify. Classify based on what the person actually does, document the basis, and check your state rules, which are sometimes stricter. This is general information, not legal advice.
How much does a designer cost to hire?
Pay varies widely by discipline, which is why the generic question is hard to answer. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), graphic designers had a median annual wage of 62,960 dollars, interior designers 67,190 dollars, commercial and industrial designers 83,910 dollars, and web and digital interface designers 104,000 dollars. Within graphic design alone the spread is large: the lowest ten percent earned under 39,520 dollars and the highest ten percent over 104,910 dollars. Adjust for your local market, the seniority you need, and whether the role is full-time, part-time, or contract. A freelance designer is billed by project or hour and only when working, which suits businesses with irregular design volume.
How many rounds should a designer interview have?
Two to three rounds is right for most small businesses. Round one is a 30-minute screen covering the role, the discipline, availability, and pay range, which avoids spending an hour on a mismatch. Round two is the substantive interview: the core question set plus a portfolio walkthrough where you pick the pieces, usually 60 to 75 minutes. Round three, if you run one, is a short paid exercise or a conversation with whoever the designer will work with daily. Score the rubric immediately after each round while the answers are fresh, and have every interviewer score independently before the group discusses. More rounds than that rarely improves the decision and costs you strong candidates, who tend to have other offers moving faster.
