for intro paragraphs and general text. Use

for section headers (e.g., Responsibilities, Qualifications, etc). 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. So we must keep the exact text as given, but we need to format with tags. We need to parse the raw text (which includes HTML tags originally). The input includes many HTML tags with style attributes etc. We must strip those and produce clean semantic HTML. We must preserve content word-for-word, meaning we cannot change the text itself, only wrap it in tags. So we need to extract the textual content from the given HTML, ignoring tags, but preserving the text exactly as appears (including punctuation, spaces?). We need to be careful about HTML entities like ' which should be kept as apostrophe? The original text: "Let's Write Africa's Story Together!" The entity ' is an apostrophe. We should preserve the character? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. The original content includes the entity '. If we convert to apostrophe, that's a change. Safer to keep the entity as is? But the output is HTML, so we could keep the entity; it will render as apostrophe. That's fine. We'll keep the entity. We need to strip all original tags and style attributes, but keep the text nodes. Let's extract the text sequentially. Given input:

  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

  19 September 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 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). So we need to convert the headings: we have

  Responsibilities

  then many

  subheadings under Responsibilities (like Customer Service, Solutions Analysis, etc). According to rules, we should use

  for section headers. Likely each major section (Responsibilities, Skills, Competencies, Education, Closing Date, etc) should be

  . Subheadings like Customer Service etc maybe should be

  or maybe also

  ? 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 headings, but we should follow that. Probably we should treat each major heading as

  . Subheadings under Responsibilities could be treated as

  or maybe

  as well? But they are not listed as examples. Safer to treat them as

  (or maybe

  but risk deviating). The instruction: "Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It implies that for those specific section headers we should use

  . For other headings maybe we can still use

  or treat as

  . To be safe, we can treat all headings as

  . But the examples list only those; but using

  for Customer Service etc might be okay as it's still a section header. However, 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 headers. It just says use

  for section headers. So we can use

  for all headings. We also need to use

  • for list items (duties, requirements, qualifications, skills). So for lists like Skills (which is a comma-separated list) we need to convert to
    • items. Similarly, Competencies list (each line maybe separate). Also responsibilities list (the many responsibilities under each subheading) maybe should be list items? The rule says use
      • for list items (duties, requirements, qualifications, skills). So duties (responsibilities) should be list items. So we need to wrap each duty in
      • . The responsibilities are currently each under a subheading with a paragraph. We could treat each responsibility as a list item under a
        . The subheadings could be

        maybe. We need to preserve all original content word-for-word. So we cannot change wording, but we can restructure with tags. That's allowed. We need to output only HTML, no markdown. Let's extract the textual content in order, ignoring original tags. We'll go through the input and capture text nodes. I'll manually extract. Start: 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. (empty p) 4. (empty p) 5. "Responsibilities" 6. (empty h2) 7. "Customer Service" 8. "Carry out standard customer service activities and handle simple customer inquiries." 9. (empty p) 10. "Solutions Analysis" 11. "Assess compliance with established standards and protocols for routine inquiries." 12. (empty p) 13. "Receiving Visitors" 14. "Receive visitors and assist with various requests for information, referring more complex matters to colleagues." 15. (empty p) 16. "Customer Relationship Management (CRM) Data" 17. "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." 18. (empty p) 19. "Customer Needs Clarification" 20. "Interview the customer, following a multilevel sales script, to clarify the customer's requirements." 21. (empty p) 22. "Customer Relationship Development / Prospecting" 23. "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." 24. (empty p) 25. "Operational Compliance" 26. "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." 27. (empty p) 28. "Business Development" 29. "Carry out routine business development support tasks and assist others by following established procedures." 30. (empty p) 31. "Sales Opportunities Creation" 32. "Identify potential customers by obtaining information, referrals, and recommendations from existing customers." 33. (empty p) 34. "Data Exploration" 35. "Select appropriate data from information provided by others and input that data into spreadsheets or standard formats." 36. (empty p) 37. "Network of Influence" 38. "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." 39. (empty p) 40. (empty p) 41. "Skills" 42. (empty p) 43. (empty p) 44. "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" 45. (empty p) 46. (empty h3) 47. "Competencies" 48. (empty p) 49. (empty p) 50. "Balances Stakeholders" 51. (empty h3) 52. (empty h3) 53. "Builds Networks" 54. (empty h3) 55. (empty h3) 56. "Communicates Effectively" 57. (empty h3) 58. (empty h3) 59. "Customer Focus" 60. (empty h3) 61. (empty h3) 62. "Ensures Accountability" 63. (empty h3) 64. (empty h3) 65. "Instills Trust" 66. (empty h3) 67. (empty h3) 68. "Interpersonal Savvy" 69. (empty h3) 70. (empty h3) 71. "Manages Complexity" 72. (empty p) 73. (empty p) 74. (empty p) 75. "Education" 76. "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" 77. (empty p) 78. "Closing Date" 79. "19 September 2026 , 23:59" 80. (empty p) 81. (empty p) 82. (empty p) 83. (empty p) 84. "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." Actually the text inside includes italic and bold tags, but we need to preserve the text word-for-word, including the tags? The original content includes ... . According to rule preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes the tags? The original content includes those tags. However, we are supposed to output clean semantic HTML, not keep the original formatting tags. The instruction says "Return ONLY the cleaned job text." In the first part (job listing editor) they said remove formatting etc. But now the second part says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The input given includes HTML tags with styles etc. We need to strip those and produce clean semantic HTML. The instruction "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" refers to the textual content, not the markup. So we should ignore the original tags and just keep the text. So for the italic/bold part, we should extract the text: "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 should not keep the tags. So we treat that as plain text. Thus item 84 text: "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." 85. (empty p) 86. (empty p) 87. (empty p) 88. "The Old Mutual Story!" (inside span with emphasis-2, italic, bold bold). Actually the text: "The Old Mutual Story!" So the text is "The Old Mutual Story!" (with double bold). We'll keep that text. Now we have all text nodes. Now we need to produce HTML with

        for intro paragraphs and general text. Use

        for section headers. Use

        • for list items (duties, requirements, qualifications, skills). We need to decide structure. Intro paragraphs: first two lines: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These are introductory. So wrap each in

          . Then we have empty paragraphs (ignore). Then section "Responsibilities" as

          . Under Responsibilities, we have multiple subheadings each with a duty paragraph. According to rule, duties should be list items. So we could make a

          where each duty is
          • . The subheadings could be omitted or maybe we keep them as part of the duty text? The duty text currently does not include the subheading; the subheading is separate heading. We need to preserve all original content word-for-word, meaning we must keep the subheading text as well. So we need to include "Customer Service", "Solutions Analysis", etc as text. We could either keep them as headings (

            ) or as part of list items (maybe preceding the duty). The rule says use

            for section headers (e.g., Responsibilities...). It doesn't forbid using

            for subheadings. So we could treat each subheading as

            as well, and the duty paragraph as

            or maybe as part of list? But duties should be

            • . So perhaps we make each duty as
            • and include the subheading as part of the
            • text? That would change the original ordering (subheading then duty). But we could keep both:
            • Customer Service: Carry out ... but that adds punctuation not original. Can't add