housing UI/UX Designer Interview: Questions & Prep (2026)

Housing.com (part of REA India) is one of India's leading property portals, connecting home buyers, renters, and real estate agents across the country. As of July 2026, knok jobradar tracked 29 open UI/UX Designer roles in India, with Delhi leading at 8 openings, Bangalore at 6, and Mumbai at 4. Housing.com had 188 open roles at that point, making it an active hiring company. The design team works on complex, high-stakes products: property search, listing pages, map-based discovery, virtual tours, and lead-generation flows built for an audience that ranges from tech-savvy metro professionals to first-time buyers in smaller cities.

Interviews typically span a portfolio review, one or two product-thinking or design exercise sessions, and a final conversation with a senior designer or hiring manager. Candidates report the exact structure varies by team and seniority level. Expect detailed questions on your process, how you handle ambiguity, and how your design decisions have driven real outcomes.

1. Walk us through your most complex UX project. What was the problem, and how did your design solve it?

1. Housing.com serves users with very different digital literacy levels, from metro professionals to first-time buyers in Tier 2 cities. How do you design for this range?

1. Our property search has dozens of filters. How would you redesign the filter experience for mobile?

1. Describe a time you had to convince stakeholders to go with your design recommendation over theirs.

1. How do you approach designing a map-based property discovery feature where users can zoom, cluster, and tap into listings?

1. Walk us through your end-to-end design process from receiving a brief to handing off to engineering.

1. How do you measure whether a design is actually working after it launches?

1. Housing.com surfaces trust signals like verified listings, RERA registration numbers, and agent reviews. How do you present this information without cluttering the interface?

1. Tell us about a design you shipped that did not perform as expected. What did you learn from it?

1. How do you handle conflicting feedback from product managers, engineers, and business stakeholders?

1. What is your approach to working within and contributing to a shared design system across multiple product teams?

1. If you could improve one flow in the current Housing.com app, what would it be and why?

Q: Walk us through your most complex UX project.

*Situation:* My team was redesigning the home loan application flow for a fintech product. The existing flow had a steep drop-off at the document upload step, which our funnel analytics confirmed.

*Task:* I was the sole UX designer responsible for reducing that drop-off and making the flow feel less intimidating for first-time loan applicants.

*Action:* I ran several user interviews with people who had abandoned mid-flow. The core insight was that users did not know which documents they would need until they were already partway through the form. I redesigned the entry point to show a 'documents you will need' checklist before the form started. I also broke the lengthy multi-step form into three clearly named stages and added a persistent progress indicator throughout.

*Result:* After launch, the team saw a meaningful improvement in completion rates based on our funnel data. I am happy to walk through the full case study in detail.

---

Q: How do you handle conflicting feedback from different stakeholders?

*Situation:* On a search results page redesign, the product manager wanted more filters visible upfront, the engineering lead wanted fewer components to reduce load time, and the business team wanted a sponsored listing banner at the top of results.

*Task:* I needed to find a solution that addressed all three constraints without designing by committee.

*Action:* I mapped each stakeholder concern to a user need. More visible filters meant faster decision-making. Fewer components meant faster page load, which also benefits users directly. The banner was a revenue requirement I could not remove, but I could reposition it. I proposed a collapsible filter drawer that loads progressively, and negotiated moving the banner below the first three results so it did not hurt the first impression. I also presented a simple test plan so we could validate the banner placement with real data before committing.

*Result:* All three stakeholders agreed to the proposal. The collapsible filter pattern was later adopted across two other flows in the same product.

---

Q: Tell us about a design that did not perform as expected.

*Situation:* I redesigned an onboarding flow for a rental app, simplifying it by removing what I believed were redundant preference questions around budget range and furnishing type.

*Task:* The goal was to increase the number of users who completed onboarding and reached the search results page.

*Action:* I removed the preference-setting steps, assuming users would apply filters in search instead. After launch, I monitored session recordings and noticed users running multiple searches with no results, because their budget and requirements were not saved anywhere.

*Result:* Onboarding completion went up, but the quality of leads surfaced to landlords dropped noticeably. I reintroduced a lightweight preference prompt as a contextual nudge inside the search interface. The lesson: optimising for a single metric like completion rate can mask problems further down the funnel.

Use STAR for behavioural questions. Every story should have a clear Situation (the context), Task (your specific role), Action (what you did and why), and Result (what changed). Keep results honest: if you do not have a hard metric, describe a qualitative outcome and say so clearly rather than guessing at numbers.

Use a design process framework for craft questions. When asked 'how do you approach X', walk through Discover, Define, Ideate, Prototype, Test, and Iterate. At Housing.com, anchor each stage to real estate context: for Discover, speak to the mix of urban and semi-urban users; for Test, mention low-tech usability methods if you have used them with less digitally familiar participants.

For product critique questions, use a structured lens: user goals first, then business goals, then technical constraints. When asked to improve the Housing.com app, start by saying 'Who is this flow for and what are they trying to accomplish?' before proposing solutions. Interviewers want to see thinking, not just visual taste.

For numbers and metrics, be precise about what you personally owned versus what the broader team achieved. Saying 'the team saw improvement in the funnel' is fine. Claiming a specific figure you did not personally track is a red flag experienced interviewers catch quickly.

Product thinking over pure craft. Housing.com is a marketplace with complex user journeys. Interviewers typically look for designers who ask 'why does this flow exist?' before they open Figma. Show that you understand the business model: seller leads, buyer intent, and agent commission structures.

Empathy for a diverse Indian audience. The platform serves users across income levels, cities, and comfort with technology. Candidates who assume high digital literacy or fast internet throughout their answers often receive pushback. Talk about bandwidth-conscious choices, vernacular language support, or low-data mode considerations where relevant.

Cross-functional collaboration skills. Housing.com teams are reportedly fast-moving. Interviewers look for designers who work closely with engineers and product managers, give and receive feedback constructively, and understand what is technically feasible before committing to a design direction.

Ownership of outcomes. A polished portfolio is table stakes. What stands out is the ability to say: 'I designed this, we tested it, here is what happened, and here is what I would do differently.' Candidates who close the loop on their own work consistently get noticed.

Comfort with design systems. With 188 open roles and multiple product teams, Housing.com values designers who can work within a shared component library and contribute back to it, not just produce one-off screens for a single feature.

Step 1: Study the product in depth. Spend focused time on the Housing.com app and website. Pick two or three flows (property search, shortlisting, contacting an agent) and note where the experience feels smooth and where it creates friction. You will almost certainly be asked to critique or improve the product in some form.

Step 2: Prepare three portfolio stories. Each story should follow STAR and include the problem brief, your specific contribution, a key design decision with rationale, and an outcome. If you have real estate or marketplace experience, lead with that story.

Step 3: Practise your process out loud. Record yourself explaining a past project in under five minutes. Interviewers often feel more confident in a candidate who can narrate their thinking clearly without rambling or jumping between topics.

Step 4: Refresh your tools knowledge. Candidates report that Figma and developer handoff workflows come up often. Be ready to discuss how you document component states, edge cases, and annotations for engineering teams.

Step 5: Prepare questions for your interviewer. Ask about the design team structure, how design decisions get made, and what a typical sprint looks like for a designer. This signals genuine interest in the role rather than just the company name.

While you are deep in interview prep, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR for you, so your job search does not stall while you are focused on this.

Jumping to solutions too fast. When given a design exercise or a 'how would you improve X' question, candidates who skip problem definition and go straight to wireframes often lose the interviewer early. Take a moment to state your assumptions and clarify the user goal before picking up a pen or opening a design tool.

Portfolios with no outcomes. Showing screens is easy. If every project ends with a Figma prototype and no mention of what happened after launch, that is a gap interviewers notice. Even a qualitative outcome ('users said they found it less confusing in our usability sessions') is better than silence.

Ignoring the Indian context. Designs that assume fast internet, large screens, or high digital literacy can feel disconnected from Housing.com's actual user base. Mention bandwidth-conscious choices, vernacular language support, or offline-friendly patterns where they are relevant to your examples.

Being defensive about feedback. If an interviewer challenges a design choice you made, they are often testing how you handle critique, not actually disagreeing with you. Stay curious: 'That is a fair point, here is why I made that call, and here is how I would explore your concern in a next iteration.'

Skipping clarifying questions in design exercises. Attempting a design task without clarifying the target user, the platform (mobile or web), and the success metric is a common slip. Interviewers at product companies typically reward the candidate who asks good questions before opening a design tool.