Senior Manager - Product Owner.DataCo

The user wants me to format the job description as clean semantic HTML. Let me analyze the content: 1. The job description is for a Senior Product Owner role at MTN-i (MTN Group's AI-driven data & intelligence commercialization business) 2. It contains various sections: Global Influences, Industry Drivers, Organisational Mandate, Education, Experience, Competencies, Personal Attributes, Discover and Validate Customer Problems, Define Product Vision and Strategy, Own Technical Product Definition, Lead End-to-End Product Delivery, Product Commercialisation and Monetisation, Data, Analytics and Advanced Technology, AI Leadership and Technology Advisory 3. There are lists under Education, Experience, Competencies, Personal Attributes, and several duty sections 4. I need to use

for section headers,

• for list items,

  for paragraphs 5. No CSS classes, no inline styles, no divs, no br tags 6. Preserve all original content word-for-word 7. Return ONLY the HTML, no markdown fences, no explanation Let me structure this carefully: - "Global Influences" - this is context, not a job section header. But it's part of the job description. I should keep it as a paragraph or h4? The instructions say to use h4 for section headers like Responsibilities, Qualifications, etc. "Global Influences" could be considered a section header. Let me think... The examples given are Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. "Global Influences" is more of an intro/context section. I'll keep it as a paragraph since it's introductory context. Actually, looking at it again, it's a section header in the original text. But the instruction says "Category labels that aren't part of the job" should be removed. "Global Influences" is part of the job description though. Hmm, but it's more like context/background rather than a job section. Let me keep it as a paragraph since it's introductory context about the industry landscape. Actually, re-reading: "Category labels that aren't part of the job (e.g., 'Internships' as a standalone line)" - this refers to category labels that aren't actual job info. "Global Influences", "Industry Drivers", "Organisational Mandate" are all part of the job description context. I'll keep them as paragraphs. Wait, but "Education:", "Experience:", "Competencies:", "Personal Attributes", "Discover and Validate Customer Problems", "Define Product Vision and Strategy", "Own Technical Product Definition", "Lead End-to-End Product Delivery", "Product Commercialisation and Monetisation", "Data, Analytics and Advanced Technology", "AI Leadership and Technology Advisory" - these are clearly section headers. I should use h4 for these. Let me also note: "Lead with Care Can-do with Integrity Collaborate with Agility Serve with Respect Act with Inclusion" - this seems like values/culture statement. It's part of the job description. I'll keep it as a paragraph. Also "Organization Values:" and the Y'ello Family stuff - this is culture/values context. Keep as paragraph. Let me now construct the HTML: For the values line "Lead with Care Can-do with Integrity Collaborate with Agility Serve with Respect Act with Inclusion" - this is a list of values. Should I make it a ul? The instructions say use ul

• for list items. These are values, so yes, I could make them li items. But they're not really a list in the traditional sense. Hmm, they are separated by line breaks. I think making them a ul with li items makes sense since they're distinct values. Actually, let me reconsider. The instruction says "Use
  • for list items (duties, requirements, qualifications, skills)". These values are more like a list of values. I'll make them a ul with li items. Now let me go through each section: 1. Intro paragraph(s) - MTN transformation context 2. "Global Influences:" - paragraph 3. "Industry Drivers:" - paragraph 4. "Organisational Mandate:" - paragraph 5. Organization Values paragraph 6. Values list (Lead with Care, etc.) 7. Education section - h4 + ul 8. Experience section - h4 + ul 9. Competencies section - h4 + ul 10. Personal Attributes section - h4 + ul 11. Discover and Validate Customer Problems - h4 + ul 12. Define Product Vision and Strategy - h4 + ul 13. Own Technical Product Definition - h4 + ul 14. Lead End-to-End Product Delivery - h4 + ul 15. Product Commercialisation and Monetisation - h4 + ul 16. Data, Analytics and Advanced Technology - h4 + ul 17. AI Leadership and Technology Advisory - h4 + ul Note: The last item in AI Leadership section is cut off ("•  &nbs") - I should preserve what's there. Also note: "•  •    " patterns - these are bullet points with non-breaking spaces. I need to handle the formatting carefully. The original uses "•    " which is a bullet character followed by non-breaking spaces. In HTML, I can represent this as just the bullet character or use proper list markup. Since I'm using
    • , the bullet will be automatic. But I need to preserve the content word for word. The bullet character itself isn't really content - it's formatting. So I should just have the text content in
    • tags. Wait, but the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". The bullet characters are formatting, not content. So I'll remove them and just have the text in li tags. That should be fine. Let me also check: "they are expected. As telcos evolve into techcos and platform businesses, the ability to productise and monetise AI capabilities across industries such as FMCG, Retail, finance, and public services becomes a critical growth lever." - This has some weird spacing with " " - I should preserve the content but the   is a non-breaking space entity. I should probably keep it as is or convert to regular space. The instruction says preserve word for word. I'll keep   where it appears. Actually, looking more carefully at the text, there are some " " entities that represent non-breaking spaces. I should preserve them as they are part of the original content. Hmm, but actually for readability and since these are just spacing, maybe I should keep them. Let me keep them as-is. Let me also look at "nobr" - "•  &nbs" at the end - this is truncated. I'll preserve it as-is. Now, one issue: the "•    " prefix on list items. When I convert to
      • , I don't need the bullet character. But I need to make sure the text content is preserved. The text after the bullet is the actual content. Let me also handle the "•  •    " pattern - sometimes there are double bullets. Looking at the text: "•  •    4 year degree..." - this looks like a bullet followed by another bullet. I think the first "•" is the list marker and the second "•" might be a typo or artifact. I'll treat the first bullet as the list marker and the text after it as the content. Actually wait, looking more carefully: "•  •    4  year degree..." - this could be interpreted as two bullets. But in context, it's likely just a formatting artifact where the bullet character got duplicated. I'll just use the first bullet as the list marker and the text as content. Similarly for other sections: "•  •    5 – 8 years..." - same pattern. OK let me now write the HTML. I need to be careful about: - Using

        for section headers - Using

        • for lists - Using

          for paragraphs - No CSS classes, no inline styles, no divs, no br tags - Preserving all content Let me draft this: ```html

          MTN is undergoing a significant transformation to become a platform-led, data-powered, and AI-native enterprise. This journey is driven by the increasing demand for intelligent data products that are scalable, market-responsive, and rooted in strong data governance. MTN-i, as MTN Group’s A.I.-driven data & intelligence commercialization business, is tasked with accelerating value delivery from our owned and partner intelligence assets

          Global Influences:

          The global economy is undergoing rapid digital transformation, with AI and learning emerging as core differentiators for competitive advantage. Enterprises are embedding predictive intelligence into their operations, products, and customer experiences to enhance efficiency, agility, and revenue growth. Meanwhile, cloud-native analytics platforms, federated learning, and MLOps frameworks are standardising how AI is scaled across complex, multi-market organisations.
          Heightened focus on data ethics, fairness, and regulatory compliance is also shaping the design of AI systems. As governments tighten rules around data privacy, bias mitigation, and model explainability, organisations must ensure that AI is not only effective but also responsible and trustworthy.

          Industry Drivers:
          In the telecommunications sector, predictive analytics has become central to driving value from large-scale, real-time data generated by mobile networks, customer usage, and behavioral patterns. Use cases such as churn prediction, next-best-offer recommendations, network anomaly detection, and location-based targeting are no longer aspirational , they are expected. As telcos evolve into techcos and platform businesses, the ability to productise and monetise AI capabilities across industries such as FMCG, Retail, finance, and public services becomes a critical growth lever.
          Additionally, as data monetisation becomes mainstream, clients are not just asking for raw data but for intelligent insights, predictive signals, and decision-ready outputs all of which require robust data science capacity.

          Organisational Mandate:
          MTN-i is at the forefront of MTN Group’s transformation into a commercial value delivery engine that is data-powered and AI-native. The team is building a multi-OpCo data product ecosystem capable of scaling advanced analytics solutions across markets via high-value use cases.
          Within this context, the Product Owner plays a critical role in translating MTN-i’s vision into high-impact intelligence solutions while navigating a federated technology landscape, orchestrating hyper-agile delivery, and ensuring that MTN-i’s data products are competitive, compliant, and commercially viable. The Senior Product Owner will be responsible for the end-to-end creation, delivery and lifecycle management of MTN-i's data, AI and technology-enabled product portfolio.
          This is a high-impact product leadership role for an exceptional product thinker who can move seamlessly between customer problems, commercial opportunities, data, technology, AI, product architecture and execution.
          The successful candidate will take products from 0→1 and 1→n: identifying customer needs and unmet market opportunities, validating product-market fit, translating opportunities into compelling product propositions, defining technical requirements and architectures, leading cross-functional delivery, launching products into market, and continuously optimising them based on customer, commercial and operational performance.

          Organization Values: At MTN we believe that understanding our people’s needs and aspirations is key to creating experiences that delight you at work, every day. We are committed to fostering an environment where every member of our Y’ello Family is heard, understood, and empowered to live an inspired life. Our values keep us grounded and moving in the right direction. Most importantly, they keep us honest. It is not something we claim to be. It is in our DNA.
          As an organisation, we consider it our mission to create an exciting and rewarding place to work, where our people can be themselves, thrive in positivity and ignite their full potential. A workplace that boosts creativity and innovation, improves productivity, and ultimately drives meaningful results. A workplace that is built on relationships and achieving a purpose that is bigger than us. This is what we want you to experience with us!
          Our commitments go beyond an organisational promise. It is in our leadership and managerial ethos to meaningfully partner with our employees, customers, and stakeholders with a vision to realise our shared goals. 
          Our values dubbed, LIVE Y’ello, are the cornerstone of our culture.

          Lead with Care
          Can-do with Integrity
          Collaborate with Agility
          Serve with Respect
          Act with Inclusion

          Education:

          • 4 year degree in Computer Science, Business, Product Management, or related field (Master's preferred).

          Experience:

          • 5 – 8 years of relevant experience in product management, technology, data, digital platforms, consulting, fintech, telecommunications, AdTech or related environments.
          • Proven track record of taking complex products from concept/vision through customer validation, development, launch and scale.
          • Demonstrated 0→1 product development experience.
          • Experience leading multidisciplinary technology and business teams without relying solely on formal reporting lines.
          • Strong technical understanding of modern data and technology architectures.
          • Significant experience in one or more of: advertising/audience monetisation, geospatial/location intelligence, credit scoring, risk/fraud, AI/machine learning, or API/platform businesses.
          • Demonied commercial understanding of how technology products create and capture value.
          • Strong experience with Agile product development and modern product operating models.
          • Demonstrated ability to work with senior executives, customers and technical specialists.
          • Strong understanding of data privacy, security, governance and regulatory requirements.
          • Advanced analytical and problem-solving capability.
          • Strong AI literacy and demonstrated ability to assess AI technologies and their business applicability.

          Competencies:

          • Product thinking: ability to identify the right problem before building the solution
          • Technical depth: able to challenge engineers and architects credibly
          • Commercial thinking: understands how a product becomes revenue and margin
          • Analytical problem solving: ability to break ambiguous problems into structured, testable hypotheses
          • Leadership: mobilise people across organisational boundaries
          • AI fluency: distinguish genuine AI opportunity from hype

          Personal Attributes

          • Exceptional intellectual curiosity
          • Highly structured thinker
          • Entrepreneurial and commercially minded
          • Comfortable with ambiguity
          • Bias toward action and experimentation
          • Customer obsessed
          • High ownership and accountability
          • Strong executive presence
          • Excellent written and verbal communication
          • Able to simplify highly complex concepts
          • Comfortable challenging conventional thinking
          • High standards for quality and execution
          • Low ego; highly collaborative
          • Builder rather than administrator

          Discover and Validate Customer Problems

          • Conduct structured customer discovery across enterprise, government, financial services, FMCG, media, advertising, technology and other priority segments.
          • Identify unmet customer needs, pain points and emerging market opportunities.
          • Translate customer problems into clearly articulated product opportunities.
          • Develop hypotheses around customer value, willingness to pay, addressable market and competitive differentiation.
          • Lead customer interviews, design-thinking sessions, workshops and proof-of-concept engagements.
          • Build a business case and validate product-market fit before significant technology investment.
          • Develop compelling problem statements, value propositions and product hypotheses.

          Define Product Vision and Strategy

          • Develop product vision, strategy, roadmap and business cases that are rigorously interrogated and boad-ready.
          • Define target customer segments, use cases, propositions and monetisation models.
          • Determine the appropriate balance between build, buy, partner and integrate.
          • Define MVP scope and a disciplined path from MVP → product-market fit → scale.
          • Establish product success metrics, including adoption, revenue, margin, customer value, usage and retention.
          • Continuously assess market, technology and competitive developments to identify opportunities for new products and product extensions.

          Own Technical Product Definition

          • Define functional and non-functional product requirements.
          • Develop product requirements documents, user stories, acceptance criteria and product specifications.
          • Work with architects and engineering teams to define appropriate technical architectures.
          • Understand APIs, data platforms, cloud