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

materialdepot is a home interiors and building materials marketplace that helps homeowners, interior designers, and contractors discover, compare, and buy products ranging from tiles and flooring to lighting and hardware. The platform carries a large catalog with complex specifications, so the UI/UX team works on problems like search, filtering, product comparison, and checkout flows that serve very different types of buyers.

As of July 2026, knok jobradar recorded 37 open roles at materialdepot. Among UI/UX Designer openings, Delhi had 8, Bangalore had 6, Mumbai had 4, Hyderabad had 1, and Pune had 1 in that snapshot.

Candidates report the process typically runs 3-4 stages: a portfolio review call, a design assignment or take-home task, a design team interview, and a final round with a product or hiring manager. The full process typically takes 2-4 weeks. Expect the portfolio review to anchor every stage, so prepare to narrate your decisions, not just show visuals.

These questions reflect patterns candidates report for product-focused design roles at catalog-heavy e-commerce companies.

1. Walk us through a project where you improved search or product discovery for a large catalog.
2. How would you redesign the category navigation on materialdepot to help a homeowner quickly find the right tile for their bathroom?
3. How do you design for users who are not tech-savvy, such as contractors placing bulk orders from a phone?
4. Describe your research process when you have a tight deadline and cannot run full usability studies.
5. How do you balance visual appeal with conversion on a product listing page?
6. Tell us about a time you pushed back on a stakeholder request. How did you handle it?
7. How do you design catalog pages that serve both mobile shoppers browsing casually and desktop users doing detailed comparisons?
8. What metrics do you look at after a design ships to know whether it worked?
9. Walk us through how you would design a 'compare products' feature for a site with thousands of SKUs and complex specifications.
10. How do you make sure your designs work well for users in Tier 2 and Tier 3 cities with slower internet?
11. Describe a time you worked closely with developers to get a design shipped as intended.
12. How do you keep a design system consistent when multiple designers are working across different parts of the product?

Q: Walk us through a project where you improved product discovery for a large catalog.

*Situation:* At a home decor startup, users were bouncing off category pages without adding items to cart. Analytics showed people landing on 'flooring' and leaving quickly.

*Task:* I was asked to redesign the category page to reduce drop-off and improve add-to-cart behavior.

*Action:* I ran several usability sessions and found users thought in terms of room type ('my bedroom') rather than material type ('hardwood vs laminate'). I redesigned the filter structure to lead with room and style, added a visual entry point using mood-board thumbnails, and built a mobile-first filter drawer. I ran two rounds of prototype testing before handoff and documented component specs to reduce dev-to-design drift.

*Result:* Post-launch, the team tracked improvement in session depth and add-to-cart rate on that page, though the pre and post sample was small. The mood-board entry point was later reused across three other categories.

---

Q: Tell us about a time you pushed back on a stakeholder's design request.

*Situation:* A product manager wanted to add a large promotional banner at the top of the product detail page, citing the marketing team's request.

*Task:* I needed to either accommodate the request or present a data-backed alternative that protected the user experience.

*Action:* I pulled session recordings and heatmaps showing users scrolled past promotional content and focused on the first product image and price. I prepared a short comparison of three options: full banner, a compact ribbon, and an inline badge on the image. I framed each option around the PM's own goal (promotion awareness) rather than as a design preference.

*Result:* The team aligned on the compact ribbon. The PM said the structured comparison made the decision straightforward. I used this exercise to start a 'promotion placement' guideline for the team.

---

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

*Situation:* I was working on a B2B ordering tool for small hardware shop owners in smaller cities. User interviews revealed many were on slow connections and used entry-level Android phones.

*Task:* I had to redesign the order flow to work smoothly under those constraints without making the interface feel stripped down.

*Action:* I replaced image-heavy product cards with text-first layouts and lazy-loaded images. I added an offline cart that synced when connectivity returned, simplified forms to only essential fields, and used larger tap targets throughout. I tested on actual low-end devices rather than only browser throttle settings.

*Result:* Order flow completion improved according to the team's internal tracking, though the initial user base was small. The offline cart was cited in follow-up user interviews as the most valued change.

For portfolio walkthroughs: Follow a problem-to-impact structure. Start with the user problem and business context, explain your research method, share your key insight, describe your design decisions and the reasoning behind them, and close with what happened after launch. If results were limited, be honest about that rather than overstating impact.

For 'how would you design X' questions: Use a lightweight discovery frame. Name what you would first want to understand (users, goals, constraints), identify the key trade-offs, describe one or two directions you might prototype, and explain what you would measure. This shows structured thinking even without a finished answer.

For conflict or stakeholder questions: Use a three-part structure: what was being asked, what you observed or measured, and how you framed the alternative. Focus on your process. Interviewers want to see you can navigate disagreement professionally.

For 'metrics and success' questions: Name signals specific to the design (task completion rate, time on task, error rate, scroll depth, add-to-cart rate) rather than giving a vague answer like 'user satisfaction'. Connect the metric back to the original problem to show you close the loop.

Deep thinking over polished screens. materialdepot handles a complex catalog and a range of user types. Interviewers want to understand why design decisions were made, not just that you can produce high-fidelity mockups.

Comfort with e-commerce and catalog complexity. If you have worked on search, filtering, product comparison, or checkout flows, lead with those projects. If not, prepare a 'how I would approach it' answer for catalog navigation.

Research grounding. Candidates report that interviewers ask how you validated your decisions. Have a clear answer for how you conduct research when time is short, whether that is guerrilla testing, reviewing session recordings, or working from existing analytics.

Cross-functional collaboration. Interviewers typically want evidence that you work well with PMs and developers, not just within the design team.

Intellectual honesty about results. If your projects had small sample sizes or inconclusive data, say so. Product companies value honest framing far more than inflated impact claims.

Before your first call:
Spend time on materialdepot's website and app. Review the catalog navigation, search experience, product detail pages, and checkout. Form two or three specific opinions on what works and what could be improved. This gives you grounded answers when interviewers ask 'how would you redesign X.'

Prepare 3-4 portfolio projects with full narratives ready. For each, practice the problem-to-impact structure: user problem, research method, key insight, design decisions, and outcome with honest caveats on data quality.

For the design assignment (candidates report this is common):
Read the brief carefully and ask one or two clarifying questions before starting. Spend time framing the problem before jumping to solutions. Document your assumptions explicitly. Show multiple directions or iterations rather than one final answer. Explain trade-offs clearly.

For the design team interview:
Expect to present your assignment and answer questions about your process. Prepare to discuss design-developer handoff, managing feedback from multiple stakeholders, and maintaining consistency across a growing product.

Practical steps:
Learn basic home interiors and building materials vocabulary so you can speak naturally about the domain (SKU, finish type, grout, lead time). Review Glassdoor and LinkedIn for any publicly shared interview experiences from candidates at materialdepot or similar companies. Practice talking through your work out loud, because narration matters as much as the work itself.

If you want to track new openings as they appear, knok checks 150+ job sites nightly, applies to roles matching your resume, and messages HR for you.

Showing only final visuals without explaining the process. The most common portfolio mistake is walking through screens without explaining the problem, the research, or the decisions that led there. Interviewers want to understand your thinking.

Overstating impact without acknowledging data limits. Claiming strong improvements on a small or short sample without context sounds like exaggeration. State your outcomes with honest caveats about sample size and timeframe.

Treating the design assignment as a visual test. Candidates who produce the most polished mockups do not always move forward. Clear problem framing and well-reasoned decisions matter more than pixel-perfect execution.

Not researching the domain. Stumbling on basic home interiors vocabulary signals low engagement with the actual product. Spend an hour on the site before your interview.

Avoiding metrics entirely. Saying 'users liked it' is not enough. Even if your data was thin, name what you measured and what you would track next time.

Not asking questions. Candidates who clarify scope and constraints upfront consistently come across as more senior than those who silently make assumptions during a design exercise.