UI/UX Designer Interview Questions in India (2026)

UI/UX Designer interviews in India test three things together: your design thinking process, your portfolio depth, and how well you collaborate with product and engineering teams. Knok's jobradar shows 29 active openings as of July 2026, with Delhi leading at 8, Bangalore at 6, and Mumbai at 4. Panels typically run two to four rounds: a portfolio walkthrough, a take-home or live design exercise, and a final behavioural round with a hiring manager or cross-functional team.

Most interviewers are not looking for pixel-perfect work. They want to see how you frame a problem, how you involve users, and how you adapt when constraints appear. Preparing structured answers and a story-driven portfolio gives you a clear edge over candidates who show only final screens.

1. Walk me through a design project from research to shipped UI.
2. How do you balance business goals with user needs when they conflict?
3. Show me how you tested a design hypothesis with users in India.
4. How do you hand off designs to engineering at a fast-moving startup?
5. Critique this app screen, what would you improve for Indian users?
6. Tell me about a time you killed a design direction. How did you decide?

Q: Tell me about a time you had to defend a design decision to a sceptical stakeholder.

*Situation:* At my previous role, I redesigned a dashboard to reduce visible data points, based on usability testing showing users felt overwhelmed. The sales head pushed back, saying clients 'always ask for more data.'

*Task:* I needed to hold the design rationale while keeping the stakeholder's commercial concerns in view.

*Action:* I pulled the usability session recordings and showed two clips where users visibly struggled to find key metrics. I then proposed a 'show more' toggle that kept advanced data one click away, so power users were not blocked. I also framed the change as a retention argument: simpler dashboards reduce churn in the first week.

*Result:* The stakeholder agreed to a pilot. Post-launch session replays showed users reaching the key metric in roughly half the time. The toggle was rarely used, confirming most users preferred the simpler view.

---

Q: Walk me through your design process from brief to handoff.

I follow a double-diamond structure but adapt it to the team's pace. I start with a discovery phase: stakeholder interviews to understand business goals, then user research (in-depth interviews for complex tasks, surveys for quick validation). I synthesise findings into a problem statement and 'how might we' questions before sketching widely. Once I have a direction, I build low-fidelity wireframes in Figma, run quick usability tests with a small group of participants, and iterate before moving to high-fidelity. Handoff includes annotated specs, a component-level Figma file, and a walkthrough session with the engineering lead so edge cases are flagged before build starts.

---

Q: How would you design an onboarding flow for users who are not tech-savvy?

I would start by interviewing a sample of target users to understand their mental model of the product and where they expect friction. From that research I would define two or three critical first actions the user must complete to get value, then build the onboarding around those actions only, removing everything else. Concretely: short tooltips over blank states rather than a long tutorial, progress indicators so users know how far they are, and a 'skip for now' option at every step so confident users are not slowed down. I would validate the flow with moderated usability testing before release and track drop-off by step in the first week to iterate quickly.

STAR for behavioural questions: 20% situation, 10% task, 50% action, 20% result with numbers.

CIRCLES for product cases (PM): Comprehend, Identify customer, Report needs, Cut through prioritisation, List solutions, Evaluate trade-offs, Summarise recommendation.

For system design (engineering): clarify scale (DAU, QPS), draw high-level boxes, deep-dive one component, discuss failure modes and monitoring.

Signals that move UI/UX Designer candidates forward in India:
- Ownership of outcomes, not tasks
- Comfort with ambiguity and incomplete data
- Collaboration with cross-functional partners
- Understanding of India-specific constraints (UPI, logistics, multilingual users, price sensitivity)
- Realistic salary expectations aligned with level

Week 1: Audit your portfolio and sharpen your story.

Pick three to five projects that show different skills: one with strong research, one with a measurable outcome, one where you navigated constraints. For each, write a short case study covering the problem, your process, one key decision, and the result. Remove any project where you cannot explain the 'why' behind the design choices.

Week 2: Practice design exercises.

Design exercises are commonly given either as a take-home (one to two days) or a live whiteboard session (around thirty to forty minutes). Practice redesigning a familiar app screen in Figma within a time limit. Focus on thinking out loud: narrate your assumptions, state what you would research if you had more time, and call out trade-offs. Record yourself once to catch filler words and pacing issues.

Week 3: Drill the behavioural questions.

Write out STAR answers for the scenarios listed in this guide. Pay attention to the 'Result' step: quantify where you can, and if you do not have a number, describe a qualitative signal (user feedback, stakeholder sign-off, reduced support tickets). Practice with a peer or record yourself.

Week 4: Company-specific preparation.

Study the product you are interviewing for. Use it yourself, note one UX friction point and one thing done well. Research the company's design team on LinkedIn to understand their seniority mix. Prepare two to three thoughtful questions for your interviewers: about the team's research cadence, design system maturity, or how design decisions get made.

• Rambling without a clear result metric
• Badmouthing previous employers
• Quoting global salary data without India context
• Ignoring the 'why this company' question
• Over-indexing on frameworks without showing real shipped work

Fundamentals

1. Walk me through your design process from the initial brief to the final handoff.
2. How do you distinguish between UX and UI, and how do both apply in your day-to-day work?
3. What user research methods do you rely on in early-stage projects, and why?
4. How do you approach information architecture for a product with many features?

Scenario and Case Study

1. Pick one screen in our product and suggest one improvement. Walk us through your thinking.
2. You receive conflicting feedback from users and business stakeholders. How do you decide which direction to take?
3. How would you design an onboarding flow for users who are not tech-savvy?
4. A developer tells you your design cannot be built in the current sprint. What do you do?
5. How do you ensure your designs are accessible to users with visual or motor impairments?

Behavioural

1. Tell me about a time you had to defend a design decision to a sceptical stakeholder.
2. Describe a project where alignment broke down between design, product, and engineering. How did you fix it?
3. Share a design that did not perform as expected after launch. What did you learn from it?

Design thinking and process frameworks. Be fluent in the double-diamond model and design thinking stages. Interviewers commonly ask you to narrate your process for a real project, so prepare a short version and a detailed version and practice both.

User research methods. Know when to use qualitative methods (in-depth interviews, contextual inquiry, diary studies) versus quantitative ones (surveys, A/B tests, funnel analysis). Candidates report being asked to choose a method for a given scenario and justify the choice on the spot.

Wireframing and prototyping tools. Figma is the industry default for most Indian product companies right now. Know auto-layout, components, and the prototyping mode well. Familiarity with FigJam for workshops is a bonus.

Interaction design principles. Hick's Law, Fitts's Law, Gestalt principles, and Jakob's Law come up in both portfolio walkthroughs and direct questions. Be ready to cite them naturally in context, not recite them from memory.

Accessibility. WCAG 2.1 AA is the commonly referenced standard. Know contrast ratios, focus states, touch target sizes, and screen-reader considerations. This topic is increasingly tested even in mid-level rounds.

Design systems. Be ready to explain what a design system is, why teams adopt them, and how you contributed to or consumed one. Atomic design terminology (atoms, molecules, organisms) is widely understood across Indian product teams.

Metrics and success measurement. Know task success rate, time-on-task, System Usability Scale (SUS), and NPS at a conceptual level. Industry surveys suggest product companies now expect designers to tie their work to measurable outcomes.

Developer handoff and collaboration. Understand how Figma's dev mode works, how to write useful annotations, and how to handle design QA. Interviewers at product companies often include an engineer on the panel.

Showing only final screens, not the process. Interviewers want to understand your thinking. A polished mockup with no context tells them very little. Always walk through your research, early sketches, and what changed between versions.

Being unable to explain design decisions. Every colour choice, spacing decision, and component placement should have a reason you can articulate. 'It looked better' is not an answer. 'I used a card pattern here because users needed to scan multiple items quickly' is.

Ignoring the business context. Good design solves both user problems and business problems. Candidates who talk only about user needs without acknowledging constraints (time, revenue, platform limitations) come across as junior.

Not doing your homework on the company's product. Interviewers notice when a candidate has never used the product. Spend time with it, note what works, and have a considered observation ready before the call.

Being defensive about feedback during the exercise. Interviewers sometimes push back on your choices deliberately to see how you handle critique. Acknowledge the concern, ask a clarifying question, and then explain your reasoning or offer to adapt. Digging in without listening is a red flag.

Skipping accessibility. Even if you have never worked on an accessible product, you are expected to know the basics. Not mentioning it at all in a design exercise suggests a gap that senior designers will notice.