,

,

• . No other tags. Must preserve all original content word-for-word, no additions, deletions, rephrasing. Must remove any tags like , , etc? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. But we need to format as clean semantic HTML using only allowed tags. We can keep the text content as is, but we cannot keep the original HTML tags like

  etc. We need to output only the cleaned HTML with allowed tags. The original content includes many tags and text. We must preserve the words exactly as they appear, but we can wrap them in appropriate tags. We need to identify sections: headings like "Responsibilities", "Customer Service", etc. Use

  for section headers. The original uses

  for Responsibilities,

  for subheadings. We need to use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should map each heading to

  . The original headings are

  Responsibilities

  then

  Customer Service

  etc. We need to output

  Responsibilities

  then each subheading maybe also as

  ? The instruction says use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So each of those should be

  . The original has many subheadings under responsibilities (Customer Service, Solutions Analysis, etc). Those are also headings but maybe they are subsections; we could treat them as regular paragraphs? The instruction says use

  for section headers, not necessarily for subheadings. But we could also use

  for each subheading? It says "e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". Those are main sections. The subheadings like "Customer Service" are part of responsibilities section; they could be considered headings but not required to be

  . The rule says use

  for section headers (e.g. Responsibilities, Qualifications...). So we should use

  for those main headings. For subheadings, we can just keep them as plain text? But they are headings in the original. The instruction says preserve ALL original content word-for-word, do not add, remove, summarise, or rephrase. So we must keep the text "Customer Service" exactly as appears. We can wrap it in a

  maybe? Or we could keep it as is, but we need to preserve the text. The original has

  Customer Service

  then a

  ... So we need to output the text "Customer Service" somewhere. Could we just keep it as plain text? The instruction says use

  for introductory paragraphs and general text, and

  • for list items. It doesn't forbid using other tags for headings besides

    . But we must use

    for section headers. So we can use

    Responsibilities

    then for each subheading we could just keep the text as part of a paragraph? But the original has

    Customer Service

    then a

    ... So the heading "Customer Service" is separate. We could treat it as a heading but not required to be

    . The rule only mandates using

    for section headers like Responsibilities, Qualifications, etc. It doesn't forbid using other heading tags? It 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 we cannot use other tags for subheadings, but we should avoid extra tags. Probably we should just keep the subheading text as part of a paragraph? But that would lose the heading distinction. However we must preserve the original content word-for-word, including the heading tags? The original includes

    Customer Service

    . If we remove the

    tags, we are removing markup but preserving the words "Customer Service". That's okay because we are not removing content, just markup. The words remain. So we can output "Customer Service" as plain text (maybe within a

    ? but that would add extra text). The instruction says use

    for introductory paragraphs and general text. So we could output the heading text as a paragraph? But that would add extra content (the word "Customer Service" is not a paragraph of description; it's a heading). However we can still output it as a paragraph; it's still text. The instruction doesn't forbid using

    for headings, just says use

    for section headers. So we should not use

    or

    . So we can just output the heading text as part of a paragraph? But that would change the structure. However we must preserve the words exactly, but we can wrap them in

    maybe. That would add

    tags around "Customer Service". That's okay because we are not adding new words, just wrapping. The content remains "Customer Service". So we can output

    Customer Service

    maybe. But the instruction says use

    for introductory paragraphs and general text. Headings are not general text; they are headings. But we can still use

    for them? Might be okay. Better approach: Use

    for main sections like "Responsibilities". Then for each subheading like "Customer Service", we can just output it as a paragraph (maybe as part of the responsibilities section). But we need to preserve the order and content. Let's parse the original: Original snippet:

    Let's Write Africa's Story Together!

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

    Responsibilities

    Customer Service

    Carry out standard customer service activities and handle simple customer inquiries.

    Solutions Analysis

    Assess compliance with established standards and protocols for routine inquiries.

    Receiving Visitors

    Receive visitors and assist with various requests for information, referring more complex matters to colleagues.

    Customer Relationship Management (CRM) Data

    Ensure that basic customer details held in the system are accurate, and make notes of follow-up actions that have been promised, together with notes of actions taken during each sales call.

    Customer Needs Clarification

    Interview the customer, following a multilevel sales script, to clarify the customer's requirements.

    Customer Relationship Development / Prospecting

    Make calls (by telephone or in person) to allocated potential customers to develop relationships. Provide a first point of contact for resolving customer queries and complaints.

    Operational Compliance

    Follow a range of mandatory procedures to ensure that work is carried out to the required quality standards and/or to ensure adherence to external regulatory codes and internal codes of conduct.

    Business Development

    Carry out routine business development support tasks and assist others by following established procedures.

    Sales Opportunities Creation

    Identify potential customers by obtaining information, referrals, and recommendations from existing customers.

    Data Exploration

    Select appropriate data from information provided by others and input that data into spreadsheets or standard formats.

    Network of Influence

    Demonstrate understanding of the value of networking by participating in and contributing to a network of people, technologies, and ideas both inside and outside the company.

    Skills

    Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships

    Competencies

    Balances Stakeholders
    Builds Networks
    Communicates Effectively
    Customer Focus
    Ensures Accountability
    Instills Trust
    Interpersonal Savvy
    Manages Complexity

    Education

    NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)

    Closing Date

    30 July 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 output clean HTML using only

    ,

    ,

    • . No other tags. So we must remove all style attributes, class attributes, , , , etc. But we must preserve the text content word-for-word. So we need to output the text exactly as appears, but without the markup tags. However we can wrap them in allowed tags. We need to preserve all original content word-for-word. That includes the text "Let's Write Africa's Story Together!" which is HTML entity for apostrophe. Should we output the literal characters? The original includes ' which is HTML entity for apostrophe. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must output the exact characters as they appear, including the HTML entity? The original text includes "Let's Write Africa's Story Together!" with ' entities. Should we keep them as is? Probably yes, because that's part of the content. But we are to output HTML; we could output the literal characters "Let's" but that would be a change (replacing ' with '). That would be a rephrase? It would be a change in representation. The instruction says preserve ALL original content word-for-word. So we must keep the exact string including the entity. So we should output "Let's Write Africa's Story Together!" exactly. Similarly, there are many  ? Not present. There are tags etc. We must not output those tags, but we must keep the text inside them. For example, Skills becomes "Skills". The original has Skills then some text after. So we need to output "Skills" as plain text. We need to produce HTML using only

      ,

      ,

      • . So we can structure:

        Responsibilities

        Customer Service

        Carry out standard customer service activities and handle simple customer inquiries.

        Solutions Analysis

        Assess compliance with established standards and protocols for routine inquiries.

        ... and so on. But we need to preserve the heading "Customer Service" as a separate line? The original had

        Customer Service

        then a

        ... So we can output

        Customer Service

        then the description paragraph. That preserves the words. Similarly for each subheading. We also have "Skills" section: there is Skills then a list of skills separated by commas. The original after that has a paragraph with a long list of skills separated by commas, then some
        etc. So we need to output that list as plain text maybe within a

        . But the instruction says use

        • for list items (duties, requirements, qualifications, skills). So for skills, we should output them as list items
        • . The original lists skills separated by commas, not as separate list items. But we can treat each skill as a list item? The instruction says use
          • for list items (duties, requirements, qualifications, skills). So we should convert the comma-separated list into
            • items. However we must preserve the original content word-for-word. If we split the list into separate
            • items, we are adding punctuation? Actually we are not adding words, just breaking the list into separate items. The original text is a single paragraph: "Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". We need to preserve that exact string. If we split into multiple
            • , we would be altering the text (adding line breaks and list tags). That would be adding markup but not changing the words. The content inside the
            • would be each skill phrase, but we would need to split the string at commas and maybe spaces. That would change the order? Not really, but we would be inserting list tags and line breaks, but the words remain the same. However we would be adding commas? Actually we would be removing commas between items? If we split, we might need to keep commas? The instruction says do not add, remove, summarise, or rephrase. Adding list tags is not adding content, but we are restructuring. However we are adding
            • tags and maybe line breaks, but the textual content inside each
            • would be the skill phrase without commas? That would remove commas, which is removing punctuation. That might be considered removal. Better to keep the entire string as a single

              maybe. But the instruction says use

              • for list items (duties, requirements, qualifications, skills). So for skills, we should output them as list items. But we must preserve the original content word-for-word. If we convert the comma-separated list into separate
              • items, we are effectively removing commas and adding list structure. That might be considered a change. However the instruction says "Use
                • for list items (duties, requirements, qualifications, skills)". So we must use that for skills. So we need to output a
                  with
                  • items each containing a skill phrase. The original skill phrases are separated by commas; we can split on ", " to get each phrase. That would remove the commas, but the phrase includes the comma? Actually the phrase includes the preceding space? The original string: "Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". If we split on ", " we get each phrase without the comma. That removes the comma, which is a character. That would be removing punctuation, which might be considered removal. But maybe it's acceptable because we are not altering the words themselves, just separating them. The instruction says "do not add, remove, summarise, or rephrase". Removing commas could be considered removal of characters. However the instruction might be interpreted as not altering the textual content, but we can restructure markup. The safest is to keep the entire string as a single

                    and not use

                    . But the instruction explicitly says use
                    • for list items (skills). So we must use that. Thus we need to output a
                      with
                      • items each containing a skill phrase exactly as appears (including any trailing spaces?). The original includes commas separating them, but we can treat each phrase as a separate item without commas. The phrase includes the preceding space? Actually after splitting, the first phrase is "Consultative Selling". That's fine. The next is "Customer Feedback Management". That's fine. So we can output each as
                      • Consultative Selling
                      etc. That preserves the words exactly (the phrase). The commas are removed, but they are not part of the phrase; they are separators. The phrase itself does not contain a comma. So we are