Zoom · Primly Community

Zoom product designer / UX interview and portfolio review: here's how it went

brand_ben · 5 replies

Just finished the Zoom product designer interview process for a mid-senior level role on their core meetings product. The portfolio review is the centerpiece of their loop and I want to give people a real picture of what that looks like.

Process overall: recruiter screen (30 min), portfolio screening call (45 min), then a 4-round virtual onsite. No take-home design challenge, which was a relief.

Portfolio screening call: this was one-on-one with a senior designer on the team. They asked me to walk through one case study in detail, then asked a second case study at a high level. What they're looking for at this stage: clear problem framing before you show any pixels, evidence you talked to real users, explicit decision points where you chose one direction over another with reasoning. The interviewer pushed back on two of my design decisions mid-walkthrough. Don't panic when that happens, it's intentional. They want to see how you respond to pushback.

Onsite structure: Portfolio deep-dive (60 min): two case studies in depth. Same deal as the screener but harder follow-ups. Be ready to defend your research methods. I got asked why I chose unmoderated usability testing over moderated for one project. Have a real answer. Design exercise (45 min): given a prompt in-session, whiteboard (virtual). Mine was: redesign the Zoom waiting room experience to reduce participant anxiety before large meetings. They care more about your process than the output. I spent the first 10 minutes defining the problem space and user goals before sketching anything. Cross-functional collaboration round: mostly behavioral. How do you work with PMs? How do you handle scope creep on design work? One question about a time engineering pushed back on a design because of implementation complexity. Hiring manager round: values, ways of working, how you like feedback delivered. Pretty conversational.

One thing that caught me off-guard: they asked about accessibility explicitly in two different rounds. Have real examples of designing for accessibility, not just "I follow WCAG 2.1 guidelines" as an answer.

Overall the team felt sharp and invested in craft. The process is longer than most startups but shorter than Google. I got good vibes.

5 replies

ux_uma

The accessibility question coming up in multiple rounds is a signal the team actually cares about it. A lot of companies pay lip service but the interview process reflects what they actually build for. The "why unmoderated vs. moderated" question is a good one too, sounds like they want designers who can defend methodological choices.

returner_ren

how many case studies total did you prep for this? I always struggle with how many is enough without over-prepping into paralysis.

brand_ben

I had 4 fully polished and 2 more I could speak to at a high level. In the actual interviews they pulled from 3 of my main 4. having a fifth in the back pocket never hurt anyone but 4 strong ones is probably the floor for a loop like this.

alex_design

The waiting room redesign prompt is a good one, lots of angles to explore. Did they push you toward mobile vs. desktop or leave the scope open for you to define?

brand_ben

Left it completely open. Defining the scope was part of the exercise. I asked one clarifying question ("are we optimizing for hosts or participants?") and they said both, which I then used as a reason to separate the experience into two user flows. That seemed to land well.