BA/Technical Product Manager

ProArch

9h•$80,000 - $100,000

About The Position

The BA/Technical Product Manager leads partner discovery and requirements analysis, translating clinical, financial, operational, product, and technical workflows into structured, traceable requirements. The role assesses how partner needs align with existing platform capabilities, documents gaps, and classifies requirements as existing functionality, configuration, new development, operational workaround, shared platform enhancement, or out of scope. The position analyzes application logic, SQL, stored procedures, configuration, integrations, and data flows to reconcile documented behavior, stakeholder expectations, and implemented system behavior. It authors business and functional requirements, user stories, acceptance criteria, assumptions, dependencies, and development tickets, maintaining a clear distinction between business needs and technical implementation details. The role facilitates cross-functional requirements and solution reviews, resolves open questions, identifies ambiguity and downstream impacts, supports prioritization, and helps prevent scope drift. It partners with engineering and architecture teams to clarify implementation approaches and track dependencies across features, integrations, implementations, and shared platform capabilities.

Requirements

At least 8 years of experience as a Business Analyst, Technical Product Manager, Product Owner, or equivalent in a software-, data-, or technology-driven environment.
Experience in healthcare technology, healthcare operations, payer/provider systems, pharmacy, claims, revenue cycle, eligibility, or related healthcare domains.
Ability to understand and reason about SQL, data structures, system logic, APIs, configuration, and technical workflows to validate platform behavior and collaborate with engineering teams.
Demonstrated ability to write clear requirements, user stories, acceptance criteria, and development tickets that engineering teams can implement with minimal rework.
Strong analytical rigor, including the ability to distinguish confirmed facts from assumptions, challenge unclear reasoning, and validate conclusions.
Experience facilitating requirements and solution-review sessions involving business, clinical, operational, and technical stakeholders.
Strong written and verbal communication skills, with the ability to adapt business and technical information for different audiences.

Nice To Haves

Familiarity with healthcare claims, eligibility, reimbursement, clinical workflows, pharmacy operations, or healthcare financial processes.
Experience working with configurable or rules-driven healthcare platforms.
Experience supporting client, provider, health system, or partner implementations.
Understanding of data pipelines, ETL processes, APIs, healthcare integrations, and data exchange concepts.
Experience managing a shared product backlog across multiple customers, implementations, or business units.
Familiarity with healthcare data standards, regulatory requirements, or privacy considerations such as HIPAA.

Responsibilities

Lead and document working sessions with clinical, finance, operations, product, and technical stakeholders to understand workflows, business rules, data requirements, and operational processes.
Translate manual and system-supported workflows into structured business and functional requirements.
Produce gap analyses mapping current-state processes and partner requirements to existing platform capabilities.
Classify requirements by disposition, including existing functionality, configuration, new development, operational workaround, shared platform enhancement, or out of scope.
Maintain a consistent, comparable, traceable, and reusable backlog structure across implementations.
Analyze application logic, SQL, stored procedures, configuration parameters, integrations, and data flows to understand system behavior.
Determine whether requirements can be met through configuration, existing functionality, process changes, or new development.
Validate platform-behavior assumptions against technical evidence and distinguish confirmed behavior from inference.
Identify discrepancies between documented behavior, stakeholder expectations, system configuration, and implemented logic.
Trace business rules to underlying parameters, data elements, calculations, integrations, and system components.
Identify configurable versus hardcoded behavior and assess impacts on future implementations.
Write business and functional requirements, user stories, acceptance criteria, assumptions, dependencies, open questions, and proposed workarounds.
Maintain separation between business-facing requirements and technical implementation details.
Ensure acceptance criteria reflect the agreed solution approach and maintain traceability from business need through solution decision and implementation.
Facilitate requirements, solutioning, and review sessions across business, clinical, product, engineering, data, and operational teams.
Drive open questions toward resolution and update documentation to reflect confirmed decisions.
Identify ambiguity, conflicting requirements, downstream impacts, and cross-feature dependencies before development begins.
Prevent scope drift and ensure implementation-specific requirements do not unintentionally become platform-wide requirements.
Support prioritization and decision-making by communicating business impact, implementation complexity, dependencies, and risk.
Translate approved requirements into development-ready tickets with problem statements, user stories, functional scope, acceptance criteria, dependencies, assumptions, and open questions.
Partner with engineering and architecture teams to clarify technical scope and implementation approach.
Track dependencies across features, integrations, implementations, and shared platform capabilities.
Identify common capabilities that can support multiple clients, workflows, or future implementations rather than creating one-off solutions.