OL

Sales Consultant-1

Full time Johannesburg, ZA
Posted 1 week, 5 days ago 73 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 (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

    tags. Return ONLY the HTML. We need to parse the given raw text (which includes some HTML tags and styling). We need to extract the content and produce HTML with appropriate tags. We must preserve original content word-for-word, meaning we cannot change wording, but we can change tags. We must not add or remove any text. So we need to output the same textual content, but with appropriate HTML tags. We need to identify sections: The raw text includes: -

    Let's Write Africa's Story Together!

    -

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

    - Several empty

    tags. -

    Job Description

    - Empty

    tags. - Then text: "To provide quality sales service that results in the production of business from new and existing sources which contributes to the profitability and growth of the company." - Empty

    tags. - Then

    • ... etc. The list items contain

      inside each

    • . The list items include duties and then a "Qualification:" item? Actually after duties list, there is a
    • Qualification:

    • then subsequent
    • items for qualifications: Matric or NQF Level 4, 2 years Short term insurance experience, DOFA, Credit clear, Criminal clear. Thus the list includes both duties and qualifications mixed. According to rules, we should use
      • for list items (duties, requirements, qualifications, skills). So we keep the list as is, but we need to wrap each item's text appropriately. The original list items have

        inside; we can keep the text but we need to output as

      • with the text (no extra

        inside? The rule says use

        • for list items. It doesn't forbid having

          inside

        • , but to keep semantic HTML, we could just put the text directly inside
        • . However we must preserve original content word-for-word. If we remove the

          tags inside

        • , we are removing tags, which is altering content? The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That likely refers to the textual content, not the markup. We can change markup but must keep the text exactly. So we can drop the inner

          tags as they are markup, not content. The content is the text inside those

          . So we can output

        • Handle incoming and outgoing sales calls in accordance with predetermined schedules, campaigns and targets.
        • etc. That preserves the text. Similarly for the skills section: after Skills there is a line of text: "Accounting, Action Planning, Computer Literacy, Data Analysis, Database Reporting, Data Compilation, Data Interpretations, Evaluating Information, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Report Review, Sales Software, Statistical Analysis Techniques". This is not a list; it's a sentence/comma-separated list. According to rules, we should use
          • for list items (duties, requirements, qualifications, skills). So we should convert that into a list? The rule says use
            • for list items (duties, requirements, qualifications, skills). It implies if the content is a list of items, we should use
              • . The skills are clearly a list of skills separated by commas. So we should split them into
              • items. However we must preserve original content word-for-word; splitting into separate
              • items does not change the textual content, just grouping. It's acceptable. Similarly for Competencies: after Competencies there is a series of lines each with a competency name followed by

                etc. The raw shows: Communicates Effectively

                Customer Focus

                Decision Quality

                Ensures Accountability

                Manages Complexity

                Optimizes Work Processes

                Plans and Aligns

                Tech Savvy So each competency appears, then empty

                tags. We need to extract the competency names: "Communicates Effectively", "Customer Focus", "Decision Quality", "Ensures Accountability", "Manages Complexity", "Optimizes Work Processes", "Plans and Aligns", "Tech Savvy". We should output them as a list (
                • ). Education: after Education we have "NQF Level 3 & NQF Level 2 - Below school leaving". That's a sentence; could be left as

                  . Not a list. Closing Date: after Closing Date we have "11 October 2026 , 23:59". Note there is a space before comma. We'll preserve exactly. Then an 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 the specific business unit in question.

                  . We need to preserve that text. According to rules, we can use

                  for introductory paragraphs and general text. So we wrap that in

                  . The inner ... we can drop as markup but keep text. So output

                  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.

                  . Finally:

                  The Old Mutual Story!

                  . Text: "The Old Mutual Story!". We'll output

                  The Old Mutual Story!

                  . We also need to handle the initial heading "Let's Write Africa's Story Together!" and the following line about Old Mutual. Those could be considered introductory paragraphs. Use

                  for them. Also there is a Job Description heading. According to rules, we should use

                  for section headers like Responsibilities, Qualifications, etc. "Job Description" could be considered a section header. So we should wrap that in

                  Job Description

                  . Similarly "Skills", "Competencies", "Education", "Closing Date". Also maybe "Qualification:" inside list is not a separate header; it's a list item. We need to decide which headings to treat as

                  . The rule says: Use

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

                  to those that match. So "Job Description" maybe not in the list but could be considered a section header; but we can still use

                  as it's a heading. The rule says use

                  for section headers (e.g. ...). It doesn't forbid using for other headings, but we should follow the pattern. Likely we should treat "Job Description", "Skills", "Competencies", "Education", "Closing Date" as

                  . Also maybe the initial "Let's Write Africa's Story Together!" is more like a title; could be

                  as well? But it's more like a tagline. The rule says use

                  for introductory paragraphs and general text. So we could keep those as

                  . The bold text inside

                  we can keep as text; we can drop the tags but keep the text. So we output

                  Let's Write Africa's Story Together!

                  and

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

                  . Now we need to output HTML with proper ordering. Let's reconstruct: Intro:

                  Let's Write Africa's Story Together!

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

                  Then maybe some empty paragraphs we ignore. Then

                  Job Description

                  Then paragraph: "To provide quality sales service that results in the production of business from new and existing sources which contributes to the profitability and growth of the company." Then the duties list: we need to output as
                  • ... each duty. We need to extract duties from the list items before the "Qualification:" item. Let's list the duties from the raw: - Handle incoming and outgoing sales calls in accordance with predetermined schedules, campaigns and targets. - Telephonically guide customers through the product offering, pricing, terms and conditions. - Provide accurate and efficient quotation/s to customers. - Maintain an agreed lead to sale ratio. - Maintain an agreed lead to quote ratio. - Maintain an agreed quote to sale ratio. - Required to work shifts as scheduled. - Manage all allocated leads. - Sell according to agreed targets for the day. - Maintain a 90% QA average on all calls. - Accurately and efficiently capture all customer data. - Finalise calls at point of contact, where possible. - Forward accurate policy documents to customers within mandated timeframes. - Deal with all customers in a professional manner in strict accordance with businesses culture, products and quality standards. - Manage time and workloads to ensure that deadlines and targets are met. - Demonstrate an excellent knowledge of the business product offerings, campaigns, rules and conditions in order to recommend the right solution to the customer. That's 16 duties. Then after that we have a list item:
                  • Qualification:

                  • . This seems like a subheading inside the list. Should we treat it as a separate

                    ? The rule says use

                    for section headers like Qualifications. So we could output

                    Qualification

                    and then list the qualification items as
                    • . However the original had it as a list item. We need to preserve content word-for-word; we can change markup but keep text. So we can output

                      Qualification

                      then a
                        with the qualification items. Qualification items: - Matric or NQF Level 4 - 2 years Short term insurance experience - DOFA - Credit clear - Criminal clear Now after that list, there is a stray "na" and some empty paragraphs. The "na" appears after a
                      and a

                       

                      (non-breaking space) then "na". Actually the raw shows:

                     

                    na

                    Skills

                    ... So there is a stray "na" which seems like an artifact. According to rules, we should remove stray numbers or formatting artifacts. "na" is likely an artifact; we should remove it. It's not part of the job description. So we omit "na". Then we have Skills heading. We'll output

                    Skills

                    . Then we need to list skills as
                    • each. Skills list (split by commas): Accounting Action Planning Computer Literacy Data Analysis Database Reporting Data Compilation Data Interpretations Evaluating Information Management Reporting Numerical Aptitude Oral Communications Professional Presentation Report Review Sales Software Statistical Analysis Techniques We must preserve the exact wording; note there is an ampersand in Education later. Now after skills, there is empty paragraphs then Competencies. Output

                      Competencies

                      . Then list competencies as
                      • . Competencies list: Communicates Effectively Customer Focus Decision Quality Ensures Accountability Manages Complexity Optimizes Work Processes Plans and Aligns Tech Savvy Now after competencies, empty paragraphs then Education. Output

                        Education

                        . Then paragraph: "NQF Level 3 & NQF Level 2 - Below school leaving". We need to preserve the ampersand entity? The original text shows "NQF Level 3 & NQF Level 2 - Below school leaving". The ampersand is encoded as &. In the output HTML, we should preserve the original content word-for-word. If we output as plain text, we need to keep the characters exactly as they appear in the source. The source shows "&" which is an HTML entity for &. If we output as plain text, we should output "&" as literal characters? Usually when preserving content, we keep the visible text, not the entity. But the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. The original content includes the characters "& amp ;" as an entity. If we change it to just "&", we are changing the content (though visually same). Safer to keep the entity as is. So we output exactly "NQF Level 3 & NQF Level 2 - Below school leaving". However note that we are outputting inside HTML; if we put the literal "&" inside HTML, it will be displayed as "&" text, not as an ampersand. But the rule is about content, not rendering. We'll keep the entity. Now after education, empty paragraphs then Closing Date. Output

                        Closing Date

                        . Then paragraph: "11 October 2026 , 23:59". Note there is a space before comma. We'll keep exactly. Then empty paragraphs then the italic bold paragraph: we output

                        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.

                        Then empty paragraphs then the final line:

                        The Old Mutual Story!

                        Now we need to ensure we didn't miss any text: The initial

                        Let's Write Africa's Story Together!

                        includes an HTML apostrophe entity '. We need to preserve that as well. The original text: Let's Write Africa's Story Together! So we should output exactly that string: Let's Write Africa's Story Together! (including the entity). Similarly the second line: Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. No entities. Now check for any other entities: In the duties list, there is "quotation/s". That's fine. Now we need to ensure we didn't inadvertently drop any text like the "na" we removed; but rule says remove stray numbers or formatting artifacts. "na" is likely an artifact, so we remove. Also there is a non-breaking space

                         

                        before "na". That's also artifact; we remove. Now we need to output HTML without any
                        , no classes, no inline styles, no
                        . Use

                        ,

                        ,
                        • . We must not add any extra text like "Here is the cleaned version". Just output HTML. Let's construct:

                          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

                          To provide quality sales service that results in the production of business from new and existing sources which contributes to the profitability and growth of the company.

                          • Handle incoming and outgoing sales calls in accordance with predetermined schedules, campaigns and targets.
                          • Telephonically guide customers through the product offering, pricing, terms and conditions.
                          • Provide accurate and efficient quotation/s to customers.
                          • Maintain an agreed lead to sale ratio.
                          • Maintain an agreed lead to quote ratio.
                          • Maintain an agreed quote to sale ratio.
                          • Required to work shifts as scheduled.
                          • Manage all allocated leads.
                          • Sell according to agreed targets for the day.
                          • Maintain a 90% QA average on all calls.
                          • Accurately and efficiently capture all customer data.
                          • Finalise calls at point of contact, where possible.
                          • Forward accurate policy documents to customers within mandated timeframes.
                          • Deal with all customers in a professional manner in strict accordance with businesses culture, products and quality standards.
                          • Manage time and workloads to ensure that deadlines and targets are met.
                          • Demonstrate an excellent knowledge of the business product offerings, campaigns, rules and conditions in order to recommend the right solution to the customer.

                          Qualification

                          • Matric or NQF Level 4
                          • 2 years Short term insurance experience
                          • DOFA
                          • Credit clear
                          • Criminal clear

                          Skills

                          • Accounting
                          • Action Planning
                          • Computer Literacy
                          • Data Analysis
                          • Database Reporting

    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 📝

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?