The TPO would serve as the technical bridge between the business/product teams, architecture, external partners, and development teams. Key responsibilities would include:
Supporting the definition, analysis, and documentation of technical requirements, integration flows, APIs, dependencies, and non-functional requirements.
Coordinating technical discussions with internal teams and third-party vendors to clarify scope, ownership, assumptions, and integration responsibilities.
Supporting solution design, architecture reviews, and the overall integration strategy for Super App initiatives.
Creating and maintaining technical documentation in Confluence, including architecture diagrams, interface specifications, data mappings, sequence flows, and implementation decisions.
Managing and refining technical Jira items, including epics, stories, enablers, acceptance criteria, dependencies, risks, and delivery tracking.
Helping translate functional requirements into clear, actionable technical requirements for development teams.
Supporting testing, defect triage, production issue analysis, and coordination across teams to identify root causes and drive resolution.
Ensuring visibility and alignment across stakeholders throughout the delivery lifecycle.