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
Rima

Senior Product Manager - Operations Platform

  • Office
  • 6+ years

Salary

$165,000 - 185,000/ year

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 wants to lower healthcare costs for employees and employers without cutting care quality, and sees this as both an ethical and a commercial goal.

It is building an agent-driven navigation platform for self-insured health plans that targets a root cause of rising costs: the people the system relies on.

The team is small and moves fast, based in New York City and New Orleans, and is fully committed.

Responsibilities

  • The largest customer, a boutique health plan, runs the navigation platform alongside a custom operations platform built for it. That platform handles payroll work, enrollment, member records, employer messages, third-party integrations and reporting for 100+ employers across 12 payroll providers.
  • The platform exists to save the customer time. It runs in production but also needs quick changes and one-off automations. A forward-deployed team fixes bugs, supports users and builds scripts such as ETL jobs, browser automation, Excel macros and Google Apps Scripts.
  • Make sure these automations are reusable, dependable in production and built into the operations platform.
  • The team is small and the role carries high ownership: you set the roadmap, the requirements and the outcomes so the CPO can stay focused on the core platform.
  • Own the roadmap: decide what gets built and in what order, and decline work that does not move a KPI.
  • Agree scope, sequencing and delivery dates with engineering based on estimates and capacity. Bring major decisions to the CPO with a recommendation.
  • Visit the customer's operations team weekly, including on site on Long Island, to watch payroll, enrollment and reconciliation work as it happens.
  • Take the roadmap and trade-offs to the customer, and flag changes to scope, timing or risk early.
  • Write specs covering users, business rules, edge cases, failure handling and acceptance criteria before work goes to engineering.
  • Settle unclear requests before they become engineering work, and check feasibility, sequencing and risk with the engineering team.
  • Split work into pieces that ship within a Monday-to-Friday sprint, and keep specs current as decisions change.
  • Prototype automations with coding agents and test your assumptions before writing the spec.
  • Test features with the customer's operations team against acceptance criteria, including payroll cutoffs, retroactive changes and mid-period eligibility changes.
  • With engineering, cover regression testing, known issues and release risk, then recommend a release based on customer readiness.
  • Coordinate rollout with engineering and the forward-deployed team: prepare the customer, share known issues and workarounds, and confirm the new workflow works in practice.
  • Write the release notes, SOPs and training material the customer's operations team needs.
  • Triage bugs, support requests and asks from the forward-deployed team and the customer. Log the problem, the current workaround, how often it occurs and its impact, not just the requested fix.
  • Find patterns behind repeat problems across employer clients and payroll providers.
  • Choose what to measure before a feature ships, and work with engineering on instrumentation in Sentry and Amplitude.
  • After release, check whether the feature moved its KPI, and use the result to decide what to build next.
  • Not in scope: pricing, contracts and commercial terms; day-to-day account management and support, which stay with the forward-deployed team; engineering execution, code quality, automated testing, deployment and monitoring, which stay with engineering.
  • First 90 days: document the customer's payroll, enrollment, reconciliation and reporting workflows, including automations, workarounds and failure points.
  • First 90 days: publish a proposed 6, 12 month roadmap with engineering, tie each item to a customer problem and KPI, and review priorities and trade-offs with the customer and CPO.
  • First 90 days: take at least one existing automation through requirements, customer acceptance and production release, working with engineering on monitoring and failure handling.
  • First 90 days: set up a recurring customer report on automation activity, failures and any evidence of time saved or errors prevented, and identify where measurement is still missing.

Requirements

  • Minimum: 5+ years shipping software products, or the same output in less time. The company cares more about what you shipped than your tenure or past employers.
  • Minimum: you have built a longer-term roadmap and tied each feature to KPIs and customer value.
  • Minimum: you have shipped reliable, integration-heavy software for operational workflows.
  • Minimum: you use AI and agent tools every day, including coding agents, LLM workflows and autonomous background agents, to prototype, analyze data and write specs, and you know their limits.
  • Minimum: you write detailed requirements, business rules and edge cases that engineers can build from, with clear acceptance criteria.
  • Minimum: you communicate clearly in writing and in conversation.
  • Minimum: you make strong trade-offs and lead trade-off discussions with all stakeholders.
  • Minimum: you listen closely, ask follow-up questions, and separate the customer's underlying problem from the solution they first ask for.
  • Preferred: experience in payroll, benefits administration or process automation, including eligibility, deductions, enrollment, reconciliation and exception handling.
  • Preferred: you have worked closely with forward-deployed or customer-facing engineers and turned one customer's workarounds into something that scales.
  • Preferred: you have shipped products built on browser automation or browser extensions, and know where they break: UI changes, authentication, session handling and silent failures.
  • Preferred: you have built automations with Playwright, Puppeteer, Selenium, Chrome extensions or RPA tools.
  • Preferred: you have turned custom, customer-specific work into a multi-tenant product.
  • Preferred: you have worked with PEOs, TPAs, payroll providers or benefits carriers, including EDI 834 or carrier feeds.
  • Preferred: you have built operational reporting and dashboards that customers rely on.
  • Preferred: you have designed human review, approvals and exception queues for automated work.
  • Preferred: you have worked on HIPAA or SOC 2 compliant systems, or with PII or PHI.

Conditions

Hold a very high bar and aim to win at the highest level, while keeping the team's humanity.

High ownership: you own problems end to end, with no handoffs.

Communicate crisply: say what you mean, raise problems early and keep decisions easy to find.

Ship in small batches and improve quickly based on member feedback.

Judged on what ships and how well it works, not on how many meetings you attend.

Tools used: Claude Code, Cursor, Grok Bot, Codex, Conductor, Notion, Figma, Storybook, GitHub, Slack, Google Workspace, Wispr Flow, Intercom and 1Password.

Stack: TypeScript, Next.js, Hono, PostgreSQL, Temporal, WXT, AWS with Terraform, Flagsmith, Sentry and Amplitude.

The problems are hard: payroll and benefits operations are complex, the data is regulated, and automation must be right every pay period.

The category is early and being rebuilt around agents that reach members wherever they are, so you will help define what it becomes.

You will help push forward how the team builds software with agents, treating it as a system to engineer.

The agents serve tens of thousands of members, and what you ship reaches them within days.

You work directly with the operations team that uses what you build.

The team shares what works and what does not when building with agents, and you learn from it.

On-site visits to the customer's operations team on Long Island about once a week, roughly 5 days per month, rising to up to 10 during rollouts or critical periods.

Travel is about 90 minutes each way from NYC, with occasional overnight stays as needed. The company covers travel costs.

Equal opportunity: candidates are considered without regard to protected characteristics.

Benefits

  • Base salary of $165,000 to $185,000, plus an equity package.
  • Flexible PTO, health insurance, dental, vision and more.

Where you’d work

From the office

The office

About the company

Rima

  • Industry: HealthTech

Office in New York City, United States

2 of their 3 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 21 checks run
  • 0 red flags

Still hiring?

14 checks

No red flags

How crowded?

7 checks

No 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
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Figma
  • Amplitude
  • Excel
  • LLMs
Seniority
Senior
Type
Full-time
Equity
Equity offered
Industry
HealthTech
Specialty
Product Manager
Show 7 more factsShow less

Role

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

Location

Work model
Office
Region
United States
Office
  • New York City, United States

Compensation

Salary
$165,000 - 185,000 / year
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Company

Industry
HealthTech

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason