Skip to main content

Commure

Software Engineer, Early Career 2027

Mountain View, CA$130k–$150kfulltimeentryAdded today

About this role

Commure is seeking early-career software engineers to join its AI-driven healthcare platform that automates clinical documentation, patient workflows, and revenue cycle management. You'll own meaningful production systems across backend, frontend, mobile, and infrastructure, working directly with clinicians to solve high-stakes problems in a fast-moving environment.

What you'll do

  • Build product features across web, mobile, and backend applications supporting clinical workflows
  • Develop reliable APIs and backend services handling high-volume healthcare data
  • Create data processing pipelines for complex healthcare information
  • Build and improve AI inference pipelines, orchestration, and quality evaluation systems
  • Enhance monitoring, observability, alerting, and application performance
  • Collaborate with product, design, and clinical teams to ship user-facing solutions

What they're looking for

  • Algorithms and data structures
  • Backend development
  • Database design
  • Distributed systems
  • Frontend development (React)
  • API design
  • Debugging and problem-solving
  • System design and reliability
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Commure

Commure builds AI-powered healthcare solutions that automate clinical documentation, billing workflows, and claims processing for healthcare organizations and their clinicians. The company is hiring full-stack engineers, R&D specialists, forward-deployed engineers, and backend developers to scale LLM-based systems and real-time automation tools across its platform serving 500+ healthcare organizations.

View all jobs at Commure

Likely interview questions

  • Walk us through a substantial project you built outside of coursework—what technical challenges did you face and how did you solve them?
  • Describe a time you debugged a complex issue across multiple layers of a system. How did you approach it?