15 Questions to Ask Before Hiring a UI/UX Designer

Hiring the wrong designer is expensive in time, money, and momentum. The right questions, asked early, save you from all three.

Weighing an agency against a senior freelancer? Here is how a UX design agency engagement compares.

Here are the questions to ask any UI/UX designer or agency before you commit, grouped so you can work through them in a call.

Portfolio and experience

• Can you show work similar to my project or industry?
• What was your exact role on these projects?
• What results did your work achieve, not just how did it look?
• Can I speak to a past client?

Process and approach

• Walk me through your process from brief to delivery.
• How do you handle research and feedback?
• How many revision rounds are included?
• Who actually does the work, you or someone else?

Pricing and timeline

• Is this a fixed price or hourly, and what does it include?
• What is the timeline, and what could delay it?
• What happens if scope changes mid-project?

Communication and ownership

• How and how often will we communicate?
• Will I own all the files and assets at the end?
• Do you also build, or just design? See why this matters in freelancer vs agency.
• What does support look like after launch?

How to read the answers

Strong candidates answer clearly, show relevant work with results, are transparent about price and who does the work, and ask good questions back. Vague answers, no relevant work, or fuzzy pricing are red flags.

Questions about who actually does the work

This is the gap between what you are shown and what you receive, and it is the most common source of disappointment in design engagements.

• Who will be doing the day-to-day work on my project?
• Is the person I am speaking to now the person who will design it?
• Is any part of this subcontracted, and to whom?
• How many other projects will be running alongside mine?
• Who is my point of contact, and what is the response time I should expect?

Agencies frequently sell with seniors and deliver with juniors. That is not automatically wrong - juniors supervised well produce good work - but you should know it before you sign, not after.

Questions about scope and change

• What exactly is included, and what is explicitly excluded?
• How many screens or pages does this quote cover, and does that include empty, loading and error states?
• What happens if we discover mid-project that we need more?
• How are changes priced - and will I see a revised number before work continues?
• What do you need from me, and by when, for the timeline to hold?

That last question matters more than it sounds. Most overruns are not designer delays, they are content delays, and a designer who has not told you what they need from you has not planned the project properly.

Questions about what happens after handoff

• What files do I receive, and do I own them outright?
• What does a developer get - and have you handed off to engineers before?
• Will there be a component system, or a set of unconnected screens?
• Who fixes it if the built version does not match the design?
• Are you available for changes after launch, and on what terms?

If the answer to "who fixes the mismatch" is unclear, you have found the seam where design engagements usually fail. One person doing both design and build removes that seam entirely, which is worth weighing against the apparent cost difference.

Questions worth asking about your own project first

Half of a bad hire is a bad brief. Before the calls, be able to answer these yourself:

• What is the one outcome this work has to produce?
• How will we know in three months whether it worked?
• Who is the single person who signs off?
• What content exists already, and what has to be written?
• What is the real budget range, and the real deadline?

Sharing the budget range is not weakness. It lets a good designer propose the right scope for it instead of guessing, and it exposes quickly whether you and they are in the same conversation at all.

What good answers sound like

Strong candidates ask you questions back, and specifically about the business rather than the brief. They are comfortable saying a request is a bad idea and explaining why. They give ranges with reasoning rather than numbers with confidence. They describe a project that went wrong without blaming the client. And they are precise about scope, because precision is what lets them commit to a price.

Weak answers are fluent but general. If you finish a call unable to state what you would receive and what it would cost, that is the answer.

Ready to hire?

If you want senior design and build from one accountable expert, that is exactly what I do. Read how to hire a UI/UX designer, see my services, or get a fixed quote in 24 hours.