OL

OMF Financial Consultant (Sterkspruit)

Full time Sterkspruit, ZA
Posted 4 days, 19 hours ago 5 views 0 applications

Job Description

We need to output clean semantic HTML per rules. Use

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). 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 content, but we need to convert formatting to HTML tags. We need to parse the given raw HTML-like text (with

    etc.) and produce clean HTML. We must not add or remove content. So we need to keep all text exactly as appears, but we can change tags to semantic ones. We need to remove style attributes etc. Also remove empty

    tags? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". If we remove empty

    tags, that would be removing content (empty tags). However empty tags have no content; removing them might be considered removing content? Probably they want to keep the text content, not the empty tags. Usually they'd want to discard empty paragraphs. But to be safe, we could keep them as

    but that adds tags? They were originally

    . Removing style attribute is altering but maybe allowed because we need to output clean semantic HTML without inline styles. The instruction: "No CSS classes, no inline styles, no
    s, no
    tags". So we must strip style attributes. That's a change but required. Also we must convert

    to something? We cannot use
    . So we need to represent line breaks via

    tags. The original had

    after a sentence. We should convert that to a paragraph break: i.e., end one

    and start another. Since we cannot add or remove content, we need to preserve the textual content; the

    is just formatting, not content. So we can replace with paragraph separation. We also need to convert section headers like Job Description to

    Job Description

    . Similarly Minimum Requirements to

    Minimum Requirements

    . Also Skills, Competencies, Education, Closing Date. Also there is some italic/bold text at end: The appointment will be made from the designated group... and The Old Mutual Story!. Those should be kept as text, maybe within

    with ... but we cannot use inline styles but we can keep and tags? The instruction says use

    for introductory paragraphs and general text,

    for section headers,
    • for list items. It doesn't forbid other tags like or . It says no CSS classes, no inline styles, no
      , no
      . It doesn't forbid or . So we can keep them. We also need to handle the list items: there is a
      • ... already. We should keep that but ensure no extra attributes. The original
          has no attributes, just
          • ... So we can keep as is. We need to ensure we don't have stray empty

            tags. Might be okay to keep them but they'd be empty. Probably better to omit them as they have no content. The instruction "Preserve ALL original content word-for-word" - empty tags have no content, so removing them doesn't affect content. I'd remove empty

            tags. Now we need to produce final HTML. Let's extract the textual content in order. 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

            This role is responsible for providing exceptional customer service and financial education and to achieve lending, servicing, transactional banking and insurance sales targets through the marketing and selling of Old Mutual and its products.

            The incumbent is individually accountable for achieving results through own efforts.

            • Meets monthly sales targets in terms of lending, transactional banking and insurance.
            • Servicing of existing Old Mutual policies such as facilitation of claims and attending to customer complaints and queries in order to meet the Net Promotor Score (NPS) requirements.
            • Check loan application documentation for accuracy, authenticity and compliance to Policy and Procedures as well as completeness
            • Accurately capture all client information on Summit as per loan application and supporting documentation
            • Suspend or reject loan applications to be re-quoted as and when required
            • Report suspicious or fraudulent loan application documents to the Branch Manager
            • Explain the Loan Application Process to facilitate client understanding of the process
            • Explain Terms and Conditions of Old Mutual Finance Products to clients
            • Issue copy of Contract / Agreement to Client
            • Print loan agreement for client’s signature
            • Correct altered loan application information sent for rework and reprint for client’s signature
            • Follow up on clients with 1st and 2nd missed instalments
            • Meets collections and arrears targets in terms of lending products.
            • Educates clients on responsible use of credit and effective money management
            • Establishes a new business pipeline through internal and external marketing, lead generation and cross sell to customers to ensure the retention and acquisition of new clients.
            • Adheres to internal regulatory and legislative governances to ensure quality business and mitigate risk.
            • Facilitates intra branch referrals by building mutually beneficial relationships with other business units (i.e. Retail Mass Market, Personal Finance, Octogen etc.)
            • Provides excellent face to face and telephonic service to customers.
            • Project / promote the professional image of Old Mutual Finance by adhering to the dress code, housekeeping, professional behavior and code of conduct
            • Builds sustainable relationships that enhances the brand.
            • Delivers on daily production standards and adheres to service and quality standards.
            • Processing of lending products and verification of the required information.

            Minimum Requirements

            • National Senior Certificate or; (Equivalent NQF level 4)
            • Minimum of 1 years 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

            29 August 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 convert to semantic HTML. Let's produce:

            Let's Write Africa's Story Together!

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

            Then we have three empty

            tags; we can omit. Then

            Job Description

            Then we have two empty

            tags; omit. Then paragraph: "This role is responsible for providing exceptional customer service and financial education and to achieve lending, servicing, transactional banking and insurance sales targets through the marketing and selling of Old Mutual and its products." Then a line break (represented by

            ) then "The incumbent is individually accountable for achieving results through own efforts." We need to represent that as two paragraphs: first sentence then second sentence. Since we cannot use
            , we split into two

            tags. Thus:

            This role is responsible for providing exceptional customer service and financial education and to achieve lending, servicing, transactional banking and insurance sales targets through the marketing and selling of Old Mutual and its products.

            The incumbent is individually accountable for achieving results through own efforts.

            Then we have two empty

            tags; omit. Then the

              list of responsibilities. Keep as
              • ... etc. After that, we have

                Minimum Requirements

                -> convert to

                Minimum Requirements

                Then the
                  list for requirements. Then there is a

                   

                  (non-breaking space). That's a paragraph with a non-breaking space; content is a space. Should we keep? It's basically whitespace; maybe we can omit as it's not meaningful content. But to be safe, we could keep as

                  but that adds a space. The instruction says preserve all original content word-for-word. The non-breaking space is a character. If we omit it, we remove content. Safer to keep as

                  . However we cannot have  ? We can keep the actual non-breaking space character? In HTML we could just put a space. But better to keep as

                  . However we need to avoid inline styles; it's fine. Then we have empty

                  tags; omit. Then

                  Skills

                  ->

                  Skills

                  Then two empty

                  tags; omit. Then the skills line: "Ability to Sell (Inactive), Communication, Company Policies, Credit Policies, Customer Centric Selling, Digital Savvy (Inactive), Interpersonal Relationship Management, Numeracy, Sales" We need to wrap in

                  as general text. Then two empty

                  tags; omit. Then

                  Competencies

                  ->

                  Competencies

                  Then two empty

                  tags; omit. Then the competencies text: "Balances Stakeholders

                  Builds Networks

                  Communicates Effectively

                  Customer Focus

                  Ensures Accountability

                  Instills Trust

                  Interpersonal Savvy

                  Manages Complexity" We see there are stray

                  tags interleaved. Those are empty tags; we should remove them as they have no content. The content words are separated by those empty tags. So the actual text is: "Balances StakeholdersBuilds NetworksCommunicates EffectivelyCustomer FocusEnsures AccountabilityInstills TrustInterpersonal SavvyManages Complexity". But that seems wrong; likely the original had each competency on separate lines but got messed with

                  . The instruction: preserve all original content word-for-word. The

                  tags are part of original content; they are tags with no content. If we remove them, we are altering content (removing tags). However we are not allowed to add or remove content; but we are allowed to change tags to semantic ones? The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". It doesn't explicitly forbid removing empty tags, but those tags are part of the original markup. However we are already stripping style attributes etc. So we are already altering markup. The goal is to output clean semantic HTML; we can discard empty tags. I'd remove the empty

                  tags. Thus the competencies text becomes a list? Actually each competency likely should be separate list items. But the original didn't have list markup; just text with empty h3 tags separating. We could treat each competency as a separate sentence? But we must preserve content word-for-word; we cannot insert
                • tags unless they were originally list items. The rule says use
                  • for list items (duties, requirements, qualifications, skills). For competencies, it's not explicitly listed as a section that should be list, but we could still use
                    • if we deem it a list. However the instruction: "Use
                      • for list items (duties, requirements, qualifications, skills)". It doesn't forbid using for other sections, but says use for those. Safer to keep as paragraph text, preserving the exact sequence of words and any tags? But we are removing the

                        tags; that changes content. However maybe we can replace each

                        with a space or line break? The original had

                        as empty tags; removing them doesn't affect visible text. So the visible text remains same. So we can just output the visible text as a paragraph: "Balances Stakeholders Builds Networks Communicates Effectively Customer Focus Ensures Accountability Instills Trust Interpersonal Savvy Manages Complexity". But we need to preserve spacing: originally there was no space between "Stakeholders" and "

                        Builds". So after removing tags, we would have "StakeholdersBuilds". That would concatenate words incorrectly. To preserve word separation, we need to insert a space where the tags were. The original had no space; but the tags themselves were empty, so the visual rendering would have no space? Actually if you have "Stakeholders

                        Builds", the browser would render "StakeholdersBuilds". So there is no space. So preserving word-for-word means we should keep it as "StakeholdersBuilds". That seems odd but it's what the original markup would produce. However likely the source had formatting errors; but we must follow instruction. Thus we need to output exactly the text as it appears between tags, preserving the empty tags? But we cannot keep

                        because we are not allowed to use

                        ? The instruction only forbids
                        ,
                        , inline styles, classes. It doesn't forbid

                        . So we could keep the

                        tags as they are. However we are supposed to use

                        for section headers, but we can still use

                        for other purposes? The instruction didn't forbid

                        . It only said use

                        for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It didn't say we cannot use other heading levels for other purposes. So we could keep the

                        tags as is. But they are empty; keeping them is fine. Thus we should output the competencies section exactly as: after the

                        Competencies

                        , we have the text: "Balances Stakeholders

                        Builds Networks

                        Communicates Effectively

                        Customer Focus

                        Ensures Accountability

                        Instills Trust

      Apply Now ↗

      How well do you match?

      Get an instant AI match score for this role — free, takes 3 minutes.

      Tailor your CV for this role

      The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.

      Tailor My CV to This Job ✍️

      Free cover letter for this job

      Upload your CV and get a tailored cover letter in seconds — free, no account needed.

      Generate a Cover Letter 📝

      Join Our South Africa Channels

      Get free job alerts on your phone

MJC
ECHO
Your MJC Assistant

I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.

How was your experience with ECHO?