Ramp · Primly Community

Ramp product designer / UX interview and portfolio review: an honest breakdown

brand_ben · 4 replies

I went through the Ramp design interview process earlier this year (2026) for a mid-level product designer role. There's almost nothing specific to Ramp design interviews online so hopefully this helps someone.

The portfolio review This is where the process starts diverging from what most design interview guides prepare you for. Ramp is a B2B fintech tool, so the people reviewing your portfolio are thinking about: can this person design dense information tables, complex approval flows, edge cases in multi-step forms? If your portfolio is mostly consumer apps with hero images and clean landing pages, you need to do some explaining.

I led with a case study on a billing dashboard I'd redesigned. That resonated immediately. The questions were fast and specific: how'd you decide on this table layout vs a card layout, what was the accessibility story for this status badge, did you user-test the approval flow or did you ship and iterate. They were not interested in my brand work. I mentioned it briefly; nobody asked a follow-up.

Expect about 45 minutes on portfolio review with 2-3 people (product, design lead, sometimes engineering). Bring 2-3 deep case studies rather than 8 shallow ones.

Design exercise They gave me a prompt during the onsite: redesign the expense submission flow for a power user who submits 50+ expenses a week. Real problem, which I appreciated. I had about 30 minutes to think and sketch (low-fi is fine), then present and take feedback for another 30.

They pushed on: how do you reduce friction at scale, what information does the user need vs what can you defer, how do you handle error states when a receipt can't be parsed. The design system question came up: if we already have components for this, how do you work within constraints vs advocate for something new.

Behavioral Standard design behavioral questions: conflict with eng, how do you handle feedback that changes your direction late, how do you communicate design decisions to stakeholders who don't read design docs.

Bottom line: Ramp wants product designers who think in systems and can handle complexity. The aesthetic bar is secondary. If you love clean minimal B2C work and find enterprise UI depressing, this might not be the fit. If you get nerd-excited by a well-designed approval modal, you'll enjoy the interview.

4 replies

ux_uma

This is really useful. Did they ask about your research process at all, or was it entirely about your visual/interaction work?

brand_ben

Research came up in the context of the case studies, not as a standalone thing. They asked how I validated design decisions in my billing dashboard case. I'd done some lightweight usability testing and they were satisfied with that. I don't think they have a dedicated UX researcher on every team so the designer is expected to do lightweight research. If you have that in your toolkit definitely highlight it.

mobile_mara

Honest question: were the interviewers actual designers, or was it a PM and an eng who vaguely understand design? Makes a big difference in how to pitch your work.

brand_ben

Mix. Design lead was definitely a designer and had sharp, specific questions. The PM interviewer was good at the product thinking angle but couldn't really engage with the component-level choices. I'd pitch to both simultaneously: lead with the user problem and business outcome, then offer to go deeper on the craft if they want it. The design lead will pick it up.