Job Description
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
. Must preserve all original content word-for-word.
We need to parse the given raw text (which includes HTML tags and style attributes). We need to extract the textual content, preserving it exactly, then wrap in appropriate tags.
We must not add or remove any content. So we need to output the same text but with HTML tags as per rules, removing style attributes etc. However we must preserve the content word-for-word, meaning we cannot drop any characters from the original text. But we are allowed to change formatting (tags). The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means the textual content (the visible characters) must stay same. We can remove HTML tags and style attributes as they are not part of the content? The original content includes those tags; but they are markup, not visible text. Usually "content" refers to the textual content. We'll assume we need to keep the words exactly as they appear, ignoring original markup. We'll strip out the given HTML tags and produce new semantic HTML.
Thus we need to extract the plain text from the given snippet, then format.
Let's extract the text:
Starting 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
na
At OM Bank, we strive to attract great people who are passionate about coming together for a higher purpose- building something unique and aspirational, always aiming to be the best they can be. We are rooted in our purpose of inspiring and enabling our customers to grow and sustain their prosperity.
The successful incumbent will be responsible for the following:
KEY RESULT AREAS
- Gather information, create business cases and prioritise the projects and enhancements for that which you control; in close conjunction with the development team you will implement these changes.
- Create a functional product roadmap aligned to business strategy with sound and demonstrable commercial rationale
- Manage all requests for change from the business within your product and align these to current enhancements and projects where possible after critical assessment
- Work directly alongside your development teams, driving the product backlog and prioritisation thereof
- Clearly communicate progress and goals with stakeholders and management
- Projects and enhancements should be cased with respect to key metrics related to this product where possible based on data, and where data is unavailable creative means should be found to demonstrate the reasonability of assumptions
- The success or failure of an enhancement or project should be related back to the same key metrics and be relatable to commercial rationale
- Develop artefacts to drive all your work forward, including user stories, requirements documents, use cases, personas, white papers, demos and presentations
- Lead, coach, and inspire product managers and specialists to foster a high-performance culture focused on delivering exceptional outcomes
- Build and maintain strong relationships with key stakeholders including executive leadership, Product Owners, external partners, and relevant regulatory bodies
Minimum Requirements:
- Relevant tertiary qualification and a proved track record of delivery.
- Minimum 7 years’ relevant Telco product and/or operational management experience.
- Exposure to or experience in developing business models for changes
- An executor who has demonstrable success in a product ownership role, where you have needed to understand commercial goals, think strategically and balance the need for a great solution with that of the current need state.
- Proven track record of a role where you live and breathe customer experience, the end-to-end journey, UX and UI
- Track record of delivering complex projects with agile development teams, (with a firm personal belief and business strategy of MVP and test, iterate, test, iterate)
- Knowledge of Kanban/Lean desirable
- Knowledge and experience in using tracking and collaboration tools such as Jira, Miro and TFS
- Knowledge and experience with typically used Agile techniques such as User Story mapping, ATDD, TDD,
- Knowledge of agile methodology and frameworks like Scrum, Kanban, Scaled Agile (SAFe)
- Commitment to deliver the agreed work through the team and relevant stakeholders
- Understand the value of team metrics and ask them to be tracked to drive team performance
- Stakeholder Management, Negotiation & Communication Skills
- Clarity on delivering clear, prioritised stories with acceptance criteria. Aligning these to Features
Skills
Adaptive Thinking, Agile Project Management, Change Management, Executing Plans, Managing Stakeholder Expectations, Policies & Procedures, Policy Development, Product Development Management, Project Communications Management, Project Life Cycle Management, Project Performance Management (PM), Project Quality Assurance, Project Scope Management
Competencies
Action OrientedBalances StakeholdersBusiness InsightCultivates InnovationDecision QualityDevelops TalentDrives EngagementDrives Results
Education
NQF Level 9 – Masters
Closing Date
19 June 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!
Now we need to extract plain text, preserving spaces and punctuation exactly as they appear (including HTML entities like ' which is an apostrophe). We need to keep them as they appear? The original text includes ' which is HTML entity for apostrophe. Should we keep it as ' or convert to ’? The instruction: preserve ALL original content word-for-word. So we should keep the entity as is. However after stripping tags, we might keep the entity. That's fine.
Now we need to structure with 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.
We need to decide which sections correspond.
From the text:
- Intro: "Let's Write Africa's Story Together!" (with entity) then "Old Mutual is a firm believer..." then blank lines then "Job Description" then "na" (maybe a placeholder). Then paragraph: "At OM Bank, we strive..." etc.
- Then "The successful incumbent will be responsible for the following:" then a bold/underline "KEY RESULT AREAS" then list items (these are duties/responsibilities). So we could treat "KEY RESULT AREAS" as a section header (maybe Responsibilities). Use Responsibilities
then - ... items.
- Then "Minimum Requirements: " then list items (requirements). So section header: Requirements (or Minimum Requirements). Use
Requirements
then list.
- Then after that there is a blank paragraph then "Skills" then a line of skills (comma-separated). This is not a list but we could treat as a paragraph? The rule: Use - for list items (duties, requirements, qualifications, skills). Skills are listed as comma-separated; we could still make each skill a list item? But the instruction says preserve ALL original content word-for-word. If we change the format from comma-separated to list items, we are altering content (adding
- and removing commas). That would be adding/removing? It changes representation but not the words? Actually we would be adding tags and removing commas, which changes the textual content (commas removed). That would violate "preserve ALL original content word-for-word". So we must keep the skills exactly as they appear: "Adaptive Thinking, Agile Project Management, Change Management, Executing Plans, Managing Stakeholder Expectations, Policies & Procedures, Policy Development, Product Development Management, Project Communications Management, Project Life Cycle Management, Project Performance Management (PM), Project Quality Assurance, Project Scope Management". We must not alter that string. So we should wrap it in a
(since it's general text). However the rule says use
- for list items (duties, requirements, qualifications, skills). But if we keep as paragraph, we violate that rule? The rule says "Use
- for list items (duties, requirements, qualifications, skills)". It implies if the content is a list, we should use
- . But the skills are not presented as a list; they are a comma-separated line. So it's not a list; it's a sentence. So we can keep as
. That's fine.
- Then "Competencies" then a series of words each followed by empty
tags. The text appears as: "Action OrientedBalances StakeholdersBusiness InsightCultivates InnovationDecision QualityDevelops TalentDrives EngagementDrives Results". So each competency is followed by two empty h3 tags. We need to preserve that exactly. So we will keep that string as is, inside a maybe.
- Then "Education" then "NQF Level 9 – Masters". So we can treat Education as
Education
then NQF Level 9 – Masters
.
- Then "Closing Date" then "19 June 2026 , 23:59". So Closing Date
then 19 June 2026 , 23:59
.
- Then the italic bold statement about appointment: "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.
" So we need to preserve that exactly. Could be a with ... . But rule says no CSS classes, no inline styles, no
, but we can use and tags? The instruction only restricts use of ,
, CSS classes, inline styles. It didn't forbid or . However we should aim to use semantic HTML: for paragraphs,
for headings, - for lists. Using and is okay but not semantic; but we must preserve original content word-for-word, which includes those tags. So we must keep ... inside the
. That means we will output a
containing 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.. That preserves the tags.
- Finally "
The Old Mutual Story!
" So we need to preserve that exactly: includes , , . We must keep them.
Thus our output HTML will consist of a series of elements: for intro paragraphs,
for section headings, - for lists (KEY RESULT AREAS and Minimum Requirements). For other sections like Skills, Competencies, Education, Closing Date, appointment note, final story, we will use
(preserving any internal tags like , , , etc.)
We must not add any extra content. Must not remove any content. Must preserve original spacing? We'll try to keep line breaks as they appear? Not required but we can keep them.
Let's extract the exact textual content including the tags we want to keep.
Better approach: We'll produce HTML that mirrors the original but with semantic tags for headings and lists, while preserving inner content exactly.
We need to decide what constitutes a "section header". The original uses Job Description, Minimum Requirements:, Skills, Competencies, Education, Closing Date. Also there is a bold/underline "KEY RESULT AREAS". We'll treat those as .
We also have "The successful incumbent will be responsible for the following:" which is introductory to the responsibilities list; we can keep that as a
before the
Responsibilities
maybe.
But 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 map:
- "KEY RESULT AREAS" -> maybe Responsibilities or Key Duties. We'll use Responsibilities
(or Key Duties). The rule says we can use those examples; we can choose Responsibilities.
- "Minimum Requirements:" -> Requirements.
- "Skills" -> Skills.
- "Competencies" -> maybe Competencies (not in examples but could be considered similar to Skills). We'll still use Competencies
.
- "Education" -> Education.
- "Closing Date" -> Closing Date.
- "Job Description" maybe not needed as a heading; could be introductory.
We also have "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer..." as intro.
We also have "na" after Job Description; that's weird but we must keep it.
Now we need to produce HTML.
Let's list the pieces in order:
1.
Let's Write Africa's Story Together!
-> We'll output Let's Write Africa's Story Together!
(remove style attribute). Keep inner tags.
2. 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.
3. Three empty -> we should keep them? They are empty paragraphs. The rule says preserve ALL original content word-for-word. Empty paragraphs are content (they are just ). We should keep them as . But we must remove style attribute. So repeated three times.
4. Job Description
-> Job Description
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 ✍️
. Must preserve all original content word-for-word. We need to parse the given raw text (which includes HTML tags and style attributes). We need to extract the textual content, preserving it exactly, then wrap in appropriate tags. We must not add or remove any content. So we need to output the same text but with HTML tags as per rules, removing style attributes etc. However we must preserve the content word-for-word, meaning we cannot drop any characters from the original text. But we are allowed to change formatting (tags). The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means the textual content (the visible characters) must stay same. We can remove HTML tags and style attributes as they are not part of the content? The original content includes those tags; but they are markup, not visible text. Usually "content" refers to the textual content. We'll assume we need to keep the words exactly as they appear, ignoring original markup. We'll strip out the given HTML tags and produce new semantic HTML. Thus we need to extract the plain text from the given snippet, then format. Let's extract the text: Starting 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
na
At OM Bank, we strive to attract great people who are passionate about coming together for a higher purpose- building something unique and aspirational, always aiming to be the best they can be. We are rooted in our purpose of inspiring and enabling our customers to grow and sustain their prosperity.The successful incumbent will be responsible for the following:
KEY RESULT AREAS
- Gather information, create business cases and prioritise the projects and enhancements for that which you control; in close conjunction with the development team you will implement these changes.
- Create a functional product roadmap aligned to business strategy with sound and demonstrable commercial rationale
- Manage all requests for change from the business within your product and align these to current enhancements and projects where possible after critical assessment
- Work directly alongside your development teams, driving the product backlog and prioritisation thereof
- Clearly communicate progress and goals with stakeholders and management
- Projects and enhancements should be cased with respect to key metrics related to this product where possible based on data, and where data is unavailable creative means should be found to demonstrate the reasonability of assumptions
- The success or failure of an enhancement or project should be related back to the same key metrics and be relatable to commercial rationale
- Develop artefacts to drive all your work forward, including user stories, requirements documents, use cases, personas, white papers, demos and presentations
- Lead, coach, and inspire product managers and specialists to foster a high-performance culture focused on delivering exceptional outcomes
- Build and maintain strong relationships with key stakeholders including executive leadership, Product Owners, external partners, and relevant regulatory bodies
Minimum Requirements:
- Relevant tertiary qualification and a proved track record of delivery.
- Minimum 7 years’ relevant Telco product and/or operational management experience.
- Exposure to or experience in developing business models for changes
- An executor who has demonstrable success in a product ownership role, where you have needed to understand commercial goals, think strategically and balance the need for a great solution with that of the current need state.
- Proven track record of a role where you live and breathe customer experience, the end-to-end journey, UX and UI
- Track record of delivering complex projects with agile development teams, (with a firm personal belief and business strategy of MVP and test, iterate, test, iterate)
- Knowledge of Kanban/Lean desirable
- Knowledge and experience in using tracking and collaboration tools such as Jira, Miro and TFS
- Knowledge and experience with typically used Agile techniques such as User Story mapping, ATDD, TDD,
- Knowledge of agile methodology and frameworks like Scrum, Kanban, Scaled Agile (SAFe)
- Commitment to deliver the agreed work through the team and relevant stakeholders
- Understand the value of team metrics and ask them to be tracked to drive team performance
- Stakeholder Management, Negotiation & Communication Skills
- Clarity on delivering clear, prioritised stories with acceptance criteria. Aligning these to Features
Skills
Adaptive Thinking, Agile Project Management, Change Management, Executing Plans, Managing Stakeholder Expectations, Policies & Procedures, Policy Development, Product Development Management, Project Communications Management, Project Life Cycle Management, Project Performance Management (PM), Project Quality Assurance, Project Scope ManagementCompetencies
Action OrientedBalances StakeholdersBusiness InsightCultivates InnovationDecision QualityDevelops TalentDrives EngagementDrives ResultsEducation
NQF Level 9 – MastersClosing Date
19 June 2026 , 23:59The 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!
Now we need to extract plain text, preserving spaces and punctuation exactly as they appear (including HTML entities like ' which is an apostrophe). We need to keep them as they appear? The original text includes ' which is HTML entity for apostrophe. Should we keep it as ' or convert to ’? The instruction: preserve ALL original content word-for-word. So we should keep the entity as is. However after stripping tags, we might keep the entity. That's fine. Now we need to structure withfor 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.
We need to decide which sections correspond.
From the text:
- Intro: "Let's Write Africa's Story Together!" (with entity) then "Old Mutual is a firm believer..." then blank lines then "Job Description" then "na" (maybe a placeholder). Then paragraph: "At OM Bank, we strive..." etc.
- Then "The successful incumbent will be responsible for the following:" then a bold/underline "KEY RESULT AREAS" then list items (these are duties/responsibilities). So we could treat "KEY RESULT AREAS" as a section header (maybe Responsibilities). Use Responsibilities
then - ... items.
- Then "Minimum Requirements: " then list items (requirements). So section header: Requirements (or Minimum Requirements). Use
Requirements
then list.
- Then after that there is a blank paragraph then "Skills" then a line of skills (comma-separated). This is not a list but we could treat as a paragraph? The rule: Use - for list items (duties, requirements, qualifications, skills). Skills are listed as comma-separated; we could still make each skill a list item? But the instruction says preserve ALL original content word-for-word. If we change the format from comma-separated to list items, we are altering content (adding
- and removing commas). That would be adding/removing? It changes representation but not the words? Actually we would be adding tags and removing commas, which changes the textual content (commas removed). That would violate "preserve ALL original content word-for-word". So we must keep the skills exactly as they appear: "Adaptive Thinking, Agile Project Management, Change Management, Executing Plans, Managing Stakeholder Expectations, Policies & Procedures, Policy Development, Product Development Management, Project Communications Management, Project Life Cycle Management, Project Performance Management (PM), Project Quality Assurance, Project Scope Management". We must not alter that string. So we should wrap it in a
(since it's general text). However the rule says use
- for list items (duties, requirements, qualifications, skills). But if we keep as paragraph, we violate that rule? The rule says "Use
- for list items (duties, requirements, qualifications, skills)". It implies if the content is a list, we should use
- . But the skills are not presented as a list; they are a comma-separated line. So it's not a list; it's a sentence. So we can keep as
. That's fine.
- Then "Competencies" then a series of words each followed by empty
tags. The text appears as: "Action OrientedBalances StakeholdersBusiness InsightCultivates InnovationDecision QualityDevelops TalentDrives EngagementDrives Results". So each competency is followed by two empty h3 tags. We need to preserve that exactly. So we will keep that string as is, inside a maybe.
- Then "Education" then "NQF Level 9 – Masters". So we can treat Education as
Education
then NQF Level 9 – Masters
.
- Then "Closing Date" then "19 June 2026 , 23:59". So Closing Date
then 19 June 2026 , 23:59
.
- Then the italic bold statement about appointment: "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.
" So we need to preserve that exactly. Could be a with ... . But rule says no CSS classes, no inline styles, no
, but we can use and tags? The instruction only restricts use of ,
, CSS classes, inline styles. It didn't forbid or . However we should aim to use semantic HTML: for paragraphs,
for headings, - for lists. Using and is okay but not semantic; but we must preserve original content word-for-word, which includes those tags. So we must keep ... inside the
. That means we will output a
containing 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.. That preserves the tags.
- Finally "
The Old Mutual Story!
" So we need to preserve that exactly: includes , , . We must keep them.
Thus our output HTML will consist of a series of elements: for intro paragraphs,
for section headings, - for lists (KEY RESULT AREAS and Minimum Requirements). For other sections like Skills, Competencies, Education, Closing Date, appointment note, final story, we will use
(preserving any internal tags like , , , etc.)
We must not add any extra content. Must not remove any content. Must preserve original spacing? We'll try to keep line breaks as they appear? Not required but we can keep them.
Let's extract the exact textual content including the tags we want to keep.
Better approach: We'll produce HTML that mirrors the original but with semantic tags for headings and lists, while preserving inner content exactly.
We need to decide what constitutes a "section header". The original uses Job Description, Minimum Requirements:, Skills, Competencies, Education, Closing Date. Also there is a bold/underline "KEY RESULT AREAS". We'll treat those as .
We also have "The successful incumbent will be responsible for the following:" which is introductory to the responsibilities list; we can keep that as a
before the
Responsibilities
maybe.
But 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 map:
- "KEY RESULT AREAS" -> maybe Responsibilities or Key Duties. We'll use Responsibilities
(or Key Duties). The rule says we can use those examples; we can choose Responsibilities.
- "Minimum Requirements:" -> Requirements.
- "Skills" -> Skills.
- "Competencies" -> maybe Competencies (not in examples but could be considered similar to Skills). We'll still use Competencies
.
- "Education" -> Education.
- "Closing Date" -> Closing Date.
- "Job Description" maybe not needed as a heading; could be introductory.
We also have "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer..." as intro.
We also have "na" after Job Description; that's weird but we must keep it.
Now we need to produce HTML.
Let's list the pieces in order:
1.
Let's Write Africa's Story Together!
-> We'll output Let's Write Africa's Story Together!
(remove style attribute). Keep inner tags.
2. 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.
3. Three empty -> we should keep them? They are empty paragraphs. The rule says preserve ALL original content word-for-word. Empty paragraphs are content (they are just ). We should keep them as . But we must remove style attribute. So repeated three times.
4. Job Description
-> Job Description
Requirements
then list. - Then after that there is a blank paragraph then "Skills" then a line of skills (comma-separated). This is not a list but we could treat as a paragraph? The rule: Use- for list items (duties, requirements, qualifications, skills). Skills are listed as comma-separated; we could still make each skill a list item? But the instruction says preserve ALL original content word-for-word. If we change the format from comma-separated to list items, we are altering content (adding
- and removing commas). That would be adding/removing? It changes representation but not the words? Actually we would be adding tags and removing commas, which changes the textual content (commas removed). That would violate "preserve ALL original content word-for-word". So we must keep the skills exactly as they appear: "Adaptive Thinking, Agile Project Management, Change Management, Executing Plans, Managing Stakeholder Expectations, Policies & Procedures, Policy Development, Product Development Management, Project Communications Management, Project Life Cycle Management, Project Performance Management (PM), Project Quality Assurance, Project Scope Management". We must not alter that string. So we should wrap it in a
(since it's general text). However the rule says use
- for list items (duties, requirements, qualifications, skills). But if we keep as paragraph, we violate that rule? The rule says "Use
- for list items (duties, requirements, qualifications, skills)". It implies if the content is a list, we should use
- . But the skills are not presented as a list; they are a comma-separated line. So it's not a list; it's a sentence. So we can keep as
. That's fine. - Then "Competencies" then a series of words each followed by empty
tags. The text appears as: "Action OrientedBalances StakeholdersBusiness InsightCultivates InnovationDecision QualityDevelops TalentDrives EngagementDrives Results". So each competency is followed by two empty h3 tags. We need to preserve that exactly. So we will keep that string as is, inside amaybe. - Then "Education" then "NQF Level 9 – Masters". So we can treat Education as
Education
thenNQF Level 9 – Masters
. - Then "Closing Date" then "19 June 2026 , 23:59". SoClosing Date
then19 June 2026 , 23:59
. - Then the italic bold statement about appointment: "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.
" So we need to preserve that exactly. Could be awith ... . But rule says no CSS classes, no inline styles, no
, but we can use and tags? The instruction only restricts use of,
, CSS classes, inline styles. It didn't forbid or . However we should aim to use semantic HTML:for paragraphs,
for headings,
- for lists. Using and is okay but not semantic; but we must preserve original content word-for-word, which includes those tags. So we must keep ... inside the
. That means we will output a
containing 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.. That preserves the tags. - Finally "
The Old Mutual Story!
" So we need to preserve that exactly: includes , , . We must keep them. Thus our output HTML will consist of a series of elements:for intro paragraphs,
for section headings,
- for lists (KEY RESULT AREAS and Minimum Requirements). For other sections like Skills, Competencies, Education, Closing Date, appointment note, final story, we will use
(preserving any internal tags like , , , etc.) We must not add any extra content. Must not remove any content. Must preserve original spacing? We'll try to keep line breaks as they appear? Not required but we can keep them. Let's extract the exact textual content including the tags we want to keep. Better approach: We'll produce HTML that mirrors the original but with semantic tags for headings and lists, while preserving inner content exactly. We need to decide what constitutes a "section header". The original uses Job Description, Minimum Requirements:, Skills, Competencies, Education, Closing Date. Also there is a bold/underline "KEY RESULT AREAS". We'll treat those as
. We also have "The successful incumbent will be responsible for the following:" which is introductory to the responsibilities list; we can keep that as a
before the
Responsibilities
maybe. But the rule says usefor section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should map: - "KEY RESULT AREAS" -> maybe Responsibilities or Key Duties. We'll use
Responsibilities
(or Key Duties). The rule says we can use those examples; we can choose Responsibilities. - "Minimum Requirements:" -> Requirements. - "Skills" -> Skills. - "Competencies" -> maybe Competencies (not in examples but could be considered similar to Skills). We'll still useCompetencies
. - "Education" -> Education. - "Closing Date" -> Closing Date. - "Job Description" maybe not needed as a heading; could be introductory. We also have "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer..." as intro. We also have "na" after Job Description; that's weird but we must keep it. Now we need to produce HTML. Let's list the pieces in order: 1.Let's Write Africa's Story Together!
-> We'll outputLet's Write Africa's Story Together!
(remove style attribute). Keep inner tags. 2.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.
3. Three empty -> we should keep them? They are empty paragraphs. The rule says preserve ALL original content word-for-word. Empty paragraphs are content (they are just ). We should keep them as . But we must remove style attribute. So repeated three times. 4.Job Description
->Job Description
- for lists (KEY RESULT AREAS and Minimum Requirements). For other sections like Skills, Competencies, Education, Closing Date, appointment note, final story, we will use
- for lists. Using and is okay but not semantic; but we must preserve original content word-for-word, which includes those tags. So we must keep ... inside the
- . But the skills are not presented as a list; they are a comma-separated line. So it's not a list; it's a sentence. So we can keep as
- for list items (duties, requirements, qualifications, skills)". It implies if the content is a list, we should use
- for list items (duties, requirements, qualifications, skills). But if we keep as paragraph, we violate that rule? The rule says "Use
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 ✍️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.