PI

Lead, Product Strategy

Full-time Lead Nigeria, NG
Posted 3 days, 14 hours ago 209 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor - I receive raw scraped text from a job website - My job: extract ONLY actual job info, return clean, readable format - Must REMOVE: social sharing, author bylines, "you may also like", navigation, comments, ads/promotions, cookie/subscription notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts - Must KEEP and STRUCTURE: job title, company/org, location, job description/responsibilities, requirements/qualifications, how to apply, salary (if mentioned), deadline/closing date, job ID/reference number, contract type/level - Return ONLY the cleaned job text. No commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text. Wait, the user actually gave me a task description AND a job description. The prompt says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then there are rules about HTML formatting. Then: "Job description:" followed by the actual job text. But the very first part of the prompt says: "You are a job listing editor. You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format." And it lists what to remove/keep. Then it says: "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." But then the user also says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules. There's a conflict/mixture of two different output formats: plain text cleaned vs semantic HTML. I need to figure out which one the user actually wants at the end. Let's read carefully: The prompt starts with "You are a job listing editor...". Then there's a section "REMOVE all of the following..." and "KEEP and STRUCTURE:" and "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." Then: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules. Then: "Job description:" and the text. Then: "Rules: ... Return ONLY the HTML. No markdown fences, no explanation, no preamble." It seems like there are two personas/instructions mixed. The first part is the "job listing editor" task, the second part is "format it as clean semantic HTML". Which one to follow? Looking at the very end: "Job description:" followed by the job text, and then "Rules: ... Return ONLY the HTML. No markdown fences, no explanation, no preamble." I think the user wants me to take the job description text, clean it (remove irrelevant stuff), and then format it as clean semantic HTML according to the rules given. But the first part says "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." which sounds like plain text. However, the second set of rules explicitly says to use

,

,
    ,
  • , no CSS classes, no inline styles, no
    , no
    , preserve ALL original content word-for-word, if no clear sections just wrap paragraphs in

    , RETURN ONLY the HTML. No markdown fences, no explanation, no preamble. Given that the prompt explicitly provides HTML rules and then the job description, and ends with "Return ONLY the HTML. No markdown fences, no explanation, no preamble.", I'll assume the desired output is the HTML format. But wait, there's a tension: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" vs the first part's "REMOVE all of the following: Social sharing text, Author bylines, ... Advertisements or promotions, Cookie/subscription notices, Duplicate text, Category labels that aren't part of the job, Stray numbers or formatting artifacts". I need to remove the stuff listed in the first part, and then format the remaining as HTML per the second part. Let's examine the job description text provided. It starts with "### Job Summary", then "### Job Details", then "Key Responsibilities:", then sections like "Product Strategy & Vision", bullet points, then "### Requirements", then a list of requirements. I need to clean it: remove any social sharing, bylines, etc. Looking at the text, it seems relatively clean already, but I should check for any stray stuff. The text provided is just the job content, no obvious social sharing or bylines within it. It has headings like "### Job Summary", "### Job Details", "Key Responsibilities:", section titles, bullet points. I need to output clean semantic HTML using

    ,

    ,
      ,
    • . No
      , no
      , no CSS classes/inline styles. Rules for HTML: - Use

      for introductory paragraphs and general text - Use

      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
        s, no
        tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in

        tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. I need to map the job description content to these HTML tags. Let's parse the job description text: "### Job Summary As the Lead, Product Strategy, you will lead the strategic direction of Piggytech's product portfolio, ensuring our existing and future products deliver exceptional customer value while advancing the company's long-term business objectives. You will work closely with Engineering, Design, Data, Marketing, Operations, Risk, Compliance, Customer Success, and senior management to identify opportunities, define product strategy, execute high-impact initiatives, and build products that solve meaningful customer problems at scale. This role requires a strategic product leader with extensive experience building and scaling digital products, managing Product Managers, influencing executive stakeholders, and balancing customer needs with commercial outcomes in a fast-paced, high-growth environment. ### Job Details **Key Responsibilities:** **Product Strategy & Vision** - Define and lead the product strategy across PiggyVest, PocketApp, PiggyVest Business, and future products, ensuring alignment with Piggytech's vision, business objectives, and long-term growth strategy. - Develop and continuously refine a cohesive product portfolio strategy that delivers seamless customer experiences across saving, investing, payments, and other financial services. - Translate business strategy into clear product priorities, strategic initiatives, and measurable outcomes that drive sustainable growth. - Identify new product opportunities, adjacent markets, customer segments, and emerging business models that strengthen Piggytech's market leadership. **Product Portfolio Leadership** - Oversee the strategic direction and performance of Piggytech's product portfolio, ensuring each product delivers measurable customer and business value. - Balance short-term delivery with long-term innovation by continuously evaluating product investments, priorities, and resource allocation. - Drive strategic alignment across products to maximise synergies, shared capabilities, and customer lifetime value. **Product Management Leadership** - Lead, mentor, and develop a high-performing team of Product Managers, fostering a culture of ownership, customer obsession, innovation, and excellence. - Establish product management standards, frameworks, and operating rhythms that enable consistent execution and scalable product development. **Customer, Market & Industry Intelligence** - Develop deep insights into customer behaviour, market trends, competitive dynamics, and the evolving financial services landscape to inform product strategy. - Champion continuous customer discovery through research, experimentation, usability testing, and data analysis. - Anticipate changes in technology, regulation, and customer expectations, ensuring Piggytech remains at the forefront of innovation. **Innovation & Future Product Development** - Drive the exploration, validation, and development of new products, platform capabilities, and revenue opportunities that expand Piggytech's ecosystem. - Evaluate emerging technologies—including AI, automation, embedded finance, open banking, and other industry innovations—to identify opportunities that improve customer experience and business performance. - Foster a culture of experimentation by encouraging teams to test ideas, validate assumptions, and learn quickly. **Roadmap Execution & Delivery** - Guide Product Managers in developing strategic, outcome-driven product roadmaps aligned with customer needs and business priorities. - Partner with Engineering, Design, Data, Marketing, Risk, Compliance, Operations, and other stakeholders to ensure timely and high-quality execution. - Proactively identify strategic risks, remove delivery blockers, and ensure effective decision-making throughout the product lifecycle. **Commercial Strategy & Growth** - Balance customer value with commercial objectives by identifying opportunities to increase customer acquisition, engagement, retention, revenue, and operational efficiency. - Develop business cases for new products, strategic initiatives, partnerships, and market expansion opportunities. - Monitor product performance and ensure strategic initiatives deliver measurable business outcomes. ### Requirements - Bachelor's degree in Computer Science, Engineering, Business, Economics, Information Systems, or a related field. - Minimum of 8 years' experience in Product Management, with at least 3 years leading or managing Product Managers. - Demonstrated success defining product strategy and scaling multiple digital products in a high-growth technology environment. - Proven experience managing product portfolios and leading cross-functional product teams. - Strong understanding of product discovery, product development, Agile methodologies, experimentation, product analytics, and customer research. - Experience building consumer-facing digital products at scale, preferably within fintech, financial services, payments, banking, investing, lending, or related industries. - Strong commercial acumen with the ability to balance customer needs, business objectives, and technical considerations. - Excellent analytical, strategic thinking, problem-solving, and decision-making skills. - Outstanding communication, stakeholder management, negotiation, and leadership capabilities. - Demonstrated ability to influence senior executives and drive alignment across multiple teams in a fast-paced environment." Now, I need to convert this to HTML using

        ,

        ,
          ,
        • . Important: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I must keep all the text exactly as is, including bullet points, headings, etc., but format them with the specified tags. Also: "If text has no clear sections, just wrap paragraphs in

          tags". This text has clear sections. How to structure? - The "### Job Summary" is an introductory paragraph. Should be

          . - "### Job Details" might be a section header. But the rules say use

          for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. "Job Details" might not be in that list, but it's a header. I need to decide. The list includes "Key Responsibilities" which maps to Responsibilities, and "Requirements" maps to Requirements. "Job Details" could be treated as a section header, maybe

          Job Details

          , but the rules say "e.g." so it's not exhaustive. I'll use

          for section headers that correspond to the listed ones, but I need to be careful. Let's look at the structure: - "### Job Summary" -> content paragraph - "### Job Details" -> then "**Key Responsibilities:**" then sections with headings like "Product Strategy & Vision", "Product Portfolio Leadership", etc., each with bullet points. - Then "### Requirements" then bullet points. The rules for HTML say: "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use

          for headers like "Responsibilities", "Qualifications", "Requirements", etc. But the text has "### Job Details", "Key Responsibilities:", then sub-headings like "Product Strategy & Vision", "Product Portfolio Leadership", etc. And "### Requirements". I need to output clean semantic HTML. I should probably treat the main sections as

          , and the bullet points as
          • . Let's think about how to map: - "### Job Summary" content:

            ...

            - "### Job Details" could be

            Job Details

            , but the content inside has "Key Responsibilities:" which might be

            Key Responsibilities

            , but the rules say "Use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, ...)". So "Key Responsibilities" maps to "Responsibilities". The sub-headings under it ("Product Strategy & Vision", etc.) are not explicitly listed, but they are section headers within the responsibilities. I could treat them as

            as well, or maybe just keep them as part of the text. But the rule says "Use

            for section headers (e.g. ...)". It doesn't say I must use

            for every header, but it's a guideline. Since it says "If text has no clear sections, just wrap paragraphs in

            tags", and this text has clear sections, I should use

            for the section headers. However, "Preserve ALL original content word-for-word" means I can't change the wording of the headers, but I can wrap them in tags. The original has "### Job Summary", "### Job Details", "**Key Responsibilities:**", then "**Product Strategy & Vision**", etc. The markdown bold ** might be removed since we're outputting HTML without markdown. I need to convert the content to HTML tags, but preserve the text word-for-word. So I should keep the exact text, just wrap in HTML tags. Let's outline the HTML structure I'll produce:

            As the Lead, Product Strategy, you will lead the strategic direction of Piggytech's product portfolio, ensuring our existing and future products deliver exceptional customer value while advancing the company's long-term business objectives. You will work closely with Engineering, Design, Data, Marketing, Operations, Risk, Compliance, Customer Success, and senior management to identify opportunities, define product strategy, execute high-impact initiatives, and build products that solve meaningful customer problems at scale. This role requires a strategic product leader with extensive experience building and scaling digital products, managing Product Managers, influencing executive stakeholders, and balancing customer needs with commercial outcomes in a fast-paced, high-growth environment.

            Job Details

            Key Responsibilities

            • Product Strategy & Vision
              • Define and lead the product strategy across PiggyVest, PocketApp, PiggyVest Business, and future products, ensuring alignment with Piggytech's vision, business objectives, and long-term growth strategy.
              • ... etc But wait, the sub-headings like "Product Strategy & Vision" are themselves headings with bullet points under them. The structure is nested. I need to decide how to handle nesting. The rules don't mention nested lists, but I can use
                • for list items. I could flatten it, but "Preserve ALL original content word-for-word" might mean I should keep the structure as is, but in HTML. I could do nested
                    , but the rule says "Use
                    • for list items (duties, requirements, qualifications, skills)". It doesn't forbid nested lists, but says "No CSS classes, no inline styles, no
                      s, no
                      tags". It doesn't say no nested
                        . I think nested
                          is fine. However, "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" means I must include every bullet point exactly as is. I can structure them in HTML lists. Let's look at the original text structure: - "### Job Details" - "**Key Responsibilities:**" - Then sections with headings: "Product Strategy & Vision", each with 4 bullet points. - Then "Product Portfolio Leadership", with 3 bullet points. - Then "Product Management Leadership", with 2 bullet points. - Then "Customer, Market & Industry Intelligence", with 3 bullet points. - Then "Innovation & Future Product Development", with 3 bullet points. - Then "Roadmap Execution & Delivery", with 3 bullet points. - Then "Commercial Strategy & Growth", with 3 bullet points. Then "### Requirements" with 18 bullet points. I need to output HTML. I'll try to structure it logically. Possible approach: - Treat "Job Summary" as

                          - Treat "Job Details" as

                          Job Details

                          - Under that, "Key Responsibilities" as

                          Key Responsibilities

                          - Then a
                            with
                          • for each of the main section headings? Or nest the bullet points directly under

                            Key Responsibilities

                            ? The bullet points have sub-headings. I could do:

                            Key Responsibilities

                            • Product Strategy & Vision

                              • ...bullet points...
                            • ...
                            But the rule says "Use

                            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say I can't use

                            for other headers, but it's suggested. I'll use

                            for the main section headers that appear in the

      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 ✍️

      Free cover letter for this job

      Upload your CV and get a tailored cover letter in seconds — free, no account needed.

      Generate a Cover Letter 📝

      Join Our Nigeria Channels

      Get free job alerts on your phone

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?