Technical Product Manager - Xenoss

The delivery owner for an eight-person team building a video media planning platform inside a fixed three-month window against a hard go-live date. The role owns requirements, the backlog, sprint cadence, acceptance criteria, and user acceptance testing. It is the single day-to-day point of contact for the client.

The role also carries the commercial edge of delivery. Scope was agreed feature by feature against a prioritised inventory, and the committed set is what the date and the price were built on. Several inputs the build depends on are client-owned and arrive during the build rather than before it. Holding the agreed scope, resolving ambiguity in client-authored requirements before it reaches development, and chasing client dependencies to a date are the parts of the job that determine whether the platform ships on time.

AdTech background is required at a strong general level. Technical depth is required to the point of being useful without the architect in the room: following an engineering discussion, reading an API contract, and judging whether a requirement is testable. Writing code is not part of the role.

Key Responsibilities

Delivery (primary)

• Own the backlog and sprint cadence — planning, prioritisation, ceremonies, and the flow of work through an eight-person team.
• Maintain a single source of truth for scope, traceable from the client’s prioritised feature inventory through to delivered functionality.
• Track delivery against the three monthly milestones, including their exit criteria, and report progress to the client and internally.
• Surface risk, slippage and dependency exposure early, with the options for handling it rather than the problem alone.

Scope and requirements

• Translate client requirements into buildable, testable work items with acceptance criteria the team and the client both recognise.
• Resolve ambiguity and contradiction in client documentation before it reaches development, rather than allowing an assumption to be built.
• Run change control. Anything outside the committed set is either explicitly re-scoped and re-costed or recorded on the roadmap. Nothing enters the build informally.
• Protect the committed scope under date pressure, and make the trade-off visible when scope, date and quality come into conflict.

Client interface and dependency management

• Act as the single day-to-day point of contact for the client throughout the build.
• Maintain the dependency register — each client-owned input with a named owner and a date, chased until it lands.
• Prepare and run client sessions, including methodology and requirements workshops with the client’s own specialists.
• Report status honestly, including bad news, at the point it is known rather than at the point it becomes unavoidable.

Acceptance and release