MongoDB · Primly Community

MongoDB product designer / UX interview and portfolio review: my experience

brand_ben · 3 replies

went through the MongoDB product designer interview process last fall. applied for a role on the Atlas Cloud experience team. I have 8 years of experience, agency background, now more product-focused. sharing because design interview write-ups for companies like MongoDB are rare.

the process was longer than I expected for a non-FAANG company. here's the breakdown:

initial screen with recruiter (30 min): standard background, why MongoDB, timeline.

design screen with a senior designer (60 min): they pulled up my portfolio and walked through two projects with me. they wanted to understand my process, not just the outcome. specifically they asked: 'what did you cut and why' and 'what would you do differently.' they probed hard on any project where the final design looked polished but I hadn't explained the decision-making well. lesson: for every case study you present, know your reasoning, your constraints, and your regrets.

design challenge (take-home, 1 week): I was given a prompt about improving the onboarding experience for a new Atlas user who had never used a document database before. realistic and relevant. I spent probably 12-15 hours on it. they asked for research synthesis, a problem framing, and 3 concept directions with one explored in higher fidelity.

panel onsite (3 rounds via video): portfolio deep-dive with 2 designers: 45 min, they picked a project from my take-home and asked follow-up questions. very collaborative. cross-functional round with a PM and a front-end engineer: how do you work with PM on scope, how do you communicate design decisions to engineers. practical questions. behavioral with the design director: values alignment, how I handle design feedback from stakeholders, how I think about craft vs. velocity.

the design bar at MongoDB felt high. they're not looking for someone to generate Figma frames quickly. they want someone who can explain tradeoffs and work across functions.

level would have been senior designer. comp was around $175-185k total for NYC. I turned it down for a role that was a better team fit but the process was good.

3 replies

ux_uma

the 'what did you cut and why' question is such a useful signal. any designer can show you the final design. very few can articulate what didn't make it and why. good for them for asking it.

alex_design

12-15 hours on a take-home is a lot but for a complex enterprise product like Atlas that honestly sounds right. the onboarding prompt they gave you is a genuinely hard problem. document model mental models are a known friction point for devs coming from SQL.

apm_aisha

the cross-functional round with PM and eng together is interesting. a lot of companies do those separately. putting them in the same room tells you something about how those three functions actually work there.