Plaid · Primly Community

Plaid product designer / UX interview and portfolio review: what to bring and what they focus on

alex_design · 5 replies

went through plaid's product designer loop a couple months ago for a senior role. this is my attempt to write the post i wish existed before i started prepping.

format: recruiter call portfolio screen with a hiring manager (45 min): walk through 2-3 projects, expect to go deep on one design exercise (take-home, 5 day window): redesign or concept for a specified fintech scenario virtual onsite: portfolio deep dive, design critique, cross-functional scenario, and a values/behavioral round

the portfolio screen:

they want to see fintech-adjacent or complex-data-display work. i'm not saying only apply if you've done banking apps, but you need to be able to talk about how your work translates. if you've designed dashboards, data visualization, forms with high stakes (medical, financial, identity) that all signals well. show work where the constraint was real.

the take-home:

i can't share the exact prompt but it was scenario-based: design a specific feature for a fintech context. they gave me about a page of context and constraints. they're not looking for a pretty prototype. they want to see your process: how you frame the problem, what questions you ask, how you handle the tradeoffs, what you'd test and why. i did a figma deck with annotated thinking, not just polished screens.

the design critique round:

they showed me a real or real-feeling UI (i think it was plaid-adjacent, not obviously internal) and asked me to critique it. i talked about information hierarchy, error states, what happens when the API call fails, mobile considerations. they pushed on my reasoning more than on specific fixes.

what they care about overall: systems thinking. can you design a component in a way that scales across many use cases? fintech-aware constraints: regulatory, accessibility, trust/credibility signals in financial interfaces the developer handoff perspective. plaid is developer-first, so the design needs to live in an API-driven context. behavioral: they asked "tell me about a design decision you pushed back on and how that went."

what i'd tell someone prepping: the take-home is where they make their decision. treat it like a 5-day sprint for a real client. show your thinking, not just your output.

5 replies

brand_ben

the point about the developer handoff is interesting for a B2B-ish product like plaid. is the audience mostly developer-facing (like the dashboard that bank developers use) or is it also consumer-facing (the link widget)? curious how they think about that split in design.

alex_design

replying to brand_ben: both, and that's part of what makes it interesting. the link widget is consumer-facing but embedded by developers who have their own design constraints. you're designing for a user who exists inside someone else's product. the design critique round touched on exactly this tension.

ux_uma

did you have to do any user research component in the take-home or onsite? wondering if they evaluate research skills separately or if it's all embedded in the design exercise.

alex_design

no separate research round for the IC designer role. but in the take-home i included a "what i'd want to learn" section with research questions i'd want answered before shipping. they brought it up positively in the debrief from what my recruiter told me. so i'd recommend showing that thinking even if you can't actually do the research.

nonprofit_nia

this is really thorough. the note about high-stakes forms (medical, financial, identity) translating well is helpful for people like me coming from less obvious backgrounds. i've designed grant application flows which have a similar "you can't mess this up" weight to them.