Company
Plasmidsaurus
Annual salary
$175k – $235k/yr
Location
San Francisco, CA
Listed
24d ago
- Experience:
- 4 to 10 years
- Workplace:
- In office 3 days per week (MWF) in South San Francisco
- Equity:
- None
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
Plasmidsaurus is seeking a Product Manager to own the UX and growth of the non-biology aspects of their web app. You will distill customer feedback into a roadmap, improve key customer workflows, and manage surfaces including onboarding, payments, and logistics to ensure a experience for researchers.
Common questions
How do I apply for the Product Manager | Software (US) role at Plasmidsaurus? +
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 Plasmidsaurus role pay? +
The listing gives $175k – $235k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. In office 3 days per week (MWF) in South San Francisco.
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 →