Senior Product Manager - Operations Platform
Job details
- Pay
- $165,000 – $185,000 a year
- Work mode
- On-site
- Employment
- Full-time
- Level
- Senior
- Experience
- 5+ years
- Posted
- Nov 12, 2026
- Last confirmed open
- Nov 13, 2026
- Job function
- Product › Product Management › Product Manager
About this role
Full time | On-site in NYC (Union Square) | 20% travel | Reports to Chief Product Officer
What is Rima
Rima's mission is to improve population health by giving people technology to make navigating their employer sponsored health plans easy. We see a world where it is possible to reduce the economic burden on employees and employers without sacrificing quality of care. This is both a moral imperative and a business opportunity.
Rima is building an agentic navigation platform for self insured health plans to tackle the root cause underlying rising healthcare costs. We are empowering the individuals on which the entire system depends.
We’re a small, fast-moving team based in NYC and New Orleans. We are all in.
The Role
Our largest customer, a boutique health plan, uses our navigation platform and a custom operations platform purpose built for them. The operations platform covers payroll operations, enrollment, member management, employer communications, vendor integrations, and reporting for 100+ employers across a dozen payroll providers.
The purpose of the operations platform is to save our customer time. It is in production while also demanding rapid iteration and creative one-off automations. A forward-deployed team handles bug fixes and support, and builds automations such as ETL scripts, browser automation, Excel macros, and Google Apps Scripts.
Your job is to make sure these automations are reusable, reliable in production, and integrated into the operations platform.
We're a small team, and this is a high-ownership role. You own the roadmap, the requirements, and the results, so our CPO can focus on the core platform.
Minimum qualifications
- You've shipped software products for 5+ years, or shipped more in less time. We care more about what you’ve shipped than your tenure or previous employers.
- You've built and delivered a longer-term roadmap and tied each feature to KPIs and customer value.
- You've shipped reliable, integration-heavy software for operational workflows.
- You use AI and agentic tools every day, including coding agents, LLM workflows, and autonomous background agents. You use them to prototype, analyze data, and write specs, and you know where they fall short.
- You write detailed requirements, business rules, and edge cases that engineering can build from and that define clear acceptance criteria.
- You communicate clearly in writing and in conversation.
- You are excellent at making trade-offs and facilitating trade-off discussions with all stakeholders.
- You listen closely, ask follow-up questions, and distinguish the customer's underlying problem from the solution they initially request.
Preferred qualifications
- You've worked in payroll, benefits administration, or process automation. You are familiar with eligibility, deductions, enrollment, and reconciliation operations and the long tail of exceptions.
- You've worked closely with forward-deployed or customer-facing engineers, and you can turn one customer's workarounds into a product that scales.
- You've shipped products built on browser automation or browser extensions. You know where they break: changing UIs, authentication, session handling, and failures nobody notices.
- Built automations yourself with Playwright, Puppeteer, Selenium, Chrome extensions, or RPA tools.
- Turned custom, customer-specific work into a multi-tenant product.
- Worked with PEOs, TPAs, payroll providers, or benefits carriers, including EDI 834 or carrier feeds.
- Built operational reporting and dashboards that customers rely on.
- Designed human review, approvals, and exception queues for automated work.
- Worked on HIPAA or SOC 2-compliant systems, or with PII and PHI.
What you'll do
Own the roadmap
- Decide what the team builds and in what order, and turn down work that doesn't move a KPI.
- Make scope, sequencing, and delivery commitments with engineering, based on estimates and capacity. Escalate consequential decisions to the CPO with a recommendation.
Talk to the customer directly
- Meet weekly with the customer's operations team, including on site on Long Island, to observe payroll, enrollment, and reconciliation workflows firsthand.
- Walk the customer through the roadmap and trade-offs, and communicate changes to scope, timing, or risk early.
Write requirements engineering can build from
- Write specs covering the user, business rules, edge cases, failure handling, and acceptance criteria before work reaches engineering.
- Resolve unclear requests before they become engineering work. Check feasibility, sequencing and risk with the engineering team.
- Break work into pieces that ship within a Monday-to-Friday sprint. Keep the spec current as decisions change.
- Use coding agents to prototype an automation and test your assumptions before you write the spec.
Own product acceptance, release readiness, and rollout
- Test features with the customer's operations team against acceptance criteria, including payroll cutoffs, retro changes, and mid-period eligibility changes.
- Work with engineering on regression coverage, known issues, and release risks. Make a release recommendation based on customer readiness.
- Coordinate rollout with engineering and the forward-deployed team: prepare the customer, communicate known issues and workarounds, and check that the new workflow works in practice.
- Write the release notes, SOPs, and training material the customer's operations team needs.
Turn requests into structured product input
- Triage bugs, support requests and asks from the forward-deployed team and the customer. Record the problem, the current workaround, how often it happens and the impact, not just the fix someone asked for.
- Find the patterns behind repeat problems across employer clients and payroll providers.
Measure whether it worked
- Decide what to measure before a feature ships, and work with engineering on the instrumentation in Sentry and Amplitude.
- Check after release whether the feature changed the KPI it was tied to. Use the results to decide what to build next.
What you won't own
- Pricing, contracts or commercial terms.
- Day-to-day account management and support, which stay with the forward-deployed team.
- Engineering execution, technical quality, automated testing, deployment, and monitoring, which stay with the engineering team.
What success looks like in your first 90 days
- Document the customer's payroll, enrollment, reconciliation, and reporting workflows, including the automations, workarounds, and failure points.
- Publish a proposed 6–12 month roadmap with the engineering team. Tie each item to a customer problem and KPI, and review priorities and trade-offs with the customer and CPO.
- Take at least one existing automation through requirements, customer acceptance, and production release, working with engineering on monitoring and failure handling.
- Establish a recurring customer report showing automation activity, failures, and available evidence of time saved or errors prevented. Identify gaps where measurement is not yet available.
How we work
- Love and excellence. We strive to win at the highest level and hold an extremely high bar, without losing the humanity that makes us who we are.
- High ownership. You own problems end to end. No hand-offs, no "not my problem."
- Crisp communication. We say what we mean, raise problems early, and keep decisions easy to find.
- Fast iteration. We ship in small batches, learn from members, and improve quickly.
- Results over process. We care about what ships and how well it works, not how many meetings you attended.
- Our tools. Claude Code, Cursor, Grok Bot, Codex, Conductor, Notion, Figma, Storybook, GitHub, Slack, Google Workspace, Wispr Flow, Intercom, and 1Password.
- Our stack. TypeScript, Next.js, Hono, PostgreSQL, Temporal, WXT, AWS with Terraform, Flagsmith, Sentry, and Amplitude.
Why work at Rima
- Hard problems. Payroll and benefits operations are complex, the data is regulated, and automation has to be right every pay period. You'll work where all three meet.
- Early in a category being reinvented. Benefits navigation is being rebuilt around agents that reach members wherever they are. We're early, and you'll help shape what it becomes.
- Push agentic development forward. We treat building software with agents as a system to engineer, and you'll help design it.
- Real impact, fast. Our agents serve tens of thousands of members, and what you ship reaches them in days.
- Close to users. You'll work directly with the operations team using what you built, not through layers of tickets.
- Learn from how the team uses agents. The team shares what works—and what doesn’t—when building with agents.
- Competitive comp and benefits. Base salary range $165,000-$185,000, plus an equity package, flexible PTO, health insurance, dental, vision and more.
Travel
Expect on-site visits to the customer's operations team on Long Island about once a week, roughly 5 days per month, increasing to up to 10 during rollouts or critical periods. Travel takes about 90 minutes each way from NYC, with occasional overnight stays as needed. Rima covers travel costs.
Compensation
Range: $165K - $185K