,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve all original content word-for-word, no adding/removing/rephrasing. Must convert given raw text (which includes HTML tags) into proper semantic HTML per rules. We need to parse the raw job description text (which includes HTML tags with styles etc). We need to extract the content and reformat. Given the raw text:

  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,

  for section headers (Responsibilities, Skills, Competencies, Education, Closing Date, etc). Use

  • for list items (duties, requirements, qualifications, skills). However the content includes responsibilities as separate paragraphs under each subheading (Customer Service etc). Those are duties. Should we wrap each duty as
  • under a
    under a

    Responsibilities? The original has headings

    Responsibilities

    then many

    subheadings each with a paragraph. According to rules: Use

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

    Responsibilities

    to

    Responsibilities

    . Then the subheadings like Customer Service etc could be considered as sub-sections; but we are not instructed to use any other heading levels; we could treat each duty as a list item under Responsibilities. However the rule says: Use
    • for list items (duties, requirements, qualifications, skills). So we should convert the duties into a list. Thus we need to extract each duty paragraph text and put as
    • . The duty paragraphs are: - Carry out standard customer service activities and handle simple customer inquiries. - Assess compliance with established standards and protocols for routine inquiries. - Receive visitors and assist with various requests for information, referring more complex matters to colleagues. - 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. - Interview the customer, following a multilevel sales script, to clarify the customer's requirements. - 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. - 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. - Carry out routine business development support tasks and assist others by following established procedures. - Identify potential customers by obtaining information, referrals, and recommendations from existing customers. - Select appropriate data from information provided by others and input that data into spreadsheets or standard formats. - 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. We need to preserve original content word-for-word, including HTML entities like '. Should we keep them as is? Yes, preserve original content word-for-word. So we must not decode them. Keep "customer's". Also note there are extra empty
      tags; we should ignore empty paragraphs (they have no content). Also there are stray
      empty tags; ignore. Now after Responsibilities section, we have Skills section: after

      Skills

      then some empty paragraphs then a line: "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". This is a comma-separated list of skills. Should we convert to
      • each skill? According to rule: Use
        • for list items (duties, requirements, qualifications, skills). So yes, each skill as
        • . Need to preserve original wording exactly, including commas? The original text is a single sentence with commas separating items. If we split into list items, we are altering the content (removing commas, adding structure). But rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. However we also need to use
          • for list items. This is a conflict: if we keep the original sentence as is, we cannot also put each skill as separate
          • without altering content. The instruction: "Use
            • for list items (duties, requirements, qualifications, skills)". It implies that if the original content contains a list (maybe separated by commas or line breaks), we should represent it as
              • . But we must preserve original content word-for-word. The original content is a comma-separated list; we could keep it as a single

                containing that sentence, but then we wouldn't be using

                • . However the rule says to use
                  • for list items. I think we need to convert the comma-separated list into list items, but we must preserve the wording of each item exactly (without the commas separating them). The original phrase "Consultative Selling, Customer Feedback Management, Customer-Focused, ..." If we split, we lose the commas between items but each item text remains same. The commas are delimiters, not part of the items. So we could argue we are not removing content; we are just restructuring. The commas are not part of the items; they are separators. The rule "preserve ALL original content word-for-word" might be interpreted as not to change the wording of each item, but we can change formatting. Usually in such tasks, they expect to convert comma-separated lists into
                    • . I'll do that. Thus Skills: each item as
                    • . Need to trim spaces. List: - 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 Now Competencies section: after

                      Competencies

                      then empty paragraphs then we see a weird pattern: "Balances Stakeholders
                      Builds Networks
                      Communicates Effectively
                      Customer Focus
                      Ensures Accountability
                      Instills Trust
                      Interpersonal Savvy
                      Manages Complexity
                      " It appears each competency is followed by empty
                      maybe as separators. So the list of competencies: Balances Stakeholders, Builds Networks, Communicates Effectively, Customer Focus, Ensures Accountability, Instills Trust, Interpersonal Savvy, Manages Complexity. We need to convert to
                      • each. Education: after

                        Education

                        then text: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". That's a single line; could be a

                        . Closing Date: after

                        Closing Date

                        then "19 September 2026 , 23:59". Note there is a space before comma? Actually "19 September 2026 , 23:59". Keep as is. Then there is a paragraph with italic bold:

                        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.

                        . This is a note; should be a

                        . Then final:

                        The Old Mutual Story!

                        . This is a tagline; keep as

                        . Now we need to output HTML with

                        for intro paragraphs and general text,

                        for section headers,

                        • for list items. We must not use any CSS classes, inline styles, no
                          , no
                          . Also we must not use

                          ,

                          ,

                          etc; only

                          for section headers. For other headings like the subheadings under Responsibilities (Customer Service etc) we should not output them as headings; we will convert duties to list items, so we don't need those headings. However we might need to keep the subheadings as part of the duty? The original duty paragraphs are under those subheadings; but if we convert to list items, we lose the subheading labels. Could we include them as part of the duty text? Eg "Customer Service: Carry out standard customer service activities..." But that would be adding text (the subheading). Not allowed. Better to treat each duty as list item without the subheading label. The subheadings are not part of the duty text; they are just categories. The rule says preserve ALL original content word-for-word. If we drop the subheadings, we are removing content. That's not allowed. So we must keep the subheadings somewhere. Perhaps we should keep them as part of the list items, i.e., each list item includes the subheading heading plus the duty description. But the subheading is currently in an

                          tag; its text is e.g., "Customer Service". The duty paragraph follows. If we combine them, we are adding a colon or something not originally present. However we could keep the subheading as a separate

                          (or maybe as part of the

                          but we would be adding no extra text, just placing the subheading text inside the

                          before the duty text. That would be adding the subheading text which was originally present as separate heading; we are not adding new words, just repositioning them. The original content includes the heading text "Customer Service" and the paragraph text. If we put both inside a single

                          , we are not adding or removing any words; we are just changing the structure. That seems acceptable under "preserve ALL original content word-for-word" meaning we cannot change the wording, but we can change the tags. So we can wrap each heading and its following paragraph into a

                          . However there is an empty

                          after each heading; we ignore empties. Thus for each duty we would have

                          Customer ServiceCarry out standard customer service activities and handle simple customer inquiries.

                          but we need a space between? The original had heading in its own tag, then paragraph. If we concatenate directly, we lose the separation. But we could include a space or maybe a newline; but adding a space is adding content? It's a whitespace; arguably not changing wording. Safer to put them as separate

                          inside the

                          ? But we cannot have

                          inside

                          ? Actually we can;

                          can contain

                          . That would preserve the original structure: heading as maybe

                          ?? But we are not allowed to use other heading tags; we could use

                          for the heading text as well. But the heading text originally was in

                          . Changing to

                          changes the tag but not the text. That's allowed. So we could do

                          Customer Service

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

                          . That preserves both texts exactly. However the rule says use

                          for section headers only; for other text we use

                          . So using

                          for the heading inside

                          is okay. Thus for Responsibilities section, we will have

                          Responsibilities

                          then

                          with each
                          • containing two

                            s: first the subheading (e.g., Customer Service), second the duty description. Now we need to check if there are any other sections like "Qualifications", "Requirements", etc. Not present. Now Skills: we have heading Skills. We'll make

                            Skills

                            then
                            with each skill as
                            • (just the skill text). The original had the skills list as a sentence after some empty

                              tags. We'll extract the skill items. Competencies: heading Competencies ->

                              Competencies

                              then
                              with each competency as
                              • . Education: heading Education ->

                                Education

                                then

                                with the text. Closing Date: heading Closing Date ->

                                Closing Date

                                then

                                with the

  Translated by AI — may not be perfect

  Show original