Technical Product Manager

We are looking for a Technical Product Manager to join our growing engineering organization (headquartered in Reigate, ~300 engineers) developing a wide range of market leading InsurTech solutions. You will join us at an exciting time as we focus increasingly on cloud/SaaS solutions, upgrading existing products to new technologies and modern UX, as well as developing brand-new applications.

As a Technical Product Manager, you will be involved in the definition and development of work items within a specific Product Stack, working with senior stakeholders such as other Product Managers, Engineering Managers and Architects, to define and prioritise a backlog of user stories to be implemented by one or two scrum teams.

The Role:

•Work with the wider Product Management team to understand the relevant market/competitors/end-users, and influence the definition of the product vision and feature-level roadmap,

•Collaborate with stakeholders (including internal subject matter experts, internal end-users) and members of the scrum team(s) to translate this roadmap into a user-story backlog which can be consumed and implemented by one or two engineering teams,

•Ensure the backlog is in a “clean” state at all times, maintaining a clear epic/feature/story hierarchy, triaging new requirements/defects efficiently, and appropriately tagging backlog items which qualify for capitalisation and R&D tax relief,

•Articulate this backlog into quarterly release increments, working with the team to ensure the upcoming quarterly increment is appropriately defined and planned, covering the various necessary dimensions involved in the development of the product under consideration (. functional and non-function product requirements, but also research work, as well as infrastructure and service-related requirements),

•Continuously re-prioritise the user-story backlog considering the direction from the Product Manager, feedback from the team, the value of the work item (effort vs. benefit) and potential dependencies between stories,

•Ensure there is at least 1-2 sprints worth of user stories defined against the agreed “Definition of Ready” (DoR), in particular by working with the QA engineer(s) to define clear and complete acceptance criteria,

•If necessary, produce the necessary artefacts to meet the DoR (. wireframes/UI mockups),

•Provide input to the sprint planning process, ensuring the scrum team is sufficiently familiar with the proposed stories upfront to facilitate a smooth planning process,

•Lead and support the scrum team during execution of the sprint and the release increments by providing clarification or further direction where necessary, and taking an active role in mitigating impediments,

•Formally accept/reject user stories implemented by the team once they meet the “definition of done”,

•Contribute to the production of internal or external product documentation,

•Keep abreast with Agile/Scrum best practices and new trends, and as appropriate, participate in sprint planning meetings, daily stand-ups, sprint retrospectives, and other scrum of scrum ceremonies, striving to continuously improve the team velocity, its processes and engineering practices.