Who we are

ParkourSC is a Silicon Valley-based company building a vertical AI platform for life sciences supply chains. Pharma, biologics, and CDMO teams use us to prevent exceptions that put temperature-sensitive, regulated products at risk, and to resolve the ones that remain before they become a crisis. When a cold-chain excursion happens, our platform takes it from stability calculation through disposition and regulatory documentation, within defined guardrails and without manual intervention, and it fits how each customer's network runs. Our customers include top-10 pharmaceutical companies, so the problems we take on are dense: regulatory, operational, and technical at the same time.

About the role

We are looking for a Product Manager / Business Analyst to sit between those customers and our development team. You will take business problems and turn them into technical requirements, epics and stories that engineers can build from without a second round of interpretation.

This is a hands-on requirements and backlog role, not a people-management role. You will own the clarity of what gets built.

What you will do

Requirements and analysis

Elicit business requirements directly from customers, internal SMEs (quality, manufacturing, supply chain) and support/escalation channels.
Translate them into unambiguous technical requirements: functional behaviour, data model implications, edge cases, non-functional expectations, and explicit out-of-scope statements.
Model current-state and target-state processes (BPMN-style flows, state diagrams, data mappings) so that everyone is arguing about the same picture.
Challenge requirements that are workarounds for a deeper process problem and say so.

Backlog ownership

Write and maintain Jira epics, features and user stories with testable acceptance criteria — Given/When/Then or equivalent, covering negative and boundary cases, not just the happy path.
Groom and prioritise the backlog with engineering and QA; run refinement sessions and keep stories ready ahead of sprint commitment.
Sequence work into coherent feature sets and keep a forward view of what the next two to three increments contain and what they depend on.
Be the day-to-day answer to what did you mean by this for developers and testers and sign off that what was built is what was specified.

Validation and GxP documentation support

Contribute to computerised-system validation artefacts: user requirement specifications, functional specifications, requirement-to-test traceability.
Maintain traceability between customer requirement, story, acceptance criteria and test evidence so that an audit trail exists by construction rather than by archaeology.
Work within change-control and documentation practices appropriate to a regulated product.

Customer-facing discovery

Join customer workshops, discovery calls and demos; run requirement walkthroughs and playback sessions.
Document and circulate decisions, open questions and assumptions — and chase the open questions closed.

What we are looking for

Required

7–10 years in product ownership, business analysis or a closely related requirements role, with a substantial portion in enterprise or B2B software delivery.
Demonstrable experience in pharmaceutical, biotech, medical device or another regulated life-sciences setting — you understand why GxP, data integrity and audit trails change how software must be specified.
Working knowledge of pharmaceutical manufacturing concepts: batch and lot handling, bill of materials, production orders, deviations and quality events, release processes.
Proven ability to write technical requirements and Jira artefacts that a development team can build from with minimal clarification.
Fluency with Agile delivery (Scrum or Kanban) and the tooling around it — Jira and Confluence as a minimum.
Strong written English. Much of this role is writing precisely for an audience that will act on what you wrote.
Ability to work independently: you take a vague problem, structure it, decide what needs deciding, and escalate the rest with a recommendation rather than an open question.
Comfortable managing several parallel workstreams and shifting priorities without dropping threads.
Overlap of at least four hours daily with Central European (CET/CEST) working hours.

Advantageous — we will teach the rest

Cold chain and temperature-controlled logistics: excursion handling, mean kinetic temperature, stability budgets, time-out-of-refrigeration, lane qualification, packaging and shipper qualification.
Familiarity with GDP, Annex 1/Annex 11, 21 CFR Part 11, or GAMP 5.
Exposure to ERP/MES/WMS or other related systems (SAP, Oracle, Track & Trace platforms) and to how they exchange master and transactional data.
Reading-level comfort with APIs, JSON, SQL and data integration patterns — enough to specify an interface, not to implement it.
Experience supporting a computerised system through validation or a customer audit.
Prior work with distributed or offshore engineering teams.

How we will know you can learn quickly

Our domain is deep and no candidate arrives knowing all of it. What we look for is evidence that you have entered an unfamiliar technical domain before, become credible in it within a few months, and can point to what you did to get there.

How we work

Small, senior product and engineering team; low process overhead, high documentation standards.
Requirements are written down and reviewed. Verbal-only decisions do not survive here.
You will get context, access to SMEs and customer exposure — and then you will be expected to run with it.

What we offer

Salary: Competitive, commensurate with experience (discussed openly during the interview process)
Statutory benefits as per country labour law
Remote-first working with [equipment / co-working allowance]
Direct exposure to pharmaceutical customers and to the regulatory reality of the products we build

How to apply

Send your CV along with a short note covering a product or feature area you owned end to end, and how you specified it.