Job Description

Overview:

: Product Owner - SNOW4Business Product Inventory Onboarding
Location: Onsite (UK/RO rotation as required)

Function: Group Digital & IT - SN4B / CSM Platforms

Product Domain: Customer Onboarding, Product Inventory (TMF-637/632), G-DxL Integration, ServiceNow CSM (EVE / SN4B), Portal Journeys (COVE), Assurance & SLA Enablement

Seniority: Senior Product Owner (Complex Market Enablement)
Responsibilities:

Role Purpose

The Product Owner (PO) will own the end-to-end Product Inventory Onboarding capability within Vodafone's SNOW4Business programme, beginning with Romania and scaling to all markets.
This role is accountable for translating the CSI-52126 feature set, TMF integration specifications, product-lifecycle rules, and portal behaviour into a clear, governed, technically rigorous product roadmap that aligns Group standards, local market needs, and ServiceNow platform constraints.
The PO ensures that onboarding journeys across TMF-632 (Customer), TMF-637 (Product Inventory), G-DxL orchestration, EVE/SNOW product models, lifecycle state transitions, SLAs, add-on modelling, entitlement flows, and COVE portal behaviour work seamlessly and predictably at scale.

Key Responsibilities

2.1 Product Ownership & Roadmap GovernanceOwn the SN4B Product Inventory Onboarding roadmap for Romania and future markets. Maintain a high-granularity backlog aligned to: + TMF-637 Create & GET operations + TMF-632 pre-requisites (customer account skeleton creation)
+ DXL canonical event patterns
+ SNOW async orchestration and queue sequencing
+ Portal capability uplift (COVE / Liferay / new portal direction)
Prioritise features based on: + Market readiness + Data model maturity
+ Integration dependencies
+ State-transition risk
+ Security & SPDA gates
+ Regression impact on existing SN4B/EVE customers


2.2 Requirements Refinement & Technical AlignmentConvert high-level requirements into precise, testable user stories that reflect: + Unique identifier rules (Product Instance ID, Customer ID + Taxonomy ID) + SLA indicator instantiation (Premium vs Standard blueprint)
+ Assurance Partner ID logic and vendor mapping
+ Suspended/Inactive business rules and ticket behaviour
+ Add-on product modelling (child BS/TS creation & relationship mapping)
+ Entitlement propagation rules for users and products
Manage the interplay between: + Business Service creation + Technical Service instantiation
+ CMDB relationships
+ Portal visibility rules
+ AGF routing logic


2.3 Backlog Ownership for Complex IntegrationsOwn all product stories that depend on: + G-DxL create/update orchestration + GET Product Instance operation behaviour
+ API enhancements to COVE (getBusinessService, capabilities sync, search via Primary Resource ID)
+ SNOW async processing queues and error-handling design
Ensure design consistency across multiple specifications and existing frameworks: + EVE model (BS, TS, CI) + SN4B deviations
+ Legacy entitlement tables vs new capability model
+ Market-specific onboarding vs Group-driven onboarding


2.4 Market Stakeholder Management (Romania + Future Markets)Act as the authoritative Group PO to Romania's VBU Ordering & Portal teams for: + Payload structure definitions + Validation rules
+ Error-handling processes
+ Add-on product interpretation
+ Portal limitations and enablement constraints
Drive clarity on open items:
Portal future-state direction (Liferay+ COVE2.0 / OPF) + New product model migration timeline
+ User entitlement propagation model per market
+ RBAC / capability definitions


2.5 Product Lifecycle GovernanceOwn the governance of Product Instance lifecycle: + Active + Suspended
+ Inactive
Ensure technical validation logic for allowed and disallowed transitions is correctly implemented and tested. Align ticket behaviour, SLA clock rules, and COVE controls to lifecycle semantics.

2.6 Data Model & Architecture AlignmentEnsure Product Instance attributes are clearly mapped and consumed end-to-end: + Primary Resource ID + Assurance Partner ID
+ Start/End dates
+ SLA indicator
+ Key-value pairs
Work with Group architecture to ensure: + CMDB CI model changes are approved + Relationship types (Main vs Add-On) are correctly modelled
+ Backward compatibility for non-RO products is preserved
+ No regression on DigiCom (CSI-3086) or SN4B features


2.7 Testing Strategy & Production ReadinessProvide clear PO-level guidance to testing teams covering: + Negative tests for lifecycle violations + Duplicate BS prevention
+ Add-on onboarding restrictions
+ SLA indicator validation
+ Entitlement propagation logic
+ Isolation of RO onboarding from Group Create/Update customer journeys
Validate SPDA, ADRB, and Tech Security controls before release.

2.8 Governance & ComplianceEnsure the product meets all Vodafone Group governance requirements: + SPDA (Security & Privacy by Design) + Group & UK Tech Security
+ Architectural Review Boards
+ TMF compliance
+ Data retention & access control NFRs
Own the documentation set (HLD, LLD, solution intent updates, RAID, decision logs).

Requirements:
Required Skills and Experience

3.1 Technical Expertise
The PO must demonstrate deep understanding of:ServiceNow CSM, including: + Business Services + Technical Services
+ CMDB modelling
+ Entitlement frameworks
+ SLA/Contract behaviours
+ Scripted REST APIs
TMF APIs, specifically: + TMF-632 (Customer) + TMF-637 (Product Inventory)
+ TMF-638 (Service Inventory - future scope)
G-DxL canonical integration layer, async message handling, and queue sequencing. Portal ecosystems: + COVE + Legacy Liferay portals
+ New portal direction (OPF / COVE2.0)
Product lifecycle management and its impact on: + Ticket behaviour + SLA clocks
+ Portal permissions
+ AGF routing


3.2 Product LeadershipProven experience delivering multi-market enablement products. Ability to define and lead incremental releases across multiple impacted platforms. Strong competency in driving consensus across Group, RO, COVE, DXL and DevOps.

3.3 Analytical & Decision-Making CapabilityAbility to interpret complex payloads, data models, state machines, and architecture diagrams. Ability to challenge markets on data quality, product modelling, and compliance.

3.4 Communication & Stakeholder EngagementTranslate highly technical design decisions into stakeholder-ready communications. Facilitate design authority sessions across Group, Market, DXL, ServiceNow, Security, and Portal teams.


Key Deliverables Product roadmap for SN4B Product Inventory Onboarding L3/L4 functional specifications and acceptance criteria Updated solution intent, RAID, decision logs Market onboarding artefacts (Romania + future markets) SPDA documentation & sign-off Backlog refinement packs (for SNOW, DXL, Portal teams) Test-readiness and regression governance documentation Post-MVP rollout plan including scaling strategy


Success Measures Zero-defect integration for TMF-637 create/update and GET operations Full alignment across Group DX, DXL, SNOW, and Portal stakeholders Accurate lifecycle behaviour enforced across all product instances Add-on modelling working end-to-end (BS, TS, relationships, portal visibility) No regression to DigiCom or existing SN4B customer journeys Successful market cutover for Romania with fully automated onboarding * Reduced manual onboarding effort and improved incident/service request routing accuracy