Stripe · Primly Community

Stripe product designer UX interview and portfolio review, my experience going through the loop

alex_design · 5 replies

finished the stripe product designer loop last month, staff level equivalent. stripe has a small but very intentional design team so the bar is high and the process reflects that.

screening:

initial recruiter screen was pretty standard. the first real filter was a portfolio review with the hiring manager. 45 minutes, they asked me to walk through 2-3 projects. the question they kept asking: "where was the hardest decision, and what made it hard?" they were clearly not looking for "here's the problem, here's my beautiful solution." they wanted to see how i navigate ambiguity, conflict with stakeholders, or constraints that forced a compromise.

the onsite (4 panels, all virtual): design exercise: 90 minutes, given the week before. the prompt was open-ended: improve one part of stripe's dashboard for a specific user segment. they gave me access to a stripe sandbox to poke around. i focused on the developer onboarding experience for first-time integrations, specifically the error messaging when API calls fail. walked through my design decisions live. they pushed on every choice. portfolio deep dive: one more portfolio round, different interviewer. this one focused on product thinking. "how did you decide what not to design?" was a specific question. cross-functional: panel with an engineer and PM. they asked how i navigate getting designs built accurately. real question about spec handoffs, redlines, and what happens when implementation drifts from design. values + leadership: how do you influence product direction without authority. i had a solid story here from a previous role and it landed well.

what they care about:

stripe is very developer-facing in their product surface. if you've never designed B2B or developer tools, spend time in stripe's actual product before the interview. understand how developers think, what error states matter, why clarity beats delight in this context. your consumer-app portfolio alone won't be enough.

also: write well. stripe's design team cares about words. labels, empty states, error messages. if you've done content design work, bring it up.

level was staff designer. offer was base $195k, equity around $400k/4yr in sf. the equity situation at stripe is something to evaluate carefully given where they are pre-IPO.

5 replies

brand_ben

the 'what did you decide NOT to design' question is underrated as an interview question. shows whether you understand scope and prioritization or just got excited and shipped features. going to steal this for my own interviewing.

ux_uma

the note about writing well is real. i reviewed a designer's portfolio for a fintech role last year and the empty state copy was all placeholder text. immediately looked less credible. it's details like that.

sam_recovering

the design exercise being a week in advance is thoughtful. take home gives you real time to think instead of whiteboard-sweating a 30 min prompt. did they give any feedback on what approach they were hoping to see?

alex_design

no prescribed direction, they genuinely wanted to see what i prioritized. i think going narrow and deep (one specific thing, done well) beats trying to redesign the whole dashboard. they said as much in debrief.

intl_isla

on the equity point: how did you think about the pre-IPO risk? that's always the part i can't model cleanly.