“Why do you want to work at HubSpot?” — how to answer it well

“I want to work at HubSpot because I've been on the other side of the product. I ran demand gen at a 30-person company where HubSpot was the only reason two of us could run what normally takes a team of eight. That experience is also the reason I care about the customer segment — I know exactly what it feels like when a tool assumes you have an ops team and you don't. And the Culture Code line that stuck with me is 'solve for the customer', because it's the tie-breaker I already use: last year I killed a campaign that was hitting its MQL number because the leads were converting badly downstream, and I'd rather explain that than hit a vanity target.”

“Two things. The problem space is genuinely hard in an interesting way — you're building software for people who will never read a manual, which puts an enormous premium on defaults and reliability. That's the kind of constraint I like designing under. Second, I want to work somewhere transparency is structural rather than aspirational; HubSpot publishes the Culture Code and I could tell from my interviews so far that people actually reference it. I've worked in the opposite environment and I'm not going back to guessing at strategy.”

“Because at HubSpot support isn't the cost center. The customer base is small businesses where one bad onboarding costs them a quarter, and the company structures around that instead of deflecting tickets. I spent three years in CS for a product with a self-serve motion, and the work I was proudest of was rewriting our onboarding sequence after I traced 40% of churn to week two. That is the same job I'd want to do here, just at a scale where it matters to a lot more people.”