Aspiring Financial Advisor

for intro 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
  , no
  . 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. We have raw HTML with many tags and styles. Need to extract the textual content, preserving word-for-word, then format as semantic HTML. We must not add or remove content. So we need to output the same text but wrapped in appropriate tags. We need to identify sections: The original includes: -

  Let's Write Africa's Story Together!

  -

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

  -

  -

  -

  Aspires to be a Financial Advisor

  -

  -

  We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies.
  
  The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions.

  -

  -

  Skills

  -

  -

  -

  -

  -

  Competencies

  -

  -

  - Action Oriented

  Balances Stakeholders

  Builds Networks

  Collaborates

  Communicates Effectively

  Customer Focus

  Decision Quality

  Ensures Accountability

  -

  Education

  - Bachelors Degree (B), High School (Grade 12) (Required)

  -

  Closing Date

  - 20 October 2026 , 23:59

  -

  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.

  -

  -

  -

  The Old Mutual Story!

  We need to preserve all content word-for-word. That includes the text inside tags, including HTML entities like ' and " etc. We must not remove any characters. We need to output semantic HTML: Use

  for intro paragraphs and general text. Use

  for section headers (Skills, Competencies, Education, Closing Date, etc). Use

  • for list items (duties, requirements, qualifications, skills). However, the content does not have explicit list items; we have competencies listed as separate lines but not in list format. The rule says: Use
    • for list items (duties, requirements, qualifications, skills). If the original text is not in list format, we should not artificially create list items? The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we cannot change the structure to list if it wasn't a list originally. However, we can wrap paragraphs in

      . For section headers we use

      . The original had Skills, Competencies, etc. Those are section headers. We should convert those to

      tags, preserving the text inside (including the bold tags? We must preserve content word-for-word, but we are allowed to change markup to semantic HTML. The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That refers to the textual content, not the markup. So we can replace Skills with

      Skills

      as long as we keep the text "Skills". The bold tags are markup, not content. So we can drop them. Similarly for other headers. We need to decide what constitutes a section header. The original had: -

      Skills

      -

      Competencies

      -

      Education

      -

      Closing Date

      Also there is "Aspires to be a Financial Advisor" inside .... That seems like a job title? Actually it's a line: "

      Aspires to be a Financial Advisor

      " That could be considered a section header? Possibly "Aspires to be a Financial Advisor" is like a tagline. We could treat it as a heading? 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 forbid using

      for other headings, but we should follow the pattern. However, we could also just wrap it in

      as general text. The rule: "If text has no clear sections, just wrap paragraphs in

      tags". There are clear sections: Skills, Competencies, Education, Closing Date. Also maybe "Aspires to be a Financial Advisor" is a subtitle. We could treat it as a

      with emphasis? But we must preserve content. We could wrap it in

      as is. Also there is a line: "Action Oriented

      Balances Stakeholders
      Builds Networks
      Collaborates
      Communicates Effectively
      Customer Focus
      Decision Quality
      Ensures Accountability". This appears after the Competencies header and before Education. It seems to be a list of competencies, each followed by empty
      tags. The original likely had each competency as a heading? Actually the pattern: "Action Oriented
      Balances Stakeholders
      Builds Networks
      Collaborates
      Communicates Effectively
      Customer Focus
      Decision Quality
      Ensures Accountability". It seems each competency is followed by two empty

      tags. Possibly the original had each competency as a heading with some styling. But we need to preserve the text exactly: "Action Oriented", then "

      ", then "Balances Stakeholders", etc. However, we must output semantic HTML, not preserve the original markup. We can treat the list of competencies as items. The rule says use
      • for list items (duties, requirements, qualifications, skills). Competencies could be considered skills or qualifications. So we could make a
        with each competency as
        • . But we must preserve the content word-for-word: we cannot add or remove any text. If we change "Action Oriented
          Balances Stakeholders" into list items, we are removing the
          tags and the spacing. That would be removing markup, but the rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does that apply to markup? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". The "content" likely refers to the textual content, not the markup. However, the
          tags are markup, not content. So we could remove them as part of converting to semantic HTML. But we must ensure we don't lose any textual content. The text "Action Oriented" and "Balances Stakeholders" etc are present. The
          tags are empty, so they contain no content. Removing them does not remove any content. So it's okay. Thus we can convert the competencies block into a
          • list. Similarly, the "Skills" header currently has no list items after it; there is just empty paragraphs. So maybe there are no skills listed; we just keep the header and maybe no list. Education: after Education we have "Bachelors Degree (B), High School (Grade 12) (Required)". That's a line of text. Could be considered a requirement; we could keep as

            . Closing Date: after header we have "20 October 2026 , 23:59". Keep as

            . Then there is a paragraph with italic and 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.

            ". That's a note. We'll keep as

            . Finally, a line: "

            The Old Mutual Story!

            ". That's just a tagline. Keep as

            . We also have introductory paragraphs: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." plus blank paragraphs. We also have the line "Aspires to be a Financial Advisor" inside .... That could be considered a tagline or job title. We'll keep as

            . Then the paragraph: "We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies." plus the role at a glance sentence. That's two sentences separated by
            
            . We need to preserve the content word-for-word, including the double line break? The original had
            
            between the two spans. That's markup for line breaks. We need to preserve the content word-for-word, but we are converting to semantic HTML; we cannot use
            . The rule says no
            tags. So we need to represent line breaks somehow without
            . We could separate into two

            paragraphs. That would preserve the textual content (the sentences) but not the exact markup. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we split into two paragraphs, we are not removing any text; we are just changing how it's presented. The content (the sentences) remains same. The line break is not content; it's formatting. So it's acceptable. Thus we can make two

            for those sentences. Now we need to output only HTML, no markdown fences, no explanation. Let's construct: Start with maybe a

            for the title? The title "Let's Write Africa's Story Together!" could be considered a heading. But rule says use

            for section headers like Responsibilities, Qualifications, etc. Not explicitly forbidding other headings. Could use

            for that as well. But we could also keep as

            . I'd treat it as an introductory paragraph, maybe

            . However, it's emphasized with bold. Could be a tagline. I'll use

            . Similarly, "Old Mutual is a firm believer..." as

            . Then blank paragraphs: we have two empty

            . Those contain no content. Should we keep them? The rule says preserve ALL original content word-for-word. Empty paragraphs have no content, but they are markup. If we omit them, we are removing markup but not content. The rule likely expects we ignore empty paragraphs as they have no content. Safer to omit them because they add no meaningful content. However, if we strictly preserve markup, we would need to keep them. But we are converting to semantic HTML, not preserving markup. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". It doesn't say preserve markup. So we can drop empty paragraphs. Thus we skip empty paragraphs. Next: "

            Aspires to be a Financial Advisor

            " -> we can output as

            Aspires to be a Financial Advisor

            . (We drop u, b, span tags.) Next: The two sentences: we can output as two

            :

            We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies.

            The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions.

            Note: we must preserve the HTML entities ' and " exactly. So we keep them. Next: Skills header:

            Skills

            After that, there were empty paragraphs; no list items. So we just leave the header and maybe no list. Could add a

            after? But there is no content. We'll just output the header. Next: Competencies header:

            Competencies

            Then we need a list of competencies. The original list: Action Oriented, Balances Stakeholders, Builds Networks, Collaborates, Communicates Effectively, Customer Focus, Decision Quality, Ensures Accountability. We need to output as
            • Action Oriented
            • Balances Stakeholders
            ... etc. Note: Ensure we preserve the exact text, including spaces. The original had "Action Oriented" then "
            " then "Balances Stakeholders". So the text is exactly those phrases. We'll output each as
            • . Next: Education header:

              Education

              Then a paragraph: "Bachelors Degree (B), High School (Grade 12) (Required)". Note there are two spaces before "(Required)"? In original: "Bachelors Degree (B), High School (Grade 12) (Required)". There are two spaces between "12)" and "(Required)". We must preserve that exactly. So we output

              Bachelors Degree (B), High School (Grade 12) (Required)

              . Next: Closing Date header:

              Closing Date

              Then paragraph: "20 October 2026 , 23:59". Note there is a space before the comma after 2026? Original: "20 October 2026 , 23:59". Yes there is a space before comma. We must preserve that. So

              20 October 2026 , 23:59

              . Next: the appointment paragraph: "

              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.

              ". We'll output as

              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.

              . (We drop i and b tags.) Finally: the Old Mutual Story line: "

              The Old Mutual Story!

              ". Output as

              The Old Mutual Story!

              . Now we need to ensure we haven't missed any text. Let's scan original for any other text: - After Skills header, there were empty paragraphs and an
              etc. No text. - After Competencies header, there were empty paragraphs then