Datrics · Healthcare / RCM track · Senior · Remote · Full-time

1. Role mission

Own the product surface end to end: understand how our clients' revenue cycle actually works, turn that into a clear set of priorities and decisions, and validate ideas fast by building working prototypes yourself with AI-assisted coding tools — instead of writing specs that sit in a backlog waiting for engineering capacity. You don't need to be a classically trained engineer or designer; you need to be genuinely dangerous with AI coding tools, so you can go from a client call to something clickable within days.

2. Context

Datrics builds a Revenue Cycle Management platform for US clinics, hospitals and nursing homes. Our users are billers, coders, AR follow-up staff and practice managers — people who live in dense worklists all day and have no patience for pretty ideas that don't solve their actual problem. The processes we're modelling (claim submission, denial management, AR aging, appeals, payment posting) are genuinely complicated, and getting the process right matters more than getting the pixels right.

3. What you will do

• Sit in on client conversations and workflow walkthroughs; map how work actually gets done today, including the spreadsheets and workarounds nobody mentions in the demo
• Turn that into product decisions: what we build, what we deliberately don't, and where automation replaces a manual step versus assisting it
• Use AI-assisted coding tools (Cursor, Claude Code, v0, Lovable, Replit or similar) to rapidly prototype ideas and put something real in front of users — a prototype in two days beats a spec debate over two weeks
• Validate prototypes with actual client workflows before committing engineering time to build them properly
• Hand off validated concepts to engineering with full context — not a spec nobody reads, but a working example they can react to
• Prioritize ruthlessly: maintain a clear view of what matters most and why, and be able to defend that to founders and clients
• Watch how features get used after launch and close the loop

4. Requirements

Must have

• 3–5+ years in product management, business/process analysis, or a similar hybrid role with heavy client discovery
• Hands-on, real experience shipping working prototypes with AI coding tools — not "curious about AI," but someone who actually builds small things with them regularly
• Strong process/requirements analysis: you can interview a domain expert, model their workflow, and identify where the real cost sits
• Enough technical literacy to reason sensibly about data models and sanity-check what an AI tool generates, even if you're not writing production code yourself
• Comfort with ambiguity and with owning a decision rather than escalating it