Product Design and UX Interview Questions India 2026: Portfolio, Design Process, and Case Studies

Product designer and UX designer salary in India (2024-25):

Junior UX designer (0-2 years): 5-14 LPA at product companies; 3-7 LPA at agencies. Mid-level product designer (3-5 years): 15-35 LPA at Indian product companies. Senior product designer (5-8 years): 30-65 LPA at top product companies. Lead or principal designer (8+ years): 50-100 LPA TC.

Highest-paying design roles in India:

• CRED (known for exceptional design culture): 40-90 LPA TC for senior designers
• PhonePe and Razorpay (design-led fintech): 25-60 LPA for 5-8 years
• Flipkart and Swiggy (consumer design at scale): 20-55 LPA
• India-based teams of Atlassian, Uber, and LinkedIn: 30-80 LPA

Design skills that command the highest premium: product thinking (connecting design decisions to business metrics and user outcomes), design systems (building and maintaining a scalable component library), and data-informed design (A/B test design, quantitative UX research).

Portfolio presentation guide for Indian UX/product design interviews:

1. Number of case studies: present 2-3 deep case studies rather than a gallery of 10 shallow ones. Depth signals expertise more than breadth.

2. Structure for each case study: - Problem context: what is the business context? who are the users? what metric are we improving? - Research: what did you learn from user interviews, analytics, or competitor analysis? - Definition: what is the specific problem you decided to solve, and why did you choose this? - Ideation and design process: how did you explore solutions? what alternatives did you consider and discard? - Final design: the actual UI with the rationale for key decisions - Outcome and learning: what was the result? what metric moved? what would you do differently?

1. Most common mistake: presenting only the final UI without the process. Interviewers at product companies want to understand how you think, not just what you made.

1. What to include for each case study: screenshots of the final design (Figma embed or PDF), metrics (before and after if available), and 1-2 screenshots of research artefacts (user interview quotes, affinity map, user journey).

1. Length: 15-20 minutes for the portfolio walkthrough; pace yourself. Practice the walkthrough out loud 3-4 times before the interview.

Product thinking questions asked at Indian product companies:

1. 'How do you decide what to design next?' Strong answer framework: (1) understand the user problem (qualitative research: user interviews, support ticket analysis, usability testing), (2) understand the business context (what metric are we trying to move? what is the priority against other initiatives?), (3) evaluate the opportunity size (how many users are affected? how often? how severe?), (4) consider feasibility (can engineering implement this in the current sprint? what is the technical complexity?). Design decisions made purely on aesthetics or HiPPO (Highest Paid Person's Opinion) without this framework are a red flag for interviewers at mature product companies.

2. 'How do you measure the success of a design change?' Identify the north star metric and the guardrail metrics. For a redesign of the checkout flow: north star = checkout conversion rate (% of users who complete a purchase after adding to cart); guardrail metrics = payment success rate (must not decrease), cart abandonment rate (should decrease or stay flat), time on checkout page (should decrease or stay flat). Set up A/B test before launching (if traffic volume allows), measure for statistical significance (typically 2 weeks minimum), and report results including both positive and negative effects.

3. 'How do you handle conflict between design and engineering?' Good answer: 'I try to understand the engineering constraint early by involving engineers in the design process during ideation, not just at handoff. When a conflict arises, I ask the engineer to explain the constraint specifically so I can find a design solution that achieves the same user outcome with less implementation complexity. I distinguish between cosmetic preferences (where engineering's time is worth more than the marginal design quality gain) and user-experience-critical design decisions (where I will advocate strongly).'

Design system interview questions:

1. 'What is a design system and what does it include?' A design system is a single source of truth for a product's design and engineering teams. It typically includes: - Design tokens: the smallest design decisions codified as variables (colour values, typography scale, spacing units, border-radius values) - Component library: reusable UI components (Button, Card, Modal, Form inputs) with usage guidelines - Pattern library: how components combine to form common UI patterns (navigation, forms, onboarding flows) - Design guidelines: principles, voice and tone, accessibility standards - Documentation: when to use each component, how to customise, what to avoid

2. 'How do you maintain consistency between Figma and the engineering component library?' Best practice: use Figma variables that map directly to design tokens in the codebase (CSS variables or design token JSON). The design token layer is the single source of truth; changes flow both to Figma variables and to the engineering tokens file. Tools like Style Dictionary (Amazon) or Tokens Studio for Figma automate this sync.

3. What CRED looks for in designers: CRED is known for hiring designers who combine exceptional visual craft with deep product thinking. Expect: a detailed portfolio walkthrough with emphasis on visual design quality, a design exercise (a real problem CRED faces, given on the day), and questions about your design process, how you handle ambiguity, and how you balance aesthetics with usability and engineering feasibility. CRED's brand is renowned for polish; bring work that demonstrates you can execute at a very high visual quality bar.