OL

Commissioned Financial Advisor

Full time Blantyre, MW
Posted 1 week, 5 days ago 125 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

    . Return ONLY the HTML. We need to parse the given raw text (which includes HTML tags and style attributes). We must extract the content and produce clean HTML. We must preserve original content word-for-word. That means we cannot change wording, but we can change tags to semantic ones. We must keep the text exactly as appears (including punctuation, spaces?). We need to remove style attributes etc. Also remove empty tags. Let's extract the meaningful content. Given raw:

    Lets 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

    Provide a quality service to customers while identifying opportunities to secure new business or support retention. Responsibilities may include processing cases, dealing with complex queries, and investigating and resolving customer problems.

    Solutions Analysis

    Analyze specific problems and issues to find the best solutions. Solutions could be technical or professional in nature.

    Receiving Visitors

    Receive visitors and assist with various requests for information, referring more complex matters to colleagues.

    Customer Relationship Management (CRM) Data

    Schedule follow-up actions and enter relevant information into the CRM system after each contact with a customer to create a call plan and to ensure that the organization has quality data to enable effective customer retention and business development activities.

    Customer Needs Clarification

    Set clear objectives for each sales call or meeting; tailor standard materials to make presentations to decision-makers and influencers within the customer organization; and ask relevant questions to gather information, to evaluate the customer's level of interest, and to identify and respond to areas requiring further information or explanation.

    Customer Relationship Development / Prospecting

    Develop and implement a relationship management plan for potential customer accounts to identify and build relationships with relevant decision-makers and influencers within the customer organization and to enable effective two-way flow of information and resolution of issues.

    Operational Compliance

    Develop knowledge and understanding of the organization's policies and procedures and of relevant regulatory codes and codes of conduct to ensure own work adheres to those standards. Obtain authorization from a supervisor or manager for any exceptions from mandatory procedure.

    Business Development

    Monitor and assess sales and market data for a specific geographic region that will assist management in identifying areas in the market where business can be developed.

    Sales Opportunities Creation

    Develop a personal network within the business sector and represent the organization at business sector events. Obtain market intelligence and enhance the visibility and reputation of the organization, its products, and its services.

    Data Exploration

    Conduct research and select relevant information to enable analysis of key themes and trends using primary data sources and business intelligence tools.

    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.

    • Providing financial advice in line with the Company's customer value proposition and compliance framework.
    • Developing, implementing, monitoring, and reviewing business plans to achieve individual performance targets.
    • Prospecting and conducting business within assigned markets.
    • Selling and promoting the Company's range of life assurance and related financial products.
    • Building and maintaining strong relationships with existing and prospective clients.
    • Ensuring excellent customer service and adherence to Company policies and procedures.

     

    Skills

    Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships

    Competencies

    Action Oriented

    Balances Stakeholders

    Builds Networks

    Collaborates

    Communicates Effectively

    Customer Focus

    Drives Results

    Ensures Accountability

    Education

    repeated)

    NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent

    Closing Date

    The Old Mutual Story!

    We need to produce HTML with

    for intro paragraphs and general text. Use

    for section headers (Responsibilities, Skills, Competencies, Education, Closing Date? Actually Closing Date is a section header; we should use

    . Also maybe "Job Description" is a section header? The text includes Job Description then a paragraph. According to rules, we should use

    for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. "Job Description" maybe not listed but could be considered a section header; but we can treat it as

    as well? The instruction: Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., not exhaustive. So we can use

    for any clear section header like Job Description, Responsibilities, Skills, Competencies, Education, Closing Date, etc. We must preserve all original content word-for-word. That includes the text inside tags. We must not add or remove any characters. So we need to output the exact same textual content, just wrapped in appropriate tags. We need to strip out all original tags and replace with our semantic tags, but keep the inner text unchanged. We must also remove empty tags like

    ,

    , etc. We must not add any extra spaces or characters not originally present. However, we may need to add new tags and line breaks? The instruction says return ONLY the HTML. It didn't forbid adding whitespace for readability, but safer to not add extra spaces beyond what is needed for tags. However, we need to produce valid HTML; we can include line breaks between tags for readability but that adds characters (newline). Not sure if that's considered adding content. Usually it's okay but to be safe we can output a single line? But readability not required. However, we need to ensure we don't alter the original text content. Adding newlines between tags does not alter the original text content (the text nodes). It's extra characters but not part of the text nodes. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely refers to the textual content, not the markup. Adding newlines is not part of the content. I think it's fine. We'll produce something like:

    Lets 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

    Provide a quality service to customers while identifying opportunities to secure new business or support retention. Responsibilities may include processing cases, dealing with complex queries, and investigating and resolving customer problems.

    Solutions Analysis

    Analyze specific problems and issues to find the best solutions. Solutions could be technical or professional in nature.

    ... and so on for each responsibility heading. But note: The original had

    Responsibilities

    then

    then

    Customer Service

    etc. So the section header "Responsibilities" is a heading, then each responsibility is a subheading (

    ). According to rules, we should use

    for section headers. So we can treat "Responsibilities" as

    , and each subheading like "Customer Service" also as

    ? Or maybe we should treat them as

    as well. 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 forbid using

    for subsections. So we can use

    for each heading. Thus we will convert all headings (

    ,

    ,

    ) to

    . Also the bolded sections like Job Description, Skills, etc become

    . Now list items: The
    • list after responsibilities should be kept as
      • ... etc. Those are duties? Actually they appear after responsibilities and before Skills. They are likely additional duties. We'll keep them as
        • . Now Skills: The text after Skills is a comma-separated list: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". According to rules, we should use
          • for list items (duties, requirements, qualifications, skills). So we need to split that into list items. However, we must preserve original content word-for-word. If we split the sentence into separate list items, we are altering the content (adding
          • tags and removing commas). But the rule says use
            • for list items (duties, requirements, qualifications, skills). It also says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. There's a conflict: If we keep the comma-separated string as a single paragraph, we are not using
              • for list items. But the rule says to use
                • for list items. Which takes precedence? Likely we need to format as list items, but we must keep the wording inside each
                • exactly as originally (i.e., each skill phrase). The original text is a comma-separated list; we can turn each phrase into an
                • while preserving the phrase exactly (including commas inside? there are none inside). We would remove the commas separating them, but those commas are delimiters not part of the skill phrases. The original content includes commas between items. If we remove them, we are removing characters (commas and spaces). That would be removing original content. However, maybe we can keep the commas inside the
                • text? For example,
                • Building Trust,
                • would keep the comma but then we have extra commas. The original had "Building Trust, Consultative Selling, ..." If we make each item
                • Building Trust,
                • Consultative Selling,
                • etc, we keep the commas but also add extra commas after each item (which were originally there as separators). Actually original had a comma and a space between items. If we put each item with trailing comma and space inside
                • , we would duplicate the separator? Let's think: Original string: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships" If we split on ", " we get items without the comma. The original separators are ", ". If we wrap each item in
                • and put nothing after, we lose the ", " separators. That's removal of original content (the commas and spaces). If we keep the comma inside each
                • except maybe the last, we would have extra commas. For example:
                • Building Trust,
                • Consultative Selling,
                • ... The original had a comma after each item except the last. So if we keep the comma inside each
                • , we preserve the commas. The separators between
                • tags would be nothing (or maybe whitespace). That would change the formatting but not the textual content if we consider the commas as part of the items. The original text had commas as part of the list; they are not separators but part of the items? Actually in English list, the comma is a separator, not part of the item. But the instruction to preserve original content word-for-word likely means we cannot drop any characters from the original text. If we wrap each item in
                • and keep the comma inside the
                • , we still have the commas present in the output (they are inside the
                • text). The separators between
                • tags are not part of the original text; they are new markup. That's acceptable because we are not altering the original text content; we are adding tags around it. The commas remain. So we can do:
                • Building Trust,
                • Consultative Selling,
                • ... but note the last item originally had no trailing comma. So we should not add a comma after the last item. So we need to split preserving the commas as part of each item except last. Thus we need to produce list items exactly as the original phrases with their trailing commas (except last). Let's extract items: 1. Building Trust, 2. Consultative Selling, 3. Customer-Focused, 4. Customer Service, 5. Customer Understanding, 6. Direct Selling, 7. Identifying Sales Opportunities, 8. Oral Communications, 9. Probing Questions, 10. Qualifying Prospects, 11. Sales Data Management, 12. Sales Software, 13. Strategic Selling, 14. Strengthening Customer Relationships Note: The original had "Strengthening Customer Relationships" without trailing comma. Thus we will output
                  • Building Trust,
                  • Consultative Selling,
                  • ... etc. Now Competencies: The text after Competencies is: "Action Oriented

                    Balances Stakeholders

                    Builds Networks

                    Collaborates

                    Communicates Effectively

                    Customer Focus

                    Drives Results

                    Ensures Accountability". There are empty

                    tags between each competency. So the visible text is: Action Oriented Balances Stakeholders Builds Networks Collaborates Communicates Effectively Customer Focus Drives Results Ensures Accountability. Actually there may be line breaks? The original shows each competency followed by

                    (two empty h3). So we need to extract the words: Action Oriented, Balances Stakeholders, Builds Networks, Collaborates

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 Malawi 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?