Healthcare Systems Analyst (Technical)

Healthcare Systems Analyst (Technical)
Location: Minnesota, MN
Duration: 9-12 Month

JD:

Systems Analyst (Technical) Drug Cost Estimator & Provider Search

Role Summary

We are seeking a technically-oriented Systems Analyst to support the continued evolution of our Drug Cost Estimator (DCE) and Provider Search (PS) digital products.

This role acts as the technical backbone of the product team, partnering with Product Managers, Business Analysts, Product Owners, and Engineering to translate complex business and regulatory requirements into clear, system-level specifications.

The Systems Analyst will focus on deep system behavior, data flows, and integrations, ensuring that highly complex logic such as drug pricing, benefit coverage, and provider data is accurately designed, implemented, and maintained at scale.

Key Responsibilities

1. System-Level Requirements & Technical Decomposition

• Translate business requirements into detailed system requirements, technical user stories, and implementation-ready specifications
• Analyze end-to-end system behavior across DCE and PS, including front-end inputs, back-end services, APIs, and downstream dependencies
• Define complex business logic at a system level, including:
  • Drug pricing and cost calculations (deductibles, tiers, phases)
  • Eligibility and plan benefit logic
  • Provider search filtering, ranking, and network inclusion logic
• Ensure requirements are complete, consistent, and aligned to business intent

2. Data Flows, APIs & Integration Design

• Map and document data flows across multiple systems, including:
  • Pharmacy pricing engines, formulary data, and benefit services (DCE)
  • Provider directories, network data, and search/indexing services (PS)
• Define API interactions, service orchestration, and data mappings between systems
• Identify data dependencies, transformation rules, and edge cases that impact user-facing outputs
• Ensure data accuracy and traceability from source systems to user experience

3. Partnership with Product & Business Analysis

• Complement Business Analysts by taking requirements to a deeper technical level (the how, not just the what )
• Partner with Product Managers and Product Owners to:
  • Clarify feasibility and constraints
  • Identify technical trade-offs early
• Participate in feature refinement and backlog grooming to ensure engineering-ready stories

4. Engineering Enablement & Agile Delivery

• Serve as the primary liaison between product and engineering, ensuring shared understanding of system behavior
• Create technical artifacts such as:
  • Data flow diagrams
  • Sequence diagrams
  • Service interaction models
• Support engineering teams with:
  • Requirement clarification
  • Data mapping and logic validation
• Ensure features are fully defined, testable, and aligned with system architecture before development

5. Testing, Validation & Accuracy Assurance

• Partner with QA to define test scenarios aligned to system logic and edge cases
• Validate that outputs (e.g., drug cost calculations, provider results) are:
  • Accurate
  • Consistent
  • Compliant with business rules
• Support UAT readiness and defect triage, particularly where issues stem from data or system logic

6. Production Support & Continuous Improvement

• Investigate and resolve complex production issues, including:
  • Incorrect drug pricing or cost outputs
  • Missing or inaccurate provider results
• Perform root cause analysis across systems and data pipelines
• Identify opportunities to improve:
  • Data quality and latency
  • System performance and scalability
  • Integration reliability
• Drive enhancements that improve consumer trust and experience

What Makes This Role Critical for DCE & Provider Search

• These tools depend on highly complex, multi-system logic (pricing, eligibility, provider data)
• Errors directly impact consumer trust, compliance, and conversion
• Success requires:
  • Deep understanding of data + systems, not just UX or business flows
  • Ability to trace outputs back through multiple dependencies
  • Strong partnership across Product, BA, Engineering, and data teams