You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
BambooHR

Senior Product Manager, Agent Platform

  • Remote
  • 6+ years

Salary

Not stated

Similar roles pay $165K - 230K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is remote-friendly for this role, but the position is tied to the state listed on the job. Employment is conditional on passing a background check and a credit check.

The company uses AI in its own workflows and wants people who will explore how AI can improve their work and help rethink HR.

The team is building a people intelligence platform for HR and has a long-standing market position with steady, sustainable growth.

This is the first dedicated product manager for the agent platform that every team building agents relies on. There is no existing product front door, no roadmap, and no vision document, so you will write the roadmap while inheriting production load, live consumers, and years of architecture.

The company is committed to including people with disabilities and will provide reasonable accommodations during hiring; candidates can ask their recruiter. It is an equal opportunity employer. Candidates can read the AI guidelines for candidates to see how AI is used in recruiting and what is not allowed.

Responsibilities

  • Own product direction for the Agent Runtime: durable execution, human-in-the-loop gates, auditability, and capacity and reliability as the number of agents grows.
  • Make and answer for the architecture decision on the legacy agent platform.
  • Own a dated migration to a new runtime, sequenced by consumer impact so downstream AI experiences never meet a regression unexpectedly.
  • Own agent governance as a product: the trust framework each agent action passes before it acts, built on the platform's authorization and attribution patterns.
  • Define and drive usage instrumentation, including instigation flags, output lifecycle events, and a metering schema that leaves monetization options open.
  • Run intake and prioritization for all teams building agents, and publish whether they should build on current tools or wait for the new runtime.
  • Set and maintain the line between the platform agents run on and the AI experience surfaces built on it, with named consumer stakeholders on every decision that affects them.
  • Decide how agents are triggered: which platform events they may respond to and what subscribing to those events requires.
  • Act as the named consumer stakeholder for context and signal standards, state what agents need from workplace signals, and shape decisions on how agents use them.

Requirements

  • You are aligned with the company's values.
  • You have 5+ years of product management experience on platform, infrastructure, or developer-facing products.
  • You have technical depth in execution systems, workflows, or eventing, and can reason about durable execution, retries, and what makes a migration safe.
  • You have owned a product for internal platform consumers, with disciplined intake, published contracts, and a roadmap those consumers can see.
  • You can drive alignment across teams without direct authority.
  • You can make migration calls when engineering convenience and consumer safety conflict.
  • You are comfortable with AI and agent systems and with how fast their patterns change.
  • You measure before you claim, write decisions down, and sequence work by consumer impact.
  • Within 180 days you will deliver a written architecture decision for the legacy agent platform with a dated, consumer-sequenced migration plan.
  • Within 180 days you will set up an intake path for teams building agents and publish guidance on building now or waiting for the runtime.
  • Within 180 days you will establish runtime capacity and reliability reporting that leadership can act on.
  • Within 180 days you will ship the first version of the metering schema with instigation and lifecycle events flowing.
  • Nice to have: experience with agent frameworks, LLM orchestration, or workflow engines such as Temporal.
  • Nice to have: experience leading a migration or sunset on a system with live production consumers.
  • Nice to have: product experience with usage-based pricing or metering.

Conditions

The role is remote within the state listed on the job.

Employment depends on passing a background check and a credit check.

Equal opportunity employer.

Benefits

  • Recognised as a great place to work by several organisations, including Inc and the Salt Lake Tribune.
  • Comprehensive health, life, and disability insurance.
  • 4 weeks of vacation, 12 company holidays, parental leave, and volunteer time off.
  • 401k with up to 6% company match.
  • $2000 paid-paid vacation bonus.
  • EAP through Headspace.

About the company

BambooHR

  • Industry: SaaS

7 of their 12 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 2 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

2 red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details10 facts · Role, Location, Compensation, Company
Tech stack
  • LLMs
Seniority
Senior
Industry
SaaS
Specialty
Product Manager
Region
United States
Pay period
Annual
Show 4 more factsShow less

Role

Category
Product & Project
Specialty
Product Manager
Seniority
Senior
Experience
5+ years
Tech stack
  • LLMs

Location

Work model
Remote
Region
United States

Compensation

Salary
Salary by agreement
Pay period
Annual

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason