Software Engineer, Biller Workflows

These aren't basic CRUD screens. They're fast, data-dense, keyboard-driven workflows over millions of claims, sitting on real healthcare plumbing (EDI transactions, payer automations). AI is central to how we drive productivity, but we don't solve everything with an agent — we put LLMs in the loop only where day-to-day friction is highest.

We're mid-way through a generational rebuild of these surfaces, and there's an enormous amount to build: rebuilding the claims workspace, making bulk operations safe over tens of thousands of records, stitching together a unified claim activity timeline, and putting AI to work where billers feel the most friction. As a Software Engineer II, you'll own end-to-end features across this work and see them run in production for billers every day.

You'll join a small, tight-knit team that owns the claims, appointments, and eligibility surfaces end-to-end. It's a hands-on group that ships fast, reviews each other's work closely, and sits right next to the billing operators who use what we build — so you'll see the impact of your features in days, not quarters. You'll work alongside senior engineers who'll help you go deep on the domain and grow into bigger problems over time — and, as the team scales, take a growing hand in setting the technical standards and direction we all build on.

What You’ll Do

• Own features end-to-end on the claims, appointments, and payments-posting surfaces — from design phase through production rollout
• Write production-ready code with meaningful tests and observability, and design clean interfaces and data models that hold up as the surfaces grow
• Partner with product, design, and billing operations to make sure what you ship actually solves the biller's workflow problem
• Build reliability and observability into your features — dashboards, logging, and alerting that make production issues fast to catch and root-cause
• Review code and designs with an eye toward correctness, performance on data-dense screens, and a consistent user experience
• Help set the technical standards and direction the team builds on as we scale — shaping component patterns, API and data-fetching conventions, and testing and observability practices, and helping onboard and level up teammates

What You Have

• 3+ years building full-stack applications, with a track record of shipping features end-to-end in production
• Solid frontend skills — you build clean, maintainable UIs and can diagnose and fix common rendering issues in data-dense screens
• API and data-layer fundamentals — you can build backend endpoints handling filtering and pagination over sizable datasets, and reason about the queries behind them
• Sound technical judgment for feature-level work — you evaluate tradeoffs, escalate risks appropriately, and avoid over-engineering
• Good debugging and observability instincts — comfortable with monitoring, logging, and alerting
• Clear communication — you keep teammates and partners informed, and ask questions early when things are unclear
• Ownership mindset and bias for action — you take responsibility for your features and follow through with urgency and customer focus

Nice to Have

• Familiarity with healthcare billing data — EDI X12 (270/271, 276/277, 835, 837) — or a demonstrated ability to ramp on a gnarly domain quickly
• Experience shipping LLM-powered features into production workflows, not just demos
• Exposure to analytical/OLAP stores alongside a transactional database
• Strong product intuition and a track record of influencing UX/UI decisions to improve usability
• Experience working in regulated industries (healthcare, finance, insurance) with attention to security and compliance

Please be aware that all official communication from us will come exclusively from email addresses ending in @commure.com. Any emails from other domains are not affiliated with our organization.

Employees will act in accordance with the organization’s information security policies, to include but not limited to protecting assets from unauthorized access, disclosure, modification, destruction or interference nor execute particular security processes or activities. Employees will report to the information security office any confirmed or potential events or other risks to the organization. Employees will be required to attest to these requirements upon hire and on an annual basis.