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

myhq is a flexible workspace platform that connects individuals, startups, and enterprise teams with coworking spaces across Indian cities. The UI/UX Designer role sits at the heart of their product team, shaping how users discover spaces, complete bookings, and manage memberships on web and mobile.

myhq currently has 30 open roles, reflecting an active hiring phase. With Delhi leading at 8 openings and Bangalore close behind at 6, competition is real but so is opportunity. Candidates typically go through two or three rounds: an initial screen, a portfolio review with the design team, and a final round that often includes a case study or design assignment. The process emphasizes practical product thinking, so expect to explain your design decisions in depth rather than just show finished screens.

These questions come up often in myhq UI/UX Designer interviews, based on what candidates report:

1. Walk us through a project in your portfolio where you improved a booking or discovery flow.
2. How do you approach designing for users who may have limited digital experience?
3. Tell us about a time you had to simplify a complex feature without losing important functionality.
4. How do you handle disagreement with a product manager over a design decision?
5. myhq serves both individual users and enterprise clients. How would you design differently for each segment?
6. Describe your process for conducting user research when time and budget are tight.
7. How do you decide between using a familiar UI pattern and introducing a new interaction model?
8. Walk us through how you would improve the workspace discovery experience on a platform like myhq.
9. How do you hand off designs to developers and make sure the final product matches your intent?
10. Tell us about a design you shipped that did not perform as expected. What did you do next?
11. How do you balance aesthetics with usability when stakeholders push for a visually bold but less intuitive design?
12. What tools do you use for prototyping, and how do you choose between fidelity levels?

Q: Walk us through a project where you improved a booking or transaction flow.

*Situation:* At my previous company, our mobile checkout flow had a significant drop-off problem the team wanted to address.
*Task:* I was asked to audit the flow and propose a redesign within a single sprint.
*Action:* I ran several usability sessions with real users and identified that the address entry step was causing the most confusion. I redesigned it using autofill and a map picker, and reduced the total number of steps by combining redundant confirmation screens into one.
*Result:* After shipping, the team tracked a measurable improvement in completion. I will be honest that the observation window was short and other factors may have contributed, so I treat it as a directional signal rather than a definitive win.

---

Q: How do you handle disagreement with a product manager?

*Situation:* A PM wanted to add a promotional banner on the main booking screen, which I felt would distract users mid-task.
*Task:* I needed to push back constructively without blocking the release timeline.
*Action:* I put together a short document comparing task-completion patterns on cluttered versus clean booking screens, drawing on publicly available research. I also proposed an alternative placement at the post-booking confirmation step, where intent to explore offers is naturally higher.
*Result:* The PM agreed to test my placement first. Candidates report that this kind of data-backed, alternative-first framing tends to work well when navigating design and product disagreements.

---

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

*Situation:* I redesigned an onboarding flow for a B2B product and was confident that a progress bar would motivate users to complete setup.
*Task:* The goal was to increase the share of users who finished onboarding.
*Action:* I shipped the new flow and tracked step-by-step drop-off using analytics.
*Result:* The progress bar actually increased anxiety for enterprise admins who felt overwhelmed seeing many remaining steps. I iterated by revealing the bar later in the flow and showing only steps remaining. The bigger lesson was to test with the actual user segment, not convenience participants. A consumer-app pattern does not always translate to an enterprise context.

For portfolio walkthroughs: structure your answer as context (what product, who the users were), the problem you were solving, your process (research, ideation, iteration), the tradeoffs you made, and the outcome. Avoid narrating what the design looks like. Interviewers want to hear your reasoning, not just see the screens.

For 'how do you approach X' questions: lead with your guiding principle, give a concrete example from your work, then state what you would do differently now. This shows self-awareness without being self-deprecating.

For disagreement or conflict questions: use a simple three-part structure. What you believed and why, how you raised it (with data or alternatives rather than just opinion), and what you decided together. Avoid framing yourself as the one who was always right.

For design assignment presentations: walk through your assumptions first, your process second, and your solution third. Make it easy for the panel to question your assumptions rather than your execution. Saying 'I assumed X because Y, and if that assumption is wrong then Z' signals design maturity and intellectual honesty.

myhq's product helps users compare, book, and manage real-world workspaces, so interviewers typically look for designers who can simplify complex decision-making flows. Based on what candidates report, three qualities stand out.

Product thinking over pure craft. Knowing Figma is expected. What gets you hired is showing that your design choices connect to user goals and business outcomes. Be ready to explain why you made a choice, not just what it looks like.

Comfort with ambiguity. Flexible workspace is a category where user needs vary widely. A solo freelancer books very differently than an enterprise team. Candidates who can scope a problem, make reasonable assumptions, and move forward tend to do better than those who wait for complete information before sketching anything.

Collaboration signals. myhq is a product-driven company. Candidates report that showing how you work with PMs, engineers, and researchers carries as much weight as the quality of your portfolio itself.

Week 1: Know the product. Use the myhq app and website as a real user. Map the booking flow, note friction points, and form a specific opinion on what you would improve and why. Come to the interview with a well-reasoned critique and a rough alternative direction. Do not criticize without a suggestion.

Week 2: Sharpen your portfolio. Pick two or three projects most relevant to marketplace, booking, or productivity tools. For each, prepare a concise verbal walkthrough covering the problem, your process, and the outcome. Practice out loud. Hearing yourself explain your work reveals gaps you will not catch by reading your notes silently.

Prepare for a design assignment. Many candidates report receiving a take-home case study or a live whiteboard exercise. Practice designing a booking or onboarding flow under a time constraint. Focus on clear problem framing and honest articulation of tradeoffs, not visual polish.

Research the category. Look up what publicly reported design challenges coworking and flexible workspace platforms face, such as discoverability, trust-building for unfamiliar locations, and the gap between individual and enterprise user needs. This gives you vocabulary to connect your past work to myhq's specific context.

If you are actively applying to roles like this, knok checks 150+ job sites nightly, applies to jobs that match your resume, and messages HR on your behalf, so you are not losing ground while you are busy preparing.

Showing only finished screens. Interviewers at product companies want to see how you think, not just the final output. Include wireframes, rejected ideas, and notes on why you made specific tradeoffs. A polished deck with no visible thinking raises red flags.

Vague impact claims. Saying 'users loved it' or 'it improved engagement' without context is unconvincing. Even if you do not have hard numbers, describe what signals you tracked and what direction they moved. Honest, specific observations beat inflated claims every time.

Ignoring the developer handoff step. Candidates often talk about design but skip how they worked with engineers. Mentioning how you annotate specs, how you handle edge cases, or how you follow up during implementation shows professional maturity.

Designing for yourself. When given an assignment, candidates often jump to their preferred solution. Show that you started by questioning assumptions and thinking about different user types before sketching anything. Interviewers notice when research and problem definition are skipped.

Not asking questions. Interviews are two-way. Candidates who ask nothing about the team, the design process, or current product challenges come across as passive. Prepare at least three thoughtful questions and use them.