CarDekho Product Designer Interview: Questions, Experience & Prep (2026)

CarDekho is one of India's largest automotive marketplaces, connecting buyers and sellers of new and used cars across the country. The platform covers everything from car discovery and comparison to financing and insurance, which means Product Designers here work on flows that directly affect high-stakes purchase decisions.

As of July 2026, CarDekho has 7 open Product Designer roles. This sits within a wider market of 393 Product Designer openings tracked by knok jobradar, with Bangalore leading at 62 openings and Delhi at 33.

Expected salary ranges for Product Designers in India:

The interview process at CarDekho typically involves a portfolio review, one or two design rounds with case studies, and a final discussion with senior stakeholders. Candidates report that the focus is heavily on your thinking process, not just polished visuals.

These questions come up repeatedly based on what candidates report from CarDekho design interviews. They reflect the company's core concerns: marketplace dynamics, trust-building in high-value purchases, and designing for a diverse Indian audience.

1. Walk me through a project where you simplified a complex user flow. What were the constraints?
2. CarDekho users often compare multiple cars before deciding. How would you improve the car comparison experience?
3. How do you design for users with low digital literacy or those buying a car for the first time?
4. Describe how you would approach designing the car financing or EMI calculator journey.
5. How do you balance lead-generation goals (for dealers) with a smooth user experience?
6. Tell me about a time data changed or challenged a design decision you had already made.
7. How would you redesign the used-car listing page to increase buyer trust?
8. How do you collaborate with engineers when your original design needs to be adapted for implementation?
9. Walk me through how you would run user research for Tier 2 or Tier 3 city users who are new to online car buying.
10. Describe a situation where two stakeholders had conflicting requirements. How did you resolve it?
11. How would you define and measure the success of a new feature you designed?
12. What does a good onboarding experience look like for a marketplace app, and how have you applied that thinking in past work?

Use the STAR format (Situation, Task, Action, Result) to structure your answers. Here are three examples tailored to the kind of work CarDekho values.

---

Q: Tell me about a project where you used data to validate or change a design decision.

*Situation:* I was working on the search results page for a home-services app. We had designed a 'Best Match' default sort order that we felt would help users find quality providers faster.

*Task:* After launch, conversion from search to booking was lower than expected, and my task was to investigate why.

*Action:* I pulled session recordings and saw that most users immediately switched to 'Lowest Price' sort. I ran a short survey and found users did not trust the 'Best Match' algorithm because it was not explained anywhere. I redesigned the sort default to show price prominently while adding a small tooltip explaining how 'Best Match' was calculated.

*Result:* The change improved trust signals and the team observed a meaningful lift in users staying on the default sort. The approach was adopted into the product design guidelines going forward.

---

Q: Describe a time you designed for users with low digital literacy.

*Situation:* At my previous company, we launched a used-vehicle inspection booking flow. A large portion of our users were from smaller cities and were comfortable with smartphones but not with multi-step forms.

*Task:* My task was to reduce drop-offs in a multi-step booking form.

*Action:* I did guerrilla testing at a local car market and found users were confused by fields asking for 'RC number' with no explanation. I replaced jargon with plain-language labels, added inline examples, and broke the form into one question per screen. I also added a 'Call us instead' option for users who gave up mid-flow.

*Result:* Form completion improved noticeably in the next release cycle, and support calls about form confusion dropped based on the team's weekly tracking.

---

Q: How have you handled conflicting feedback from stakeholders?

*Situation:* I was designing a promotional banner system for an e-commerce client. The marketing team wanted large, colourful banners on the home screen. The product team felt this cluttered the main navigation.

*Task:* I needed to find a solution both teams could accept without a long escalation.

*Action:* I ran a quick concept test with a small group of users, showing each side's preferred version. Instead of presenting a winner, I used the findings to reframe the conversation: both teams cared about conversions, and the data showed users ignored banners that blocked navigation. I proposed a smaller, sticky banner format that preserved navigation clarity.

*Result:* Both teams agreed to a pilot. The solution went live and neither team raised the issue again in subsequent planning cycles.

For case study questions (like 'How would you redesign X'), use a structured walkthrough: start with the user and the problem, not your solution. Mention who the users are, what they are trying to do, and where they currently struggle. Then describe your design direction and the trade-offs you considered.

For behavioural questions (Tell me about a time...), STAR is your default: Situation, Task, Action, Result. Keep Situation and Task brief. Spend most of your answer on Action (what you specifically did, not what 'the team' did) and close with a concrete Result. If the result was not perfect, say what you learned.

For product-sense questions (How would you improve the car comparison page?), follow this pattern:
1. Clarify the goal: is this about conversion, retention, or trust?
2. Identify the user segment: first-time buyer vs. repeat researcher.
3. State the current friction point.
4. Propose one or two solutions with reasoning.
5. Describe how you would measure success.

For process questions (How do you work with engineers?), show collaboration without friction. CarDekho interviewers typically want to see that you can advocate for the user experience while being pragmatic about what ships.

CarDekho Product Designer interviews typically probe for four things.

User empathy with commercial awareness. CarDekho is a marketplace, so every design decision has a business side (dealers pay for leads, users must trust the platform). Interviewers want to see that you understand both sides and do not treat them as opposites.

Clear thinking over pretty slides. Candidates consistently report that panellists interrupt portfolio walkthroughs to ask 'Why did you make that choice?' and 'What did you cut?' Your reasoning matters more than visual polish.

Comfort with ambiguity. Product teams here work on a large, live product used by car buyers across the country. Interviewers want evidence that you can scope a problem yourself rather than waiting for a detailed brief.

Tier 2 and Tier 3 user awareness. A significant share of CarDekho users come from smaller cities. Showing that you have thought about low-bandwidth conditions, regional language considerations, or first-time internet users will set you apart from candidates who only design for metro power users.

One week before the interview:
Use the CarDekho app and website as a real user would. Try comparing two cars, checking an EMI, and browsing a used-car listing. Note three things that work well and three friction points. These become your case study material.

Your portfolio:
Select two or three projects that show end-to-end thinking: research, wireframes, trade-offs, and outcomes. If you do not have marketplace or fintech experience, prepare a short self-initiated redesign of one CarDekho flow. Even a lightweight 'problem plus one solution' exercise shows initiative.

Practice STAR answers for the most common behavioural themes: data-driven decisions, stakeholder conflict, shipping under constraints, and designing for diverse users.

Research the company:
Look at CarDekho's publicly available product updates and app store reviews. Reviews from users in smaller cities often surface pain points that make excellent talking points in a case study.

On the day:
When given a case study prompt, spend the first few minutes asking clarifying questions out loud. Interviewers typically reward this more than candidates who jump straight to solutions. Bring a notebook to sketch flows if it is an in-person round.

If you are applying to multiple companies at the same time, knok checks 150+ job sites nightly, applies to roles matching your resume, and messages HR for you, so you can put your energy into interview prep rather than tracking listings.

Skipping the 'why' in portfolio walkthroughs. Walking through screens without explaining the problem you were solving is the most common reason candidates do not progress. Lead with the user problem, not the UI.

Designing only for the happy path. CarDekho users encounter edge cases constantly: a car listing with missing details, a financing application that fails mid-way, a slow network in a Tier 3 city. Show that you think about error states and recovery flows.

Treating business goals as the enemy of UX. Saying 'the business wanted X but I fought for the user' signals poor collaboration. Interviewers at product companies want to see you balance both, not pick sides.

Over-engineering the solution in a case study. Candidates sometimes propose complex feature sets when the interviewer wants to see prioritisation. Suggest one well-reasoned solution and explain what you would do in a second phase.

Not asking questions. Jumping into a case study answer without clarifying the goal or user segment is a red flag. A short 'Can I ask a couple of questions first?' almost always lands well.