KC

Senior Manager, Digital Payments

Full-time Kenya, KE
Posted 3 days, 12 hours ago 20 views 0 applications

Job Description

We need to output clean semantic HTML with

for intro paragraphs and general text,

for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use
  • for list items (duties, requirements, qualifications, skills). No CSS classes, no inline styles, no
    , no
    . Preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. We have raw HTML with many style tags etc. We need to extract the text content and then format as semantic HTML. We must keep all original content word-for-word. That means we cannot change wording, but we can restructure into HTML tags. We must preserve the text exactly as appears (including punctuation, spaces?). We need to be careful: The original includes some extra spaces like " " and line breaks. We should preserve the textual content, but we can ignore HTML tags and just output the plain text content, then wrap in appropriate tags. We need to identify sections: The text starts with a paragraph with empty content? Actually first line:

     

    which is a non-breaking space. Then a paragraph with KEY RESPONSIBILITIES: (bold). Then a ul with li items each containing paragraphs with responsibilities. Then after the ul, a paragraph with MINIMUM POSITION REQUIREMENTS: then numbered list items (1., 2., 3.) and then a ul under 3. We need to output as semantic HTML: Use

    for section headers: "KEY RESPONSIBILITIES:" and "MINIMUM POSITION REQUIREMENTS:" maybe also "Professional qualification..."? But the instruction: Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat "KEY RESPONSIBILITIES:" as a header (

    KEY RESPONSIBILITIES:

    ) and "MINIMUM POSITION REQUIREMENTS:" as a header (

    MINIMUM POSITION REQUIREMENTS:

    ). The content under each should be in

    for intro paragraphs and

    • for list items. We need to preserve all original content word-for-word. That includes the bullet points text exactly as they appear, including any bold tags? We must strip HTML tags but keep the text. The bold tags are just styling; we should not include them in output because we are not allowed to add CSS classes or inline styles, but we can keep the bold text as plain text (the bold styling is lost). However the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove the tags, we are removing markup, but the textual content inside remains. The instruction likely refers to the textual content, not the markup. Since we are converting to semantic HTML, we drop the original markup and replace with our own tags. That's acceptable. We must ensure we don't lose any words. Let's extract the text. First, the initial empty paragraph with  : that's just a space; we can ignore as it's not meaningful content. Probably we should not output an empty

       

      because that would be adding content? The instruction says preserve ALL original content word-for-word. The   is a character entity representing a space. If we drop it, we are removing content. But maybe we can ignore leading/trailing whitespace. Usually they'd accept ignoring empty paragraphs. Safer to include an empty

      ? But that would be adding a tag not originally there. The instruction says no
      s, but

      is allowed. However adding an empty

      might be considered adding content not originally present. The original had a

      with  . If we output

      we are changing content (removing  ). If we output

       

      we would be preserving the entity but that's an HTML entity; we could keep it as is inside

      . However we are not allowed to add CSS classes or inline styles, but we can keep the entity. The original had

       

      . We cannot keep align or style attributes. So we must strip those. The instruction says no CSS classes, no inline styles, no
      s, no
      tags. It doesn't forbid keeping other attributes like align? Probably they want clean semantic HTML, so we should strip all attributes. So we will output

       

      ? That would have the entity but no attributes. That is preserving the content word-for-word (the  ). However the entity is a character; we could also output a regular space. But to be safe, output

       

      . However the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we change   to a regular space, that's a change. So we should keep  . But note that the entity is inside a

      tag; we are stripping attributes but keeping the inner HTML  . That's acceptable. After that, we have a paragraph with KEY RESPONSIBILITIES: bold. We'll output

      KEY RESPONSIBILITIES:

      (no bold). The bold is lost but the text remains. Then we have a
        with
      • items each containing a

        with the responsibility text. We need to output

        • for each responsibility. The inner

          can be omitted? The instruction says use

          • for list items (duties, requirements, qualifications, skills). It doesn't forbid having

            inside

          • , but better to just put the text directly inside
          • . However we must preserve the text word-for-word. If we strip the

            tags, we are removing markup but not text. That's likely acceptable. Thus for each responsibility, we output

          • followed by the responsibility sentence exactly as appears (including any internal bold? we will drop bold markup). Ensure we keep punctuation and spaces. Let's extract each responsibility text: From the HTML: 1. Define the bank’s digital payments, wealth and investments product portfolio strategy ensuring alignment to the division and the bank’s overall strategy to deliver set KPIs and seek peer and senior management alignment. Note there is a non-breaking space after strategy? Actually the text: "Define the bank’s digital payments, wealth and investments product portfolio strategy ensuring alignment..." The   is a space. We'll keep as a space? We'll keep the text as "Define the bank’s digital payments, wealth and investments product portfolio strategy ensuring alignment..." (the   becomes a normal space). But to be precise, we could keep the   entity. However inside
          • we can't have HTML entities? We can. But we said we will strip attributes but can keep entities. Safer to keep the entity as is: "strategy ensuring". However the instruction says preserve original content word-for-word. The original had  . So we should keep that entity. But then we would have to output it inside
          • as plain text, which is fine. However the
          • content is text; we can include the entity as characters. So we will output exactly the string between the tags, including  . Let's copy each responsibility text exactly as inside the

            tags, preserving any  . I'll extract from the given HTML: First li:

            Define the bank’s digital payments, wealth and investments product portfolio strategy ensuring alignment to the division and the bank’s overall strategy to deliver set KPIs and seek peer and senior management alignment.

            So the inner text (including the strong) is: "Define the bank’s digital payments, wealth and investments product portfolio strategy ensuring alignment to the division and the bank’s overall strategy to deliver set KPIs and seek peer and senior management alignment." Note there is a space after strategy? Actually the strong includes "strategy " then after closing strong, there is "ensuring". So the   is between strategy and ensuring. We'll keep that. Second li:

            Develop commercial models that directly impact top-line revenue and bottom-line operating costs while delivering best in class product experiences across our channels

            Text: "Develop commercial models that directly impact top-line revenue and bottom-line operating costs while delivering best in class product experiences across our channels" Third li:

            Coordinate the implementation of activities across assigned products in partnership with marketing and customer experience to drive customer engagement to grow NPS & reduce CES, grow product as per set KPIs

            Text: "Coordinate the implementation of activities across assigned products in partnership with marketing and customer experience to drive customer engagement to grow NPS & reduce CES, grow product as per set KPIs" Note there is & for ampersand. Fourth li:

            Daily drive of the assigned digital payments, wealth and investments portfolio performance in partnership with other divisions to ensure customer uptake, usage of the products, reduction in attrition & churn and effective recovery of customers as well as consideration of regulatory requirements. 

            Text: "Daily drive of the assigned digital payments, wealth and investments portfolio performance in partnership with other divisions to ensure customer uptake, usage of the products, reduction in attrition & churn and effective recovery of customers as well as consideration of regulatory requirements. " Note trailing   after period. Fifth li:

            Launch and scale payment features across mobile apps, wallets, and embedded platforms, ensuring seamless, secure and intuitive payment journeys with high adoption.

            Text: "Launch and scale payment features across mobile apps, wallets, and embedded platforms, ensuring seamless, secure and intuitive payment journeys with high adoption." Sixth li:

            Liaise with the vendors & technology teams to ensure correct definition, implementation and documentation of product requirements for new products and customizations of existing to meet specific customer needs.

            Text: "Liaise with the vendors & technology teams to ensure correct definition, implementation and documentation of product requirements for new products and customizations of existing to meet specific customer needs." Seventh li:

            Identify, document & implement changes for process improvement, in liaison with internal stakeholders from technology and other departments 

            Text: "Identify, document & implement changes for process improvement, in liaison with internal stakeholders from technology and other departments " Eighth li:

            Interpret and analyze product performance, customer insights and market research data to evaluate ideas, suggestions and make recommendations to drive growth.

            Text: "Interpret and analyze product performance, customer insights and market research data to evaluate ideas, suggestions and make recommendations to drive growth." Ninth li:

            Undertake coaching and mentoring for team members and provide leadership in execution of the division’s strategy.

            Text: "Undertake coaching and mentoring for team members and provide leadership in execution of the division’s strategy." Tenth li:

             

            Text: " " (just a non-breaking space). This is an empty list item basically. We should preserve it. So we will output
          •  
          • . Now after the ul, we have a paragraph with MINIMUM POSITION REQUIREMENTS: (bold). Then numbered list:

            MINIMUM POSITION REQUIREMENTS:

            Then:

            1.  A Bachelor’s degree from a recognized university.

            Note there is a space after "1." and   then text. Second:

            2 Professional qualification in Product Management, Project Management, AGILE Practices, Digital Payments is required.

            Third:

            3.At least six years in managerial experience in leading digital product management and managing teams, including specific experience in the following areas:

            Then a
              with li items:
              • Digital Payments, Wallets &/or investment product management or development
              • Delivery/Management of Consumer products and services in a high growth environment
              • Building relationship networks & Managing teams
              • Project Delivery/ Management
              • Experience in the sales of financial services is an added advantage.

                 

              Note the last li contains two

              tags: one with the sentence, another with  . We need to preserve that. We need to output as semantic HTML: For the requirements section, we should have

              MINIMUM POSITION REQUIREMENTS:

              . Then we need to represent the numbered list. The instruction says use
              • for list items (duties, requirements, qualifications, skills). So we should convert the numbered list into
                • as well, preserving the text including the leading numbers? The original text includes "1. ", "2 ", "3." etc. If we convert to
                  • , we would be changing the format (removing the numbers). But the instruction says use
                    • for list items. It doesn't say we must keep the numbering. However we must preserve ALL original content word-for-word. If we change "1. " to just the text without the number, we are removing content (the numbers and period). That would violate preservation. So we need to keep the numbers as part of the list item text. We can still wrap each line in
                    • and keep the number text inside. That satisfies using
                      • for list items while preserving the original wording (including the numbers). So we will output
                        • 1.  A Bachelor’s degree from a recognized university.
                        • etc. But note there is an   after the number. We'll keep that. For the third requirement, there is no space after "3."? It's "3.At least six years...". We'll keep that. Then we have a sublist under 3. The original uses a
                            with
                          • items. We should preserve that as a nested
                            • inside the
                            • for requirement 3. That's okay. The last li under that sublist contains two

                              tags: one with the sentence, another with  . We need to preserve both. So inside that

                            • we will have

                              Experience in the sales of financial services is an added advantage.

                               

                              . However the instruction says use
                              • for list items, but doesn't forbid having

                                inside

                              • . It's okay to keep

                                tags inside

      Apply Now ↗

      How well do you match?

      Get an instant AI match score for this role — free, takes 3 minutes.

      Tailor your CV for this role

      The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.

      Tailor My CV to This Job ✍️

MJC
ECHO
Your MJC Assistant

I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.

How was your experience with ECHO?