CarDekho UI/UX Designer Interview: Questions, Experience & Prep (2026)

CarDekho is one of India's largest automotive marketplaces, connecting car buyers with dealers, loans, and insurance products. The product spans web and mobile, serving users who are often first-time buyers navigating a complex, high-stakes purchase. UI/UX designers here work on flows like car search, EMI calculators, lead forms, and comparison tools, often balancing aggressive business targets with genuine user needs.

As of July 2026, knok's job radar shows 7 open roles at CarDekho across design and product functions. Candidates typically go through a portfolio review, a design task, and two or three rounds of interviews covering process, stakeholder thinking, and business sense. The team values designers who can think in systems, move fast, and communicate their decisions clearly.

These questions come up repeatedly across CarDekho design interviews, based on candidate-reported experiences.

1. Walk us through a project where you redesigned a complex user flow. What steps did you take and what changed?
2. CarDekho's users include first-time car buyers as well as repeat customers. How do you design for such different levels of intent and familiarity?
3. How do you balance lead generation goals (the business metric) against making the experience feel non-pushy for the user?
4. Describe a time you had to defend a design decision to a product manager or business stakeholder who pushed back.
5. How do you approach designing for users on low-end Android devices or slow mobile networks?
6. You've been asked to redesign CarDekho's car comparison feature. Walk us through how you would start from scratch.
7. Tell us about a time your research findings surprised you and changed the direction of your design.
8. How do you decide when a design is ready to hand off to engineering, and what does that handoff look like?
9. What's your experience with design systems or component libraries? How did you contribute to or build one?
10. How do you measure whether a design change actually improved the experience after it shipped?
11. Describe a situation where you had to ship something you weren't fully satisfied with. What was the compromise and how did you handle it?
12. How do you keep your designs consistent across a large product with many team members touching the same components?

Use these as models for structuring your own stories. Replace the specifics with your real experience.

Q: Walk us through a project where you redesigned a complex user flow.

*Situation:* At my previous role, the loan application flow had a high drop-off rate, especially on mobile. Users were abandoning the form midway through.

*Task:* I was asked to identify where and why users were dropping off and propose a redesign that would reduce abandonment.

*Action:* I started by pulling session recordings and exit surveys to find the exact steps where users left. The biggest pain point was a single long form asking for documents and income details upfront before users had any sense of whether they'd qualify. I broke the form into stages: eligibility check first, then personal details, then document upload. I also added a progress indicator and inline validation so users got feedback in real time.

*Result:* After the redesign shipped, the team tracked a meaningful improvement in completion rates over the following month. Stakeholders were happy with the outcome and we applied the same staged-form pattern to two other flows.

---

Q: Describe a time you had to defend a design decision to a stakeholder who pushed back.

*Situation:* I was designing a car dealer listing page, and the sales team wanted to add a large, high-contrast banner ad for a partner brand above the fold.

*Task:* My role was to present the design rationale and find a solution that served both user clarity and the business need.

*Action:* I ran a quick usability session with a small group of participants and found that users confused the partner banner with the actual dealer's content, leading them to call the wrong number. I brought the recording clips to the review meeting rather than just stating an opinion. I then proposed an alternative placement below the dealer contact section, clearly labeled as 'sponsored,' which preserved the ad revenue goal without creating confusion.

*Result:* The stakeholder agreed after seeing the recordings. The revised placement was approved, and the sales team later reported that click-through quality was higher than with the original above-fold banner.

---

Q: How do you approach designing for users on low-end devices or slow networks?

*Situation:* While working on a fintech app, we noticed that a large share of our users were on entry-level smartphones with limited RAM and inconsistent connectivity.

*Task:* I was responsible for redesigning a dashboard screen that was loading slowly and felt cluttered on smaller screens.

*Action:* I audited the screen for unnecessary elements and found that several micro-animations and shadow effects added visual weight without improving comprehension. I removed purely decorative motion, flattened the visual hierarchy, and reduced the number of data points shown by default, offering a 'see more' option for advanced users. I worked closely with the engineering team to lazy-load non-critical content.

*Result:* The redesigned screen loaded noticeably faster on low-end test devices in our lab. User complaints about the screen dropped in the next support cycle, and the simplified layout also performed better in a follow-up usability session.

For design process questions: Lead with the problem, not the solution. Interviewers want to hear how you diagnosed the situation before jumping to wireframes. A simple structure: what was the problem, who were the users, what constraints existed, what did you explore, what did you ship, what did you learn.

For 'how do you balance business vs. user needs' questions: Show you understand both sides. Acknowledge the business goal (leads, conversions, revenue), then explain how you looked for solutions that serve the user while supporting that goal. If you made a trade-off, name it honestly and explain why it was the right call at that time.

For stakeholder conflict questions: Use specifics. Vague answers like 'I always try to align everyone' don't land. Describe a real moment of disagreement, the evidence or reasoning you used, and the outcome. CarDekho interviewers are looking for designers who can hold a point of view without being combative.

For design system and handoff questions: Show you've thought beyond visuals. Mention naming conventions, documentation, how you worked with engineers on tokens or specs, and what broke down and had to be fixed. This signals maturity.

For self-critique and compromise questions: Be honest. Saying 'I shipped something imperfect because of a deadline' is fine, as long as you explain what you learned and what you'd do differently. Pretending every project was perfect reads as inexperienced.

Based on candidate-reported feedback, CarDekho design interviews prioritize a few things above others.

Product thinking over visual polish. The team builds for real users who are buying or financing cars, often in stressful situations. Interviewers respond well to designers who start with 'what is the user trying to do and what's getting in the way' rather than jumping to aesthetics.

Clear communication of process. You will almost certainly be asked to walk through a project. Practice telling the story in a logical sequence: problem, research, exploration, decision, outcome. Candidates who ramble or skip straight to the final screen typically don't progress.

Business awareness. CarDekho is a marketplace business. Leads, dealer conversions, and finance product uptake matter. Designers who can speak about how their work connected to a business outcome are more memorable than those who only talk about user delight.

Collaborative attitude. The interview may include questions about working with PMs, engineers, or sales teams. Show that you can push back constructively and build consensus without being passive.

Mobile-first thinking. A significant portion of CarDekho's traffic comes from mobile. Candidates who demonstrate sensitivity to mobile constraints, including performance, smaller screens, and varying device quality, stand out.

Step 1: Prepare two or three portfolio stories. Each story should follow the problem-process-outcome arc. Have one story ready that involves a business constraint (a deadline, a competing stakeholder goal, or a resource limit) because CarDekho interviewers typically probe for real-world complexity.

Step 2: Use CarDekho's app and website as a user. Search for a car, compare two models, start a loan inquiry. Note what feels smooth and what feels confusing. Forming your own point of view on the product shows genuine interest and gives you material for 'how would you improve this' questions.

Step 3: Prepare for a design task. Candidates typically report receiving a take-home or in-session task. Set aside a focused session to practice redesigning a familiar flow from another product, so you're comfortable with the time pressure and with presenting your reasoning out loud.

Step 4: Review your design system and handoff experience. If you've contributed to a component library, documented design tokens, or worked closely with a frontend team, prepare to talk about that in concrete detail.

Step 5: Prepare questions to ask the panel. Good questions include: how does the design team work with product and business stakeholders, what does the feedback and review process look like, and what are the biggest UX challenges in the current roadmap. This signals that you're thinking seriously about the role.

Showing only the final design. Interviewers at CarDekho want to understand how you think, not just what you made. If your portfolio presentation skips the messy middle (the dead ends, the pivots, the trade-offs), you lose the opportunity to show your process.

Treating all users as smartphone-savvy. CarDekho reaches buyers across India, including people who are less comfortable with complex digital flows. Designs that assume a high level of digital literacy miss a large part of the actual audience.

Avoiding conflict in your stories. Candidates sometimes smooth over disagreements, saying things like 'everyone agreed it was the right call.' Interviewers can tell when a story has been sanitized. Real projects involve real friction: be honest about it and show how you handled it.

Not connecting design to outcomes. Saying 'the design looked much cleaner' is weak. Even approximate outcomes matter: 'the team saw a drop in support tickets about that screen' or 'conversion on that step improved in the next review cycle.' If you don't have metrics, describe qualitative signals.

Skipping mobile considerations. If your portfolio pieces are all desktop-first or you can't speak to how your designs adapt to smaller screens or lower device specs, this will be noticed. CarDekho is a mobile-heavy product.

Arriving without questions. Not having anything to ask the panel signals low preparation or low interest. Prepare at least two genuine questions about the team, the product, or the design process.