The Product Delivery Manager will support the Head of Product by translating product strategy and high-level feature definition into shipped, high‑quality features. The PDM will own day‑to‑day coordination between Product and Engineering: analysing upcoming work, planning sprints and capacity, overseeing testing and acceptance, and ensuring clear communication in both directions.
Key responsibilities include:
Discovery & requirements
- Own the definition of product requirements that clarify scope, risks, and dependencies.
- Translate product ideas into clear, actionable tickets with acceptance criteria.
Planning & coordination
- Lead sprint planning and resource planning with engineering leads.
- Maintain a clear picture of roadmap, sprint status, and blockers for stakeholders.
Delivery, QA & acceptance
- Coordinate regression testing (manual and/or automated) for new releases.
- Be accountable for completion of work against requirements and acceptance criteria; formally accept or reject features on behalf of Product.
- Own defects from discovery through resolution and feed learnings back into planning.
Team communication
- Be the primary communication bridge between Head of Product and engineering teams.
- Ensure engineers get timely decisions and context; ensure Product gets accurate, concise delivery updates.
Proactive roadmap support
- Spot upcoming dependencies, risks, and capacity constraints early; propose options and phasing.
- Lead on modernisation and technical work alongside feature delivery to keep the platform healthy.
Showcase & stakeholder updates
- Organise demos/reviews of finished features and present outcomes back to the Head of Product and stakeholders.
- Own documentation of what was delivered each cycle and what is next.
Experience & Skills Required
- 3–5+ years in a delivery‑focused role (Delivery Manager, Technical Project Manager, Agile Project Manager, or similar) in a software product environment.
- Strong understanding of Agile product development (frontend, backend, QA) and how changes move from idea → code → release.
- Hands‑on experience with sprint planning, backlog refinement, and release coordination using tools like ClickUp/Jira/Asana.
- Comfortable shaping requirements, defining acceptance criteria, and working with MVP and iterative delivery.
- Excellent attention to detail.
- Excellent written and verbal communication; confident presenting to product and engineering leadership.
- Demonstrable experience of collaborating with engineering teams and simultaneously working with business stakeholders.
Weekly Commitment:
- 15-20 hours a week.