Y Combinator Sales Engineer (Ambient AI)
Posted Updated 30
views
Description
- This is a presales role. You’ll partner with Account Executives on Commure Ambient pilots and on advanced AI pilots with healthcare practices: coding, orders, Patient 360, carry forward, and pre-visit summaries, running live inside ten EHRs (athenahealth, eClinicalWorks, AdvancedMD, ModMed, NextGen, Practice Fusion, WebPT, Prompt, iKnowMed, and Meditech Expanse)
- You’ll typically have several pilots in flight at once, and you’ll work closely with Engineering, our template team, and our implementation and operations teams to make each one succeed
- Scope pilots. Lead the technical scoping call for each pilot, working directly with the providers who’ll use Ambient and the decision makers evaluating it. Capture specialty, note types, EHR, and workflow, and turn it into a technical scope the deal can move forward on
- Build EHR integrations. Stand up the integration for each pilot across browser automation, DOM injection, and API paths. Our target from approved requests to a live integration the customer can use. When a note doesn’t land in the chart, you’ll find out why and fix it
- Bring advanced AI into the pilot. Confirm which beyond-the-note features the customer’s EHR supports, configure them, and help providers put them to work: ICD coding, orders, Patient 360, carry forward, and pre-visit summaries
- Get templates right. Translate gold-standard notes and specialty requirements into template requests for our template engineering team, and triage template updates during the pilot on a 24-hour SLA
- Keep pilots healthy. Own the pilot Slack channel as the thread of record, triage in-pilot requests (template, integration, app feature) within 24 hours, and keep status and usage current in Salesforce so the AE always knows how the pilot is going
- Enable the sales team. Field integration and feature questions from AEs, help run the weekly integrations sales desk where engineering commitments to deals are made and tracked, and own the technical sections of RFPs and security questionnaires
- Hand off well. Deliver each new customer to implementation with the integration, templates, provider list, and known issues documented, so go-live picks up right where the pilot left off
- Make the team better. Escalate integration and product findings to Engineering with clear reproduction steps, and help build the tooling and playbook (debugging queries, checklists, wiki) that lets the next SE ramp faster than you did
- What Success Looks Like:
- Pilots start on the date we committed to the customer
- In-pilot issues are triaged within speed and urgency
- Providers in your pilots are using Ambient, and where the EHR supports it, coding, carry forward, and Patient 360
- Your pilots convert, and implementation can pick up your hand-offs without rework
- The ability to explain to a physician or technical teams how ambient AI builds a note, where it can miss, and what to do about it, in plain language
- A strong sense of ownership. Pilots launch on an SE’s approval, and you take that responsibility seriously
- Strong organization. You can juggle several pilots across multiple EHRs, keep Salesforce current, use Slack as your thread of record, and write updates that are short and specific
- Hands-on experience with at least one ambulatory EHR (athenahealth, eClinicalWorks, AdvancedMD, NextGen, ModMed, Practice Fusion, WebPT). Epic, Cerner, or Meditech Expanse is a plus
- Healthcare fluency: clinical documentation, specialty workflows, HIPAA, and the security questionnaires (SOC 2, HITRUST) that come with selling into practices
- Comfort reading and debugging an integration: browser automation, DOM, REST APIs, JSON schemas, HL7/FHIR. You can use SQL and internal tooling to figure out why a note didn’t land
- 3–7 years in sales engineering, solutions engineering, implementation, or healthcare IT. Engineers who want to spend more time with customers are welcome