Our mission

We’re building infrastructure for modern healthcare delivery.

Traditional healthcare is plagued with outdated, monolithic EHRs designed to maximize billing outcomes. Patient outcomes and provider experiences have been afterthoughts, as these systems have bolted on non-API-first solutions. None of this is built for how clinically excellent healthcare is actually delivered—longitudinally and collaboratively, with the patient at the center.

Healthie is the world’s leading API-first, ONC-Certified EHR for healthcare delivery outside of the hospital. We provide the powerful infrastructure every scaling organization needs—EHR, scheduling, patient engagement, billing, and more—all accessible via modern APIs and a white-labeled UI. Our platform makes it simple for organizations of any size to launch, customize, and scale their care delivery models without reinventing the wheel.

Today, over 2 billion API calls are made to Healthie every month, as thousands of organizations—working with more than 21 million patients in total—rely on Healthie to deliver clinically excellent healthcare in over 35 specialties, from preventative medicine to complex chronic care management.

We believe in the power of technology to improve access to healthcare—and we’re building the rails that make this a reality. We work fast and with quality because we provide business-critical, healthcare-critical software that clinicians and patients need for a better healthcare system. We’re customer-obsessed, operate with lightning-fast processes and responses, make our product roadmap public so customers can see what we’re building, and remain relentlessly focused on how care gets delivered.

Healthie is backed by leading investors, and while we've $42M raised to date, more importantly, we operate with fiscal responsibility and have been profitable for more than half of our time as a company.

Learn more at https://www.gethealthie.com/

About the role

Revenue Operations is a core strategic function at Healthie, and our Customer teams (Customer Success and Customer Support) is where much of our next-stage growth is won or lost. As we scale toward $100MM+ in ARR, our customer lifecycle — onboarding, health, renewals, and expansion — is moving natively into Salesforce as we migrate off our standalone CS platform. We need a builder who can make that system real, trustworthy, and fast.

We're hiring a Senior Salesforce Developer for Customer Operations to own the engineering behind our customer lifecycle in Salesforce. This is a developer-first role: you'll write the Apex, build the flows and Lightning components, design the custom objects, and stand up the API integrations that turn Stripe billing, product usage, and Customer activity into clean, actionable signal for our Customer teams. You are equal parts Salesforce engineer and Customer Success + Support operator — you understand how Customer teams actually work, and you build systems that make them faster without heroics.

This role is deliberately hands-on. You've done this at a company with real scale — where data volume, governance, and complexity are non-negotiable — and you can operate at startup cadence, shipping quickly, owning ambiguity, and iterating in the open. You'll report to Bill Coffin, Director of Revenue Operations, and partner closely with our VP of Customer Management (Caseley), our VP of Customer Support (Justin), our GTM Systems Admin (Aaron), and teams across Finance, Product, and Engineering.

What You’ll Own

Salesforce Development & Engineering

Build the Customer lifecycle natively in Salesforce — Apex classes and triggers, Flows, Lightning Web Components (LWC), validation rules, and custom objects for onboarding, health, renewals, expansion, and churn.
Write production-grade, tested code — meaningful Apex test coverage, bulk-safe logic, and thoughtful use of code vs. declarative tooling based on what actually scales.
Own deployment hygiene — sandboxes, source control (Git / SFDX), and a repeatable release process. No changes straight into production, no undocumented org drift.
Refactor toward maintainability — pay down clicks-not-code debt where it's brittle, and leave the org cleaner than you found it.

Customer Operations

Own Customer Ops workflows in Salesforce — the systems behind onboarding SLAs, customer health scoring, renewal management, expansion signals, and churn-risk playbooks for both solo and group practices.
Lead the Vitally → Salesforce migration — data model design, field mapping, parity testing, and cutover, in close partnership with the Customer Management team. When it's done, CM works exclusively in Salesforce, with no dropped context.
Make handoffs clean — sales → onboarding → CSM → renewal should carry full context automatically. Nothing falls through the cracks between systems or teams.
TranslateCustomer CS strategy into systems — sit with the CM + Support team, understand how they actually work, and turn their motion into workflows that reduce manual effort.
Work with GTM Tech Stack integrations, especially with our Help Desk platform, Help Scout
Experience implementing Customer Project management tooling

Integrations & APIs

Own the API integrations that feed Customer data— Stripe (billing and subscription events), ChartMogul, product usage (Mixpanel / Chameleon), CSAT / NPS Scoring, Automated call capturing and Insights, and HubSpot, built and maintained so data flows accurately and on time.
Work fluently across REST, Bulk, and webhook patterns — build resilient integrations and middleware, handle rate limits and failures gracefully, and instrument them so breakage is visible before a stakeholder finds it.
Make product usage actionable — surface the signals (billing volume, charting time, multi-provider growth) that tell Customer Success and Customer Support when to intervene, upsell, or save an account.

Data Integrity & AI-Ready Systems

Build for clean, structured data by default — every object and workflow you ship should generate the structured data that reporting and AI depend on. If a process doesn't produce clean data, change the process.
Contribute to the data dictionary — clear definitions, ownership, and source-of-truth designation for the Customer and lifecycle fields you own. Flag drift when you see it.
Feed the AI layer real signal — the blocker on AI-assisted Customer workflows (health scoring, account research, meeting prep, expansion prompts) is data availability. Prioritize the pipelines and backfills that give those workflows something real to act on.
Document what you build and manage change — UAT, training, and written decision docs so systems outlive their builders.
Own data integrity across the customer stack — partner with GTM Systems to build repeatable reconciliation pipelines (Stripe ↔ SFDC ↔ ChartMogul, account dedupe) so every system agrees on the same number, discrepancies surface automatically, fixes land in the pipeline rather than manual cleanup, and the CS and revenue layers stay in sync.

AI-Native Engineering

Use AI as a first-class tool in your own workflow — Claude Code and similar tools to build, test, and ship faster, not as a shortcut to lower quality.
Build AI-powered workflows inside Salesforce — practical automations that save the Customer team time and catch risk earlier, designed with a clean data model behind them.

How You’ll Spend Your Time

This is not a pure strategy role and not a pure systems role. It is deliberately both. You'll work in a sprint-based build team with a real intake process.

Approximate time allocation:

45% — Building & Engineering: hands-on Salesforce development (Apex, LWC, Flows), API integrations, and Customer workflow builds
25% — Ops Enablement & Design: lifecycle architecture and stakeholder work with the Customer Management team
20% — Data Integrity, Testing & Deployment: test coverage, release hygiene, documentation, and data governance
10% — Collaboration & Meetings: Customer Management, RevOps, Product, Engineering, and Finance

What Success Looks Like

In the first 6 months, success means:

The customer lifecycle runs natively in Salesforce — Vitally is fully migrated and the Customer Management team works exclusively in SFDC.
Stripe ↔ Salesforce and product-usage ↔ Salesforce integrations are live, accurate, and trusted.
Health scores and expansion signals surface to CSMs automatically — no manual pulls, no guesswork.
Customer team handoffs carry full context end-to-end, and no information is dropped between teams.
Your builds are tested, version-controlled, and documented — the org runs on systems, not heroics.
AI-assisted CS workflows have clean, structured data to run on.

At scale, success means Healthie can grow faster without adding proportional operational complexity.

About you

6–10+ years in Salesforce development, RevOps engineering, or GTM / Customer systems — with meaningful time spent writing code, not just configuring
Hands-on Salesforce developer: Apex, SOQL, triggers, Flows, LWC, and custom object modeling. Comfortable with sandboxes, source control, and a real deployment process (SFDX / Git / CI)
Strong API integration experience: REST and Bulk APIs, webhooks, and middleware. Direct, hands-on experience with Stripe billing and subscription APIs specifically
Deep understanding of Customer Success Ops workflows: onboarding, health scoring, renewals, expansion, and churn — you know how Customer teams operate and what they need from their systems
Scaled-company rigor and startup speed: you've operated inside a larger organization where data volume, governance, and complexity are serious — and you thrive at startup operating rhythm, with ambiguity, ownership, and fast iteration
AI-native: you already use AI tools in your engineering workflow and are excited to build AI-powered systems, not just talk about them
SaaS fluency: comfortable with ARR, NRR, gross/net retention, churn, and expansion, and how they're represented in systems
Strong communicator: you can translate cleanly between Customer Success, Finance, Product, and Engineering, and set realistic expectations under change
Understands HIPAA constraints on tooling and data flows

Nice to Have

Salesforce certifications (Platform Developer I / II, Administrator)
Experience with Salesforce Revenue Cloud, PandaDoc, or quote-to-cash builds
Prior migration off a dedicated Customer Success platform (Vitally, Gainsight, ChurnZero, Totango) into Salesforce
Data warehouse / analytics engineering exposure (dbt, SQL, BI layers)
Python or another scripting language for integrations and tooling

Details

Hybrid work schedule in New York, NY
Reports to Bill Coffin, Director of Revenue Operations
Full-time; U.S. work authorization is required

Interview process

Quick chat with someone from our Talent team(20 mins)
Interview with Bill Coffin, Director of Revenue Operations — hiring manager (30 mins)
Technical interview with Aaron, GTM Systems Admin — Salesforce development & integrations deep dive (45 mins)
Take-home or live technical assessment (a scoped Salesforce build / API integration exercise)
In-person group presentation with Aaron, Bill, Vivek (Sr. Director, Growth & RevOps), Caseley (VP of Customer Management) (45–60 mins)
Final round with Vivek, Sr. Director, Growth & Revenue Operations (30 mins)
Reference checks

Learn more at gethealthie.com/careers

Healthie is subject to HIPAA and other security and privacy frameworks, and this job entails training and conformance to expectations regarding security and compliance.

Healthie participates in e-verify.

Healthie is committed to equal employment opportunity. All qualified applicants will receive consideration for employment without regard to and will not be discriminated against based on age, race, gender, color, religion, national origin, sexual orientation, gender identity, veteran status, disability or any other protected category. We're proud to be building a diverse and inclusive environment that encourages collaboration, creativity, and growth. Whatever your background, please apply if this is a role that would make you excited to come into work every day.

Senior Salesforce Developer, Customer Success Operations

About the Role

Skills

Full job details