Technical Product Owner
Outside IR35
Are you a dynamic and experience Technical Product Owner interesting in leading one of our product team in the realm of connected mobility? Essential experience for this role includes working with data pipelines and data points.
What is the role?
The Technical Product Owner is engaged short-term to perform a structured gap analysis for a technical project and translate findings into clear, testable requirements that engineering teams can estimate, plan, and deliver. The role ensure the target state is well-defined and the path to get there is unambiguous.
What will you do?
Requirements Pack: functional & integration & data, each testable.
Delivery-ready breakdown: epics/features/stories (or equivalent) aligned to the requirements.
Stakeholder playback notes and decisions log.
What are we looking for in you?
You are a strategic thinker with deep expertise in product management
You are a thought leader who drives innovation and change
You have excellent influencing skills across multiple senior stakeholders
You mentor others and elevate product management capabilities across teams
You are outcome-obsessed and customer-centric
What will be your Key Responsibilities in the role?
Scope and target-state definition
Align stakeholders on objectives, outcomes, constraints, and success measures.
Define in-scope systems, integrations, data sources, environments, and interfaces.
Capture assumptions, dependencies, risks, and decision owners.
Current-state assessment
Review existing artefacts (architecture, APIs, data models, tickets, release notes, incidents).
Map current workflows and system behaviours (including edge cases and failure modes).
Inventory integrations (API/event/file) and key data flows, ownership, and operational touchpoints.
Gap analysis
Identify gaps between current and target state across:
Functional behaviour
Data coverage/quality/retention/lineage
Integrations and contracts (versioning, error handling)
Operational readiness (monitoring, alerting, runbooks, support)
Assess impact, priority, dependencies, and risk for each gap.
Requirements definition
Write precise, implementation-ready requirements and acceptance criteria.
Maintain traceability from gap, requirement, planned delivery item.
Partner with engineering on feasibility trade-offs while protecting outcomes.
Backlog and handover
Translate requirements into delivery structure (epics/features/stories) ready for estimation.
Facilitate playback sessions with stakeholders and engineering to resolve ambiguity.
Support initial sizing and planning, ensuring a shared understanding of “done”.
What is important to us? What are our values?
Always thoughtful
We believe that we should treat each other as equals by respecting and cherishing our diverse backgrounds and abilities. We look out for one another’s wellbeing by remembering that our successes are determined by the sum of all our efforts.
Confidently collaborative
We are stronger together. We are dynamic, capable of forging highly effective relationships to achieve amazing results. It is what sets us apart.
Constantly adapting
Our success depends on looking to the future and always evolving. Through reflection and continuous improvement, we empower everyone to contribute to how we evolve as TCEU, as teams and as individuals.
Responsibly progressive
We trust each other to get the right things done in the right way. We take responsibility for our actions and deliver results, whether individually or as a team.
Discovering Direct IT Contract Opportunities for Contract Spy members.