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

  . Return only HTML. We need to parse the given job description text (which includes HTML tags and style attributes). We must extract the content and produce clean HTML. We must preserve all original content word-for-word. That means we cannot change wording, but we can change tags to semantic ones. Must keep the exact text content (including spaces, punctuation). We need to remove style attributes, classes, etc. Also need to remove empty tags. We need to identify sections: The original has:

  Let's Write Africa's Story Together!

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

  Job Description

  Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts.

  Responsibilities

  Customer Service

  Provide a quality service to customers while identifying opportunities to secure new business or support retention. Responsibilities may include processing cases, dealing with complex queries, and investigating and resolving customer problems.

  Solutions Analysis

  Analyze specific problems and issues to find the best solutions. Solutions could be technical or professional in nature.

  Receiving Visitors

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

  Customer Relationship Management (CRM) Data

  Schedule follow-up actions and enter relevant information into the CRM system after each contact with a customer to create a call plan and to ensure that the organization has quality data to enable effective customer retention and business development activities.

  Customer Needs Clarification

  Set clear objectives for each sales call or meeting; tailor standard materials to make presentations to decision-makers and influencers within the customer organization; and ask relevant questions to gather information, to evaluate the customer's level of interest, and to identify and respond to areas requiring further information or explanation.

  Customer Relationship Development / Prospecting

  Develop and implement a relationship management plan for potential customer accounts to identify and build relationships with relevant decision-makers and influencers within the customer organization and to enable effective two-way flow of information and resolution of issues.

  Operational Compliance

  Develop knowledge and understanding of the organization's policies and procedures and of relevant regulatory codes and codes of conduct to ensure own work adheres to those standards. Obtain authorization from a supervisor or manager for any exceptions from mandatory procedure.

  Business Development

  Monitor and assess sales and market data for a specific geographic region that will assist management in identifying areas in the market where business can be developed.

  Sales Opportunities Creation

  Develop a personal network within the business sector and represent the organization at business sector events. Obtain market intelligence and enhance the visibility and reputation of the organization, its products, and its services.

  Data Exploration

  Conduct research and select relevant information to enable analysis of key themes and trends using primary data sources and business intelligence tools.

  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.

  Requirements: Skills, Qualifications and Experience required

  • Grade 12 (Matric).
  • Valid Driver’s licence and Own Car
  • FAIS Compliance
  • Clear criminal and credit check
  • Minimum of 3 years working experience (preferably in sales)
  • Computer literacy (MS Word, Powerpoint and Outlook)
  • Excellent communication skills (written and verbal)
  • Presentations skills an added advantage

   

  Skills

  Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships

  Competencies

  Action Oriented

  Balances Stakeholders

  Builds Networks

  Collaborates

  Communicates Effectively

  Customer Focus

  Drives Results

  Ensures Accountability

  Education

  NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent

  Closing Date

  15 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 produce HTML with

  for paragraphs,

  for section headers. The sections: Responsibilities (currently

  Responsibilities

  then subheaders

  ...). According to rules, we should use

  for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we need to convert each section header to

  . Subheaders like Customer Service etc. Are they considered sub-sections? 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 other heading levels? It says use

  for section headers. Likely we should treat each major section as

  . Subsections maybe also

  ? But we could keep them as

  as well, but that might be odd. However we must preserve content word-for-word; we can change tags but not text. So we can change

  Responsibilities

  to

  Responsibilities

  . The subheaders like

  Customer Service

  could also become

  Customer Service

  or maybe we keep them as

  as they are sub-sections under Responsibilities. The rule didn't forbid using

  for any header. It said use

  for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It didn't say we cannot use other headings, but to be safe we can convert all heading tags to

  . However we must preserve the text exactly; changing

  to

  is allowed as it's just tag change, not content. So we will convert all heading tags (

  ,

  ,

  ) to

  . Also we need to wrap paragraphs in

  . The list items already in

  • . We should keep them as is, but ensure no extra attributes. The original
    • has no attributes, fine. We need to remove empty tags like
      ,
      ,
      , etc. Also remove stray spaces like   (the non-breaking space appears as a separate

       

      maybe). We should keep the content but remove empty tags. The non-breaking space is a character; we should keep it? It appears as a

       

      containing a non-breaking space. If we remove the

      tag, we would lose that space. But maybe it's just formatting; we could keep it as a

      with a space? The rule says preserve ALL original content word-for-word. So we must keep that non-breaking space character. If we wrap it in a

      tag, that's fine. But we could also keep it as a

      with that space. However we need to remove empty tags; this tag is not empty because it contains a non-breaking space. So we should keep it as

       

      (but we need to represent the entity). In HTML output we can just put the actual character or the entity. Safer to keep as   or just a space? The original is a non-breaking space (U+00A0). We can output as a plain space? That would change content. Better to output the entity  . But we can also just output a regular space; but that might be considered a change. The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact characters. The non-breaking space is a character; we can represent it as   or as the actual Unicode character. In HTML output, we can just include the character; it's fine. We'll output a literal non-breaking space? Might be tricky in this text. Safer to output  . But we also have many empty
      etc. Those should be removed entirely. Also there are
      empty. We need to produce final HTML with only meaningful content. Let's extract the meaningful text blocks: 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. Job Description (maybe as a heading? Actually it's Job Description inside a p. We'll treat as a heading? It's not a section header per list, but we could make it

      Job Description

      or keep as

      Job Description

      . The rule says use

      for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). "Job Description" is not in that list, but it's a heading. Could treat as

      as well? Might be okay. But to be safe, we could keep it as

      Job Description

      . However we need to use

      for section headers; but we are not required to forbid other tags for non-section headers. The rule: "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 other headings. So we can keep the bold text inside a

      . However we also need to remove inline styles and classes. So we will convert

      Job Description

      to

      Job Description

      . 4. The paragraph after that: "Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts." This is a paragraph. 5. Then Responsibilities section: heading Responsibilities, then subsections each with heading and paragraph. We need to decide how to structure: Could keep each subsection heading as

      and its paragraph as

      . That would be many

      tags. That's okay. 6. Then after responsibilities, we have a bold paragraph: "

      Requirements: Skills, Qualifications and Experience required

      " followed by

      list. We'll convert that heading to

      Requirements: Skills, Qualifications and Experience required

      (keeping the text). The inside can be removed; we just keep the text. 7. Then after list, there are some empty paragraphs and a non-breaking space paragraph. We'll keep the non-breaking space as

       

      maybe. 8. Then Skills heading:

      Skills

      followed by a line of text: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". We'll convert heading to

      Skills

      and the line as

      ...

      . 9. Then Competencies heading: similar, with list of competencies each preceded by
      empty tags. The text appears as: "Action Oriented
      Balances Stakeholders
      Builds Networks
      Collaborates
      Communicates Effectively
      Customer Focus
      Drives Results
      Ensures Accountability". So we need to parse that: It seems each competency is separated by empty
      tags. The actual text: "Action Oriented", then empty h3, then empty h3, then "Balances Stakeholders", etc. So we need to keep the text as is, but remove the empty h3 tags. So the resulting text should be: "Action OrientedBalances StakeholdersBuilds NetworksCollaboratesCommunicates EffectivelyCustomer FocusDrives ResultsEnsures Accountability"? Wait there is no spacing. Actually original: "Action Oriented
      Balances Stakeholders
      Builds Networks
      Collaborates
      Communicates Effectively
      Customer Focus
      Drives Results
      Ensures Accountability". So between each competency there are two empty h3 tags. If we remove those tags, we get concatenated words without spaces: "Action OrientedBalances StakeholdersBuilds NetworksCollaboratesCommunicates EffectivelyCustomer FocusDrives ResultsEnsures Accountability". That seems wrong; likely the original intended each competency on its own line, but the h3 tags were used as separators. However we must preserve content word-for-word, meaning we cannot remove the h3 tags if they are part of content? But they are tags, not content. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That refers to text content, not markup? It says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. I think it means the textual content, not the HTML tags. We can change tags but must keep the text exactly. So we can remove the empty h3 tags because they are not content. However removing them will cause the text to concatenate without spaces, altering the textual content (since the spaces between words are part of the text? Actually there is no space between the closing

      and the next word