BA/Technical Product Manager

<h2>Partner Discovery &amp; Requirements Analysis</h2><ul>
<li>Lead and document working sessions with clinical, finance, operations, product, and technical stakeholders to understand existing workflows, business rules, data requirements, and operational processes.</li>
<li>Translate manual and system-supported workflows into structured business and functional requirements.</li>
<li>Produce gap-analysis documentation mapping current-state processes and partner requirements to existing platform capabilities.</li>
<li>Classify requirements based on appropriate disposition, such as existing functionality, configuration, new development, acceptable operational workaround, shared platform enhancement, or out of scope.</li>
<li>Maintain a consistent backlog structure across implementations so requirements remain comparable, traceable, and reusable.</li>
</ul><h2>System Reconciliation &amp; Technical Analysis</h2><ul>
<li>Analyze application logic, SQL, stored procedures, configuration parameters, integrations, and data flows to understand existing system behavior.</li>
<li>Determine whether business requirements can be satisfied through configuration, existing functionality, process changes, or new development.</li>
<li>Validate assumptions about platform behavior against available technical evidence and distinguish confirmed system behavior from inferred behavior.</li>
<li>Identify discrepancies between documented behavior, stakeholder expectations, system configuration, and implemented logic.</li>
<li>Trace business rules to underlying parameters, data elements, calculations, integrations, and system components.</li>
<li>Identify where behaviors are configurable versus hardcoded and assess the impact on future implementations.</li>
</ul><h2>Requirements Authoring</h2><ul>
<li>Write clear business and functional requirements, user stories, acceptance criteria, assumptions, dependencies, open questions, and proposed workarounds.</li>
<li>Maintain appropriate separation between business-facing requirements and technical implementation details.</li>
<li>Ensure acceptance criteria reflect the agreed solution approach, including configuration changes, operational workarounds, or new functionality.</li>
<li>Apply a consistent standard for distinguishing standalone requirements from assumptions, configuration decisions, implementation details, or operational procedures.</li>
<li>Maintain traceability from business need through solution decision and development implementation.</li>
</ul><h2>Cross-Functional Facilitation &amp; Governance</h2><ul>
<li>Facilitate requirements, solutioning, and review sessions across business, clinical, product, engineering, data, and operational teams.</li>
<li>Drive open questions toward resolution and update requirements and documentation to reflect confirmed decisions.</li>
<li>Identify ambiguity, conflicting requirements, downstream impacts, and cross-feature dependencies before development begins.</li>
<li>Prevent scope drift and ensure implementation-specific requirements do not unintentionally become platform-wide requirements.</li>
<li>Support prioritization and decision-making by clearly communicating business impact, implementation complexity, dependencies, and risk.</li>
</ul><h2>Ticket Creation &amp; Scoping</h2><ul>
<li>Translate approved requirements into development-ready tickets containing problem statements, user stories, functional scope, acceptance criteria, dependencies, assumptions, and open questions.</li>
<li>Partner with engineering and architecture teams to clarify technical scope and implementation approach.</li>
<li>Track dependencies across features, integrations, implementations, and shared platform capabilities.</li>
<li>Identify common capabilities that can support multiple clients, workflows, or future implementations rather than creating one-off solutions.</li>
</ul><h2>Requirements</h2><ul>
<li>8+ years of experience as a Business Analyst, Technical Product Manager, Product Owner, or equivalent role in a software-, data-, or technology-driven environment.</li>
<li>Experience working within healthcare technology, healthcare operations, payer/provider systems, pharmacy, claims, revenue cycle, eligibility, or related healthcare domains.</li>
<li>Ability to understand and reason about SQL, data structures, system logic, APIs, configuration, and technical workflows well enough to validate platform behavior and collaborate effectively with engineering teams.</li>
<li>Demonstrated ability to write clear requirements, user stories, acceptance criteria, and development tickets that engineering teams can implement with minimal rework.</li>
<li>Strong analytical rigor with the ability to distinguish confirmed facts from assumptions, challenge unclear reasoning, and validate conclusions.</li>
<li>Experience facilitating requirements and solution-review sessions involving business, clinical, operational, and technical stakeholders.</li>
<li>Strong written and verbal communication skills, with the ability to adapt business and technical information for different audiences.</li>
</ul><h2>Preferred Qualifications</h2><ul>
<li>Familiarity with healthcare claims, eligibility, reimbursement, clinical workflows, pharmacy operations, or healthcare financial processes.</li>
<li>Experience working with configurable or rules-driven healthcare platforms.</li>
<li>Experience supporting client, provider, health system, or partner implementations.</li>
<li>Understanding of data pipelines, ETL processes, APIs, healthcare integrations, and data exchange concepts.</li>
<li>Experience managing a shared product backlog across multiple customers, implementations, or business units.</li>
<li>Familiarity with healthcare data standards, regulatory requirements, or privacy considerations such as HIPAA.</li>
</ul><h2>Key Competencies</h2><ul>
<li>Requirements elicitation and translation</li>
<li>Healthcare workflow analysis</li>
<li>Technical and data analysis</li>
<li>System behavior reconciliation</li>
<li>Product and backlog management</li>
<li>Stakeholder facilitation and decision-driving</li>
<li>Cross-functional collaboration</li>
<li>Analytical rigor and structured problem-solving</li>
<li>Dependency and impact analysis</li>
<li>Documentation discipline and traceability</li>
</ul>