Lead Business Systems Analyst

Requirements ownership (approx. 80%)

• Own requirements end to end for Module 3 enablement — elicitation, documentation, prioritisation, traceability from business objective through to delivered capability and acceptance.
• Act as the translator between HEOR business stakeholders and the AI&D and platform engineering teams: convert domain and workflow need into requirements the engineers can build against, and convert technical constraints back into decisions the business can actually make.
• Plan and lead requirements definition working sessions and workshops, bringing the Lead AI Engineer in where feasibility needs to be assessed live rather than discovered later.
• Work with business SMEs to surface nuanced requirements that differ across sections and content types, and document them at a level of precision an engineer can act on without a follow-up conversation.
• Define acceptance criteria for AI-generated content — factual grounding, source traceability, completeness against the section template, tone and terminology consistency — in terms the business owns and the engineers can test against.
• Build on the substantial documentation already produced through the POC work rather than restarting discovery. Establish quickly what is complete, what remains, and what is at risk.
• Refine requirements iteratively across the execution period as SME review cycles reveal what the platform can and cannot yet do, without losing the thread of what was originally agreed.

Delivery coordination (approx. 20%)

• Hold the pod’s delivery cadence: backlog, sprint rhythm, stand-ups and review cycles, run in the client’s tooling.
• Sequence work realistically against actual capacity and state clearly what can and cannot be delivered within the pilot window.
• Own weekly progress and status reporting to Amgen — at a level of candour that surfaces problems while they are still cheap to fix.
• Identify, log and escalate blockers, risks and dependencies early, particularly those sitting with the core APEX build team, with source-content availability, or with SME review capacity.
• Maintain the risk, issue, decision and assumption log for the engagement.

Stakeholder leadership

• Hold the day-to-day relationship with HEOR subject-matter experts and the wider business group, and be the single point they come to for scope and progress.
• Coordinate across the three organisations involved — HEOR, AI&D and the platform team — without formal authority over any of them.
• Push back on requirements, scope additions and timeline expectations where the evidence warrants, with reasoning rather than resistance.
• Protect the engineers’ focus: absorb coordination load, filter noise, and ensure they receive requirements that are decided rather than still being argued.
• Document and hand over requirements, decisions and open items in a form the Amgen team can own after the pilot.

Required qualifications

• Experience.10+ years in business analysis, business systems analysis or a comparable requirements-owning role, including a minimum of 3 years on AI, GenAI, machine learning or intelligent-automation programmes.
• AI lifecycle fluency.Demonstrable experience across the full AI delivery lifecycle — not a single pilot. Practical understanding of hallucination, non-determinism, human-in-the-loop requirements and output variability, and how each changes the way requirements must be written.
• Hands-on GenAI literacy.Working familiarity with GPT/Claude-class tooling — enough to understand how prompting, templatisation and output structuring work, and to hold a credible conversation with engineers about what is and is not achievable.
• Requirements craft.Strong elicitation technique, functional and non-functional specification, acceptance criteria, and traceability discipline across multiple interconnected workstreams.
• Workshop leadership.Proven ability to plan and lead requirements workshops with senior, non-technical business stakeholders and drive them to decisions rather than discussion.
• Delivery discipline.Experience running an agile delivery cadence — backlog, sprints, status reporting, risk and dependency management — for a small team.
• Influence without authority.A track record of holding multiple organisations to commitments from outside all of them, evidenced by unblocking programmes rather than documenting them.
• Autonomy.Demonstrated ability to own a workstream and set its working practices without close supervision, in a client-facing setting.
• Tooling.Proficiency with Jira; familiarity with Smartsheet and SharePoint.
• Communication.Excellent written and verbal English, at the standard required to write for and present to senior commercial stakeholders in the US and Europe, and to disagree constructively.

Preferred qualifications

• Prior delivery within a life sciences, pharmaceutical or biotech commercial organisation — market access, HEOR, medical affairs or commercial analytics. Useful context, but not a screening filter.
• Experience with AI-assisted document authoring, content generation, knowledge management or large-scale content transformation.
• Exposure to retrieval-augmented generation and the requirement implications of grounding and source attribution.
• Familiarity with regulated or GxP-adjacent documentation environments and their traceability expectations.
• Experience in a self-directed vendor pod operating alongside, but independently of, a client’s internal build team.
• Formal certification in business analysis (CBAP/CCBA), agile delivery (CSPO, PSM) or project management (PMP).