M-Pesa Africa: Executive Head of Product – Digital

for paragraphs,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve original content exactly, but we need to format with tags. The input already contains some HTML tags like

  , ,

  ,
  • , etc. We need to output only HTML, preserving content word-for-word, but we can re-tag as needed. However we must not add or remove content. So we need to output the same text but with appropriate tags:

    for paragraphs,

    for section headers,

    • for list items. Also need to keep maybe? The rules didn't forbid . It said use

      for introductory paragraphs and general text,

      for section headers,

      • for list items. It didn't say we cannot keep other tags like . It said preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text, including existing tags like ,   etc. But we also need to wrap sections appropriately. However the original already has

        tags etc. We need to output only HTML, no markdown fences. Likely we should output the cleaned HTML as per rules, but we must keep the content exactly, including existing tags. However we may need to adjust to use

        for section headers like "Core competencies, knowledge and experience:" etc. The original has for those headers. We need to change them to

        but that would change content (removing and adding

        ). That would be altering content, which is not allowed per "preserve ALL original content word-for-word". But the instruction says: "Use

        for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It seems they expect us to replace the section headers with

        tags, but that would change the markup. However they said preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. This is contradictory. Usually in such tasks, they want you to keep the text content same, but you can change tags. The phrase "preserve ALL original content word-for-word" likely refers to the textual content, not the tags. So we can change tags but keep the text inside unchanged. So we should extract the textual content and wrap appropriately. Thus we need to parse the given HTML snippet, extract text, and produce new HTML with

        ,

        ,

        • . Let's do that. Given snippet:

          M-Pesa Africa is the largest FinTech providing services to more than 60 million customers and 5 million businesses solutions across Financial Services, Enterprise, Merchant and Retail. We are now well on our way to becoming the preferred digital payment method across the markets that we serve, for both in-store, remote and online payments. With headquarters in both Nairobi and Johannesburg, we serve markets that include Kenya, Tanzania, DRC, Lesotho, Ghana, Egypt, Ethiopia, and Mozambique. 

          
          We are a united, energetic and passionate team. A place where leaders coach, teams connect, and everyone is empowered to go further, faster. A place where heroes become superheroes; through growth, opportunity, and the chance to work with the best minds in FinTech. 

          
          The EHOD – Digital will be responsible for championing the digital transformation of M-Pesa as we prepare for millions of our customers and merchants to transition from feature phones to smartphones. This includes bringing the voice of the customer, industry trends and design thinking to the M-Pesa app and actively engaging and influencing key internal and external stakeholders. You will be the “linchpin” between the engineering teams and the business.
           

          Core competencies, knowledge and experience:

          • Strong knowledge of mobile money, fintech and financial services 
          • Experience with emerging market consumers, and multicultural sensitivity  
          • Keen understanding of digital product lifecycle & software/mobile development 
          • Experience with Agile/Lean management 
          • Analytical bent of mind, structured thinker with strong business acumen 
          • Results-driven self-starter 
          • Solid influencing and negotiation skills

           

          Education & Experience:

          • >8  years of professional experience with at least 5 years of digital product management at a fintech, bank or other relevant digital business 
          • Bachelor’s degree required, a Master’s degree in a related field preferred 
          • Certification in Scaled Agile Framework 
          • Contagious passion for, and commitment to driving mobile money growth and innovation  
             
          • Champion App Product Strategy & Execution: 
            • Own the vision for the consumer fintech app across 7 Markets
            • Leading 80+ people across Engineering, UX and Product to achieve product delivery 
            • Drive the roadmap, incorporate industry and customer research to create a transformative product 
            • Be a customer advocate, drive superior customer experience via UI/UX, define customer journeys based on customer need, define acceptance criteria for every customer journey 
            • Master product backlog: prioritize for business impact and superior customer experience 
            • Rally product creation colleagues to drive timely results – developers, business analysts, architects, delivery managers, operations support, etc.  
          • Spearhead Partnerships to Drive Innovation: 
            • Define partnership strategy for the app including loyalty and rewards to drive engagement 
            • Drive business development with relevant 3rd parties, negotiate key commercial and product terms and support legal on contracting across 7 markets
          • Build "trusted advisor" relationship with business leaders across M-Pesa markets: 
            • Co-develop launch and go to market plans with local product managers to drive uptake and engagement 
            • Offer strategic support on the digital strategy and business case Strong knowledge of mobile money, fintech and financial services
            • Drive commercial rationalisation of the service roadmaps balancing requirements from multiple markets
               
          We need to produce HTML with

          for paragraphs,

          for section headers,

          • for list items. We need to identify sections: - Intro paragraph(s): first three

            blocks (maybe combine?). They are: 1) "M-Pesa Africa is the largest FinTech providing services to more than 60 million customers and 5 million businesses solutions across Financial Services, Enterprise, Merchant and Retail. We are now well on our way to becoming the preferred digital payment method across the markets that we serve, for both in-store, remote and online payments. With headquarters in both Nairobi and Johannesburg, we serve markets that include Kenya, Tanzania, DRC, Lesotho, Ghana, Egypt, Ethiopia, and Mozambique. " 2) "
            We are a united, energetic and passionate team. A place where leaders coach, teams connect, and everyone is empowered to go further, faster. A place where heroes become superheroes; through growth, opportunity, and the chance to work with the best minds in FinTech. " Note there is a leading
            inside the

            . We need to preserve content word-for-word, but we can't use
            . However we must not add
            . The rule says no
            tags. So we must omit the
            but that would remove content. However the
            is just a line break; maybe we can treat it as part of the paragraph and just not include the tag, but the text after
            starts with a space? Actually the snippet: "

            
            We are a ..." So there is a
            then text. If we remove
            , we lose that line break but the text remains. The rule says no
            tags, but we must preserve content word-for-word. This is contradictory. Probably they expect us to strip out
            tags as they are not allowed. The instruction: "No CSS classes, no inline styles, no

            s, no
            tags". So we must not output
            . So we will omit them. That is removing a tag, but maybe acceptable because they forbid
            . We'll follow the rule: no
            . So we will not output
            . We'll keep the text. Thus paragraph 2 becomes: "We are a united, energetic and passionate team. A place where leaders coach, teams connect, and everyone is empowered to go further, faster. A place where heroes become superheroes; through growth, opportunity, and the chance to work with the best minds in FinTech. " But we also have tags inside. We can keep them. Paragraph 3: "
            The EHOD – Digital will be responsible for championing the digital transformation of M-Pesa as we prepare for millions of our customers and merchants to transition from feature phones to smartphones. This includes bringing the voice of the customer, industry trends and design thinking to the M-Pesa app and actively engaging and influencing key internal and external stakeholders. You will be the “linchpin” between the engineering teams and the business.
             " Remove
            at start and end. So paragraph: "The EHOD – Digital will be responsible for championing the digital transformation of M-Pesa as we prepare for millions of our customers and merchants to transition from feature phones to smartphones. This includes bringing the voice of the customer, industry trends and design thinking to the M-Pesa app and actively engaging and influencing key internal and external stakeholders. You will be the “linchpin” between the engineering teams and the business. " Now after that we have a section header: "

            Core competencies, knowledge and experience:

            " This should be

            Core competencies, knowledge and experience:

            Then a

            list with items. We'll keep
            • as is. Then a paragraph with   (maybe empty). We'll output a

               

              ? But we could omit empty paragraphs. The rule: preserve ALL original content word-for-word. The   is a non-breaking space. We could keep it inside a

              . But maybe we can just output

               

              . However they said no
              but   is okay. Then "

              Education & Experience:

              " =>

              Education & Experience:

              Then a
              list. Then there is a weird nested list: after that, there is another
              that starts with
              • Champion App Product Strategy & Execution: 
                ... This seems to be a continuation of the previous list? Actually the original after Education & Experience list, there is a closing
                then another
                with items that have strong headers and nested lists. This looks like responsibilities section. So we need to treat those as a new section maybe "Key Duties" or "Responsibilities". The original didn't have a header for that; it's just a list after Education & Experience. We could treat it as a section header maybe "Key Duties". But we must not add content not originally present. However we can infer a header? The rules say use

                for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). If there is no clear header, we just wrap paragraphs in

                . But here we have a list that seems to be responsibilities. We could add a

                Responsibilities

                before the list. But that would be adding content not originally present. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Adding a header would be adding content. So we cannot add a header that wasn't there. However the original had no header for that list; it's just a list after Education & Experience. So we should keep it as a list directly after the previous list? But that would be two consecutive
                elements, which is okay. However the original had a
                then another
                . So we can keep that structure. Thus after Education & Experience list, we output the next
                as is. But note that the nested list items have headers like "Champion App Product Strategy & Execution:" etc. Those are inside
                • . We should keep them. Thus final HTML:

                  M-Pesa Africa is the largest FinTech providing services to more than 60 million customers and 5 million businesses solutions across Financial Services, Enterprise, Merchant and Retail. We are now well on our way to becoming the preferred digital payment method across the markets that we serve, for both in-store, remote and online payments. With headquarters in both Nairobi and Johannesburg, we serve markets that include Kenya, Tanzania, DRC, Lesotho, Ghana, Egypt, Ethiopia, and Mozambique. 

                  We are a united, energetic and passionate team. A place where leaders coach, teams connect, and everyone is empowered to go further, faster. A place where heroes become superheroes; through growth, opportunity, and the chance to work with the best minds in FinTech. 

                  The EHOD – Digital will be responsible for championing the digital transformation of M-Pesa as we prepare for millions of our customers and merchants to transition from feature phones to smartphones. This includes bringing the voice of the customer, industry trends and design thinking to the M-Pesa app and actively engaging and influencing key internal and external stakeholders. You will be the “linchpin” between the engineering teams and the business. 

                  Core competencies, knowledge and experience:

                  • Strong knowledge of mobile money, fintech and financial services 
                  • Experience with emerging market consumers, and multicultural sensitivity  
                  • Keen understanding of digital product lifecycle & software/mobile development 
                  • Experience with Agile/Lean management 
                  • Analytical bent of mind, structured thinker with strong business acumen 
                  • Results-driven self-starter 
                  • Solid influencing and negotiation skills

                   

                  Education & Experience:

                  • >8  years of professional experience with at least 5 years of digital product management at a fintech, bank or other relevant digital business 
                  • Bachelor’s degree required, a Master’s degree in a related field preferred 
                  • Certification in Scaled Agile Framework 
                  • Contagious passion for, and commitment to driving mobile money growth and innovation  
                     
                  • Champion App Product Strategy & Execution: 
                    • Own the vision for the consumer fintech app across 7 Markets
                    • Leading 80+ people across Engineering, UX and Product to achieve product delivery 
                    • Drive the roadmap, incorporate industry and customer research to create a transformative product 
                    • Be a customer advocate, drive superior customer experience via UI/UX, define customer journeys based on customer need, define acceptance criteria for every customer journey 
                    • Master product backlog: prioritize for business impact and superior customer experience 
                    • Rally product creation colleagues to drive timely results – developers, business analysts, architects, delivery managers, operations support, etc.  
                  • Spearhead Partnerships to Drive Innovation: 
                    • Define partnership strategy for the app including loyalty and rewards to drive engagement 
                    • Drive business development with relevant 3rd parties, negotiate key commercial and product terms and support legal on contracting across 7 markets
                  • Build "trusted advisor" relationship with business leaders across M-Pesa markets: 
                    • Co-develop launch and go to market plans with local product managers to drive uptake and engagement 
                    • Offer strategic support on the digital strategy and business case Strong knowledge of mobile money, fintech and financial services
                    • Drive commercial rationalisation of the service roadmaps balancing requirements from multiple markets
                       
                  But note we have
                  inside some list items (the Education & Experience list item 4 has "
                   " at end). Also the last nested list item has "
                   ". We must not output
                  . So we need to remove those
                  tags. However that would be removing content. But the rule says no
                  tags. So we must omit them. We'll just keep the   maybe. Thus for item 4: "Contagious passion for, and commitment to driving mobile money growth and innovation  
                   " => remove
                  leaving "Contagious passion for, and commitment to driving mobile money growth and innovation   "? Actually there is   before
                  and   after. If we remove
                  , we get two consecutive  . We'll keep as is: "  ". But we could just keep one  ? Safer to keep exactly as original but without
                  . So we output "  ".

  Translated by AI — may not be perfect

  Show original