Technical Programme Management:

•       Proven experience as a TechnicalProgramme Manager, Senior Scrum Master, or Delivery Lead in a software productor technology company — ideally in an early-stage or high-growth startupenvironment.

•       Strong track record of managing deliveryacross multiple concurrent technical workstreams simultaneously, includingengineering, infrastructure, and data/ML workstreams.

•       Deep fluency in agile deliverymethodologies — Scrum, Kanban, or hybrid approaches — with strong opinionsabout what works and what doesn't in a fast-paced environment.

•       Experience owning and enforcingDefinition of Ready, Definition of Done, sprint planning, retrospectives, andbacklog grooming at an organisational level.

•       Demonstrable experience managingtechnical debt as a first-class delivery concern, not an afterthought.

‍

Technical Understanding:

•       Strong enough technical understanding offull stack engineering (frontend, backend APIs, cloud infrastructure) to manageestimates, challenge scope, and understand blockers without needingline-by-line explanation.

•       Familiarity with DevOps andinfrastructure concepts — CI/CD pipelines, IaC, containerisation, cloudenvironments — sufficient to understand the work being done and the risksinvolved.

•       Working knowledge of MLOps and AI/MLmodel development lifecycles — understanding how models move from research andprototyping through to production deployment, and what the handoff processinvolves.

•       Familiarity with LLM/GPT productdevelopment — understanding the nature of building AI-powered features, agenticworkflows, and generative product experiences, including the unique deliverychallenges they present (probabilistic outputs, evaluation complexity,governance requirements).

•       Comfort engaging with technicalconversations at a conceptual level — not needing to write code, but needing tounderstand what engineers and scientists mean when they describe their work.

‍

Delivery Tools & Practices:

•       Strong experience with project anddelivery management tooling — Notion experience is a preference; the idealcandidate has used it and is comfortable building and maintaining deliveryworkflows within it.

•       Experience with engineering workflowtools such as GitHub, Linear, Jira, or equivalent — understanding howdevelopment tickets, PRs, and code review processes are managed.

•       Ability to design clear, practicaldelivery processes that a technical team will actually follow — notover-engineered bureaucracy, but the right amount of structure for ahigh-performing startup team.

‍

Communication & Leadership:

•       Exceptional communication skills — ableto run a tight, effective stand-up, write a clear delivery update, and have adifficult conversation about a slipping deadline with equal confidence.

•       Strong relationship-building skills —able to earn the trust and respect of highly technical team members without atechnical background of their own.

•       Calm under pressure — able to re-plan,reprioritise, and re-communicate clearly when things don't go to plan, which ina startup is often.

•       A proactive, ownership mindset — notwaiting to be asked, but continuously looking ahead for what might go wrong andacting on it before it does.

‍

‍

Responsibilities:

Delivery Management & SprintExecution:

•       Own and run the daily stand-up across ourproduct team — keeping them tight, purposeful, and focused on blockers andprogress rather than status theatre.

•       Lead sprint planning sessions: workingwith the SMEs to define, size, and sequence work into well-structured,achievable sprints.

•       Maintain and manage the backlog acrossall workstreams — ensuring cards are well-defined, correctly prioritised, andalways ready to be picked up.

•       Track sprint velocity, identify deliveryrisks early, and proactively escalate or re-plan when commitments are at risk.

•       Own the sprint retrospective process —driving continuous improvement in how the team works, not just what they build.

•       Produce clear, concise sprint reportsand delivery updates for the leadership team.

‍

Definition of Ready, Definition of Done& Engineering Best Practice:

•       Own and enforce the Definition of Ready— ensuring every card entering a sprint is properly scoped, estimated, hasclear acceptance criteria, and has all dependencies identified before workbegins.

•       Own and enforce the Definition of Done —ensuring code review, testing, documentation, sign-off, and deployment criteriaare consistently met before any work is marked complete.

•       Champion best practice in sprinthygiene: well-written cards, sensible timing estimations, appropriate taskbreakdown, and clear ownership.

•       Monitor and drive adherence to codereview processes — ensuring reviews are completed in a timely manner, feedbackis constructive, and quality standards are upheld.

•       Maintain a live technical debt registerand ensure technical debt work is a standing, visible part of every sprint —never deprioritised into oblivion.

•       Ensure architectural and governancestandards are reflected in the way work is defined and delivered.

‍

Cross-Team Coordination &Dependency Management:

•       Coordinate delivery across alldisciplines identifying cross-team dependencies and ensuring they are surfacedand resolved early.

•       Manage the handoff between socialscience direction, data science model development and engineeringproductionisation — ensuring the work we do from research to production hasclear acceptance criteria, deployment plans, and sign-off processes.

•       Coordinate delivery across new productworkstreams and core platform/pipeline work — ensuring neither track blocks theother and that shared infrastructure decisions are made collaboratively.

•       Act as the primary point of contact fordelivery status across the organisation — giving the leadership team real-timevisibility into what is being built, when it will land, and what is at risk.

‍

Estimation, Roadmap Planning& Capacity Management:

•       Work closely with the SMEs to buildreliable delivery estimates for new product features, infrastructure work, andAI/ML model development.

•       Maintain a rolling view of team capacity— accounting for planned leave, context-switching costs, and the reality ofworking in a fast-paced startup environment.

•       Support the Leadership team in translatingthe product and technology roadmaps into sprint-level delivery plans withrealistic timelines.

•       Challenge and interrogate estimatesconstructively — asking the right questions to surface hidden complexity,unclear requirements, or unrealistic assumptions before they become deliveryproblems.

•       Track actuals against estimates overtime to improve planning accuracy and build a clearer model of team velocityacross different types of work.

‍

Tooling, Process &Documentation:

•       Own Hive's delivery tooling — with apreference for Notion as the primary workspace for sprint boards, backlogmanagement, documentation, and delivery tracking.

•       Establish and maintain clear, consistentprocess documentation: how sprints work, how cards are written, how work isreviewed and signed off, and how releases are managed.

•       Ensure the team is working from a singlesource of truth — that the state of every workstream is visible, up to date,and accessible to anyone who needs it.

•       Identify tooling gaps and recommendimprovements to how the team plans, tracks, and communicates work.

‍

Stakeholder Communication &Reporting:

•       Provide the leadership team withregular, clear delivery updates — translating complex multi-workstream progressinto concise, accurate summaries.

•       Flag risks, blockers, and scope changesproactively — with a proposed solution wherever possible, not just a problemstatement.

‍

‍

‍