Went through the HubSpot product designer loop in early 2026. It was one of the more thoughtful design interview processes I've been through, which is a weird thing to say, but here we are.
Context: I was interviewing for a product designer role on one of their CRM product teams. The JD mentioned UX, systems thinking, and working closely with PMs and engineers, which matched the reality.
What the process looked like: Recruiter screen. They asked the usual, plus: what draws you to B2B product design. Have a real answer. HubSpot knows they're not a consumer brand. They want designers who are energized by complex workflows, not just pretty interfaces. Portfolio review with a hiring manager (60 min). This is the most important round. They don't just want to see pretty screens. They want to understand your process: how did you scope the problem, how did you work with research (did you do any?), how did you navigate constraints, what tradeoffs did you make. Bring 2-3 case studies and be able to go deep on at least one. I went deep on a table/data-dense redesign I'd done at a previous job. That resonated because HubSpot's CRM has a LOT of dense data views. Design exercise (take-home, 3 days). I was given a fictional CRM feature scenario and asked to produce a design brief + wireframes. They specifically said not to over-polish. A PDF or Figma with clear thinking mattered more than pixel-perfect mockups. I put in maybe 8 hours. That felt right. Onsite (half-day, virtual). Three rounds: Present your exercise. 20 min presentation, then lots of questions. One interviewer played a skeptical PM. Not in a mean way, but they pushed on feasibility and scope. Cross-functional collaboration round. Stories about working with engineering, PMs, researchers. Conflict resolution. Timeline crunch. Values/culture round. Same HEART stuff.
The bar felt like: can you think clearly about complex product problems, communicate decisions, and play well with others. Less about visual craft than I expected, more about structured thinking.
One specific thing they pushed on in my exercise debrief: error states and edge cases. They noticed I hadn't designed what happens when a CRM import fails. Good catch, fair call.
I got an offer. Senior designer level. I'd say the process respected my time more than average.