Company
Roger Healthcare
Annual salary
$160k – $240k/yr
Location
San Francisco, CA
Listed
39d ago
- Experience:
- 3+ years
- Workplace:
- 3 days in-office in San Francisco, CA (minimal travel, around 1%)
- 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 San Francisco, CA.
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 Product Manager, AI Platform with 3+ years of product experience who has an engineering background and is scrappy and low-ego. You'll be one of Roger's first product hires. Your job is to turn the legacy, spreadsheet-heavy workflows of home health agencies into products built on AI from the ground up, inside Roger's new medical record system. In this industry, shipping faster means patients get care sooner.
What you need
- 1+ years of product management experience, ideally recent and at an early-stage or high-growth startup (big-tech-only backgrounds are not a fit)
- 2+ years of hands-on engineering experience (full stack, founding engineer or forward deployed engineer) before moving into product, and able to think from first principles
- Strong product sense from B2B SaaS. Healthcare AI, or modernizing legacy workflows in regulated industries, is a big plus
- Low ego, deeply focused on customers, fast and scrappy, and willing to do the hands-on work
- Able to work hybrid 3 days a week in San Francisco and authorized to work in the US without sponsorship
What will you be doing?
Talk with and shadow home health customers across intake, scheduling, billing and documentation to find their biggest pain points
Build quick prototypes, for example with Claude, then demo them, run walkthroughs and gather feedback to iterate fast
Spend at least half your time with engineering: break down customer insights, give product feedback and review what gets built from start to finish
Turn requests from single customers into scalable features that work across all agencies, covering both new 0-to-1 products and improvements to the core platform
Own results such as adoption, usage, NPS and time saved for users, and share what you learn with the founders every week
Common questions
How do I apply for the Product Manager, AI Platform (US) role at Roger Healthcare? +
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 Roger Healthcare role pay? +
The listing gives $160k – $240k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. 3 days in-office in San Francisco, CA (minimal travel, around 1%).
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 →