Pinterest · Primly Community

Pinterest product designer / UX interview and portfolio review: what they're actually evaluating

alex_design (Primly starter) · 5 replies

I went through the Pinterest design loop last fall for a senior IC role. Sharing because design interview breakdowns are weirdly rare compared to SWE write-ups.

First thing to know: Pinterest has strong design opinions. They care about visual quality AND systems thinking AND user insight. You need all three. If your portfolio is strong on craft but you can't talk about user problems in structured, evidence-based terms, you'll get filtered. If your portfolio is all process and weak on the final output, also a problem.

Portfolio screen (45 min) One recruiter, sometimes joined by a design manager. They'll ask you to walk through 1-2 projects. Pick work that shows: a real constraint, a messy middle phase, a concrete decision you made and why, and an outcome. Don't over-polish into a case-study teleprompter. They ask follow-up questions and they can tell when you're reciting versus remembering.

For Pinterest specifically: consumer-facing work reads better than pure enterprise. They want to see you think about emotion and delight, not just task completion.

Design challenge (1 week, take-home) Mine was a prompt around improving content discovery. Nothing said "build a Pinterest feature" but the domain was relevant. They gave a user research brief and some constraints. I spent about 8 hours total. The deliverable was a Figma deck: problem framing, explorations, final concept, rationale.

Things they cared about in the debrief: why I narrowed to this solution over alternatives, accessibility decisions, what I'd validate first. Not pixel-perfect. They want thinking.

Design critique round They showed me an existing interface (not Pinterest, but a consumer app) and asked me to critique it. Structure this out loud: identify the user goal, what's working, what's creating friction, what you'd change. They're watching how you organize a critique, not just whether you spot the obvious issues.

Cross-functional round Half design, half collaboration. Expect questions like: how have you pushed back on product direction, how have you worked with eng constraints, how do you involve research when timelines are short.

Overall it was one of the more substantive design loops I've been through. They take design seriously as a function, which isn't universal.

由 AI 翻译，查看原文

5 replies

brand_ben (Primly starter)

The bit about consumer-facing work reading better is real. I've been at an agency for 5 years and I always worry my work looks too B2B when I go for consumer roles. Did you find Pinterest cared about the visual style of your portfolio or just the thinking?

alex_design (Primly starter)

Both, but if I had to rank it: thinking first, visual execution second. The caveat is that visual execution still has a floor. Sloppy UI will get you dinged. But a beautifully designed portfolio with shallow reasoning won't get you through either.

ux_uma (Primly starter)

Really appreciate you mentioning the design critique round. Did they give you context on the user beforehand, or did you have to ask clarifying questions at the start?

pm_priya (Primly starter)

The cross-functional round sounds basically identical to the PM behavioral round. Makes sense, but good to know design isn't getting a pass on the influence/push-back questions.

Primly Team

One stage people tend to underestimate in design loops is the follow-up questioning inside the portfolio review. The project itself matters, but the signal often comes from how you reason under interruption: can you name the decision, the options you considered, the constraint you could not change, and the evidence you trusted most.

A useful structure is to anchor every answer in a single “decision log” moment: what was unclear, what you did to reduce uncertainty (research, prototypes, metrics, crits), what tradeoff you accepted, and how you validated the outcome. Then add one sentence on what you would do differently with more time. That last part reads as maturity, not weakness.

A common failure mode is staying at the level of artifacts and activities, instead of explicitly connecting choices to user impact and product goals.

What portfolio question or follow-up caught you off guard in your Pinterest (or similar) interview, and how did you answer it?