Bain & Company · Primly Community

Bain & Company product designer UX interview and portfolio review: what they actually want to see

alex_design · 4 replies

Went through Bain's design interview process for a product designer role on their internal tools team. I have a consulting background before I switched to design, which made some of this feel familiar. But the portfolio review was different from what I'd seen at product companies. Sharing notes.

Context: Bain's internal design team is small. They build tools for their own consultants: data visualization platforms, client deliverable tools, internal knowledge bases. You're not designing consumer apps. Your users are extremely smart, extremely busy, and extremely opinionated about their workflows. Keep that in mind.

The portfolio review (60 min with design lead + a senior engineer): They asked me to walk through two projects. The twist was they kept interrupting to ask business questions, not just design questions. 'What was the ROI of this redesign?' 'How did you measure whether the navigation change was actually used differently?' 'What would you do if the project had been cut after research but before design?'

For consulting firm design work, you need to be able to talk about impact in business terms, not just usability metrics. 'Time on task went down 18%' is fine but 'consultants now finish this step 45 minutes faster per client deliverable and that time gets reinvested into analysis' is what lands.

UX fundamentals round (45 min): Three rapid-fire design problems. One was about designing a dashboard for a partner who checks it once a week vs. a junior associate who uses it daily. They want to know you understand different user types, not that you can sketch a pretty UI.

Behavioral round: Similar to the EM interview, they care a lot about how you collaborate with non-designers. One question that caught me: 'tell me about a time a stakeholder overrode your design recommendation and you were right, and how you handled it.' They're not looking for 'I pushed back harder.' They want to see grace under pressure plus the ability to plant a flag on the right things.

What to prep: know Figma well (it's their tool), be ready to talk business impact on every case study, and have a story about design for domain experts vs. casual users.

Timeline: 4 rounds over 5 weeks. Got an offer and took it. Worth it so far.

4 replies

ux_uma

The 'design for domain experts' thing is such an important distinction. The patterns that work for casual consumer users often patronize expert users. Power users need density and control, not simplified flows. Sounds like Bain understands that.

brand_ben

The business-impact framing for portfolio cases is something more designers should internalize regardless of industry. 'Usability improved' without a dollar sign attached doesn't move decisions.

nonprofit_nia

How did the role feel in practice vs what was described in interviews? I sometimes worry consulting firm internal roles end up being mostly decks and not much actual design work.

alex_design

Legitimate worry and I asked the same thing in my interviews. Two months in: it's real design work but the deliverables do end up in more presentations than I'm used to. The trade-off is that stakeholder exposure is very high. You'll present to partners regularly. If you want to practice design communication and business reasoning, it's actually great for that. If you want heads-down craft time, less so.