Technical Lead II, Backend- Revenue Systems

POS-31645

The mission:

As HubSpot grows, so does our revenue. Our job is to ensure every customer is invoiced correctly, that they understand what they're paying for, and that HubSpot's financials reflect reality. This role owns that guarantee, to our customers and our business.

Why this matters:

When a customer opens their HubSpot invoice, they're not thinking about our billing systems. They're trusting that the number is right and that they can understand it. That trust is invisible when we earn it and devastating when we break it.

HubSpot processes billions in customer transactions annually. Getting invoices right isn't just an internal concern, it's how customers experience their relationship with us, and it's how we report our business.

The challenge:

HubSpot moves fast. New products launch, pricing models evolve, edge cases emerge. The business doesn't wait for billing systems to catch up, and it shouldn't have to.

We need someone who can think differently about revenue systems in a world of constant adaptability: building systems that generate correct invoices, validate them continuously, and help customers understand exactly what they're paying for, all while the product keeps evolving around them.

Why this role, why now:

You'll lead a team responsible for invoice generation, validation, and the customer billing experience. You'll define how we build for correctness without slowing down. This is a leadership role: you'll shape how HubSpot thinks about revenue systems for years to come.

This won't be easy. But if you want to lead at industry scale, drive direct impact to the business, and help HubSpot drive revenue: this is the role.

What you'll help own:

• Technical leadership across our Revenue engineering teams
• Invoice generation & accuracy - ensuring every customer gets the right invoice at the right time
• Validation systems that prove correctness continuously, not just at launch
• The customer billing experience - helping customers understand what they owe and why

You're a fit if:

• You've led teams responsible for systems where correctness is non-negotiable
• You think in terms of "how do we know this is still right?" not just "how do we build this?"
• You see fast-moving environments as a design constraint, not an obstacle
• You're energized by building the first version of something, not just optimizing the tenth