Vercel · Primly Community

Vercel product designer / UX interview and portfolio review: what they actually care about

alex_design · 6 replies

I went through Vercel's product design interview loop last quarter. I'm a staff-level designer with a background in consulting and I've been through a lot of design interviews at this point. Vercel's was distinct enough that I wanted to document it.

The short version: They care deeply about developer experience as a craft, and your portfolio has to show that you think about technical users, not just consumer flows.

Recruiter screen: Typical 30 minutes. They asked about my experience designing for technical audiences and specifically asked whether I've used Vercel as a developer. I had. That mattered.

Portfolio review round: One hour with two designers on the team. They picked one case study from my portfolio and went deep. And I mean deep. Not "walk me through your process" deep, but "why did you make this specific decision at this specific moment" deep. They pushed on: how did you validate this was the right solution before you built it, what did you learn that changed your original direction, how did engineering constraints shape your final design.

One thing they asked that I haven't heard elsewhere: "Who was excluded from this experience, and what tradeoff did you consciously make?" I found that question genuinely good.

Design exercise: Take-home, given 72 hours. The prompt was vague enough to be a test of how you scope. I won't share the exact prompt but it was in the devtools space. I spent about 6 hours on it. I've seen candidates go 20 hours on Vercel take-homes and I don't think that helps.

Behavioral: Pretty standard, but they care about collaboration with engineers. Half the questions were about working with engineers and how I handle design-eng disagreements.

What I'd tell someone prepping: Your portfolio MUST include at least one technically complex product. Developer tools, internal tooling, data visualization, API design, something where the user is a technical person. If your whole book is consumer apps you'll feel the mismatch. Practice explaining why you cut scope, not just what you shipped. Know their product. Use the dashboard. Have opinions about it.

Offer was competitive for a mid-market design hire in 2026, remote-friendly. I took it.

6 replies

ux_uma

The 'who was excluded' question is one of the better interview questions I've heard in a while. Did they push back on your answer or was it more of a listening round?

alex_design

They pushed a little. In a good way, like they were genuinely curious about the tradeoff I described, not trying to trip me up. It felt like a real conversation. Those are the best interviews.

brand_ben

Really appreciate this writeup. How many case studies did you have in your portfolio and did you self-select which one to present or did they pick?

alex_design

I had four cases. They picked one from the list beforehand. I think they chose the most technically dense one, which was fine because I knew it cold. Pick your cases knowing someone else might choose which one you present.

firsttime_mgr

The portfolio having devtools or technical work requirement makes sense but is also a real barrier for good designers coming from consumer companies. Did you get any sense of whether they'd consider someone without that background if the rest of the portfolio was strong?

alex_design

Honest guess: probably not at senior level. At mid level maybe, if the person demonstrated real user empathy for technical users even in consumer work. But I'd put real effort into building a technical product case before applying if you don't have one.