About Helm Health

The Role

What You'll Own:

• How clients and internal operators set up plans, networks, benefit design, pricing logic, and client-specific overrides and rules.
• The interdependencies between them - where one setting cascades into others and into downstream behavior.
• Plan-year and time-based behavior, including how and when changes take effect.
• The propagation model - how a configuration decision reliably and predictably reaches every system that depends on it, with clear versioning.

• The configuration experience itself - the primary surface for non-technical and semi-technical users to make setup changes without an engineering ticket.
• Claims management workflows - review, comment, edit - with role-based access that separates who can see from who can change.
• Self-service reporting and query for ops and client-facing teams.
• Permissions, auditability, and change safety - who changed what, when, and with what blast radius, plus previews and staged rollout so a bad edit is legible and reversible before it ships.

• Partner with the owners of our pricing, adjudication, and member-facing products so configuration contracts stay consistent across everything that consumes them.
• Translate client edge cases into durable product rules rather than one-off handling.
• Define the testing that catches bad setup before it silently breaks a downstream system.

Responsibilities

• Own roadmap, prioritization, and outcomes for Configuration and Admin.
• Write PRDs and specs an engineer respects and QA can turn into an acceptance suite, including the domain edge cases.
• Run discovery with Implementation, Client Success, Ops, and client stakeholders.
• Define success metrics: time-to-configure, configuration error rate, downstream rework due to bad setup, and adoption of self-serve vs. engineering/ops tickets.
• Ship iteratively: start with the highest-friction paths, harden permissions and audit, then expand reporting. Hold a clear mental model of the shared resources the rest of the platform depends on, and protect them as they scale.

Qualifications:

• 5-8+ years in product management, with at least 2+ years on B2B platforms, admin/config tools, or complex workflow products.
• Comfort with systems that have many interdependent entities and the judgment to reason about how one change cascades downstream.
• A track record of shipping configuration UIs that non-engineers use in production — ideally with validation, environments, audit logs, or staged rollout.
• Strong written specs and the ability to sit with engineering on data-model and edge-case design.
• Healthcare, benefits, insurance, or claims experience is a strong plus, but owning a comparably complex system counts.
• Bonus: role-based access, multi-tenant SaaS, or reporting/BI surfaces.

What Success Looks Like in 6-12 Months:

• Clients and ops can handle common configuration paths without engineering tickets.
• Changes propagate predictably, with clear previews and audit trails.
• Claims reviewers have a usable management surface with appropriate access controls.
• Reporting answers the top operational questions without ad-hoc SQL.
• The contracts between configuration and the systems that consume it are documented and stable.

Collaboration

• You'll work closely with Engineering, Design, Implementation, Client Delivery, and the domain experts on pricing, quality, and claims logic.
• You own how the system is set up, and you must understand those surfaces deeply enough to keep configuration correct.

Internal Tools/Technology

• Slack / Google Workspace / Zoom
• Linear / Whimsical / Notion

Compensation

Benefits/Offerings

• Bonus + equity
• Unlimited PTO (mandatory 12 days)
• Computer + home office stipend
• 401(k) + matching
• Medical, dental, and vision insurance
• Autonomy and tons of room for career growth

Occasional Travel