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

Meragi is a wedding-tech platform that connects couples with venues, caterers, decorators, and photographers through a single app. With a product built around one of life's most emotionally charged purchases, the company expects its UI/UX designers to deliver flows that are visually polished and genuinely calm to use. As of July 2026, knok's jobradar shows Meragi has 28 open roles across teams, signaling active hiring across functions.

The UI/UX Designer role typically sits within the product team and involves end-to-end ownership: discovery research, wireframes, prototypes, visual design, and handoff to developers. Candidates report the interview process typically runs across two to three rounds, beginning with a portfolio review, followed by a design task or case study, and ending with a product and culture discussion. Most candidates hear back within two weeks of each round, though timelines vary.

Across India, UI/UX Designer openings at companies like Meragi are concentrated in metro cities. Based on knok data as of July 2026, Delhi leads with 8 listings, Bangalore follows with 6, and Mumbai has 4. Hyderabad and Pune each show 1 listing.

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

1. Meragi serves couples making a high-emotion, high-stakes decision. How do you design for users who are excited but also anxious about getting it right?

1. How do you approach user research when you have very little time or budget?

1. Show us a design decision you made that you later had to revisit. What did you learn from changing it?

1. How do you handle a situation where business goals and user needs point in opposite directions?

1. Describe your process for building a design system or component library from scratch.

1. How do you hand off designs to developers and make sure the final product matches your intent?

1. Tell us about a time you had to simplify a complex feature without losing what made it useful.

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

1. Meragi's product spans mobile and web. How do you adapt a design across platforms without starting from scratch each time?

1. Walk us through how you would approach redesigning our vendor discovery or shortlisting flow. (Candidates report a live exercise of this type may appear in later rounds.)

1. How do you prioritise design requests when multiple teams are asking for your time at once?

Q: Tell us about a time you simplified a complex feature without losing its value.

*Situation:* I was working on a multi-step booking flow for a home-services app. The original flow had too many steps, and drop-off data showed most users were abandoning midway through.

*Task:* My task was to reduce drop-off by redesigning the flow, without removing any legally required information fields.

*Action:* I ran usability sessions with five participants to find which steps caused the most confusion. I merged three address-entry steps into a single smart-fill form, moved optional fields to a post-booking screen, and added a progress indicator showing only four visible stages instead of the full sequence. I worked closely with the backend team to confirm which fields could safely be deferred.

*Result:* The redesigned flow launched within six weeks. Internally tracked completion rates improved, and the product manager reported a visible drop in support tickets related to booking confusion.

---

Q: How did you handle a conflict between what users wanted and what the business needed?

*Situation:* During a food-delivery app project, user research showed people wanted to see the full ingredient list before ordering. The business team said displaying long lists slowed page load and hurt conversion.

*Task:* I needed a design solution that addressed both concerns without either side feeling overruled.

*Action:* I proposed a collapsed 'ingredients' accordion that loaded only on tap rather than on page open. I also designed an A/B test comparing the original page, a full-display version, and the accordion version. I presented the test plan to both the UX lead and the business stakeholder before starting, so everyone agreed on how we would evaluate the result.

*Result:* The accordion version showed comparable conversion to the original while meeting the user transparency need. Both teams approved the approach, and it became a reusable pattern in our design system.

---

Q: Describe a time you delivered design work under tight deadline pressure.

*Situation:* Three days before a product demo to potential investors, the product manager told me the onboarding flow needed a complete visual refresh to match a new brand identity.

*Task:* I had to update six key screens while keeping all interactions identical so developers would not need to rewrite any code.

*Action:* I audited each screen to separate purely visual elements (colours, typography, icons) from structural ones. I updated the design tokens in Figma first, then applied them across all screens in a single batch. I held a brief daily check-in with the developer to catch any implementation questions before they became blockers.

*Result:* All six screens were ready for handoff within two days. The demo used the updated designs, and the team received positive feedback on the new visual direction.

The Design Narrative Framework works well for portfolio walkthroughs. Structure each project story around four beats: the user problem (who was struggling and why), your process (what you explored and what you ruled out), the decision (what you chose and the trade-off you accepted), and the outcome (what changed for the user or the business). Keep each beat brief. Meragi interviewers want to understand how you think, not just what the final screen looked like.

The Constraint-First Approach is useful for case study or live design questions. Before sketching anything, say out loud: 'My constraints are X, my users need Y, my success measure is Z.' This signals that you design within real conditions rather than in a vacuum, which matters at a startup where resources are finite.

The Trade-off Articulation helps with conflict or prioritisation questions. Use this structure: acknowledge both sides clearly, name the lens you used to decide (user impact vs. revenue vs. effort), state what you chose, and name what you gave up. Candidates report that Meragi interviewers respond well to designers who own the trade-off rather than pretending there was no downside.

For live design tasks, talk out loud from the very beginning. Describe what you are noticing before you start sketching. Silence in a live exercise reads as uncertainty even when you are thinking carefully.

Meragi builds for couples navigating a high-involvement, emotionally charged purchase where trust and clarity matter far more than visual flair. Interviewers typically look for these qualities in UI/UX designer candidates:

Empathy for emotional users. Wedding planning is personal and often stressful. Candidates who show they consider user anxiety, not just user tasks, stand out. Bring up moments from past work where the emotional context of a user shaped a specific design decision.

End-to-end ownership. Startup design roles rarely split research, interaction design, and visual design across different people. Be ready to walk through your full process: research, wireframes, prototypes, visual polish, and developer handoff, all as one continuous workflow.

Speed without sloppiness. Startups move fast. Interviewers want evidence that you make good decisions with limited time and incomplete information, and that you know when to go deeper versus when to ship a 'good enough' version.

Clear communication with non-designers. Meragi's teams are cross-functional. Candidates report that interviewers pay close attention to how clearly you explain design decisions to engineers, product managers, and business stakeholders.

Genuine curiosity about the product. Come with real questions about the product. Candidates who have used the Meragi app and can speak to a specific flow they found interesting, or one they would improve, make a noticeably stronger impression than those who treat the company as interchangeable.

Week one: Know the product. Download the Meragi app and use it the way a real couple would. Pick two flows, such as venue discovery and vendor shortlisting, and note one thing that works well and one you would change. Write down your reasoning so you can articulate it clearly in the interview.

Week one: Tighten your portfolio. Choose two to three projects most relevant to consumer mobile apps or marketplace products. For each, prepare a two-minute verbal walkthrough covering the problem, your process, one decision you are proud of, and one thing you would do differently today.

Week two: Practice case studies. Pick a feature on any wedding or event app and redesign it in Figma or on paper, treating it like a timed exercise. Aim to produce a clear problem statement, two to three design options, and a recommendation with trade-offs in under an hour.

Week two: Prepare your STAR stories. Write down at least four situations from past work covering: a time you simplified something complex, a time you handled a stakeholder conflict, a time you worked under pressure, and a time a design did not work as expected. Practice saying each one out loud in under two minutes.

Before the interview: Read the job description carefully. Match every skill listed to a specific example in your portfolio. If the description mentions design systems, have a project ready where you built or contributed to one.

If you are actively job-searching alongside this prep, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf, so you can spend your energy on interviews rather than applications.

1. Showing only final screens. Interviewers at product companies want to understand your thinking, not just admire the output. Include early sketches, rejected options, and the reasoning behind key decisions in your portfolio walkthrough.

1. Avoiding any mention of outcomes. Even rough measures matter. 'The redesign improved completion rates based on internally tracked data' is stronger than 'the team felt it was better.' If you genuinely have no data, explain what you would have measured and why.

1. Not knowing the Meragi product. Candidates who have not used the app struggle when asked 'how would you improve our discovery flow?' Generic answers are easy for interviewers to spot.

1. Treating a live design task as a solo exam. Interviewers often want to see collaboration instincts alongside design skill. Ask clarifying questions before you start, state your assumptions, and check in mid-way rather than working in silence until the end.

1. Underselling cross-functional work. At a startup, working effectively with engineers, product managers, and business teams is as important as visual craft. Actively highlight moments when you bridged gaps between teams or made a developer's job easier.

1. Running out of questions at the end of the interview. Always have two or three thoughtful questions ready, such as: 'What does the design review process look like here?' or 'What is the biggest user pain point the product team is focused on right now?'