for intro paragraphs and general text,

for section headers (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 the HTML. We have raw HTML with many style tags etc. We need to extract the textual content and produce semantic HTML. We must preserve all original content word-for-word. That means we cannot change wording, but we can change tags. We must keep the exact text content (including spaces? Probably preserve as is). We need to remove style attributes etc. We need to identify sections: The text includes: - Intro: "

  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." So intro 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." Then blank paragraphs (empty). Then "Job Description" bold heading. Then blank paragraphs. Then the sentence: "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 we have

  Responsibilities

  Customer Service

  ... etc. We need to convert section headers to

  . The original uses

  for Responsibilities, then

  for sub-sections like Customer Service, Solutions Analysis, etc. According to rules, we should use

  for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to treat each major section header as

  . Sub-sections 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 heading levels, but we should follow semantic HTML: likely we should keep sub-sections as

  as well? But they said use

  for section headers (list). Could interpret that only those specific section headers should be

  . Others maybe just

  . However, to preserve structure, we could treat each

  as

  as well, but that might be adding extra headers not in list. 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 heading levels for other headings, but we should avoid adding extra markup not needed. Safer: convert all heading tags (

  ,

  ,

  ) to

  for consistency, as they are section headers. But the rule says use

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

  for other headings. It says use

  for section headers. So we can treat all headings as section headers and wrap them in

  . That seems okay. Then we need to use

  • for list items (duties, requirements, qualifications, skills). The responsibilities are listed as separate paragraphs under each subheading. They are not in a list originally. Should we convert them to list items? The rule says use
    • for list items (duties, requirements, qualifications, skills). If the original text already has them as separate paragraphs, we could keep them as

      . But the rule says to use

      • for list items. It implies if there are duties etc that are listed, we should put them in
        • . However, we must preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing format from

          to

        • is not adding or removing content, just changing tags. That's allowed because we are not altering text. So we can wrap each duty in
        • inside a
          . But we need to decide grouping: The responsibilities are grouped under subheadings like Customer Service, Solutions Analysis, etc. Each subheading has a paragraph describing duty. Could treat each duty as list item under a
          for Responsibilities section. Or we could keep subheadings as

          and then a

          with
          • for each duty. Similarly, Skills section: a paragraph listing skills separated by commas. Should we convert to
            • each skill? The rule says use
              • for list items (duties, requirements, qualifications, skills). So yes, we should split the comma-separated list into items. However, we must preserve original content word-for-word. Splitting into separate
              • does not change wording, just separates. That's okay. Competencies: list of items each preceded by
                etc. The original shows:

                Competencies

                Balances Stakeholders
                Builds Networks
                Communicates Effectively
                Customer Focus
                Ensures Accountability
                Instills Trust
                Interpersonal Savvy
                Manages Complexity
                ... It seems each competency is followed by empty

                tags. So the text "Balances Stakeholders

                tags. We must preserve all original content word-for-word. That means we cannot remove those tags. However, the instruction says to return clean semantic HTML, removing all formatting artifacts etc. But also says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. This is contradictory: we must remove styling tags etc but preserve content. The content includes the text; the tags are not content but formatting. So we can remove the style tags etc, but we must keep the textual content. The
                tags are also formatting; we can remove them as they are not content. The content is the words "Balances Stakeholders", etc. So we can drop the empty tags. Thus we need to extract plain text content and then wrap in appropriate semantic tags. Let's extract the textual content sequentially: 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. (blank lines) 4. "Job Description" 5. (blank) 6. "Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts." 7. "Responsibilities" 8. "Customer Service" 9. "Carry out standard customer service activities and handle simple customer inquiries." 10. (blank) 11. "Solutions Analysis" 12. "Assess compliance with established standards and protocols for routine inquiries." 13. (blank) 14. "Receiving Visitors" 15. "Receive visitors and assist with various requests for information, referring more complex matters to colleagues." 16. (blank) 17. "Customer Relationship Management (CRM) Data" 18. "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." 19. (blank) 20. "Customer Needs Clarification" 21. "Interview the customer, following a multilevel sales script, to clarify the customer's requirements." 22. (blank) 23. "Customer Relationship Development / Prospecting" 24. "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." 25. (blank) 26. "Operational Compliance" 27. "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." 28. (blank) 29. "Business Development" 30. "Carry out routine business development support tasks and assist others by following established procedures." 31. (blank) 32. "Sales Opportunities Creation" 33. "Identify potential customers by obtaining information, referrals, and recommendations from existing customers." 34. (blank) 35. "Data Exploration" 36. "Select appropriate data from information provided by others and input that data into spreadsheets or standard formats." 37. (blank) 38. "Network of Influence" 39. "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." 40. (blank) 41. (maybe a non-breaking space) "na" appears? Actually after the responsibilities block we see: "

                 

                na
                " There's a non-breaking space then "na". That seems like an artifact. "na" maybe stands for not applicable? It's part of content? It appears as stray text "na". According to rules, we should remove stray numbers or formatting artifacts. "na" could be considered a stray artifact. We should remove it. So we ignore "na". 42. (blank lines) 43. "Skills" 44. (blank) 45. "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" 46. (blank) 47. "Competencies" 48. (blank) 49. (blank) 50. "Balances Stakeholders" 51. "Builds Networks" 52. "Communicates Effectively" 53. "Customer Focus" 54. "Ensures Accountability" 55. "Instills Trust" 56. "Interpersonal Savvy" 57. "Manages Complexity" 58. (blank) 59. (blank) 60. "Education" 61. (blank) 62. (blank) 63. "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent" 64. (blank) 65. (blank) 66. (blank) 67. "Closing Date" 68. (blank) 69. (blank) 70. "01 October 2026 , 23:59" 71. (blank) 72. (blank) 73. "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." 74. (blank) 75. (blank) 76. "The Old Mutual Story!" We need to preserve the italic and bold tags? The instruction says preserve ALL original content word-for-word. The content includes the text inside those tags, but the tags themselves are formatting. We can drop them but keep the text. However, the text includes the phrase with bold and italic. We should output the text without those tags, as they are formatting. The rule says remove social sharing text, author bylines, navigation, etc. It didn't explicitly say to remove HTML tags, but we are to output clean semantic HTML. So we should strip all original tags and reapply our own semantic tags. So we will output plain text content inside appropriate tags. Thus final HTML:

                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.

                Then Responsibilities section:

                Responsibilities

                then a
                with each duty as
                • . Should we include subheadings? The subheadings like Customer Service etc are part of responsibilities; we could either keep them as

                  inside the responsibilities section or treat them as inside

                  . But the rule says use

                  for section headers (e.g., Responsibilities, Qualifications, etc). It didn't say to use for sub-sections. However, we could treat each subheading as a

                  as well, but then we would have many

                  sections. Might be okay but could be considered over-sectioning. The original had

                  Responsibilities then

                  subheadings. If we convert all to

                  , we lose hierarchy. But we are not required to preserve hierarchy, just to output clean semantic HTML. Using

                  for each heading is acceptable. Alternatively, we could keep subheadings as

                  with bold? But we must not add styling. Could use

                  for subheading text. But then we lose semantic heading. The rule didn't forbid using other heading levels; it just said use

                  for section headers (list). It didn't say we cannot use other heading levels for other headings. So we could use

                  for main sections like Responsibilities, Skills, Competencies, Education, Closing Date, etc. And for subheadings under Responsibilities we could use

                  or maybe

                  but we are not allowed to use

                  ? Not prohibited. But to keep simple, we can treat all headings as

                  . That will produce many

                  sections. Let's list all headings we encounter: - Responsibilities (h1) - Customer Service (h2) - Solutions Analysis (h2) - Receiving Visitors (h2) - Customer Relationship Management (CRM) Data (h2) - Customer Needs Clarification (h2) - Customer Relationship Development / Prospecting (h2) - Operational Compliance (h2) - Business Development (h2) - Sales Opportunities Creation (h2) - Data Exploration (h2) - Network of Influence (h2) - Skills (b) - Competencies (b) - Education (b) - Closing Date (b) - The appointment will be made... (i b) - this is a note, not a heading. - The Old Mutual Story! (i b span) - maybe a tagline. We could treat the note and tagline as

                  with and ? But we should not add styling. We'll just output as

                  with the text. Thus we will produce:

                  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

                  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