Guide6 min readUpdated
UI UX Interview Questions and How to Answer Them
UI UX interview questions for freshers with sample answers, how to present your portfolio, and how to handle a design task in the interview.
Picture a fresher walking into a design interview with a good portfolio. The first question is, "Walk me through one project." She opens the file, scrolls through screens and describes colours. The panel nods politely, but learns nothing about how she thinks. That is the most common mistake. UI UX interview questions are questions that test how you solve design problems, not only how your screens look.
A note on my background: I work as a freelancer, so my conversations with clients are pitch calls and not job panels. Still, clients ask many of the same questions, such as how I work, what I did on a past project and how I handle feedback. This guide combines that experience with what a fresher can prepare. For the steps before the interview, read how to become a UI/UX designer in India.
What UI UX interview questions are asked most often?
The most common questions ask about your process, a project from your portfolio, how you handle feedback and why you want the role. Interviewers want proof that you think in steps and can explain your reasons.
Questions you should prepare:
- "Walk me through your design process." Describe your stages in order, and give a real example for each stage.
- "Tell me about a project you are proud of." Pick one with a clear problem.
- "How do you handle feedback you disagree with?" Show that you ask for the reason, test the idea and decide with evidence.
- "How do you work with developers?" Mention clear handoff, named layers and early checks on what is possible to build.
- "How do you decide between two designs?" Refer to the user goal, a quick test or a simple measure, not personal taste.
- "What would you change in this app?" Look at one screen, name one problem, explain the cost to the user and suggest one fix.
My own process has five stages: understand, map the flow, wireframe, design the interface, then prototype and hand off. Having a short, clear version of your own process makes question 1 easy.
How do I answer UI UX interview questions for freshers?
Answer with four parts: the situation, your action, your reason and the result or lesson. Keep each answer under two minutes. If you have no job experience, use college, practice or volunteer projects and say so honestly.
Here is a hypothetical worked example for "Tell me about a time you changed a design." Suppose the practice project was a sign-up screen.
I designed a sign-up screen with five fields for a practice project. A friend tried it on her phone and stopped at the address field. I asked why. She said she did not want to type an address before seeing the app. I moved the address to after the first order and kept only phone number and name. I would now test that change with more people.
That answer is short, honest and shows a cause and a change. It does not claim a large result, and an interviewer trusts that.
Other tips for freshers:
- Do not say "I have no experience." Say "My experience is from practice projects, and here is what I learned."
- Admit what you do not know. "I have not run a formal usability test, but I tested with four people and here is what I saw" is a strong answer.
- Use plain words. Avoid terms you cannot explain. If you say "information architecture", be ready to define it. The design terms glossary helps.
How do I present my portfolio in an interview?
Present two or three projects, each in about 5 minutes, in the order: problem, your role, process, final design, lesson. Spend most time on your decisions, not on describing screens.
A simple structure for each project:
- The problem in one sentence: "Sellers on a marketplace app could not finish verification."
- Your role: what you did and what the team did.
- Two or three key decisions: each with the reason and the alternative you rejected.
- The final flow: show screens in the order a user sees them.
- The lesson: one thing you would do differently.
Choose projects that show different skills, for example one research-heavy project and one that shows detailed interface work. Be ready for the question "Which parts did you design yourself?" Answer exactly. Interviewers often check this, and honesty protects you.
Practise out loud. Time yourself. If your portfolio is not ready, the guide on building a UI/UX design portfolio covers structure. It also helps to see your portfolio as a reviewer sees it, which how to read a design portfolio explains.
What happens in a design task or whiteboard exercise?
In a design task, you receive a small problem and some time, and you show how you think. The finished screens matter less than your questions, your reasoning and your clear order of steps.
A typical prompt: "Design a booking flow for a neighbourhood clinic." Here is how I would handle it:
- Ask questions first. Who books, the patient or a family member? Do they pay by UPI before the visit? Which language do they prefer? What happens when a slot is full?
- State assumptions. Say them aloud so the interviewer can correct you.
- Define the main flow. Search doctor, pick a slot, confirm details, pay, get a WhatsApp confirmation.
- Sketch the key screens. Rough boxes are fine. Show the slot picker and the confirmation.
- Cover the failure cases. No slots, payment failed, wrong number.
- Say what you would test. Name one risky screen and how you would check it with real users.
For a take-home task, the same logic applies. Write a short note with your assumptions, your flow and what you left out. A tidy note often matters more than extra screens. Know the difference between wireframes, mockups and prototypes so you present the right level of detail.
How should I prepare in the week before the interview?
Use the week for three things: rehearse your project stories, study the company's product and prepare your questions. A short, focused plan works better than reading hundreds of questions.
- Day 1 and 2: write and rehearse your three project stories.
- Day 3: revise basics such as design thinking, user flows and usability testing. See usability testing on a small budget.
- Day 4: use the company's app or website. Note three things that work well and two that confuse you. Frame problems politely.
- Day 5: practise a 45-minute design task with a friend as the interviewer.
- Day 6: check your portfolio links, file access and laptop setup. Test the Figma link in a private window.
- Day 7: rest, and review your notes once.
Also prepare for the question on feedback. How to give design feedback shows what good feedback sounds like, which helps you receive it.
What questions should I ask the interviewer?
Ask about how design decisions are made, how designers work with developers and how the team learns from users. Good questions show that you care about the work, not only the job.
- "How does the team decide what to design first?"
- "Do designers speak with users directly?"
- "How are designs handed over to developers?"
- "What does a good first three months look like for this role?"
Avoid asking only about leave or perks in the first round. Those are fair questions later, but early questions about the work leave a better impression.
If you are building toward freelance work rather than a job, the same preparation helps in client calls. You can see how I explain my approach on my UI/UX design page.
Frequently asked questions
What should a fresher say when asked about experience?
+
Say plainly that your experience comes from practice or college projects, then describe one project with the problem, your decisions and what you learned. Honesty with a clear story works better than exaggeration.
How many portfolio projects should I prepare for an interview?
+
Prepare two or three projects that you can explain in about 5 minutes each. Choose projects that show different skills, and know exactly which parts you designed.
Do I have to finish the design task in the interview?
+
Not usually. Interviewers care about your questions, assumptions and reasoning. A clear flow with two or three key screens is better than rushed polished screens.
Is it fine to say I do not know an answer?
+
Yes. Say what you do not know, then explain how you would find out. This shows honesty and a habit of learning.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.