Business and Data Analyst

About Us

Abacus Insights is transforming how data works for health plans. Our mission is simple: make healthcare data usable, so the people responsible for care and cost decisions can act faster, with confidence.

We help health plans break down data silos to create a single, trusted data foundation. That foundation powers better decisions—so plans can improve outcomes, reduce waste, and deliver better experiences for members and providers alike. Backed by $100M from top investors, we’re tackling big challenges in an industry that’s ready for change. Our platform enables GenAI use cases by delivering clean, connected, and reliable healthcare data to support automation, prioritization, and decision workflows—and it’s why we are leading the way.

Our innovation begins with people. We are bold, curious, and collaborative—because the best ideas come from working together. We embrace the thoughtful use of AI and automation to drive innovation and efficiency, and we look for individuals who are curious and adaptable—those excited to leverage emerging technologies to enhance how we work—while keeping human insight, connection, and our clients at the center of every decision.

Ready to make an impact? Join us and let’s build the future together.

About the Role

We are seeking an experienced Business and Data Analyst to join our team. 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.

No engagement lives in isolation. 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.

Our clients are US health plans and the partners who serve them, and the engagements span everything it takes to make their data usable. That can mean standardizing and migrating data onto a new platform, meeting evolving regulatory and compliance mandates, or powering the broader analytics and reporting programs that drive payer performance — across Medicare, Medicaid, and Commercial lines of business.

This role requires regular collaboration with US-based clients, including occasional work during US business hours.

Your day to day

Own the Requirements-to-Design Arc

• 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.

Work Hands-On With Data

• Write and execute SQL to analyze and probe data, test assumptions, and prototype throughout requirements and design. Hands-on data work is core to this role, not occasional.

Be the Client-Facing Anchor

• Drive requirements-gathering and clarification conversations with clients, since incomplete or poorly elicited requirements undermine everything built downstream.
• Represent client intent throughout the engagement and remain an active point of contact through delivery.
• Translate fluently between business and technical audiences, so both sides share the same understanding.

Collaborate Across Delivery

• Be the central node connecting the client and the internal team, holding the business context and design drivers that shape the build.
• Act as the client's SME for Solution Architects, Product, QA, Account Management, and Program Management, giving them clean hand-offs with the context, business rules, and logic they need to execute without rework or reinterpretation.
• Hold the wider view across a multi-workstream engagement: understand how a decision made for one workstream affects the others, and flag those ripple effects before they surface as rework.

What you bring to the team