Jobs / United States / ProArch

ProArch

BA/Technical Product Manager

Remote (USA Only) · Remote · US only Posted 11 days ago

View original listing ↗ Tailor my CV first Source: We Work Remotely

Listed on We Work Remotely: the application continues on their site, which links to the employer. Optional: we can tailor a CV and cover letter for this job from your real experience first (the first one is free).

Where you can work from

United States only

Based on the listing's location: Remote (USA Only).

The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.

Visa sponsorship, if you would relocate

Sponsorship verdict

No sponsorship evidence yet

No government record and no wording either way. Not a refusal: ask the recruiter.

  • No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
  • The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
  • No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
  • What ProArch paid sponsored hires in similar roles1 certified filing for “PROJECT MANAGER” (Software Developers) in TX: $90k–$90k, median $90k.
  • Confirmed live todayWhen a source last listed this job as open.
Details and sources
No salary bar for this route
H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
What ProArch paid sponsored hires in similar roles
1 certified filing for “PROJECT MANAGER” (Software Developers) in TX: $90k–$90k, median $90k. Most were filed at wage level I (100%) — 1 lottery entry, ≈15% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).

US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).

A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.

Before you apply

Sponsorship unknown

No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.

These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →

About the role

Headquarters: United States URL: https://jobs.workable.com/company/u8TybTAE2YbYgRVFYov9t4/jobs-at-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. • 8+ years of experience as a Business Analyst, Technic

View original listing ↗