Opens the job on Medical Informatics Engineering's own careers site. Some companies ask you to create an account or click through another page first.
What you'd actually do: Own post-go-live relationships for assigned occupational health software accounts, driving adoption, health scoring, escalations and QBRs, and flagging expansion opportunities to Account Management.
Most people just hit Apply. Do these first and you show up with someone on the inside.
A friendly message to a current rep is the best way to stand out. Ask about their experience, not for a referral.
Enterprise Health is standing up a dedicated Client Success Management function to close a long-standing gap: Account Management has been informally absorbing CSM responsibilities alongside its commercial ownership, leaving no clean signal on client health, adoption, or sentiment. The Client Success Manager (CSM) owns the operational client relationship after go-live โ driving adoption, generating the health and Voice of Customer signal that informs commercial decisions, and resolving escalations that go beyond a routine support ticket.
The CSM is accountable for the outcomes that justify the account's continued and expanded investment in Enterprise Health, without carrying quota or negotiating contract terms. Account Management remains accountable for the commercial relationship and owns all renewals, in all cases.
for each assigned account once Deployment hands off a live client.
and proactively intervene where usage lags expectations.
so the account transition carries context, not a cold start.
for assigned accounts, built on data โ case volume and severity, adoption metrics, and sentiment โ rather than relationship intuition alone.
feeding the Client Success Leader's aggregated, prioritized theme set for Product leadership review.
the moment it surfaces, rather than waiting for a scheduled check-in.
that meet defined triggers: repeat tickets on the same root issue, client language signaling relationship risk, an SLA breach on a dedicated account, anything touching contract or scope, an unresponsive client, or a change in client contact.
directly, and share ownership of Tier 2 escalations with the Client Success Leader โ enriching the AM's initial case record with technical detail and driving it through resolution.
on complex, multi-phase recovery efforts, working alongside PMO (project plan) and Deployment (where the issue is implementation-related).
surfaced through day-to-day engagement, routing them to Account Management for pursuit and close.
without owning renewal negotiation or outcome.
for assigned accounts, coordinating with Account Management on any commercial content.
with Account Management owning the commercial components.
These boundaries exist specifically to prevent the ownership overlap this function was created to fix:
Drawn directly from the finalized Cross-Functional Ownership Model & RACI. R/A = Responsible/Accountable for that activity.
Owns onboarding success plan and adoption/engagement plan once an account hands off from Deployment.
Deployment owns the technical build and go-live; CSM owns what happens after the client is live.
Owns the day-to-day operational relationship โ usage, satisfaction, and value realization.
Account Management owns the commercial relationship and all renewals, with no exceptions.
Owns health score and risk flagging for assigned accounts.
Built from data โ case volume/severity, adoption, sentiment โ not relationship intuition alone.
Owns VoC /sentiment signal generation for assigned accounts.
Feeds the Client Success Leader's aggregated, prioritized signal to Product leadership.
Takes ownership of escalations Support elevates per defined triggers (repeat root-cause issues, relationship-risk language, SLA breaches, contract/scope mentions, unresponsive clients, contact changes).
CSM is not a pass-through for routine tickets โ Tier 1/Tier 2 Support resolves individual tickets solo.
Owns Tier 1 AM escalations directly; shares Tier 2 ownership with the Client Success Leader.
AM logs the initial case record and remains a watcher/CC โ CSM enriches, owns, and resolves.
Owns the client relationship through complex issue resolution, optimization, and multi-phase recovery efforts.
PMO owns the project plan; Deployment is consulted if the issue is configuration-related.
Identifies and flags expansion opportunities surfaced through operational engagement.
Account Management owns pursuit, negotiation, and close.
Provides health input into the renewal process.
Account Management owns renewal negotiation and the outcome.
Owns delivery of Quarterly/Executive Business Reviews for assigned accounts.
Coordinates content with AM where commercial topics are relevant.
Owns the operational components of the account strategic plan.
Account Management owns the commercial components.
day-to-day partners on the escalation path defined above; friction is worked out peer-to-peer, with the Client Success Leader as tie-break only when the two can't reach agreement.
primary interface for escalation handoffs and health input into renewals; AM and CSM don't share a leader, so this path runs through the structured escalation case log, not informal contact.
shadow deployments pre-handoff; partner on complex recovery efforts where a situation has outgrown a normal ticket.
aggregates CSM-generated health and VoC signal into the structured set presented to Product leadership.