Guide5 min readUpdated
Questions to Ask a UI UX Designer Before You Hire
Questions to ask a UI UX designer before hiring, with what a good answer sounds like. A practical guide to evaluating a design portfolio in India.
By Tithi Mondal, UI/UX Designer
Why the questions matter
Choosing a designer is hard when you cannot judge design yourself. The good news is that you do not need to. You only need to ask questions that make a designer explain their thinking. Good designers can explain why. Weak answers stay at "it looked modern".
This guide gives you the questions and what a good answer sounds like. It works for freelancers and agencies, and for interviews over a Google Meet call or a WhatsApp chat.
For the full hiring process from first search to payment, read how to hire a freelance UI/UX designer in India.
Questions about their process
1. "Can you walk me through how you design an app from start to finish?"
A good answer has clear stages in a sensible order. For example: understand the business and users, map the flow, sketch wireframes, design the interface, build a prototype and prepare files for developers. My own process follows five stages like these. If a designer jumps straight to colours and fonts, they may be skipping the thinking.
2. "What do you need from me before you start?"
A good answer asks for a brief, examples you like, user details, deadlines and any existing branding. A designer who needs nothing from you may not be planning to learn much about your product.
3. "How do you decide what goes on each screen?"
A good answer talks about user goals and flows, not just appearance. Listen for phrases such as "what the user is trying to do" and "what should be the main action".
Questions about their portfolio
Evaluating a design portfolio is more than judging how pretty it is. Use these.
4. "Which project here is closest to mine, and what was your role?"
A good answer names the exact part they did: research, flows, screens, prototype. It is honest if they worked within a team.
5. "What problem did this design solve?"
A good answer states a problem in plain language, such as "sellers did not know why their documents were rejected, so we added a clear status screen". If the answer is only about the look, ask again.
6. "What would you do differently now?"
A good answer is reflective and specific. Everyone learns, and a designer who can name a mistake is usually safer than one who claims none.
When you open a portfolio, also check these:
- Are there complete flows, not only single pretty screens?
- Do the designs suit real phones, including mid-range Android devices?
- Is there variety, or does every project look identical?
- Are the products real or only concept work? Both are fine, but you should know which.
You can see the products I have designed in my portfolio.
Questions about India and your users
7. "How do you design for users in smaller cities or users who prefer regional languages?"
A good answer mentions larger tap targets, readable text sizes, simple language, UPI payment, low data use and space for longer text in Bengali or Hindi. A designer who has built for these users will usually have examples ready. Ask to see one.
8. "How do you test a design before it is built?"
A good answer mentions a clickable prototype and showing it to a few real users. Testing does not need a lab. Five conversations with actual customers can reveal a lot.
Questions about money and timeline
9. "What exactly is included in your price?"
A good answer lists screens, revisions, prototype and handoff files. Watch for vague words like "full design". The UI/UX design cost guide explains what should be in a quote.
10. "How do you structure payments?"
A good answer is a clear schedule, such as half to begin and half on completion, or milestones for larger projects.
11. "How long will this take, and what could delay it?"
A good answer gives a range and names the main dependencies, usually your feedback and content. A designer who promises a large app design in two days deserves a second question.
12. "How many revisions are included, and what counts as a revision?"
A good answer defines it. A revision is a round of changes to the agreed scope, not a new direction. For reference, I include two to three revision rounds.
Questions about communication and handoff
13. "How will we stay in touch, and how fast do you reply?"
A good answer names the channels (Google Meet, WhatsApp, email) and a reply time. I reply to enquiries within 24 hours.
14. "What files will my developer receive?"
A good answer includes a Figma file with organised screens, spacing and colour details, exported icons and images, and a short explanation of the flow. Ask whether they will answer developer questions after delivery.
15. "Who owns the design files and the final work?"
A good answer is clear: you do, after full payment. Confirm this in writing.
Red flags to notice
A few signs should make you pause.
- They cannot explain why they made a choice.
- They guarantee results such as downloads, sales or ranking.
- The price is given before they have asked anything about your project.
- There is no written scope, or no payment schedule.
- They resist showing work in progress.
- They cannot show anything similar to your needs and cannot explain how they would approach it.
None of these alone proves a problem, but together they are a reason to look elsewhere.
How to use these questions
Pick six to eight from the list, not all fifteen. Send them in a message first, so the designer can answer in writing, and then discuss the answers on a call. Written answers also help you compare two or three designers fairly.
Compare them after a day. The person who answered clearly, asked you good questions back and was honest about limits is usually the one to trust.
If you are preparing to hire, a short written design brief makes every answer more precise. And if you would like to ask me these questions, you can get in touch any time.
Frequently asked questions
How many designers should I interview?
Two or three is enough for most projects. More than that tends to create confusion rather than clarity.
Is a design certificate important when choosing a designer?
It can show training, but the portfolio and the way a designer explains their decisions tell you more. Look at real projects first.
Should I ask for a free sample design?
Most professional designers do not work free on a full sample, because the thinking is the real work. A small paid trial or a review of existing projects is a fairer way to test fit.
What should I prepare before the first call?
A short description of your product, your users, your deadline and your budget range. Even a half page note helps the call stay useful.