Customer Engineer

About Charta Health

In an industry where the focus should rightly be on delivering quality care to patients, healthcare providers remain burdened by the complexities of non-clinical operations. Charta is changing that.

We're building the operating system for modern healthcare organizations. Our AI platform streamlines critical workflows across revenue cycle, clinical operations, and administrative functions, helping providers and payers operate more efficiently and deliver better patient care. Backed by Bain Capital Ventures, Charta is on a mission to make every healthcare dollar accountable and every chart accurate, reimagining healthcare infrastructure from the ground up.

About the Opportunity

We're looking for a Support Engineer to be the first technical line of defense behind our customer-facing team. When a client reports that something looks wrong - a chart that wasn't processed, a code that didn't appear, an integration that stopped sending data, an output that doesn't match what the clinician documented - you are the person who figures out what actually happened, why, and what it would take to fix it.

This is not a customer-facing role. Our Technical Success Managers own the client relationship and deliver outcomes to customers. You own the investigation behind them: reproducing the issue, tracing it to a root cause in data, logs, configuration, or code, resolving what you can directly, and handing Engineering a well-scoped diagnosis and proposed fix for what you can't. Your work is what lets our customer team give clients fast, accurate answers - and what protects our engineers' time for building.

Every account is mapped to an owning engineering pod, so you will always know where an escalation goes. You are accountable for the quality of the triage decision and for making sure nothing reaches an engineer that you could have resolved or scoped yourself.

What you'll do

Investigate and Diagnose: Take incoming issues from the Technical Success team - bugs, data discrepancies, processing gaps, unexpected model output - and dig in hands-on. Reproduce the problem, query the data, read logs and pipeline runs, and trace the issue to a root cause.

Triage with Judgment: Classify every issue quickly and correctly: live incident vs. one-off, deployment/configuration issue vs. product bug vs. expected behavior vs. feature gap. Route incidents to oncall, bugs and gaps to the owning pod, and close out anything that is working as designed - with the evidence to show it.

Resolve What You Can (Tier 1): Fix configuration, mapping, and data issues directly; re-run failed jobs; correct customer-specific setup; and answer "did Charta do this?" questions with a definitive, evidence-backed yes or no.

Propose Fixes (Tier 2): For code-level defects, go beyond "it's broken." Identify where in the codebase the problem lives, write up the root cause, and propose a fix - up to and including drafting the change for engineering review. Engineers should receive a ticket they can act on, not a mystery.

Hand Off Cleanly to the Customer Team: Give the Technical Success Manager a clear, plain-English summary of what happened, what was affected, what's being done, and a realistic timeline - so they can deliver the message to the client with confidence.

Own the Loop Internally: Track every open issue from intake to resolution. Follow up with Engineering, confirm fixes in production, and tell the customer team when it's safe to close the loop with the client.

Build the Knowledge Base: Turn every investigation into reusable knowledge - runbooks, known-issue write-ups, diagnostic queries, and triage guides - so the same question takes minutes, not hours, the next time, and so the customer team can self-serve more over time.

Spot Patterns: Aggregate issues across accounts to surface recurring defects, fragile integrations, and gaps in monitoring or tooling. Bring data-driven recommendations to Product and Engineering about what to fix at the source.

You'd be a great fit, if you