Business Solution Manager

Lead discovery sessions with client subject matter experts to understand the why and what behind each use case: the business context, pain points, expected outcomes, and success criteria, rather than just the surface-level data ask.

Translate each use case into a set of clear, testable requirements, with the success criteria and non-functional requirements that define what done looks like, keeping full traceability from business need to requirement.

Document the requirements unambiguously for the client and downstream teams, then translate them into a design the developers can build from: the source-to-target data flow, transformation logic, and business rules that produce the intended output.

Determine the appropriate grain and structure of a dataset given the business context, so the design answers the real question rather than an approximation of it — and trace how that grain decision ripples into every downstream report, model, or program that consumes the data.

Map the dependencies before finalizing a design: which other workstreams, reports, or client use cases touch this same data, and how a change here could break or benefit them.

Apply systems thinking as a default habit, not an exception: recognize when a design built for one client, state, or use case can become a reusable pattern, and actively design toward that reuse rather than discovering it in hindsight.

Compensation for this role is based on experience, skills, and location, and includes base salary plus eligibility for performance bonuses and equity grants.

In this role, you'll be the connective tissue between a client's business need and the design that delivers it.

You'll own the definition and quality of business requirements throughout an engagement, making sure business intent, scope, and success criteria are unambiguous, then carry that understanding through to the design itself so what reaches the developers is clean and buildable rather than a set of open questions.

Doing that well takes two things at once: command of healthcare business context, and the data literacy to work directly in the data.

This is a client-facing role, so you'll translate complex healthcare challenges into precise requirements, and you'll have the technical fluency to reason about how those requirements become a working design.

A data model built for one client's use case can share structure with a completely different client's need; a transformation rule written for one state's requirements often anticipates the next state's.

You'll need to see each requirement as part of a larger system — of clients, states, use cases, and data flows — and make design choices that hold up across that system, not just for the request in front of you.