OMF Financial Consultant (OMF Mitchell's Plain Town Centre)
Old Mutual
Job Description
for intro paragraphs and general text,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). However the job description uses , , . We need to map them to ? The rule says use for section headers. So we should replace any section header tags with . But we need to preserve content word-for-word. The content includes "Responsibilities", "Customer Service", etc. Those are headings. Should we wrap them in ? The rule: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So any heading that is a section header should be . The original has Responsibilities
. That's a section header, so we need to output Responsibilities
. Also Customer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
, . We need to map them to ? The rule says use for section headers. So we should replace any section header tags with . But we need to preserve content word-for-word. The content includes "Responsibilities", "Customer Service", etc. Those are headings. Should we wrap them in ? The rule: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So any heading that is a section header should be . The original has Responsibilities
. That's a section header, so we need to output Responsibilities
. Also Customer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
? The rule says use for section headers. So we should replace any section header tags with . But we need to preserve content word-for-word. The content includes "Responsibilities", "Customer Service", etc. Those are headings. Should we wrap them in ? The rule: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So any heading that is a section header should be . The original has Responsibilities
. That's a section header, so we need to output Responsibilities
. Also Customer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
. But we need to preserve content word-for-word. The content includes "Responsibilities", "Customer Service", etc. Those are headings. Should we wrap them in ? The rule: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So any heading that is a section header should be . The original has Responsibilities
. That's a section header, so we need to output Responsibilities
. Also Customer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So any heading that is a section header should be . The original has Responsibilities
. That's a section header, so we need to output Responsibilities
. Also Customer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
Responsibilities
. That's a section header, so we need to outputResponsibilities
. AlsoCustomer Service
etc. Those are subheadings within responsibilities; maybe they are also section headers? The rule says use for section headers, not necessarily subheadings. But to be safe, we should convert all headings that denote sections (like Responsibilities, Customer Service, Solutions Analysis, etc.) to . However the rule example includes "Responsibilities" as a top-level section. The other headings like "Customer Service" are sub-sections of responsibilities. The rule may expect we keep them as as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
as well, because they are section headers. But maybe we should keep 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 explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't explicitly say to convert all / to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
to , but to use for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
for section headers. So we should replace any heading that denotes a section with . That includes "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", "Skills", "Competencies", "Education", "Closing Date". Also maybe "Let's Write Africa's Story Together!" is a title but not a section header; it's a tagline. Should we keep as
? It is inside with bold. The content is "Let's Write Africa's Story Together!" That's probably the job title? Not sure. It appears before "Job Description". Might be a tagline. We'll treat it as part of intro paragraphs. The rule: Use for introductory paragraphs and general text. So we can keep that as text.
We must preserve all original content word-for-word, no rephrasing. So we need to copy exactly the text inside tags, converting HTML tags to appropriate ones.
We need to remove any etc. But we must keep content. The rule says no CSS classes, no inline styles, no Let's Write Africa's Story Together! Let's Write Africa's Story Together! Job Description Job Description
. So we need to strip style attributes but keep the text inside. For example
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 📝Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.