Product Manager, Data & Integrations

Product Manager, Data & Integrations

Reports to: VP, Product | Location: Noida

About the Company

Our client is a revenue cycle management (RCM) company, backed by a leading business group.

Every product they build — client analytics, AR and denial automation, eligibility verification, payment posting — needs to runs on one shared data layer and one set of payer, clearinghouse and EHR integrations. This role owns that layer. It is the foundation the rest of the product portfolio sits on.

What you will own

•The canonical data model. An schema derived from the US claim lifecycle, under formal change control. You run the process — what gets added, what gets rejected, and how downstream teams migrate.

•Payer and clearinghouse integrations. EDI transaction sets across eligibility (270/271), claim status (276/277), claims (837) and remittance (835/ERA), plus vendor APIs and payer portal automation where EDI does not reach. You own the coverage map: which payers, which clients, which transactions, at what success rate.

•The 835/ERA parser and posting logic — the highest-leverage shared asset across our AR and Payment Posting products.

•Client data onboarding. Every new client arrives on a different EHR/PM system with different files and different field definitions. You design the intake pattern that turns onboarding from a project into a process.

•The data pipeline surface. Azure SQL as the operational store, Snowflake as the analytical warehouse, and automated mapping for new sources. You define the contracts; engineering builds them.

•Data quality as a product — freshness, completeness, reconciliation against payer and client source-of-truth, and published SLAs the business can rely on.

•PHI handling in the data path — masking, minimisation and access boundaries, aligned to our HIPAA and SOC 2 obligations.

What we are looking for

Must have

•4–7 years in product management, product ownership, technical business analysis or solution architecture — on data platforms, integrations or API products.

•Strong SQL. You will query claim data daily to validate what was built and investigate discrepancies. This is used in the interview.

•Hands-on experience with integrations at the format level — file feeds, SFTP, REST APIs, webhooks, retries and reconciliation.

•Comfort with data modelling and warehousing concepts.

•Clear written English — specifications, data dictionaries and integration runbooks are core output.

•B.Tech / B.E. or equivalent.

Good to have

• US healthcare RCM experience — X12 EDI (837/835/270/271/276/277), clearinghouses (Availity, Waystar, Change Healthcare/Optum, Trizetto), or EHR/PM systems (Epic, athenahealth, eClinicalWorks, AdvancedMD).

• Exposure to Snowflake, Azure SQL, dbt or similar pipeline tooling.

• Experience moving a services team onto a product platform.

If you have deep RCM or EDI experience but have not held a product title, we want to hear from you. Domain depth is harder to hire than the product craft.

Why this role

Most product roles in healthcare data are two steps removed from the data. This one is not — you will sit with the operations floor, look at live claims, and see the effect of your decisions on client collections within weeks. Real scale, institutional backing, and ESOP in a business that is actively converting into a software company.