Senior Product Engineer, RCM Operations

Duet•New York, NY

1d•$160,000 - $185,000•Hybrid

About The Position

As a Senior Product Engineer on Billing Operations, you'll own the engineering behind Duet's revenue cycle products. You'll build the systems that move a claim from charge capture through submission, adjudication, denial, appeal, and collection, across three surfaces: internal tooling our billing operators depend on, automation that replaces manual claims and denials work, and customer-facing products clinic staff use every day. This is a deeply hands-on, full-stack role with backend as your center of gravity. You’ll own reliability of API connections between billing systems and clearinghouses, work with data to ensure data accuracy, and build dashboards that our customers and internal ops team consumes. You'll work closely with our billing operations and product teams, partnering with people who do this work manually today to turn their hard-won knowledge into durable software.

Requirements

5–8 years of experience building production web applications, with a track record of owning significant technical surface area end to end.
Direct experience with healthcare billing, claims, or revenue cycle management. You understand the claims lifecycle—submission, adjudication, denials, appeals, collections—and the rules and data structures behind it (e.g., CPT/ICD coding, EOBs/ERAs, clearinghouses, payer-specific requirements).
Strong backend and data engineering instincts. Our products ingest, process, transform, and serve data at the application layer.
Proficiency in Python and JavaScript, with experience designing and building RESTful APIs.
Full-stack capability with backend as your center of gravity. You're as comfortable modeling data and writing performant queries as you are building the UI layer that makes that data useful.
Experience with cloud data warehouses and modern data tooling.
A product engineering mindset—you think about what you're building from the user's perspective, not just the system's.
High ownership, comfort with ambiguity, and a bias toward shipping.

Nice To Haves

Experience integrating with specific EHR or practice management systems, or with clearinghouses, maps directly to what we're doing.
Familiarity with workflow automation or rule-based systems is a strong plus.
Exposure to value-based care or programs like APCM (Advanced Primary Care Management) will accelerate your impact.
Experience turning internal tools or managed services into self-serve customer-facing products.

Responsibilities

Build the connections that move billing data. Design and build the integrations that link practice management systems, our cloud data warehouse, and clearinghouses—standing up new connections as we onboard practices and partners, and extending the pipelines that carry claims, remittance, and payment data end to end.
Keep those connections reliable. Harden the integrations we already run so data keeps flowing when source systems change, APIs throttle, files malform, or clearinghouse transactions fail. Build the monitoring, alerting, and observability that catch breakage before a practice's cash flow does. Share on-call and incident response with the team, and turn every incident into a durable fix. When money stops moving, this is the work that gets it moving again.
Build customer-facing billing products. Design and ship the dashboards, worklists, and workflows that clinic staff use to manage their revenue cycle—claims status, denials, collections, charge review, and payer performance. Make complex billing data usable and trustworthy for people who aren't billers by training.
Automate the claims and denials lifecycle. Identify the repetitive, rule-driven work in claims submission, denial management, and appeals, and replace it with configurable, rule-based automation. Build systems that scrub claims before they go out, route denials intelligently, and turn human-in-the-loop processes into self-serve software.
Own quality across the board. Write thoughtful tests for integration and billing logic, where correctness is non-negotiable. Debug production issues, and ensure changes are safe, observable, and reversible. You set the bar for what production-ready means—both for the products you ship and the connections you keep alive.