Location: UK only (right to work required; no sponsorship) | Remote-first, 2–3 days/month in person + periodic travel to customer sites in Europe (France, Poland, Italy, the Nordics)

Existing Clients: Top 100 Lifesciences, MedTech and Pharma companies

Type: Contract (6 months initial, extension expected) with option to convert to permanent — we'd rather convert than re-recruit | 5 days/week preferred, 4 considered for an exceptional candidate

Company Description:

Vamstar is a UK-based, venture-backed AI company serving Pharma and MedTech enterprises. Our platform, Polaris, is an agentic AI system for commercial teams: it discovers tenders across 100+ countries, matches them to a customer's product catalogue, assesses go/no-go, assembles bid responses, tracks awards and contracts, and surfaces pricing and market intelligence. Six modules, one data model, deployed as managed SaaS on AWS with in-region AI inference. We run Polaris as large enterprise programmes across EMEA — from two-country pilots to multi-market rollouts — alongside a deployed engineering practice that works inside customer organisations.

Core responsibilities & objectives

• Own the requirements practice, not just the requirements. Set the standards for discovery, user stories, acceptance criteria, and Definition of Ready across all Polaris enterprise programmes — and enforce them, including sending back work raised by people more senior than you.
• Lead and grow the BA function. Mentor business analysts on the programmes, review their output, and build the reusable assets — discovery templates, story patterns, acceptance script templates, a requirements playbook — that let the practice scale. This role carries responsibility for the quality of every analyst's work, not just your own.
• Own the "what and whether it's right" on the most complex programmes. The Delivery Manager owns the when. You own requirement validation end-to-end: running discovery with customer tender, pricing, sales and commercial teams; testing every requirement against the mapped process, platform capability, and what the work order committed to; and saying so, in writing, early where they diverge.
• Separate what the customer asked for from what the customer needs. Propose the Polaris behaviour that meets the need, get the customer to sign the requirement — not the wish — and protect scope. Requests outside the work order are flagged as changes, with sized impact, before anyone agrees to them. Zero silently absorbed.
• Master the product to the depth of its behaviour. How discovery sources are enabled per market, how matching is tuned and what its confidence means, how assessment criteria are configured, how exports and integrations are shaped. You — and the analysts you lead — must be able to tell a customer what Polaris will and will not do before an engineer is involved.
• Own acceptance quality. UAT scripts and pass/fail definitions written before the build starts; the verdict on whether a delivered feature meets the criteria sits with your function.
• Make value measurable. Every programme's pilot KPIs defined with an agreed baseline and measurement method, with the configuration and data work in the backlog from week one — so the final pilot report is written from data, not anecdote.
• Feed the product. Turn what programmes learn into structured feedback: what is customer-specific, what should become platform, what keeps coming up.