Business Solution Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow those examples. Probably we should include sections that match content: About the role (there is "About The Role"), Responsibilities (the "Your day to day" section), Requirements (the "What You Bring To The Team"), Qualifications maybe overlapping with Requirements; but we can combine? The instruction says prefer a few substantive sections over many thin ones. We could have About the role, Responsibilities, Requirements, Benefits. Pay and Schedule not present (no specific pay or schedule). Skills maybe not separate; could be part of Requirements. Qualifications maybe same as Requirements. We'll include About the role, Responsibilities, Requirements (including qualifications), Benefits. Also maybe "About Us" but not in list; but we could include as a section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we stick to those. The posting has "About Us" at start; we could treat that as part of About the role? Probably better to include a short paragraph about the company under About the role? But the instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid About Us heading. However the examples list only those. I'd include About the role, Responsibilities, Requirements, Benefits. Also maybe "What You Would Like To See, But Not Required" could be part of Requirements or Qualifications. We'll incorporate into Requirements. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them into lists and paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Our Commitment as an Equal Opportunity Employer", "AI Use in Recruitment". Those are EEO/legal boilerplate; we must remove them. Also "About Us" is not boilerplate; it's substantive about company. Should we keep? It's about the company, not the role. Might be considered substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep About Us content. But we need a heading for it? Could use
About Us
. Not in the examples but seems okay. However the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should likely stick to those. However About Us is substantive; we could incorporate it into About the role section as a preamble. But that might mix company description with role description. The instruction says "About the role" heading for section headings (e.g. About the role...). It doesn't say we cannot have other headings, but to be safe we could treat About Us as a
before the sections, not a heading. That would preserve content without extra heading. That seems acceptable. Thus output: start with a
containing About Us paragraph(s). Then
About the role
with content: description of role (the paragraph after "About The Role" up to "Your day to day"? Actually the role description includes paragraphs about being connective tissue etc. We'll include that as prose under About the role. ThenResponsibilities
with list items from "Your day to day" bullet points (the numbered? Actually it's a paragraph with bold headings and then description). We need to extract each responsibility as list items. The text includes: - Own The Requirements-to-Design Arc (with sub-bullets) - Work Hands-On With Data - Be the Client-Facing Anchor - Collaborate Across Delivery Each has multiple sentences. We'll make each top-level asRequirements
(or Qualifications). We'll combine requirements and qualifications. Content: "What You Bring To The Team" list: Bachelor's degree..., 3+ years..., Payer experience required..., Working command..., Able to write..., Experience eliciting..., Confident client-facing..., Comfort operating..., Demonstrated systems thinking... Then "What We Would Like To See, But Not Required" list: Background..., Familiarity..., Working knowledge..., Familiarity... We'll include all as list items under Requirements. ThenBenefits
list from "What You’ll Get In Return": Unlimited paid time off..., Work from anywhere..., Comprehensive health coverage..., Equity for every employee..., Growth-focused environment..., Home office setup allowance..., Monthly cell phone allowance... We must not include Pay or Schedule sections as not specified. We must not include any boilerplate like EEO, AI Use in Recruitment. We must not include duplicated lines. We must preserve all substantive info: ensure we didn't drop any details like "Backed by $100M from top investors" etc. That is in About Us; we need to keep it. Let's craft About Us paragraph(s): The original About Us paragraph: "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." We'll put that as amaybe split into multiple paragraphs for readability but single
is fine. Now About the role paragraph: The section after "About The Role" up to before "Your day to day". Let's capture: "We are seeking an experienced Business Solution Manager 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." We'll put that as
under About the role. Now Responsibilities: We'll extract each top-level bullet. From text: "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." We'll make each top-level heading as an