OL

MFC Sales Manager (Rustenburg)

Full time Rustenburg, ZA
Posted 1 day, 15 hours ago 45 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor. - I receive raw scraped text from a job website. - Goal: Extract ONLY actual job information, return clean, readable format. - Must REMOVE: social sharing, author bylines, "you may also like", navigation, comments, ads/promotions, cookie/subscription notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts. - Must KEEP and STRUCTURE: job title, company, location, job description/responsibilities, requirements/qualifications, how to apply, salary (if mentioned), deadline/closing date, job ID/reference number, contract type/level. - Return ONLY the cleaned job text. No commentary, no headers like "Here is the cleaned version", no markdown formatting. Just the clean job listing text. Wait, the actual prompt I need to respond to has two parts: - First part: "You are a job listing editor..." with rules about removing/keeping things, and "Return ONLY the cleaned job text." - Second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific HTML rules. Let me read carefully. The user message starts with "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then it gives rules for HTML formatting. Then it says "Job description:" and pastes a lot of text. Actually, looking at the structure, it seems like there are two separate instructions or a combined one. Let me re-read the entire user message carefully. User message: "You are a job listing editor. You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format. REMOVE all of the following: - Social sharing text (Share, Facebook, Twitter, WhatsApp, Telegram, etc.) - Author bylines (by AuthorName, written by, posted by) - "You may also like" / related posts sections - Navigation text (Previous, Next, Read more, Back to) - Comments sections - Advertisements or promotions - Cookie/subscription notices - Duplicate text (if the title appears multiple times, keep it once) - Category labels that aren't part of the job (e.g., "Internships" as a standalone line) - Stray numbers or formatting artifacts KEEP and STRUCTURE: - Job title - Company/Organisation name - Location - Job description and responsibilities - Requirements/qualifications - How to apply / application instructions - Salary (if mentioned) - Deadline / closing date - Job ID / reference number - Contract type / level Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text. [then there's a blank line or separator?] "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML. Rules: - Use

for introductory 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
    s, no
    tags - 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. No markdown fences, no explanation, no preamble. Job description: [the long text]" Okay, so the user actually gave me two different sets of instructions in one message. The first is "extract and return clean text" (probably plain text, no HTML tags). The second is "format as clean semantic HTML" with specific HTML tags. Which one do I follow? The very last part says "Job description:" and then the text, and the rules before that are specifically about HTML formatting. The first part about removing/keeping stuff seems like a general instruction, but the actual task appears to be the HTML formatting one, because it has the specific "Rules" and "Job description:" section. However, note the HTML rules say: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". And "If text has no clear sections, just wrap paragraphs in

    tags". Also "No CSS classes, no inline styles, no

    s, no
    tags". The job description text has a lot of inline styles like `style="text-align:left"`, `style="text-align:inherit"`, ``, ``, `

    `, etc. The rules say "No CSS classes, no inline styles, no
    s, no
    tags". So I need to strip all styles and classes, and reformat into the specified semantic HTML structure. Also, the content has things like "na", duplicate sections, "Builds Effective Teams

    " etc. I need to extract only the actual job information, remove stuff that's not part of the job (but the HTML rules say "Preserve ALL original content word-for-word". There's a tension. Let re-read carefully.) The HTML rules say: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But the first set of rules says "REMOVE all of the following: ...". Which one takes precedence? The user message seems to combine both, maybe as a single flow: first I'm told I'm a job listing editor, then I'm told to format as clean semantic HTML. The final "Job description:" section is what I need to process. Let me read the exact boundary. The first part says "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." Then there's a blank line, then "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then rules, then "Job description: [text]". It's possible the user wants me to do the HTML formatting, as that's the last instruction with the actual input. The first part might be a general preamble or from a different prompt that got concatenated. Given the explicit "Rules" and "Job description:" at the end, I should focus on formatting that text as clean semantic HTML per the rules. But wait: the HTML rules say "Preserve ALL original content word-for-word". That means I shouldn't remove any of the job description content, even the stuff that the first set of rules says to remove (like social sharing, bylines, etc.). However, looking at the job description text provided, it doesn't seem to contain social sharing or bylines explicitly—it's just the raw job text with formatting tags. The text includes things like `

    Let's Write Africa's Story Together!

    `, which is the company/organization intro and job title. It has a lot of paragraphs, headings, lists implicitly. Let me parse the job description text and decide how to structure it into the requested HTML. HTML rules: - Use `

    ` for introductory 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 `
      `s, no `
      ` tags - 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. No markdown fences, no explanation, no preamble. Key challenge: "Preserve ALL original content word-for-word" but also use `

      ` for section headers and `
      • ` for lists. The original text has content that is already somewhat structured with ``, ``, `

        `, etc. I need to strip all styles/classes/tags and re-express the content using only `

        `, `

        `, `
          `, ``, I lose section headers. If I use `

          ` for headers, I need to identify sections. The original text has things like `

          Role Overview

          `, then later `Requirements: Skills, Qualifications and Experience required`, `Attributes / Competencies`, `Skills`, `Competencies`, `Education`, `Closing Date`. Also there are lists of competencies/attributes that are just `

          ` with bullet points like "· Strategic · Collaboration ...". And there's `

            ` style? No, the text has `·` bullet points inside `

            ` tags. Let me extract the raw text content from the HTML-like structure, ignoring the surrounding formatting tags (since I need to output clean semantic HTML without classes/styles/bre tags). I'll strip all `

            `, ``, ``, ``, `

            `, `

            `, `'`, `&`, `·`, etc.? Wait, "Preserve ALL original content word-for-word" — does that include the bullet characters `·`? Probably yes, as part of the content. But the HTML rules say use `
            • ` for list items. So I should convert the bullet points into `
            • ` items, but preserve the text inside. The `·` might be part of the list item text, or I could just have the text without the bullet, but "word-for-word" suggests keeping it. However, the instruction also says "Use `
              • ` for list items (duties, requirements, qualifications, skills)". So I should convert the `·` prefixed lines into `
              • ` items, and likely drop the `·` or keep it inside the `
              • `. I'll keep the text as is, but structure with `
              • `. Let me list out all the content segments in order, stripping the HTML formatting tags but keeping the text: Starting text: `

                Let's Write Africa's Story Together!

                ` → "Let's Write Africa's Story Together!" `

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

                ` → "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." Then empty paragraphs: `

                ` etc. I can ignore empty ones or include empty `

                `? The rule says "Use `

                ` for introductory paragraphs and general text". Empty paragraphs might be omitted, but to preserve word-for-word, maybe keep `

                `. However, empty ones aren't "content". I think it's safe to omit empty `

                ` tags, but the rule says "If text has no clear sections, just wrap paragraphs in `

                ` tags". I'll include only non-empty ones. Then: `Job Description` → "Job Description" Then empty paragraphs. Then: `Manages and coordinates the organisation’s sales function to meet the organisation’s business requirements. Manages a large-sized team of advisors to develop, maintain, and leverage relationships with prospective and existing clients to stimulate and manage demand for financial products and services.` This is a paragraph. Keep as `

                ...

                `. Then empty paragraphs. Then: `

                Role Overview

                ` → "Role Overview " (but h1 is not allowed; rules say use `

                ` for section headers. So I should convert `

                ` to `

                `? 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 say I can't use other headers, but it says "No CSS classes, no inline styles, no `
                `s, no `
                ` tags". It doesn't explicitly forbid `

                ` or `

                `, but the instruction says "Use `

                ` for section headers". I think I should use `

                ` for all section headers to comply with the rule. The rule might mean that when there are sections, use `

                `. I'll use `

                ` for headers that are clearly section headers. Then: `

                ` empty. Then: `This role manages a sales team and distribution strategy and is accountable for the sales targets and profitability of the team, over periods of up to a year.` → `

                This role manages a sales team and distribution strategy and is accountable for the sales targets and profitability of the team, over periods of up to a year.

                ` Then: `The position has been identified as a FAIS position and falls within the ambit contemplated by FAIS related to Category B. The successful candidates must therefore comply with all FAIS requirements, including the Fit and Proper requirements of Honesty and Integrity (e.g. be clear of any offence relating to fraud, dishonesty and/or any professional misconduct) as well as competence and relevant qualifications` → `

                ...

                ` Then: `Manages sales & expense budget for a sales team in a branch against set targets.` → `

                ...

                ` Then: `Responsible for distribution strategy of products within a branch.` → `

                ...

                ` Then: `Accountable for local marketing.` → `

                ...

                ` Then: `Identifies & creates coordinated sales opportunities.` → `

                ...

                ` Then: `Responsible for external networking & relationship building with key door openers.` → `

                ...

                ` Then: `Ensures delivery of customer value.` → `

                ...

                ` Then: `Manages, develops, appoints & trains sales advisors.` → `

                ...

                ` Then empty `

                `. Then: `· Strategic · Collaboration (Relating) · Leading with influence · Customer First · Execution · Innovation (Perspective) · Personal Mastery (Learning)` This is a list of competencies. The `·` are bullet points. I should convert to `
                • Strategic
                • Collaboration (Relating)
                • ...` but preserve word-for-word. The `·` might be considered part of the content. I'll include the text without the `·` inside `
                • `, or with it? "Preserve ALL original content word-for-word" — if I remove `·`, I'm changing content. But the rule also says "Use `
                  • ` for list items". I think the intent is that the list items' text should be the content, and the `·` is a bullet marker that can be dropped or kept inside the `
                  • `. To be safe, I'll keep the text as is, but wrap each in `
                  • `, possibly keeping the `·` at the start. However, `·` is not a word; it's a bullet. I'll strip it and just have the phrase, as is common. But "word-for-word" is strict. Let me re-read: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely means don't change the actual words/text, but formatting tags don't count as content. I'll keep the exact text inside `
                  • `, including the `·` maybe? I'll just put the text without `·` but if the system checks, it might fail. I'll include the `·` as part of the text, e.g., `
                  • · Strategic
                  • `. But that might not be "word-for-word" if I'm adding a tag. I think it's fine. Actually, looking at the original: `· Strategic  · Collaboration (Relating) · Leading with influence · Customer First · Execution · Innovation (Perspective) · Personal Mastery (Learning)` They are on separate lines within a `

                    ` tag? The raw text shows them inside a `

                    ` after `

                    Requirements: ...`. Wait, the text is: `

                    · Strategic  · Collaboration (Relating) · Leading with influence · Customer First · Execution · Innovation (Perspective) · Personal Mastery (Learning)

                    `. Yes, it's all in one `

                    ` with `·` prefixes. I'll convert to `

                    • ` with the text including `·` or without. I'll keep the `·` to be safe, as removing it would be removing content. Then empty `

                      `. Then: `Requirements: Skills, Qualifications and Experience required` → "Requirements: Skills, Qualifications and Experience required" Then empty `

                      `. Then: `· Gr12 (Matric) and FAIS approved Qualification ` → "· Gr12 (Matric) and FAIS approved Qualification " Then: `· FAIS Compliant ` → "· FAIS Compliant " Then: `· Product category experience 1.3/1.5/

    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?