Senior Product Manager, Growth (Canada)
Homebase • Greater Toronto Area, ON, Canada
Company
Homebase
Annual salary
$200k – $260k/yr
Location
Greater Toronto Area, ON, Canada
Listed
19d ago
- Experience:
- 8+ years
- Workplace:
- 2 days in-office (Tuesdays and Wednesdays, non-negotiable) in Greater Toronto Area, ON or San Francisco, CA
- Equity:
- Competitive equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Hybrid in Greater Toronto Area, ON, Canada.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Senior Product Manager, Growth with 8+ years of experience (4-5+ of them in growth product) to own the first 30 days of the Homebase customer journey. We need a senior PM who has worked at a startup and can take over a complex, multi-user onboarding funnel, run fast experiments, and turn more of our 150K+ small businesses from freemium into paying customers.
What you need
- 8+ years of experience, with 4-5+ years as a Product Manager on growth, onboarding, or activation (growth product, not growth marketing or user acquisition)
- Has owned end-user onboarding for a complex, multi-product or multi-user product where users arrive with different goals (e.g. HubSpot-style platforms)
- Has owned onboarding end to end, ideally at an early-stage or scrappy company rather than as one small part of a big-tech team
- Strong hands-on skills in funnel experimentation, A/B testing, and behavioral analytics (Amplitude, Mixpanel, Statsig)
- Has partnered closely with Growth Marketing on segment-specific onboarding, and can work hybrid in Toronto or SF (in office every Tuesday and Wednesday)
What will you be doing?
Owning everything that happens after a new customer signs up, from first onboarding to trial-to-paid conversion and the freemium fallback
Digging into funnel data every day in Amplitude to find where users drop off, then working with Design and Engineering to ship fixes
Running a fast A/B testing program to get business owners and their employees to their "aha moment" sooner
Working with Growth Marketing to build onboarding for specific segments (e.g. restaurant-specific flows that match targeted landing pages)
Setting an AI-first onboarding strategy and proving that the AI features you ship work
Common questions
How do I apply for the Senior Product Manager, Growth (Canada) role at Homebase? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Homebase role pay? +
The listing gives $200k – $260k/yr.
Is this role remote? +
The listing gives the location as Greater Toronto Area, ON, Canada. 2 days in-office (Tuesdays and Wednesdays, non-negotiable) in Greater Toronto Area, ON or San Francisco, CA.
Product Manager interview prep
Questions Product Manager interviewers often ask. They aren't taken from this listing.
How do you rank competing feature requests when every stakeholder believes theirs is the most urgent one on the list?
I score each request against the outcome the team has committed to for the quarter, then weigh expected impact against the effort engineering estimates. That gives me a defensible order to show stakeholders, and when someone disagrees we argue about the inputs rather than about whose request matters more.
How do you structure a roadmap so it communicates direction without promising dates the team cannot keep?
I organize the roadmap around problems to solve in rough time horizons, now, next and later, instead of a dated list of features. Commitments get firmer as work gets closer, and I state plainly which items are bets and which are committed, so sales and leadership know what they can promise to customers.
How do you plan a round of user interviews so the findings change what you build rather than confirming what you hoped?
I write the riskiest assumption down first and design questions around past behavior, not opinions about a feature idea. Asking people what they did last time the problem came up produces evidence, while asking whether they would use something produces polite agreement that tells me nothing.
How do you combine quantitative usage data with qualitative interview findings when the two seem to disagree?
I treat the numbers as telling me what is happening and the interviews as telling me why, so a disagreement usually means I am measuring the wrong thing or talking to the wrong segment. I go back and check who is in each sample before drawing a conclusion, because resolving that mismatch is often the most useful finding of the whole study.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →