Commure was incubated inside General Catalyst in 2017 as a healthcare developer platform, merged with Athelas in October 2023 at a reported $6B valuation, and put Athelas co-founder Tanay Tandon in the CEO seat. The combined company bought Augmedix, the Nasdaq-listed medical scribe firm, for about $139M in cash in October 2024, took $200M in non-dilutive financing from General Catalyst’s Customer Value Fund in June 2025, and on May 19, 2026 announced a $70M round led by General Catalyst with Sequoia, Morgan Stanley, and Kirkland & Ellis at a $7B post-money valuation. Headquarters are at 1300 Terra Bella Ave in Mountain View, though some releases carry a San Francisco dateline and job boards still use the old “Commure + Athelas” name. Coverage of the May raise put headcount near 1,200 across seven offices, with engineering also hiring in Brazil. There is no public CTO; each product line has its own engineering lead.
Process
Commure does not publish its loop, so this is stitched from candidate reports on Exponent, Blind, 1Point3Acres, and Glassdoor from 2025 and 2026, plus the 30-odd engineering postings live on Ashby in September 2026. Glassdoor rates the interview 2.8 out of 5 for difficulty and under 40 percent positive: the technical bar is moderate, the scheduling and communication around it are uneven. One Blind poster described a verbal offer on a Friday, a Saturday meeting with executives, then silence.
The most detailed public write-up, from an entry-level candidate on Exponent, ran four rounds in two weeks: a recruiter screen, a phone screen with a LeetCode-medium problem, a scenario-based object-oriented coding session, and a final system design round on a scheduling system. The rejection feedback said the team weighs design over coding speed because AI tools have made implementation cheap. Other reports point away from LeetCode. A March 2025 Blind thread calls the screen “query APIs,” 1Point3Acres entries name screens like “implementing filter logic,” “sorting API challenge,” and “TypeScript filtering tasks,” and Blind posters mention a 75-minute coding interview, which matches the Athelas-era pattern of an hour working against API documentation. Behavioral questions ride inside the recruiter and manager calls rather than getting their own round.
| Stage | Who | What it tests |
|---|---|---|
| Recruiter screen (30 min) | Recruiter | Why you are leaving, what you want next, comfort with five days in Mountain View, comp expectations |
| Technical phone screen (60 to 75 min) | One engineer | Practical coding in Python or TypeScript: filter, sort, and reshape data pulled from an API; one report got a LeetCode-medium instead |
| Full-stack coding round | One or two engineers from the hiring team | Build a small feature end to end, React front and Python back; scenario-based object-oriented design of the service layer |
| System design | Senior engineer or engineering manager | Design a scheduling or workflow system; data model, failure modes, what happens when a dependency is slow |
| Hiring manager or leadership call | EM, director, or an executive for senior roles | Ownership stories, interest in billing or clinical work, tolerance for pace |
Two things separate Commure from the pure ambient-scribe shops in the Abridge guide. The revenue engine is billing: more than half the Mountain View engineering roles open in September 2026 sit on RCM Core, AI Billing, Billing Agents, Claims Submissions, Rejections and Denials, or Payments and Reconciliation, and Ambient AI is one product line among several. And the company runs in-office: the intern posting says five days a week in Mountain View, and only one senior full-stack role on Commure Pro lists “San Francisco Bay Area or Remote.” Say so early if you need remote, because the recruiter screen is where that gets filtered.
What they actually ask
- Here is an endpoint that returns a page of claims with status, payer, and denial codes. Write a function that pulls every page, filters to Medicare Part B denials from the last 30 days, and groups them by denial reason. What breaks when the API starts returning duplicates?
- Design a scheduling system for a multi-site clinic: providers, rooms, appointment types with different durations, and patients rescheduling through a phone agent. Walk through the data model, then explain how you prevent double booking under concurrent writes.
- A denied claim comes back with a CO-16 rejection. Sketch a rules engine that decides whether to auto-correct and resubmit, route to a human, or draft an appeal letter, and describe the dry-run and audit trail you would require before it touches real money.
- Our ambient pipeline ingests a 40-minute visit as chunked audio uploads from a phone that may lose signal. Design the path through transcription, diarization, and note generation so a duplicated or out-of-order chunk never produces a duplicated note.
- Model a patient, an encounter, and a claim in classes. Now add a second payer with a different reimbursement rule without touching the original claim logic. Where does the rule live and how do you test it?
- How would you decide whether a new prompt for the SOAP note generator beats the current one across 10,000 visits, and what would you refuse to ship on offline metrics alone?
- Protected health information flows through your LLM calls. What do you redact before the request, how do you handle a vendor outage mid-visit, and what logging is acceptable under HIPAA?
Levels and comp (2026)
Commure posts salary bands on its Ashby board, which makes the structure unusually legible for a private company. As of early September 2026: Fullstack Engineer, Ambient AI at $130K to $180K; Software Engineer, AI Billing at $130K to $190K; Senior Backend Engineer, Ambient AI at $170K to $230K; Senior Software Engineer on RCM Core and AI Integrations at $180K to $230K; Staff Software Engineer on Billing Agents and Data Warehouse at $210K to $275K; Engineering Manager at $200K to $250K; Forward Deployed Engineer at $130K to $190K. Nearly all are flagged “offers equity.” Brazil roles sit on separate, lower bands. Titles are flat, engineer, senior, staff, manager, with no L-number ladder in the postings.
Self-reported entries on levels.fyi and Glassdoor put junior total comp in the mid $100Ks: base near the bottom of the posted band, a stock grant vesting 25 percent a year over four years, no cash bonus. Sample sizes are small, so treat the posted band as the anchor. On equity, understand what you hold. The $7B post-money in May 2026 is a 17 percent step up from the $6B merger price in October 2023, General Catalyst has led or joined every post-merger financing, total funding is about $823M, and the $200M Customer Value Fund deal is repaid from a share of new-customer revenue rather than equity. Ask for the strike price, the latest 409A, the preferred price per share, and whether any tender offers have run. The AI startup difficulty index covers weighing paper equity like this against a public-company offer.
Prep priorities
Learn the revenue cycle first, because that is where most open seats are. Know the life of a claim from charge capture through the 837 submission, the 835 remittance, denial codes, appeals, and patient balances, and read enough about EDI X12, clearinghouses, and ERAs versus EOBs to follow a conversation. For the ambient side, understand the pipeline from audio to SOAP note and why a note generator needs an eval set. Then sharpen practical coding over algorithms: an hour of clean Python or TypeScript against an unfamiliar REST API, with pagination and error handling, is closer to the real screen than a week of grinding trees. Keep one LeetCode-medium warm anyway. For design, rehearse a scheduling system and a long-running workflow orchestrator with retries, idempotency, and dead-letter handling, the exact words in the Senior Backend Engineer, Ambient AI posting; the system design guides on scheduling and job queues are a direct fit.
Ask the recruiter which product line the role sits on, whether the loop includes a take-home (non-engineering candidates report one), the in-office policy for your title, the round count, and what on-call looks like. Glassdoor reviews average 3.4 stars and split between people energized by watching doctors use what they built and people describing weekend work, shifting priorities, and layoffs after acquisitions. Both groups are describing the same company. Use the manager call to find out which team you would land on.
Frequently Asked Questions
How hard is the Commure coding interview?
Moderate. Glassdoor’s software engineer respondents rate it 3 out of 5, and most reports describe a practical screen around fetching and filtering API data in Python or TypeScript rather than a hard algorithm. The system design round on scheduling is where the Exponent candidate was cut, so treat design as the harder half.
Is Commure remote or in office?
In office. Nearly every engineering posting in September 2026 is pinned to Mountain View, the internship states five days a week on site, and only one senior full-stack role lists a remote option. Engineering also hires in Rio de Janeiro and São Paulo on local bands.
Does Commure pay well compared to other healthcare AI startups?
The posted bands are mid-market for the Bay Area: $130K to $190K for engineer, $170K to $230K for senior, $210K to $275K for staff, plus equity. That trails the best-funded ambient-scribe competitors on cash but is printed on the listing, so you know the ceiling before the first call. The equity rides a $7B valuation that has moved only modestly since 2023.
How long does the Commure interview process take?
Two to three weeks from recruiter call to decision in the reports that give a timeline, with four to five conversations in that span. The variance is in scheduling and follow-up rather than round count, so confirm next steps in writing after each stage.
Similar company guides
Prepping for Commure? Put it to work:
