Senior Feature Analyst

,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve original content word-for-word, no addition/removal. Must convert the given raw HTML (with inline styles etc.) into proper semantic HTML. We need to extract the content and reformat. Let's parse the raw text. The raw input includes many

  tags with style attributes and spans etc. We need to ignore those and just get the text content. We need to produce HTML with appropriate tags. We need to identify sections: There's a title: "

  Let's Write Africa's Story Together!

  " That's likely a heading but we are told to use

  for section headers like Responsibilities, Qualifications, etc. For the main title maybe we just keep as

  ? The instruction: Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't forbid using other headings for other things, but we should follow: Use

  for introductory paragraphs and general text. So the title could be a

  . However it's bold and maybe we could keep as

  with bold? But we cannot add CSS classes or inline styles, but we can keep inside

  . That's allowed: we can keep original markup? The instruction: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That means we must keep the exact text, including HTML tags? But we also need to output clean semantic HTML with only

  ,

  ,

  • . This is contradictory: If we must preserve original content word-for-word, we cannot strip out the style attributes etc. But the instruction says to format it as clean semantic HTML, using those tags, and remove all styling etc. Likely we need to extract the textual content and reformat, preserving the words but not the original markup. The phrase "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" likely refers to the textual content, not the markup. So we should keep the exact wording, but we can change tags. Thus we need to output something like:

    Let's Write Africa's Story Together!

    Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.

    Then maybe empty paragraphs removed. Then we have a Job Description heading. According to rules, we could treat that as a section header? It's not in the list but could be considered a section header. However they said use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). "Job Description" could be a section header; we could use

    Job Description

    . Then the paragraph after that is the description. Then we have "Key responsibilities will include amongst others the following:" maybe as a

    or

    ? It's a heading before a list. Could be

    Key responsibilities

    . But they said use

    for section headers like Responsibilities. So we could treat "Key responsibilities will include amongst others the following:" as a

    maybe. But better to make it a

    Key responsibilities

    and then the list. But we must preserve original wording exactly. If we change the heading text, we would be altering content. So we need to keep the exact phrase: "Key responsibilities will include amongst others the following:" as text. If we wrap it in

    , we are not changing the text, just the tag. That's allowed. Similarly for each bold heading like "Financial Planning Domain Expertise" etc. Those are headings for each responsibility. Should we treat them as

    ? They are subheadings. The instruction says use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't forbid using

    for other headings, but we could also keep them as

    with . However to be safe, we could keep them as

    with inside, as that preserves the bold tag. But we are not allowed to add CSS classes or inline styles, but we can keep . That's fine. But the list items are already in

    • . We need to keep them as
      • . Ensure no extra tags. We also have "Qualifications and Experience required:" heading, then a
        with items, then another
        after a paragraph with a non-breaking space? Actually after the first
        there is a

         

        (non-breaking space) then another
        with more items. We need to preserve those as separate
        blocks. Then we have "Skills" heading, then a paragraph with a list of skills separated by commas. That is not a list; it's a sentence. We should keep as

        with the text. Then "Competencies" heading, then empty

        tags etc. Probably ignore empty tags. Then "Education" heading, then paragraph with "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent (Required)". Keep as

        . Then "Closing Date" heading, then paragraph with "11 September 2026 , 23:59". Keep as

        . Then a paragraph with italic bold statement about appointment. Then a paragraph with italic emphasis-2: "The Old Mutual Story!" Keep as

        with The Old Mutual Story! maybe. We must remove empty

        tags. We must not add any extra content. Now produce HTML. We'll start with the title. Let's extract the text pieces: 1. Let's Write Africa's Story Together! 2. Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. 3. (blank lines) 4. Job Description 5. The Senior Feature Analyst leads the analysis and design of complex, industry aligned solutions by translating business needs into detailed functional specifications. Operating at a self-directed level, the role fosters strong crossfunctional relationships and collaborates closely with Product Owners, Solution Architects, Designers, and business stakeholders to drive product outcomes and ensure end-to-end alignment. This job provides thought leadership on business processes and leads solution development that promotes efficiency, scalability, and customer value. It guides and mentors other feature analysts, supporting the maturity of the practice and delivery of high-quality features. Additionally, this job supports product leadership in managing scope, stakeholder expectations, and the timely delivery of strategic initiatives. 6. Key responsibilities will include amongst others the following: 7. Financial Planning Domain Expertise - Provide subject matter proficiency in financial planning, wealth management, advisor practices, and industry tool usage (such as CRM, xPlan, and advisory portals) to the agile team. 8. Backlog & Agile Delivery - Support prioritizing and planning work activities within the agile team, creating and prioritizing product backlogs aligned with product vision, and refining user stories and enabler stories. 9. Requirements & Process Modeling - Lead the refinement of complex requirements by decomposing features into well-defined user stories detailing scenarios, alternative flows, and process maps for advisor and client journeys. 10. Cross-Functional Collaboration - Partner with cross-functional release teams, process engineers, and business stakeholders to ensure solutions meet customer and adviser needs while scaling efficiently. 11. Research & Modernization - Drive innovative research into financial technology trends, advisory tools, and automation opportunities to modernize systems and enhance end-user value. 12. Quality & Acceptance Criteria - Own and drive the Definition of Done, writing effective acceptance criteria that facilitate improved efficiency, test coverage, and test automation. 13. Practice Leadership & Management - Drive the feature analyst practice, mentor team members, contribute to standard methodologies, and participate in recruitment, performance management, and talent stewardship. 14. Qualifications and Experience required: - Bachelor’s Degree in Information Technology, Computer Science, Finance, or equivalent. - Business Analysis certification. - 7+ years of experience as a business analyst or systems analyst in a senior or strategic role. - Deep domain experience within the financial planning sector, with a robust understanding of advisor practices and how financial planning tools operate and are applied in the industry. - Proven agile experience, with a solid understanding of methodology and principles (SAFe advantageous). - High-level understanding of architectural landscapes, API integration pipelines, and CRM systems (e.g., xPlan). - Strong technical knowledge, data interpretation skills, and proficiency in tools like JIRA, Confluence, Figma, and MIRO. - Post-graduate qualification in finance, digital transformation, or information technology. - Lean Six Sigma Certification. - In-depth knowledge of Old Mutual products, wealth platforms, and internal processes. 15. Skills - Adaptive Thinking, Analytics Software, Application Development, Business Intelligence (BI) Analysis, Computer Literacy, Database Reporting, Data Compilation, Data Controls, Data Modeling, Data Recovery, Evaluating Information, Gap Analysis, IT Architecture, Requirements Development, User Requirements Documentation 16. Competencies - (maybe none) 17. Education - NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent (Required) 18. Closing Date - 11 September 2026 , 23:59 19. The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question. 20. The Old Mutual Story! We need to wrap each piece appropriately. We need to decide which are headings (

        ) and which are paragraphs (

        ). According to 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 the following as

        : - Job Description? Not in list but could be considered a section header. Might be safer to use

        with ? But we can use

        as it's a section header. The instruction says "e.g." not exhaustive, so we can use

        for any section header. I'll use

        for Job Description. - Key responsibilities will include amongst others the following: This is a heading for responsibilities; we can use

        . - Each subheading like Financial Planning Domain Expertise etc. Could be considered subsection headings; but not required. We could keep them as

        with . However they are bold headings; we could also use

        but that would change hierarchy. Safer to keep as

        with inside. - Qualifications and Experience required: could be

        . - Skills: could be

        . - Competencies: maybe

        but empty. - Education:

        . - Closing Date:

        . - The appointment will be made... maybe

        . - The Old Mutual Story! maybe

        with . Now list items: Already in

        • . We'll keep them. Now we need to ensure we don't have any
          tags. We'll replace
          with space? The original text had
          inside the description paragraph. We must preserve the content word-for-word, but we cannot have
          tags in output. However we can convert line breaks to spaces? The instruction: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove
          we are removing content. But we also cannot use
          tags per rules. This is a conflict. Likely we should treat
          as just line breaks that we can ignore and replace with a space, preserving the words. The original content includes the
          as markup, not visible text. The visible text is the same with or without
          . So we can drop the
          tags and just have a space. That preserves the wording (the words remain). I think it's acceptable. Thus we will take the description paragraph and replace
          with a space. Now produce HTML. Let's construct:

          Let's Write Africa's Story Together!

          ? Actually title maybe not a section header. But we can use

          . I'll use

          for title. But the title is bold; we can keep inside

          . So:

          Let's Write Africa's Story Together!

          Next paragraph:

          Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.

          Then maybe skip empty paragraphs. Then

          Job Description

          Then the description paragraph (with
          replaced by space). Let's copy the text exactly: "The Senior Feature Analyst leads the analysis and design of complex, industry aligned solutions by translating business needs into detailed functional specifications. Operating at a self-directed level, the role fosters strong crossfunctional relationships and collaborates closely with Product Owners, Solution Architects, Designers, and business stakeholders to drive product outcomes and ensure end-to-end alignment. This job provides thought leadership on business processes and leads solution development that promotes efficiency, scalability, and customer value. It guides and mentors other feature analysts, supporting the maturity of the practice and delivery of high-quality features. Additionally, this job supports product leadership in managing scope, stakeholder expectations, and the timely delivery of strategic initiatives." Make sure there is no extra spaces. Wrap in

          . Then

          Key responsibilities will include amongst others the following:

          Then we have subheadings each with a
          • . We'll keep each as:

            Financial Planning Domain Expertise

            • Provide subject matter proficiency in financial planning, wealth management, advisor practices, and industry tool usage (such as CRM, xPlan, and advisory portals) to the agile team.
            Similarly for others. Note: The original had
            before each heading. We'll ignore empty

            . Now after the last responsibility heading, we have

            Qualifications and Experience required:

            Then we have two
            blocks separated by a

             

            (non-breaking space). We'll output first
            then second
            . Ensure we keep the
            • items exactly. First
              items:
              • Bachelor’s Degree in Information Technology, Computer Science, Finance, or equivalent.
              • Business Analysis certification.
              • 7+ years of experience as a business analyst or systems analyst in a senior or strategic role.
              • Deep domain experience within the financial planning sector, with a robust understanding of advisor practices and how financial planning tools operate and are applied in the industry.
              • Proven agile experience, with a solid understanding of methodology and principles (SAFe advantageous).
              • High-level understanding of architectural landscapes, API integration pipelines, and CRM systems (e.g., xPlan).
              • Strong technical knowledge, data interpretation skills, and proficiency in tools like JIRA, Confluence, Figma, and MIRO.
              Then second
              items:
              • Post-graduate qualification in finance, digital transformation, or information technology.
              • Lean Six Sigma Certification.
              • In-depth knowledge of Old Mutual products, wealth platforms, and internal processes.
              Note: The original had a

               

              between them; we can just put them consecutively. Now

              Skills

              Then paragraph with skills list: "Adaptive Thinking, Analytics Software, Application Development, Business Intelligence (BI) Analysis, Computer Literacy, Database Reporting, Data Compilation, Data Controls, Data Modeling, Data Recovery, Evaluating Information, Gap Analysis, IT Architecture, Requirements Development, User Requirements Documentation" Wrap in

              . Now

              Competencies

              Then maybe no content; we could output nothing or just an empty

              ? Better to omit if no content. But we must preserve original content; there were empty

              tags etc. There's no actual text after Competencies heading besides empty tags. So we can output just the heading and then maybe nothing. But we should not add extra content. We'll output the heading and then maybe a

              ? That would add empty paragraph not originally there. Better to just output the heading and then move on; but we need to wrap any text in

              . Since there is no text, we can omit. Thus after

              Competencies

              we can just continue. Now

              Education

              Then paragraph: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent (Required)" Note there are two spaces before "(Required)". We'll preserve. Wrap in

              . Now

              Closing Date

              Then paragraph: "11 September 2026 , 23:59" Note there is a space before comma? Actually original: "11 September 2026 , 23:59". We'll keep exactly. Wrap in

              . Then paragraph with italic bold: "The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question." Wrap in

              . Then final paragraph: "The Old Mutual Story!" We need to preserve the content but we cannot keep class or span. We can keep The Old Mutual Story! dropping the span and class.