Job Description
,
, - . No CSS classes, no inline styles, no , no
. Must preserve all original content word-for-word, but we need to strip out the HTML tags and formatting from input, and then reformat using allowed tags.
We must keep the content exactly as given (word-for-word) but we can change tags to semantic ones. We must not add or remove any text. So we need to extract the plain text from the given HTML, preserving spaces and line breaks? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must output the same textual content, but we can wrap it in ,
, - . We must not add extra text, not remove any. So we need to produce HTML that when stripped of tags yields exactly the original plain text (including spaces and line breaks?). Usually they'd accept that we reformat but keep same words.
Thus we need to parse the input and produce sections.
Let's extract the plain text from the given HTML.
Input:
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
Key responsibilities:
- Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy.
- Influence actuarial modernisation priorities through engagement with senior management and governance forums.
- Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes.
- Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes.
- Test and develop modern actuarial technologies, platforms and automation capabilities.
- Champion best practice architecture, reusability and standardisation.
- Partner with enterprise data teams to align actuarial solutions with broader data strategy.
- Drive integration between actuarial models, data platforms and reporting environments.
- Ensure embedment of new solutions via training and knowledge share with production teams
- Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology
Key Result Areas / Outputs:
- Reduction in actuarial reporting cycle times.
- Increased automation of valuation and reporting processes.
- Simplified and standardised reporting architecture.
- Enhanced process governance and auditability.
- Measurable reduction in key-person dependencies.
- Implementation of scalable actuarial data and reporting solutions
- Translate business problems into practical, scalable, and maintainable technical solutions.
- Own solutions from concept and requirements through to development, testing, implementation, and support.
- Continuously improve operational processes, automation solutions, and processing infrastructure.
Qualifications, Skills and Experience:
Technical Skills:
- Experience with actuarial valuation environments and processes
- Experience with actuarial modelling software
- Actuarial data management (SQL, Python, Power BI etc.)
- Experience with process automation tools and techniques
- Experience with cloud-based solutions
Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments
Role Details:
Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment.
Skills
Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management
Competencies
Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives Results
Education
NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent
Closing Date
04 October 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!
We need to extract plain text. Let's do stepwise.
First line: "Let's Write Africa's Story Together!" (note HTML entity ' is apostrophe). So text: Let's Write Africa's Story Together!
Second line: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this."
Then three empty paragraphs.
Then "Job Description" (bold). Then four empty paragraphs.
Then "Key responsibilities:" (underlined bold). Then list items.
List items text:
- Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy.
- Influence actuarial modernisation priorities through engagement with senior management and governance forums.
- Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes.
- Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes.
- Test and develop modern actuarial technologies, platforms and automation capabilities.
- Champion best practice architecture, reusability and standardisation.
- Partner with enterprise data teams to align actuarial solutions with broader data strategy.
- Drive integration between actuarial models, data platforms and reporting environments.
- Ensure embedment of new solutions via training and knowledge share with production teams
- Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology
Note the last item missing period? It ends with methodology (no period). Keep as is.
Then blank line? Then "Key Result Areas / Outputs:" (underlined bold). Then list:
- Reduction in actuarial reporting cycle times.
- Increased automation of valuation and reporting processes.
- Simplified and standardised reporting architecture.
- Enhanced process governance and auditability.
- Measurable reduction in key-person dependencies.
- Implementation of scalable actuarial data and reporting solutions (note there's a non-breaking space after solutions? It shows a space then maybe ? We'll keep as "Implementation of scalable actuarial data and reporting solutions". Probably keep the space but we can ignore extra spaces? Must preserve word-for-word, but we can't represent . We'll just output a normal space.
- Translate business problems into practical, scalable, and maintainable technical solutions. (again trailing space)
- Own solutions from concept and requirements through to development, testing, implementation, and support.
- Continuously improve operational processes, automation solutions, and processing infrastructure.
Then "Qualifications, Skills and Experience:" (underlined bold). Then "Technical Skills:" (bold). Then list:
- Experience with actuarial valuation environments and processes
- Experience with actuarial modelling software
- Actuarial data management (SQL, Python, Power BI etc.)
- Experience with process automation tools and techniques
- Experience with cloud-based solutions
Then paragraph: "Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments"
Then a non-breaking space paragraph (just a space). Then "Role Details:" (bold). Then paragraph: "Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment."
Then three empty paragraphs.
Then "Skills" (bold). Then two empty paragraphs. Then the skills list: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management"
Then two empty paragraphs.
Then "Competencies" (bold). Then two empty paragraphs. Then list of competencies each followed by pairs? The text shows:
Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives Results
It seems each competency is followed by two empty h3 tags. Likely formatting artifact. We need to preserve the text word-for-word, but we cannot keep the tags because we cannot use etc but we can keep them? The rule says no tags, but doesn't forbid . However we are supposed to use only
,
, - . It says "Use
for section headers ... Use - for list items ... No CSS classes, no inline styles, no s, no
tags". It doesn't explicitly forbid other tags like , but the instruction says to format as clean semantic HTML using those tags. Likely we should not include any other tags besides p, h4, ul, li. So we should strip out the artifacts, but we must preserve the text word-for-word. Removing the tags is okay because they are not part of the content; they are formatting. The content is the competency names. So we should output each competency as a list item? The original shows them not in a list but separated by empty h3 tags. Probably they intended each as a separate line. We could treat them as a list of competencies. But we must not add or remove text. If we convert them to list items, we are not adding or removing text, just changing formatting. That's acceptable as long as the textual content remains same. However we need to decide if we should wrap them in - . The original didn't have list markup; it's just plain text with some empty tags. The instruction: "If text has no clear sections, just wrap paragraphs in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item.
Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use.
We have sections:
- Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs.
- Then "Job Description" maybe as a section header? Could be Job Description
.
- Then "Key responsibilities:" as Key responsibilities:
followed by - ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list.
- Then "Qualifications, Skills and Experience:" as Qualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe as Technical Skills:
or could be ... but we cannot use strong? We can use with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay.
- Then the paragraph about qualified actuary.
- Then "Role Details:" as Role Details:
followed by paragraph.
- Then "Skills:" as Skills:
followed by paragraph of skills list.
- Then "Competencies:" as Competencies:
followed by - each competency.
- Then "Education:" as
Education:
followed by paragraph.
- Then "Closing Date:" as Closing Date:
followed by paragraph.
- Then the appointment paragraph (maybe as ).
- Then final "The Old Mutual Story!" as
maybe.
We must not add any extra text. Ensure we keep all text exactly.
Let's compile the final HTML.
We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
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 📝
. Must preserve all original content word-for-word, but we need to strip out the HTML tags and formatting from input, and then reformat using allowed tags. We must keep the content exactly as given (word-for-word) but we can change tags to semantic ones. We must not add or remove any text. So we need to extract the plain text from the given HTML, preserving spaces and line breaks? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must output the same textual content, but we can wrap it in
,
, - . We must not add extra text, not remove any. So we need to produce HTML that when stripped of tags yields exactly the original plain text (including spaces and line breaks?). Usually they'd accept that we reformat but keep same words.
Thus we need to parse the input and produce sections.
Let's extract the plain text from the given HTML.
Input:
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
Key responsibilities:
- Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy.
- Influence actuarial modernisation priorities through engagement with senior management and governance forums.
- Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes.
- Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes.
- Test and develop modern actuarial technologies, platforms and automation capabilities.
- Champion best practice architecture, reusability and standardisation.
- Partner with enterprise data teams to align actuarial solutions with broader data strategy.
- Drive integration between actuarial models, data platforms and reporting environments.
- Ensure embedment of new solutions via training and knowledge share with production teams
- Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology
Key Result Areas / Outputs:
- Reduction in actuarial reporting cycle times.
- Increased automation of valuation and reporting processes.
- Simplified and standardised reporting architecture.
- Enhanced process governance and auditability.
- Measurable reduction in key-person dependencies.
- Implementation of scalable actuarial data and reporting solutions
- Translate business problems into practical, scalable, and maintainable technical solutions.
- Own solutions from concept and requirements through to development, testing, implementation, and support.
- Continuously improve operational processes, automation solutions, and processing infrastructure.
Qualifications, Skills and Experience:
Technical Skills:
- Experience with actuarial valuation environments and processes
- Experience with actuarial modelling software
- Actuarial data management (SQL, Python, Power BI etc.)
- Experience with process automation tools and techniques
- Experience with cloud-based solutions
Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments
Role Details:
Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment.
Skills
Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management
Competencies
Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives Results
Education
NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent
Closing Date
04 October 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!
We need to extract plain text. Let's do stepwise.
First line: "Let's Write Africa's Story Together!" (note HTML entity ' is apostrophe). So text: Let's Write Africa's Story Together!
Second line: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this."
Then three empty paragraphs.
Then "Job Description" (bold). Then four empty paragraphs.
Then "Key responsibilities:" (underlined bold). Then list items.
List items text:
- Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy.
- Influence actuarial modernisation priorities through engagement with senior management and governance forums.
- Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes.
- Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes.
- Test and develop modern actuarial technologies, platforms and automation capabilities.
- Champion best practice architecture, reusability and standardisation.
- Partner with enterprise data teams to align actuarial solutions with broader data strategy.
- Drive integration between actuarial models, data platforms and reporting environments.
- Ensure embedment of new solutions via training and knowledge share with production teams
- Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology
Note the last item missing period? It ends with methodology (no period). Keep as is.
Then blank line? Then "Key Result Areas / Outputs:" (underlined bold). Then list:
- Reduction in actuarial reporting cycle times.
- Increased automation of valuation and reporting processes.
- Simplified and standardised reporting architecture.
- Enhanced process governance and auditability.
- Measurable reduction in key-person dependencies.
- Implementation of scalable actuarial data and reporting solutions (note there's a non-breaking space after solutions? It shows a space then maybe ? We'll keep as "Implementation of scalable actuarial data and reporting solutions". Probably keep the space but we can ignore extra spaces? Must preserve word-for-word, but we can't represent . We'll just output a normal space.
- Translate business problems into practical, scalable, and maintainable technical solutions. (again trailing space)
- Own solutions from concept and requirements through to development, testing, implementation, and support.
- Continuously improve operational processes, automation solutions, and processing infrastructure.
Then "Qualifications, Skills and Experience:" (underlined bold). Then "Technical Skills:" (bold). Then list:
- Experience with actuarial valuation environments and processes
- Experience with actuarial modelling software
- Actuarial data management (SQL, Python, Power BI etc.)
- Experience with process automation tools and techniques
- Experience with cloud-based solutions
Then paragraph: "Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments"
Then a non-breaking space paragraph (just a space). Then "Role Details:" (bold). Then paragraph: "Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment."
Then three empty paragraphs.
Then "Skills" (bold). Then two empty paragraphs. Then the skills list: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management"
Then two empty paragraphs.
Then "Competencies" (bold). Then two empty paragraphs. Then list of competencies each followed by pairs? The text shows:
Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives Results
It seems each competency is followed by two empty h3 tags. Likely formatting artifact. We need to preserve the text word-for-word, but we cannot keep the tags because we cannot use etc but we can keep them? The rule says no tags, but doesn't forbid . However we are supposed to use only
,
, - . It says "Use
for section headers ... Use - for list items ... No CSS classes, no inline styles, no s, no
tags". It doesn't explicitly forbid other tags like , but the instruction says to format as clean semantic HTML using those tags. Likely we should not include any other tags besides p, h4, ul, li. So we should strip out the artifacts, but we must preserve the text word-for-word. Removing the tags is okay because they are not part of the content; they are formatting. The content is the competency names. So we should output each competency as a list item? The original shows them not in a list but separated by empty h3 tags. Probably they intended each as a separate line. We could treat them as a list of competencies. But we must not add or remove text. If we convert them to list items, we are not adding or removing text, just changing formatting. That's acceptable as long as the textual content remains same. However we need to decide if we should wrap them in - . The original didn't have list markup; it's just plain text with some empty tags. The instruction: "If text has no clear sections, just wrap paragraphs in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item.
Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use.
We have sections:
- Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs.
- Then "Job Description" maybe as a section header? Could be Job Description
.
- Then "Key responsibilities:" as Key responsibilities:
followed by - ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list.
- Then "Qualifications, Skills and Experience:" as Qualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe as Technical Skills:
or could be ... but we cannot use strong? We can use with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay.
- Then the paragraph about qualified actuary.
- Then "Role Details:" as Role Details:
followed by paragraph.
- Then "Skills:" as Skills:
followed by paragraph of skills list.
- Then "Competencies:" as Competencies:
followed by - each competency.
- Then "Education:" as
Education:
followed by paragraph.
- Then "Closing Date:" as Closing Date:
followed by paragraph.
- Then the appointment paragraph (maybe as ).
- Then final "The Old Mutual Story!" as
maybe.
We must not add any extra text. Ensure we keep all text exactly.
Let's compile the final HTML.
We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
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 📝
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
Key responsibilities:
- Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy.
- Influence actuarial modernisation priorities through engagement with senior management and governance forums.
- Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes.
- Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes.
- Test and develop modern actuarial technologies, platforms and automation capabilities.
- Champion best practice architecture, reusability and standardisation.
- Partner with enterprise data teams to align actuarial solutions with broader data strategy.
- Drive integration between actuarial models, data platforms and reporting environments.
- Ensure embedment of new solutions via training and knowledge share with production teams
- Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology
Key Result Areas / Outputs:
- Reduction in actuarial reporting cycle times.
- Increased automation of valuation and reporting processes.
- Simplified and standardised reporting architecture.
- Enhanced process governance and auditability.
- Measurable reduction in key-person dependencies.
- Implementation of scalable actuarial data and reporting solutions
- Translate business problems into practical, scalable, and maintainable technical solutions.
- Own solutions from concept and requirements through to development, testing, implementation, and support.
- Continuously improve operational processes, automation solutions, and processing infrastructure.
Qualifications, Skills and Experience:
Technical Skills:
- Experience with actuarial valuation environments and processes
- Experience with actuarial modelling software
- Actuarial data management (SQL, Python, Power BI etc.)
- Experience with process automation tools and techniques
- Experience with cloud-based solutions
Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments
Role Details:
Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment.
Skills
Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk ManagementCompetencies
Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives ResultsEducation
NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalentClosing Date
04 October 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!
We need to extract plain text. Let's do stepwise. First line: "Let's Write Africa's Story Together!" (note HTML entity ' is apostrophe). So text: Let's Write Africa's Story Together! Second line: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." Then three empty paragraphs. Then "Job Description" (bold). Then four empty paragraphs. Then "Key responsibilities:" (underlined bold). Then list items. List items text: - Develop and execute the actuarial modernisation roadmap aligned to business and actuarial strategy. - Influence actuarial modernisation priorities through engagement with senior management and governance forums. - Identify opportunities to simplify and optimise actuarial modelling, valuation and reporting processes. - Lead initiatives that reduce operational complexity, manual intervention and risk across actuarial processes. - Test and develop modern actuarial technologies, platforms and automation capabilities. - Champion best practice architecture, reusability and standardisation. - Partner with enterprise data teams to align actuarial solutions with broader data strategy. - Drive integration between actuarial models, data platforms and reporting environments. - Ensure embedment of new solutions via training and knowledge share with production teams - Liaise with stakeholders across the group as well as external parties to source solutions and develop best practice methodology Note the last item missing period? It ends with methodology (no period). Keep as is. Then blank line? Then "Key Result Areas / Outputs:" (underlined bold). Then list: - Reduction in actuarial reporting cycle times. - Increased automation of valuation and reporting processes. - Simplified and standardised reporting architecture. - Enhanced process governance and auditability. - Measurable reduction in key-person dependencies. - Implementation of scalable actuarial data and reporting solutions (note there's a non-breaking space after solutions? It shows a space then maybe ? We'll keep as "Implementation of scalable actuarial data and reporting solutions". Probably keep the space but we can ignore extra spaces? Must preserve word-for-word, but we can't represent . We'll just output a normal space. - Translate business problems into practical, scalable, and maintainable technical solutions. (again trailing space) - Own solutions from concept and requirements through to development, testing, implementation, and support. - Continuously improve operational processes, automation solutions, and processing infrastructure. Then "Qualifications, Skills and Experience:" (underlined bold). Then "Technical Skills:" (bold). Then list: - Experience with actuarial valuation environments and processes - Experience with actuarial modelling software - Actuarial data management (SQL, Python, Power BI etc.) - Experience with process automation tools and techniques - Experience with cloud-based solutions Then paragraph: "Qualified or nearly qualified actuary with 6 or more years of experience in actuarial valuation, reporting, systems design, architecture or transformation environments" Then a non-breaking space paragraph (just a space). Then "Role Details:" (bold). Then paragraph: "Lead the reimagination of our actuarial reporting value chain and build a sustainable, future-fit actuarial environment." Then three empty paragraphs. Then "Skills" (bold). Then two empty paragraphs. Then the skills list: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management" Then two empty paragraphs. Then "Competencies" (bold). Then two empty paragraphs. Then list of competencies each followed by pairs? The text shows: Balances StakeholdersBuilds NetworksBusiness InsightCollaboratesCommunicates EffectivelyCultivates InnovationDecision QualityDrives Results It seems each competency is followed by two empty h3 tags. Likely formatting artifact. We need to preserve the text word-for-word, but we cannot keep the tags because we cannot use. However we are supposed to use only
,
, - . It says "Use
for section headers ... Use - for list items ... No CSS classes, no inline styles, no s, no
tags". It doesn't explicitly forbid other tags like , but the instruction says to format as clean semantic HTML using those tags. Likely we should not include any other tags besides p, h4, ul, li. So we should strip out the artifacts, but we must preserve the text word-for-word. Removing the tags is okay because they are not part of the content; they are formatting. The content is the competency names. So we should output each competency as a list item? The original shows them not in a list but separated by empty h3 tags. Probably they intended each as a separate line. We could treat them as a list of competencies. But we must not add or remove text. If we convert them to list items, we are not adding or removing text, just changing formatting. That's acceptable as long as the textual content remains same. However we need to decide if we should wrap them in - . The original didn't have list markup; it's just plain text with some empty tags. The instruction: "If text has no clear sections, just wrap paragraphs in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item.
Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use.
We have sections:
- Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs.
- Then "Job Description" maybe as a section header? Could be Job Description
.
- Then "Key responsibilities:" as Key responsibilities:
followed by - ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list.
- Then "Qualifications, Skills and Experience:" as Qualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe as Technical Skills:
or could be ... but we cannot use strong? We can use with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay.
- Then the paragraph about qualified actuary.
- Then "Role Details:" as Role Details:
followed by paragraph.
- Then "Skills:" as Skills:
followed by paragraph of skills list.
- Then "Competencies:" as Competencies:
followed by - each competency.
- Then "Education:" as
Education:
followed by paragraph.
- Then "Closing Date:" as Closing Date:
followed by paragraph.
- Then the appointment paragraph (maybe as ).
- Then final "The Old Mutual Story!" as
maybe.
We must not add any extra text. Ensure we keep all text exactly.
Let's compile the final HTML.
We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
for section headers ... Use - for list items ... No CSS classes, no inline styles, no s, no
tags". It doesn't explicitly forbid other tags like , but the instruction says to format as clean semantic HTML using those tags. Likely we should not include any other tags besides p, h4, ul, li. So we should strip out the artifacts, but we must preserve the text word-for-word. Removing the tags is okay because they are not part of the content; they are formatting. The content is the competency names. So we should output each competency as a list item? The original shows them not in a list but separated by empty h3 tags. Probably they intended each as a separate line. We could treat them as a list of competencies. But we must not add or remove text. If we convert them to list items, we are not adding or removing text, just changing formatting. That's acceptable as long as the textual content remains same. However we need to decide if we should wrap them in - . The original didn't have list markup; it's just plain text with some empty tags. The instruction: "If text has no clear sections, just wrap paragraphs in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item.
Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use.
We have sections:
- Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs.
- Then "Job Description" maybe as a section header? Could be Job Description
.
- Then "Key responsibilities:" as Key responsibilities:
followed by - ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list.
- Then "Qualifications, Skills and Experience:" as Qualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe as Technical Skills:
or could be ... but we cannot use strong? We can use with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay.
- Then the paragraph about qualified actuary.
- Then "Role Details:" as Role Details:
followed by paragraph.
- Then "Skills:" as Skills:
followed by paragraph of skills list.
- Then "Competencies:" as Competencies:
followed by - each competency.
- Then "Education:" as
Education:
followed by paragraph.
- Then "Closing Date:" as Closing Date:
followed by paragraph.
- Then the appointment paragraph (maybe as ).
- Then final "The Old Mutual Story!" as
maybe.
We must not add any extra text. Ensure we keep all text exactly.
Let's compile the final HTML.
We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
tags". It doesn't explicitly forbid other tags like
, but the instruction says to format as clean semantic HTML using those tags. Likely we should not include any other tags besides p, h4, ul, li. So we should strip out the artifacts, but we must preserve the text word-for-word. Removing the tags is okay because they are not part of the content; they are formatting. The content is the competency names. So we should output each competency as a list item? The original shows them not in a list but separated by empty h3 tags. Probably they intended each as a separate line. We could treat them as a list of competencies. But we must not add or remove text. If we convert them to list items, we are not adding or removing text, just changing formatting. That's acceptable as long as the textual content remains same. However we need to decide if we should wrap them in - . The original didn't have list markup; it's just plain text with some empty tags. The instruction: "If text has no clear sections, just wrap paragraphs in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item.
Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use.
We have sections:
- Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs.
- Then "Job Description" maybe as a section header? Could be Job Description
.
- Then "Key responsibilities:" as Key responsibilities:
followed by - ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list.
- Then "Qualifications, Skills and Experience:" as Qualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe as Technical Skills:
or could be ... but we cannot use strong? We can use with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay.
- Then the paragraph about qualified actuary.
- Then "Role Details:" as Role Details:
followed by paragraph.
- Then "Skills:" as Skills:
followed by paragraph of skills list.
- Then "Competencies:" as Competencies:
followed by - each competency.
- Then "Education:" as
Education:
followed by paragraph.
- Then "Closing Date:" as Closing Date:
followed by paragraph.
- Then the appointment paragraph (maybe as ).
- Then final "The Old Mutual Story!" as
maybe.
We must not add any extra text. Ensure we keep all text exactly.
Let's compile the final HTML.
We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
tags". But we have clear sections: Skills, Competencies, Education, Closing Date etc. For competencies, we could treat as a list. But we need to decide based on typical job description: competencies often listed as bullet points. The original had each competency followed by two empty h3 tags, maybe to create line breaks. So we can treat each as a separate line item. Thus we will output a
- for each competency.
Similarly for skills line: "Analytical Thinking, Computer Literacy, Data Compilation, Data Controls, Executing Plans, Information Management, Insurance Product Management, Insurance Sales, Legal Practices, Market Analysis, Numerical Aptitude, Risk Management". This is a comma-separated list. Could be kept as a paragraph. But we could also make a list. However original not marked as list. Safer to keep as a paragraph.
Now Education: "NQF Level 7 - Degree, Advance Diploma or Postgraduate Certificate or equivalent"
Closing Date: "04 October 2026 , 23:59" Note there is a space before comma? Actually "04 October 2026 , 23:59". We'll keep exactly.
Then the 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."
Then final: "The Old Mutual Story!" (italic bold inside emphasis-2). Actually it's The Old Mutual Story!. So text: The Old Mutual Story!
Now we need to produce HTML with
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). We need to decide which headings to use. We have sections: - Intro: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." These could be intro paragraphs. - Then "Job Description" maybe as a section header? Could be
Job Description
. - Then "Key responsibilities:" asKey responsibilities:
followed by- ...
- Then "Key Result Areas / Outputs:" as
Key Result Areas / Outputs:
followed by list. - Then "Qualifications, Skills and Experience:" asQualifications, Skills and Experience:
. Inside that we have "Technical Skills:" maybe asTechnical Skills:
or could be... but we cannot use strong? We can use
with bold? But we cannot add inline styles. We could just keep as
Technical Skills:
but we lose bold. However we must preserve original content word-for-word, but we can change tags; the bold is formatting not content. So we can drop bold. It's okay. - Then the paragraph about qualified actuary. - Then "Role Details:" asRole Details:
followed by paragraph. - Then "Skills:" asSkills:
followed by paragraph of skills list. - Then "Competencies:" asCompetencies:
followed by- each competency.
- Then "Education:" as
Education:
followed by paragraph. - Then "Closing Date:" asClosing Date:
followed by paragraph. - Then the appointment paragraph (maybe as). - Then final "The Old Mutual Story!" as
maybe. We must not add any extra text. Ensure we keep all text exactly. Let's compile the final HTML. We'll start with
Let's Write Africa's Story Together!
Old Mutual is a firm believer in
- each competency.
- Then "Education:" as
- ...
- Then "Key Result Areas / Outputs:" as
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.