OMF Financial Consultant ( Umhlanga Gateway)

,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve all original content word-for-word, no addition/removal. Must convert the given raw HTML (with inline styles etc.) into plain text content, then wrap appropriately. We need to extract the textual content, preserving word-for-word, but we can strip HTML tags and style attributes, but keep the text exactly as appears (including entities like ' which should become apostrophe? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. However we are converting to HTML; we need to output the text content. The original content includes HTML entities like ' which represent an apostrophe. If we output as plain text, we should keep the entity? Usually when extracting text we decode entities. But "word-for-word" could mean we keep the characters as they appear in the source after decoding? The source shows "Let's Write Africa's Story Together!" which is HTML for apostrophe. If we output as plain text, we should output "Let's Write Africa's Story Together!"? That would be changing the entity to actual apostrophe, which is a change. But the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we output the entity as is, it's still the same characters: '. That would be preserving the original. However typical semantic HTML would decode entities; but we must follow instruction strictly. Safer to keep the entities as they appear. However the output is HTML; if we include ' inside HTML, it will be interpreted as an apostrophe when rendered, but that's okay; it's still the same source characters. The instruction likely expects we output the readable text, not the escaped entities. Many similar tasks expect to decode. But they said "preserve ALL original content word-for-word". The original content includes the escaped entities; but if we output them as is, it's still word-for-word. I'd keep them as is. We need to identify sections: There's a bold "Job Description" then a paragraph: "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 a series of

  sections: Responsibilities, Customer Service, etc. Actually the raw shows many

  tags each containing a heading and sometimes content? Let's parse:

  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.

  ... and so on. Thus pattern: each heading is in its own

  tag, then the description in next

  tag (sometimes empty

  as separator). So we need to convert these to proper sections: Use

  for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). The given headings include: Responsibilities, Customer Service, Solutions Analysis, Receiving Visitors, Customer Relationship Management (CRM) Data, Customer Needs Clarification, Customer Relationship Development / Prospecting, Operational Compliance, Business Development, Sales Opportunities Creation, Data Exploration, Network of Influence, Minimum Reqirements:, Skills, Competencies, Education, Closing Date, plus some other paragraphs. We need to decide which headings correspond to sections. The instruction: Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat headings like "Responsibilities", "Customer Service", etc as section headers? But they are sub-sections under Responsibilities? Actually the raw seems to have a main heading "Responsibilities" then subheadings like "Customer Service", "Solutions Analysis", etc each with description. So we could treat "Responsibilities" as a section header (

  Responsibilities

  ) and then each subheading as maybe a

  as well? But we only have

  allowed for section headers; we could use

  for each heading. That seems okay. We also need to use

  • for list items (duties, requirements, qualifications, skills). The responsibilities descriptions are paragraphs; we could keep them as

    . But maybe we should convert each duty into list items? The instruction: Use

    • for list items (duties, requirements, qualifications, skills). So if the content is a list of duties, we should wrap them in
      • . The responsibilities are enumerated as separate headings with descriptions; not a simple list. Could treat each duty as a list item under a "Responsibilities" section. But we also have separate headings for each duty; maybe better to keep as

        paragraphs. The instruction says: Use

        • for list items (duties, requirements, qualifications, skills). So if we have a block that is clearly a list (like skills line: "Ability to Sell (Inactive), Communication, Company Policies, Credit Policies, Customer Centric Selling, Digital Savvy (Inactive), Interpersonal Relationship Management, Numeracy, Sales") that's a comma-separated list; we could turn into
          • each item. Similarly for competencies list: "Balances Stakeholders", "Builds Networks", etc each on separate lines with

            empty tags. We could turn those into list items. Requirements: "1 year sales or service experience preferably in the Retail, Banking & Financial Industries" That's a single line; could be a

            or

            . Probably

            . Education: "National Certification (Nat Cert) (Required)" ->

            . Closing Date: "01 October 2026 , 23:59" ->

            . Also there is an italic bold paragraph about appointment and "The Old Mutual Story!" etc. We need to preserve all original content word-for-word. So we must not lose any text, including empty tags? We should ignore empty tags as they have no content. Also we must preserve spaces? Probably fine. We need to output only HTML, no explanation. Let's extract the textual content in order, ignoring tags but preserving text. Original snippet:

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

            Minimum Reqirements:

            1 year sales or service experience preferably in the Retail, Banking & Financial Industries

             

            Skills

            Ability to Sell (Inactive), Communication, Company Policies, Credit Policies, Customer Centric Selling, Digital Savvy (Inactive), Interpersonal Relationship Management, Numeracy, Sales

            Competencies

            Balances Stakeholders

            Builds Networks

            Communicates Effectively

            Customer Focus

            Ensures Accountability

            Instills Trust

            Interpersonal Savvy

            Manages Complexity

            Education

            National Certification (Nat Cert) (Required)

            Closing Date

            01 October 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!

            for paragraphs and

            for section headers. Use

            • for list items (duties, requirements, qualifications, skills). Let's decide structure: We could have:

              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

              Then under Responsibilities we have multiple duties. Could make a
              with each duty as
              • . The duty headings are like "Customer Service", "Solutions Analysis", etc, and the description follows. We could combine heading and description into one list item? Eg:
              • Customer Service: Carry out standard customer service activities and handle simple customer inquiries.
              But we must preserve original content word-for-word; we cannot add strong tags or punctuation not present. We could output each heading as a

              and each description as a

              . But then we are not using

              • for list items. However the instruction says use
                • for list items (duties, requirements, qualifications, skills). It doesn't forbid using

                  for other content. So we could keep duties as

                  paragraphs under a

                  Responsibilities

                  . That satisfies using
                  • only where appropriate (skills, maybe requirements). Let's do that. Thus after

                    Responsibilities

                    , we output each duty heading as

                    (maybe bold? but we must preserve original content; the heading originally had no bold except maybe some? Actually the heading text is plain; we should output exactly as appears. The heading "Customer Service" appears as text inside

                    tags; we output as

                    Customer Service

                    . Then the description as

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

                    . There's an empty

                    between sections; we can ignore. Similarly for each duty. After duties, we have

                    Minimum Reqirements:

                    then a line with the requirement text. So we could treat "Minimum Reqirements:" as a heading (

                    Minimum Reqirements:

                    ) and then the requirement line as

                    1 year sales or service experience preferably in the Retail, Banking & Financial Industries

                    . Note the original includes around the space before "year"? Actually:

                    1 year sales or service experience preferably in the Retail, Banking & Financial Industries

                    . The text is "1 year sales or service experience preferably in the Retail, Banking & Financial Industries". The just wraps a space? Actually it's " year". So the text is "1 year ...". We'll output exactly that. Then Skills:

                    Skills

                    then a line with comma-separated list. We'll treat Skills as

                    Skills

                    and then the list as
                    • each item. Need to split by commas, preserving each item exactly as appears (including spaces). Items: "Ability to Sell (Inactive)", "Communication", "Company Policies", "Credit Policies", "Customer Centric Selling", "Digital Savvy (Inactive)", "Interpersonal Relationship Management", "Numeracy", "Sales". Note there may be trailing spaces. We'll trim? Preserve word-for-word; but splitting may alter. Safer to keep as a

                      with the original text. However instruction says use

                      • for list items (skills). So we should convert to list. We'll need to split and output each item as
                      • item text. Ensure we keep the exact wording (including parentheses, etc). We'll strip leading/trailing spaces. Similarly Competencies: after Competencies we have a series of words each followed by
                        . The text appears as: "Balances Stakeholders
                        Builds Networks
                        Communicates Effectively
                        Customer Focus
                        Ensures Accountability
                        Instills Trust
                        Interpersonal Savvy
                        Manages Complexity". So each competency is separated by empty h3 tags. We'll extract each competency phrase: "Balances Stakeholders", "Builds Networks", "Communicates Effectively", "Customer Focus", "Ensures Accountability", "Instills Trust", "Interpersonal Savvy", "Manages Complexity". We'll output as
                        • each. Education:

                          Education

                          then

                          National Certification (Nat Cert) (Required)

                          . Note double spaces before "(Required)". We'll preserve. Closing Date:

                          Closing Date

                          then

                          01 October 2026 , 23:59

                          . Note space before comma. Then the italic bold paragraph:

                          The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and