📍 Los Angeles, CA (hybrid, onsite preferred, remote considered) | 💼 Full-time

Comp: $100-160k 

About Radix Health

Radix Health is on a mission to make healthcare reimbursement fairer, faster, and more transparent for providers. We help physicians—like ER doctors and specialists—get paid what they’re owed while keeping patients out of surprise billing limbo. We leverage the No Surprises Act's Independent Dispute Resolution (IDR) process to quickly and efficiently boost out-of-network reimbursement for providers at scale. In short, we work with the NSA—but the IDR process, not the government agency 😉

As a growing Series A startup backed by Bessemer Venture Partners, we’re moving quickly and building the engineering foundation that will scale with us. If you’re excited by ownership, impact, clean architecture, and solving real problems for real clinicians, you’ll fit right in.

The Role

We’re looking for a Backend Software Engineer who loves solving problems, takes initiative, and thrives in an early-stage environment. You’ll work closely with product, operations, and frontend engineering to ship features end-to-end, improve reliability, and shape the systems that power our platform.

This role is perfect for someone who is naturally curious, comfortable asking questions, and unafraid to propose new approaches when something doesn’t feel quite right. You bring a low-ego, collaborative mindset, enjoy giving and receiving feedback, and care more about delivering value than debating the perfect implementation. If you like rolling up your sleeves, learning quickly, and influencing how a product grows, you’ll love it here! 

What You’ll Do

• Ownership: Take initiative on features and improvements, collaborating with teammates to deliver reliable solutions.
• Momentum: Move fast, iterate wisely, and deliver meaningful results without sacrificing quality or reliability.
• Impact: Solve real problems that matter for our team and our users; focus on practical, scalable solutions that drive value.
• Innovation: Bring initiative and creativity to tackle challenging problems; propose new approaches and improvements that move the product forward.
• Collaboration: Work humbly and openly with teammates, leveraging others’ expertise while sharing your own; communicate clearly with both technical and non-technical partners.
• Transparency: Share context, challenges, and decisions openly—ask questions, surface risks early, and be comfortable giving and receiving feedback.
• Culture: Contribute to a healthy, low-ego team environment that values empathy, growth, and mutual respect, while fostering collaboration, learning, and knowledge-sharing

Who You Are

• Bachelor’s degree in CS or equivalent experience.
• 3+ years of experience building backend or service-oriented systems.
• Experience with an OO backend language (Python, Go, Java, etc.); no prior Python production experience required.
• Strong understanding of software fundamentals, design patterns, and API development.
• Experience with relational databases (we use PostgreSQL).
• Comfortable working with cloud infrastructure (AWS or GCP), CI/CD, and modern development workflows.

Extra Credit Experience 

• Background in FinTech or Payments, especially with systems that handle scale or compliance
• Proficiency with Python in production environments
• Experience thriving in an early-stage or growth-stage startup

Why You’ll Love Working Here

• High impact, real ownership: Your work will directly shape how healthcare providers get reimbursed—and how our platform scales.
• A team that moves fast (and cares): We’re collaborative, product-minded, and low-ego. You’ll work closely with engineering, product, ops, and leadership.
• Room to grow: We’re early, which means you’ll have space to influence architecture, processes, and the future of our engineering org.
• Meaningful problems, modern tools: You’ll work with a team that values thoughtful engineering and invests in building things the right way.
• Competitive compensation & equity: Join a well-funded Series A startup where your work really matters.