OMF Financial Consultant (OMF Rustenburg)

for paragraphs,

for section headers,

• for lists. No CSS classes, inline styles, divs, br tags. Preserve all content word-for-word. First, I'll analyze the input. It contains various tags: p with styles, spans, b, h1, h2, h3, i, etc. There are empty paragraphs. The content includes: - Introductory text: "Let's Write Africa's Story Together!" and "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 section with subsections: Customer Service, Solutions Analysis, Receiving Visitors, CRM Data, Customer Needs Clarification, Customer Relationship Development / Prospecting, Operational Compliance, Business Development, Sales Opportunities Creation, Data Exploration, Network of Influence. - Then "na" (maybe a stray). - Skills: a comma-separated list. - Competencies: a list of items each followed by empty h3 tags. - Education: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent" - Closing Date: "13 August 2026 , 23:59" - A note about appointment from designated group. - "The Old Mutual Story!" at the end. I need to structure this. The rules: Use

  for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. In the input, we have "Responsibilities" as h1, then subsections as h2. But the rule says use h4 for section headers. Should I treat each h2 as a subsection under Responsibilities? 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 mention subsections. However, the input has nested headings. I think we should keep the hierarchy: maybe Responsibilities as h4, and each sub-responsibility as h4? But the rule says only h4 for section headers. Could also use h4 for main sections and maybe h5 for subsections? But the rule only allows h4. It says "Use

  for section headers". It doesn't forbid other heading levels, but it says "Use

  for section headers". To be safe, I'll use h4 for all section headers, including subsections? But the example includes "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". Those are top-level sections. The subsections like "Customer Service" are part of Responsibilities. In typical job descriptions, they might be bullet points. However, the input has them as headings with paragraphs. I could treat each as a list item under Responsibilities. But the rule says "Use

  • for list items (duties, requirements, qualifications, skills)". The responsibilities are duties. So I could make a list of responsibilities, each with a title and description. But the input has each as a heading followed by a paragraph. I need to preserve content word-for-word. I could structure as:

    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.
    ...
    But the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means I cannot add tags if they weren't there. The original has headings (h2) and paragraphs. I could keep the headings as h4? But the rule says only h4 for section headers. Maybe I should keep the h2 as h4? But then there would be multiple h4s. That's okay. The rule doesn't say only one h4. It says "Use

    for section headers". So I can use h4 for each subsection. However, the example list includes "Responsibilities" as a section header, not each duty. But the input has "Responsibilities" as h1, then each duty as h2. I think the best is to treat "Responsibilities" as a section header (h4) and then each duty as a list item with the duty title and description. But the duty titles are headings in the original. To preserve word-for-word, I need to include the duty titles exactly as they appear. I could do:

    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.

    ... But that would be many h4s. The rule says "Use

    for section headers". It doesn't say you can't have multiple h4s. It might be acceptable. However, the rule also says "Use

    • for list items (duties, requirements, qualifications, skills)". The duties are list items. So perhaps the intended structure is to have a section header "Responsibilities" then a list of duties. But the duties have titles and descriptions. Could be a list of items where each item includes the title and description. But the original has them as separate headings and paragraphs. To preserve exactly, I might need to keep the headings as they are but convert to h4. I'll check 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 mention subsections. But the input has "Customer Service" etc. as h2. They are not in the example list. However, they are essentially "Key Duties". The example includes "Key Duties". So maybe "Customer Service" etc. are key duties. So I could have a section "Key Duties" or "Responsibilities" and then list them. But the input already has "Responsibilities" as a heading. I'll keep "Responsibilities" as h4, then each duty as a list item with the duty name and description. However, the duty names are headings in the original. To preserve word-for-word, I must include the exact text "Customer Service", "Solutions Analysis", etc. I can put them as bold or as part of the list item. But the rule says no CSS classes, no inline styles, but bold is allowed? It says no inline styles, but or are HTML tags, not styles. The input uses for bold. I can keep if present. But the rule says "No CSS classes, no inline styles, no

      s, no
      tags". It doesn't forbid or . However, the output should be clean semantic HTML. Using is semantic. But the instruction says "Preserve ALL original content word-for-word". That includes the bold markup? The original has tags around some headings. In the input, "Job Description" is wrapped in . "Skills" and "Competencies" and "Education" and "Closing Date" are wrapped in . The responsibilities subsections are in

      tags, not bold. The competencies list items are followed by empty

      tags. That's weird. I need to parse the input text as plain text? The user gave me HTML but said "Job description:" and then the HTML. I think they want me to convert that HTML to clean semantic HTML. So I should strip all the messy tags and restructure. Let me extract the text content in order: 1. "Let's Write Africa's Story Together!" (from span with emphasis-2 and b) 2. "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." (from span with emphasis-2) 3. "Job Description" (bold) 4. "Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts." 5. "Responsibilities" (h1) 6. "Customer Service" (h2) 7. "Carry out standard customer service activities and handle simple customer inquiries." 8. "Solutions Analysis" (h2) 9. "Assess compliance with established standards and protocols for routine inquiries." 10. "Receiving Visitors" (h2) 11. "Receive visitors and assist with various requests for information, referring more complex matters to colleagues." 12. "Customer Relationship Management (CRM) Data" (h2) 13. "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." 14. "Customer Needs Clarification" (h2) 15. "Interview the customer, following a multilevel sales script, to clarify the customer's requirements." 16. "Customer Relationship Development / Prospecting" (h2) 17. "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." 18. "Operational Compliance" (h2) 19. "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." 20. "Business Development" (h2) 21. "Carry out routine business development support tasks and assist others by following established procedures." 22. "Sales Opportunities Creation" (h2) 23. "Identify potential customers by obtaining information, referrals, and recommendations from existing customers." 24. "Data Exploration" (h2) 25. "Select appropriate data from information provided by others and input that data into spreadsheets or standard formats." 26. "Network of Influence" (h2) 27. "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." 28. "na" (stray) 29. "Skills" (bold) 30. "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" 31. "Competencies" (bold) 32. "Balances Stakeholders" 33. "Builds Networks" 34. "Communicates Effectively" 35. "Customer Focus" 36. "Ensures Accountability" 37. "Instills Trust" 38. "Interpersonal Savvy" 39. "Manages Complexity" 40. "Education" (bold) 41. "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent" 42. "Closing Date" (bold) 43. "13 August 2026 , 23:59" 44. "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." (italic bold) 45. "The Old Mutual Story!" (italic bold) Now, I need to output clean HTML. I'll structure as: - Intro paragraphs: first two sentences. - Job Description paragraph. - Responsibilities section: header h4 "Responsibilities", then each duty as a list item? Or as subsections with h4? The rule says use ul li for list items (duties). So I'll make a list of duties. Each duty has a title and description. I'll put the title in bold (since original had them as headings) and then the description. But to preserve word-for-word, I need to include the exact title text. I'll do:

      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.
      ...

      But the original has each duty as a heading followed by a paragraph. That's essentially a definition list. However, the rule says use ul li for list items. I think it's acceptable. - Skills: header h4 "Skills", then list of skills. The skills are comma-separated. I'll split by commas and make each a list item. But preserve the exact text? The rule says preserve all original content word-for-word. If I split, I'm altering the formatting. But the original is a single paragraph with commas. The rule says "Use

      • for list items (duties, requirements, qualifications, skills)". So skills should be a list. I'll split by commas and trim. But need to keep the exact skill phrases. I'll split on ", ". - Competencies: header h4 "Competencies", then list of competencies. Each competency is a line (original had each followed by empty h3). I'll make a list. - Education: header h4 "Education", then paragraph. - Closing Date: header h4 "Closing Date", then paragraph. - The appointment note: paragraph. - The Old Mutual Story: paragraph. Also, there is "na" stray. Should I include? It appears after responsibilities. Probably an artifact. The rule says remove stray numbers or formatting artifacts. "na" might be an artifact. I'll omit it. Now, I need to output only HTML, no markdown fences. Let's construct. First, wrap introductory paragraphs in

        :

        Let's Write Africa's Story Together!

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

        Then 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.

        Then Responsibilities:

        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:

        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:

        Competencies

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

        Education

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

        Closing Date:

        Closing Date

        13 August 2026 , 23:59

        Appointment note:

        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:

        The Old Mutual Story!

        Check for any missing content: The "Job Description" heading was bold in original. I didn't include a header for "Job Description". The rule says use h4 for section headers like "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 section. I could include it as h4. But the content