Company
Albert Invent
Annual salary
$200k – $230k/yr
Location
Oakland, CA
Listed
44d ago
- Experience:
- 4 to 7 years
- Workplace:
- 1-2 days in-office in Oakland, CA (San Francisco Bay Area). No relocation support.
- 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 Oakland, 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 an Agent Product Manager with 4-7 years of product management experience to turn the AI capabilities Albert ships every week into agent skills that customers use and pay for. We want a high-energy, hands-on PM who has shipped AI products to external customers, ideally in vertical B2B SaaS (think Harvey, Procore, Benchling). You will sit between our core product teams and our forward-deployed teams, and you won't manage a fixed engineering team. Your job is to get the most out of an AI agent platform that is already strong. As one of Albert's first Agent PMs, you'll have real ownership in a field so new that nobody has much experience in it yet.
What will you be doing?
Own agent skills on Albert's platform from start to finish, turning new AI features (skills, MCP connectors, multi-agent orchestration, artifact generation, memory and automation) into solutions for real chemistry and materials science R&D workflows.
Write, test and improve skills, prompts and evals yourself, working with the core AI team and AI PMs when you need them, and bring engineers in only when necessary.
Work with forward-deployed scientists and customer teams to map enterprise workflows and find high-impact automation opportunities, then turn those into repeatable, paid-for capabilities.
Work in fast, project-based cycles: own an initiative for about a month, ship it, then move on to the next one as the platform releases new features each week.
Use AI in your daily work, including rapid prototyping, and help set the playbooks and evaluation standards for agent work at Albert.
Common questions
How do I apply for the Agent Product Manager (US) role at Albert Invent? +
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 Albert Invent role pay? +
The listing gives $200k – $230k/yr.
Is this role remote? +
The listing gives the location as Oakland, CA. 1-2 days in-office in Oakland, CA (San Francisco Bay Area). No relocation support.
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 →