RCM Product Engineer

Job Description

About Sunlight

Sunlight is bringing back the independent doctor. Hospitals and corporations have bought more than 85,000 physician practices since 2018, and only 18% of physicians are still independent. Practice costs rose about 11% in 2025 while Medicare pay has fallen more than 30% since 2001. Independent practices aren't losing on medicine. They're losing on operations.

We are the patient-to-payment operating layer for independent physicians: one partner that replaces the five or six administrative vendors a typical practice juggles. We combine software, AI and expert people to run the business side of the practice, so physicians get paid in full and keep ownership and clinical control.

We came out of stealth with $17.4M in seed funding led by Basis Set Ventures, and are based in Miami and New York. Our founder and CEO, Sina Chehrazi, previously founded Nayya Health. We're growing the services we offer practices, starting with billing and revenue cycle, and we're focused on doing that work better and faster than it's done today, with people and relationships at the core. The goal is simple: make running a practice easier, so physicians can focus on being doctors.

The Role

We're hiring an RCM Product Engineer to own products in our revenue cycle business end to end: discover the problems worth solving, prioritize, build, launch and keep improving. Building is the core of the job. You'll own real products from day one.

This is not a roadmap-and-stakeholders role, and it's not a ticket queue either. Some weeks you'll be mostly defining problems: sitting with our team and the practices we serve, mapping a workflow, and turning it into a crisp spec. Other weeks you'll be deep in execution: building, prototyping with AI, triaging an issue, shipping a fix. We need someone who is comfortable moving between the two in the same afternoon.

You'll work directly with engineering, data, operations, customer success and go-to-market. We're early stage, small and tight-knit, so you'll get exposure across the whole company and wear many hats.

What you'll do

Define the problems

\n
• Map how work actually gets done across our services, the practices we serve and the vendors they already rely on, step by step, and find where time and money leak.
\n
• Size each opportunity and decide what we build or automate first.
\n
• Know the industry inside out: how practices get paid, where payers and paperwork slow them down, and what actually moves a practice's bottom line. Start from those outcomes and work backward to what we build.
\n
• Turn ambiguous requirements into well-scoped specs at a fast clip: a clear problem, the user, the data, edge cases, acceptance criteria.
\n
• Connect the dots across services. The same data from a practice should power every service we offer, not separate workflows.
\n

Build and ship

\n
• Own what you build from first idea to launch to iteration, and retiring it when it stops pulling its weight.
\n
• Write production code every week, across the full stack: the interfaces our team and practices use every day, and the backend services and data pipelines behind them.
\n
• Prototype tools and agents with AI, and take the ones that work to production.
\n
• Design human-in-the-loop workflows where AI handles the busywork and our people review, correct and own the outcome.
\n

Run the day to day

\n
• Work side by side with engineering, data, operations and design to get things into people's hands quickly.
\n
• Own the backlog, prioritization and release cadence for what you build.
\n
• Triage issues from our team and the practices we serve, closing the loop fast.
\n
• Define and track the numbers that matter: turnaround time, error rates, hours saved, and dollars collected for practices.
\n

What you bring

Must have

\n
• 5+ years of full-stack engineering experience building and shipping production software, with at least part of it at a startup or on a zero-to-one product.
\n
• Strong grasp of architecture and backends: how data is modeled, stored and moved, and how systems hold up as they grow.
\n
• Strong design sense and empathy for end users. You hold a high bar for usability.
\n
• A track record of writing specs that are fast and good (examples appreciated).
\n
• High ownership mindset. You drive projects from design through delivery and ship things yourself, not just spec them.
\n
• Strong independent judgment. Handed a messy, half-defined problem, you separate what's known from what isn't, identify the missing evidence, narrow the scope, and come back with a useful recommendation and explicit assumptions.
\n
• Hands-on with AI tools and LLM-powered products. You use AI daily to prototype, analyze data and move faster, and you know where it works and where it doesn't. You can also smell "AI slop" almost instantly, in a product or in writing.
\n
• Comfortable with ambiguity and a mixed week: discovery in the morning, a production bug in the afternoon.
\n
• Great communication skills, especially async and in writing. You articulate technical and product tradeoffs clearly, and your specs, updates and messages are crisp enough that people can act on them without a follow-up meeting.
\n

Strong plus

\n
• Healthcare revenue cycle experience: medical billing, claims (837/835), denials, coding (CPT, modifiers), payer contracts, or RCM software.
\n
• Experience with healthcare data: claims, remittances, price transparency files, Medicare fee schedules.
\n
• Experience building tooling for data labeling, annotation or human-in-the-loop AI workflows.
\n
• Automated operations and internal workflows for a services business and/or worked at a company that grew through acquisition.
\n

Compensation, benefits and location

\n
• Compensation: Competitive base salary plus equity.
\n
• Benefits: Comprehensive medical, dental and vision insurance, paid time off, and company-sponsored benefits.
\n
• Location: Miami preferred. New York City is a strong second. Both are hybrid, in office Tuesdays and Thursdays. We'll consider candidates outside Miami and New York for the right person.
\n