---
title: "BA/Technical Product Manager at ProArch – All Job Board"
---

# BA/Technical Product Manager at ProArch

Written by

[admin](https://alljobboard.com/author/admin/)

in

- [United States (Remote)](https://maps.google.com/maps?q=United%20States%20%28Remote%29&zoom=14&size=512x512&maptype=roadmap&sensor=false)
- Posted 5 days ago

![ProArch](https://alljobboard.com/wp-content/plugins/wp-job-manager/assets/images/company.png)

 **ProArch**

### Partner Discovery & Requirements Analysis

- Lead and document working sessions with clinical, finance, operations, product, and technical stakeholders to understand existing workflows, business rules, data requirements, and operational processes.
- Translate manual and system-supported workflows into structured business and functional requirements.
- Produce gap-analysis documentation mapping current-state processes and partner requirements to existing platform capabilities.
- Classify requirements based on appropriate disposition, such as existing functionality, configuration, new development, acceptable operational workaround, shared platform enhancement, or out of scope.
- Maintain a consistent backlog structure across implementations so requirements remain comparable, traceable, and reusable.

### System Reconciliation & Technical Analysis

- Analyze application logic, SQL, stored procedures, configuration parameters, integrations, and data flows to understand existing system behavior.
- Determine whether business requirements can be satisfied through configuration, existing functionality, process changes, or new development.
- Validate assumptions about platform behavior against available technical evidence and distinguish confirmed system behavior from inferred behavior.
- 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 where behaviors are configurable versus hardcoded and assess the impact on future implementations.

### Requirements Authoring

- Write clear business and functional requirements, user stories, acceptance criteria, assumptions, dependencies, open questions, and proposed workarounds.
- Maintain appropriate separation between business-facing requirements and technical implementation details.
- Ensure acceptance criteria reflect the agreed solution approach, including configuration changes, operational workarounds, or new functionality.
- Apply a consistent standard for distinguishing standalone requirements from assumptions, configuration decisions, implementation details, or operational procedures.
- Maintain traceability from business need through solution decision and development implementation.

### Cross-Functional Facilitation & Governance

- Facilitate requirements, solutioning, and review sessions across business, clinical, product, engineering, data, and operational teams.
- Drive open questions toward resolution and update requirements and 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 clearly communicating business impact, implementation complexity, dependencies, and risk.

### Ticket Creation & Scoping

- Translate approved requirements into development-ready tickets containing 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.

### Requirements

- 8+ years of experience as a Business Analyst, Technical Product Manager, Product Owner, or equivalent role in a software-, data-, or technology-driven environment.
- Experience working within 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 well enough to validate platform behavior and collaborate effectively 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 with 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.

### Preferred Qualifications

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

### Key Competencies

- Requirements elicitation and translation
- Healthcare workflow analysis
- Technical and data analysis
- System behavior reconciliation
- Product and backlog management
- Stakeholder facilitation and decision-driving
- Cross-functional collaboration
- Analytical rigor and structured problem-solving
- Dependency and impact analysis
- Documentation discipline and traceability

Originally posted on Himalayas

**Source:** this listing was published by [Himalayas](https://himalayas.app/). [View the original posting and apply](https://himalayas.app/companies/proarch/jobs/ba-technical-product-manager?utm_source=api) — applications are handled there, not on this site.

To apply for this job please visit [himalayas.app](https://himalayas.app/companies/proarch/jobs/ba-technical-product-manager?utm_source=api).

## More posts

- ### [Holiday Party Networking: How to Job Hunt Without Making It Awkward](https://alljobboard.com/holiday-party-networking-job-search/)

[November 13, 2026](https://alljobboard.com/holiday-party-networking-job-search/)
- ### [How to Negotiate a Start Date After the Holidays (With Scripts)](https://alljobboard.com/negotiate-start-date-after-holidays/)

[November 13, 2026](https://alljobboard.com/negotiate-start-date-after-holidays/)
- ### [Should You Quit Before or After Your Year-End Bonus?](https://alljobboard.com/quit-before-or-after-year-end-bonus/)

[November 13, 2026](https://alljobboard.com/quit-before-or-after-year-end-bonus/)
- ### [How to List a Seasonal Job on Your Resume (With Examples)](https://alljobboard.com/seasonal-job-on-resume/)

[November 13, 2026](https://alljobboard.com/seasonal-job-on-resume/)

```json
{
    "@context": "http://schema.org/",
    "@type": "JobPosting",
    "datePosted": "2026-11-10T00:19:30+00:00",
    "validThrough": "2027-01-08T23:59:59+00:00",
    "title": "BA/Technical Product Manager at ProArch",
    "description": "<h3>Partner Discovery &amp; Requirements Analysis</h3>\n<ul>\n<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>\n<li>Translate manual and system-supported workflows into structured business and functional requirements.</li>\n<li>Produce gap-analysis documentation mapping current-state processes and partner requirements to existing platform capabilities.</li>\n<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>\n<li>Maintain a consistent backlog structure across implementations so requirements remain comparable, traceable, and reusable.</li>\n</ul>\n<h3>System Reconciliation &amp; Technical Analysis</h3>\n<ul>\n<li>Analyze application logic, SQL, stored procedures, configuration parameters, integrations, and data flows to understand existing system behavior.</li>\n<li>Determine whether business requirements can be satisfied through configuration, existing functionality, process changes, or new development.</li>\n<li>Validate assumptions about platform behavior against available technical evidence and distinguish confirmed system behavior from inferred behavior.</li>\n<li>Identify discrepancies between documented behavior, stakeholder expectations, system configuration, and implemented logic.</li>\n<li>Trace business rules to underlying parameters, data elements, calculations, integrations, and system components.</li>\n<li>Identify where behaviors are configurable versus hardcoded and assess the impact on future implementations.</li>\n</ul>\n<h3>Requirements Authoring</h3>\n<ul>\n<li>Write clear business and functional requirements, user stories, acceptance criteria, assumptions, dependencies, open questions, and proposed workarounds.</li>\n<li>Maintain appropriate separation between business-facing requirements and technical implementation details.</li>\n<li>Ensure acceptance criteria reflect the agreed solution approach, including configuration changes, operational workarounds, or new functionality.</li>\n<li>Apply a consistent standard for distinguishing standalone requirements from assumptions, configuration decisions, implementation details, or operational procedures.</li>\n<li>Maintain traceability from business need through solution decision and development implementation.</li>\n</ul>\n<h3>Cross-Functional Facilitation &amp; Governance</h3>\n<ul>\n<li>Facilitate requirements, solutioning, and review sessions across business, clinical, product, engineering, data, and operational teams.</li>\n<li>Drive open questions toward resolution and update requirements and documentation to reflect confirmed decisions.</li>\n<li>Identify ambiguity, conflicting requirements, downstream impacts, and cross-feature dependencies before development begins.</li>\n<li>Prevent scope drift and ensure implementation-specific requirements do not unintentionally become platform-wide requirements.</li>\n<li>Support prioritization and decision-making by clearly communicating business impact, implementation complexity, dependencies, and risk.</li>\n</ul>\n<h3>Ticket Creation &amp; Scoping</h3>\n<ul>\n<li>Translate approved requirements into development-ready tickets containing problem statements, user stories, functional scope, acceptance criteria, dependencies, assumptions, and open questions.</li>\n<li>Partner with engineering and architecture teams to clarify technical scope and implementation approach.</li>\n<li>Track dependencies across features, integrations, implementations, and shared platform capabilities.</li>\n<li>Identify common capabilities that can support multiple clients, workflows, or future implementations rather than creating one-off solutions.</li>\n</ul>\n<h3>Requirements</h3>\n<ul>\n<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>\n<li>Experience working within healthcare technology, healthcare operations, payer/provider systems, pharmacy, claims, revenue cycle, eligibility, or related healthcare domains.</li>\n<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>\n<li>Demonstrated ability to write clear requirements, user stories, acceptance criteria, and development tickets that engineering teams can implement with minimal rework.</li>\n<li>Strong analytical rigor with the ability to distinguish confirmed facts from assumptions, challenge unclear reasoning, and validate conclusions.</li>\n<li>Experience facilitating requirements and solution-review sessions involving business, clinical, operational, and technical stakeholders.</li>\n<li>Strong written and verbal communication skills, with the ability to adapt business and technical information for different audiences.</li>\n</ul>\n<h3>Preferred Qualifications</h3>\n<ul>\n<li>Familiarity with healthcare claims, eligibility, reimbursement, clinical workflows, pharmacy operations, or healthcare financial processes.</li>\n<li>Experience working with configurable or rules-driven healthcare platforms.</li>\n<li>Experience supporting client, provider, health system, or partner implementations.</li>\n<li>Understanding of data pipelines, ETL processes, APIs, healthcare integrations, and data exchange concepts.</li>\n<li>Experience managing a shared product backlog across multiple customers, implementations, or business units.</li>\n<li>Familiarity with healthcare data standards, regulatory requirements, or privacy considerations such as HIPAA.</li>\n</ul>\n<h3>Key Competencies</h3>\n<ul>\n<li>Requirements elicitation and translation</li>\n<li>Healthcare workflow analysis</li>\n<li>Technical and data analysis</li>\n<li>System behavior reconciliation</li>\n<li>Product and backlog management</li>\n<li>Stakeholder facilitation and decision-driving</li>\n<li>Cross-functional collaboration</li>\n<li>Analytical rigor and structured problem-solving</li>\n<li>Dependency and impact analysis</li>\n<li>Documentation discipline and traceability</li>\n</ul>\n<p>Originally posted on Himalayas </p>\n<p class=\"job-source\"><strong>Source:</strong> this listing was published by <a href=\"https://himalayas.app/\" rel=\"dofollow\">Himalayas</a>. <a href=\"https://himalayas.app/companies/proarch/jobs/ba-technical-product-manager?utm_source=api\" rel=\"dofollow\">View the original posting and apply</a> &mdash; applications are handled there, not on this site.</p>\n",
    "hiringOrganization": {
        "@type": "Organization",
        "name": "ProArch"
    },
    "identifier": {
        "@type": "PropertyValue",
        "name": "ProArch",
        "value": "https://alljobboard.com/job/ba-technical-product-manager-at-proarch/"
    },
    "jobLocation": {
        "@type": "Place",
        "address": "United States"
    },
    "jobLocationType": "TELECOMMUTE",
    "directApply": true
}
```