Commissioned Financial Adviser ( Bizana/ Shelly Beach / Kokstad / Port Shepstone / Umzimkulu / Mount Frere and Surroundings)
Old Mutual
Job Description
,
for section headers, - for list items. No CSS classes, no inline styles, no , no
. Must preserve all original content word-for-word, no addition/removal/summarization/rephrasing. So we need to parse the given raw HTML and extract text content, then reformat according to rules.
Given raw HTML includes many tags with styles etc. We need to extract the textual content exactly as appears (preserving spaces, line breaks? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text, but we can change tags to semantic HTML. However we must not alter the text itself. So we need to output the same textual content, but with appropriate tags.
We need to identify sections: Intro paragraphs, then maybe a paragraph describing role, then list of responsibilities (ul li), then Skills heading, then list of skills (but currently it's just a paragraph with many comma-separated skills). Then Competencies heading, then list of competencies (each on its own line preceded by etc). Then Education heading, then education text. Then Closing Date heading, then date. Then a paragraph with italic bold about appointment. Then a final emphasis-2 line.
We must preserve all text exactly, including punctuation and spaces. However we need to wrap paragraphs in . For headings we use
. For list items we use - . The original had
...
. We need to keep the text inside li exactly as is, but we can change the wrapping: we should output - Responsible for the procurement of new business
etc. Ensure we don't add or remove any words.
We must not add extra text like "Responsibilities". The heading for that list is not present; the list appears after a paragraph. There's no explicit heading "Responsibilities". According to rules, we use for section headers like Responsibilities, Qualifications, etc. If there is no clear section header, we just wrap paragraphs in
. The list is under no heading; we could treat it as a list without a heading. That's okay.
But we need to decide where to put headings: The original has bolded "Skills", "Competencies", "Education", "Closing Date". Those are headings. We should convert those to
. Also there is an initial bolded "Let's Write Africa's Story Together!" which is inside emphasis-2 and b. That seems like a title/intro. Should we treat that as a heading? It's not one of the listed section headers, but we could still treat as maybe? The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., but not limited to? It says use for section headers (e.g. ...). Likely any heading should be . So we can convert those bolded headings to . Also the initial "Let's Write Africa's Story Together!" maybe is a tagline; could be considered a heading but not in list. Safer to treat as
? But it's bolded and emphasized. The instruction: preserve all original content word-for-word. Changing tags is allowed, but we must not change text. So we can wrap that text in
or
. Which is more appropriate? Since it's a title/intro, maybe
is okay. However the instruction says use for section headers (e.g. Responsibilities, Qualifications...). It doesn't forbid using for other headings. I'd treat it as as well.
But we need to be careful not to add extra text like colon or anything.
Now we need to strip all original tags and produce clean HTML.
Let's extract the text pieces in order as they appear in the raw HTML.
Raw HTML:
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies.
The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions.
Responsible for the procurement of new business
Expand sales of products and services with existing customers
Work mainly on own leads
Skills
Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships
Competencies
Action Oriented
Balances Stakeholders
Builds Networks
Collaborates
Communicates Effectively
Customer Focus
Drives Results
Ensures Accountability
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)
Closing Date
30 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 text nodes in order, ignoring tags.
Let's go step by step.
1. First p: text: "Let's Write Africa's Story Together!" (note the HTML entity ' is apostrophe). We must preserve the original content word-for-word. The original had ' which is an HTML entity for apostrophe. Should we keep it as ' or convert to apostrophe? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. The original content includes the entity '. So we must keep that exactly. Similarly " for quotes. So we must keep the entities as they appear. So we should not decode them. So we keep "Let's Write Africa's Story Together!".
2. Second p: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " Note there is a trailing space before closing span? The text includes a space after the period before closing span. We must preserve that space? Probably yes. We'll keep exactly as appears: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " (including trailing space). However HTML collapses spaces but we must keep as is.
3. Third p: empty.
4. Fourth p: empty.
5. Fifth p: contains two spans with br between. The text: first span: "We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies." Then
then second span: "The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions." So combined with line breaks? The original had
which we must not use (
tags not allowed). We need to represent that as something else? Since we cannot use
, we must preserve the content word-for-word but we cannot include
tags. However the instruction says: No
tags. So we must omit them, but that would be removing content. However maybe we can treat the line break as just whitespace; we can replace
with a space or newline? But that would be altering content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove
tags, we are removing content. But the rule also says No
tags. There's a conflict. We need to interpret: The original content includes
tags, but we are not allowed to use
tags in output. So we must remove them, but that would be removing content. However maybe the intention is that the raw text already had
tags as formatting, but we should treat them as line breaks and represent them as separate paragraphs () instead. Since we cannot use
, we can convert the line break into a paragraph break. That would be adding a
tag, but not adding textual content. The instruction about preserving original content word-for-word likely refers to the textual content, not the markup. So we can change tags as needed, but must not alter the actual words. So we can treat the
as a paragraph separator, resulting in two
elements. That seems reasonable.
Thus we will output two
elements: first containing the first sentence, second containing the second sentence.
6. Then a
empty.
7. Then the with three ...
- with the text inside. The text inside each
is: "Responsible for the procurement of new business", "Expand sales of products and services with existing customers", "Work mainly on own leads". We must preserve exactly those strings.
8. Then a
empty.
9. Then empty.
10. Then Skills
=> heading "Skills". We'll output Skills
.
11. Then two empty tags.
12. Then text: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". This is a paragraph of skills. We'll wrap in
.
13. Then
empty.
14. Then empty.
15. Then Competencies
=> heading Competencies
.
16. Then two empty tags.
17. Then text: "Action Oriented". Then
etc. The pattern: after each competency there is an empty . So the text appears as: "Action OrientedBalances StakeholdersBuilds NetworksCollaboratesCommunicates EffectivelyCustomer FocusDrives ResultsEnsures Accountability". So we need to extract each competency line as separate text pieces. The empty tags are just separators. We'll treat each competency as a list item? The original didn't have list markup; they are just separated by empty h3 tags. We could output them as a - list under Competencies heading. But the instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered a list. It's appropriate to make a list. However we must preserve original content word-for-word; converting to list items does not change the text. So we can output
- Action Oriented
- Balances Stakeholders
... etc.
But we need to decide if we should keep them as paragraphs separated by line breaks. Since there is no explicit list markup, but we can still use - as it's a list of items. The instruction says use
- for list items (duties, requirements, qualifications, skills). It doesn't forbid using for other lists. I'd use
- for competencies.
Thus after the heading
Competencies
, we output - Action Oriented
- Balances Stakeholders
- Builds Networks
- Collaborates
- Communicates Effectively
- Customer Focus
- Drives Results
- Ensures Accountability
.
18. Then after that, we have three times (empty).
19. Then Education
=> heading Education
.
20. Then text: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". Note there are two spaces before "(Required)"? In the original: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". There are two spaces before the opening parenthesis. We must preserve that exactly.
21. Then empty.
22. Then Closing Date
=> heading Closing Date
.
23. Then text: "30 October 2026 , 23:59". Note there is a space before the comma after 2026? Actually it's "30 October 2026 , 23:59". There's a space before the comma. We must preserve that.
24. Then four empty tags.
25. Then
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 output ...
? But we cannot use or ? The instruction only mentions ,
, - . It says No CSS classes, no inline styles, no s, no
tags. It doesn't forbid or . However to keep semantic HTML, we could just use and preserve the text without the italic/bold tags, as they are styling. The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove and tags, we are removing markup but not textual content. The textual content remains same. So it's acceptable to drop those tags as they are not required for semantic HTML. However we must not add any tags not allowed; and are allowed but not necessary. Safer to just output
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 text.
26. Then two empty tags.
27. Then
The Old Mutual Story!
. Text: "The Old Mutual Story!" with double tags and . We'll output The Old Mutual Story!
.
Now we need to output the HTML in order, with appropriate tags.
We must not include any empty tags? The instruction: If text has no clear sections, just wrap paragraphs in
tags. It doesn't say to omit empty paragraphs. But empty paragraphs have no content; we could omit them as they add no information. However preserving original content word-for-word: empty paragraphs have no textual content, so removing them doesn't remove any text. It's probably fine to omit them. But to be safe, we could keep them as
. However empty tags are allowed? They
. Must preserve all original content word-for-word, no addition/removal/summarization/rephrasing. So we need to parse the given raw HTML and extract text content, then reformat according to rules. Given raw HTML includes many tags with styles etc. We need to extract the textual content exactly as appears (preserving spaces, line breaks? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text, but we can change tags to semantic HTML. However we must not alter the text itself. So we need to output the same textual content, but with appropriate tags. We need to identify sections: Intro paragraphs, then maybe a paragraph describing role, then list of responsibilities (ul li), then Skills heading, then list of skills (but currently it's just a paragraph with many comma-separated skills). Then Competencies heading, then list of competencies (each on its own line preceded by etc). Then Education heading, then education text. Then Closing Date heading, then date. Then a paragraph with italic bold about appointment. Then a final emphasis-2 line. We must preserve all text exactly, including punctuation and spaces. However we need to wrap paragraphs in
. For headings we use
. For list items we use - . The original had
...
. We need to keep the text inside li exactly as is, but we can change the wrapping: we should output - Responsible for the procurement of new business
etc. Ensure we don't add or remove any words.
We must not add extra text like "Responsibilities". The heading for that list is not present; the list appears after a paragraph. There's no explicit heading "Responsibilities". According to rules, we use for section headers like Responsibilities, Qualifications, etc. If there is no clear section header, we just wrap paragraphs in
. The list is under no heading; we could treat it as a list without a heading. That's okay.
But we need to decide where to put headings: The original has bolded "Skills", "Competencies", "Education", "Closing Date". Those are headings. We should convert those to
. Also there is an initial bolded "Let's Write Africa's Story Together!" which is inside emphasis-2 and b. That seems like a title/intro. Should we treat that as a heading? It's not one of the listed section headers, but we could still treat as maybe? The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., but not limited to? It says use for section headers (e.g. ...). Likely any heading should be . So we can convert those bolded headings to . Also the initial "Let's Write Africa's Story Together!" maybe is a tagline; could be considered a heading but not in list. Safer to treat as
? But it's bolded and emphasized. The instruction: preserve all original content word-for-word. Changing tags is allowed, but we must not change text. So we can wrap that text in
or
. Which is more appropriate? Since it's a title/intro, maybe
is okay. However the instruction says use for section headers (e.g. Responsibilities, Qualifications...). It doesn't forbid using for other headings. I'd treat it as as well.
But we need to be careful not to add extra text like colon or anything.
Now we need to strip all original tags and produce clean HTML.
Let's extract the text pieces in order as they appear in the raw HTML.
Raw HTML:
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies.
The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions.
Responsible for the procurement of new business
Expand sales of products and services with existing customers
Work mainly on own leads
Skills
Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships
Competencies
Action Oriented
Balances Stakeholders
Builds Networks
Collaborates
Communicates Effectively
Customer Focus
Drives Results
Ensures Accountability
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)
Closing Date
30 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 text nodes in order, ignoring tags.
Let's go step by step.
1. First p: text: "Let's Write Africa's Story Together!" (note the HTML entity ' is apostrophe). We must preserve the original content word-for-word. The original had ' which is an HTML entity for apostrophe. Should we keep it as ' or convert to apostrophe? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. The original content includes the entity '. So we must keep that exactly. Similarly " for quotes. So we must keep the entities as they appear. So we should not decode them. So we keep "Let's Write Africa's Story Together!".
2. Second p: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " Note there is a trailing space before closing span? The text includes a space after the period before closing span. We must preserve that space? Probably yes. We'll keep exactly as appears: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " (including trailing space). However HTML collapses spaces but we must keep as is.
3. Third p: empty.
4. Fourth p: empty.
5. Fifth p: contains two spans with br between. The text: first span: "We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies." Then
then second span: "The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions." So combined with line breaks? The original had
which we must not use (
tags not allowed). We need to represent that as something else? Since we cannot use
, we must preserve the content word-for-word but we cannot include
tags. However the instruction says: No
tags. So we must omit them, but that would be removing content. However maybe we can treat the line break as just whitespace; we can replace
with a space or newline? But that would be altering content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove
tags, we are removing content. But the rule also says No
tags. There's a conflict. We need to interpret: The original content includes
tags, but we are not allowed to use
tags in output. So we must remove them, but that would be removing content. However maybe the intention is that the raw text already had
tags as formatting, but we should treat them as line breaks and represent them as separate paragraphs () instead. Since we cannot use
, we can convert the line break into a paragraph break. That would be adding a
tag, but not adding textual content. The instruction about preserving original content word-for-word likely refers to the textual content, not the markup. So we can change tags as needed, but must not alter the actual words. So we can treat the
as a paragraph separator, resulting in two
elements. That seems reasonable.
Thus we will output two
elements: first containing the first sentence, second containing the second sentence.
6. Then a
empty.
7. Then the with three ...
- with the text inside. The text inside each
is: "Responsible for the procurement of new business", "Expand sales of products and services with existing customers", "Work mainly on own leads". We must preserve exactly those strings.
8. Then a
empty.
9. Then empty.
10. Then Skills
=> heading "Skills". We'll output Skills
.
11. Then two empty tags.
12. Then text: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". This is a paragraph of skills. We'll wrap in
.
13. Then
empty.
14. Then empty.
15. Then Competencies
=> heading Competencies
.
16. Then two empty tags.
17. Then text: "Action Oriented". Then
etc. The pattern: after each competency there is an empty . So the text appears as: "Action OrientedBalances StakeholdersBuilds NetworksCollaboratesCommunicates EffectivelyCustomer FocusDrives ResultsEnsures Accountability". So we need to extract each competency line as separate text pieces. The empty tags are just separators. We'll treat each competency as a list item? The original didn't have list markup; they are just separated by empty h3 tags. We could output them as a - list under Competencies heading. But the instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered a list. It's appropriate to make a list. However we must preserve original content word-for-word; converting to list items does not change the text. So we can output
- Action Oriented
- Balances Stakeholders
... etc.
But we need to decide if we should keep them as paragraphs separated by line breaks. Since there is no explicit list markup, but we can still use - as it's a list of items. The instruction says use
- for list items (duties, requirements, qualifications, skills). It doesn't forbid using for other lists. I'd use
- for competencies.
Thus after the heading
Competencies
, we output - Action Oriented
- Balances Stakeholders
- Builds Networks
- Collaborates
- Communicates Effectively
- Customer Focus
- Drives Results
- Ensures Accountability
.
18. Then after that, we have three times (empty).
19. Then Education
=> heading Education
.
20. Then text: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". Note there are two spaces before "(Required)"? In the original: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". There are two spaces before the opening parenthesis. We must preserve that exactly.
21. Then empty.
22. Then Closing Date
=> heading Closing Date
.
23. Then text: "30 October 2026 , 23:59". Note there is a space before the comma after 2026? Actually it's "30 October 2026 , 23:59". There's a space before the comma. We must preserve that.
24. Then four empty tags.
25. Then
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 output ...
? But we cannot use or ? The instruction only mentions ,
, - . It says No CSS classes, no inline styles, no s, no
tags. It doesn't forbid or . However to keep semantic HTML, we could just use and preserve the text without the italic/bold tags, as they are styling. The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove and tags, we are removing markup but not textual content. The textual content remains same. So it's acceptable to drop those tags as they are not required for semantic HTML. However we must not add any tags not allowed; and are allowed but not necessary. Safer to just output
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 text.
26. Then two empty tags.
27. Then
The Old Mutual Story!
. Text: "The Old Mutual Story!" with double tags and . We'll output The Old Mutual Story!
.
Now we need to output the HTML in order, with appropriate tags.
We must not include any empty tags? The instruction: If text has no clear sections, just wrap paragraphs in
tags. It doesn't say to omit empty paragraphs. But empty paragraphs have no content; we could omit them as they add no information. However preserving original content word-for-word: empty paragraphs have no textual content, so removing them doesn't remove any text. It's probably fine to omit them. But to be safe, we could keep them as
. However empty tags are allowed? They
...
- Responsible for the procurement of new business etc. Ensure we don't add or remove any words. We must not add extra text like "Responsibilities". The heading for that list is not present; the list appears after a paragraph. There's no explicit heading "Responsibilities". According to rules, we use
Responsible for the procurement of new business
Expand sales of products and services with existing customers
Work mainly on own leads
...
. We'll convert each to - with the text inside. The text inside each
is: "Responsible for the procurement of new business", "Expand sales of products and services with existing customers", "Work mainly on own leads". We must preserve exactly those strings. 8. Then a
empty. 9. Then empty. 10. ThenSkills
=> heading "Skills". We'll outputSkills
. 11. Then two emptytags. 12. Then text: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". This is a paragraph of skills. We'll wrap in
. 13. Then
empty. 14. Then empty. 15. ThenCompetencies
=> headingCompetencies
. 16. Then two emptytags. 17. Then text: "Action Oriented". Then
etc. The pattern: after each competency there is an empty . So the text appears as: "Action OrientedBalances StakeholdersBuilds NetworksCollaboratesCommunicates EffectivelyCustomer FocusDrives ResultsEnsures Accountability". So we need to extract each competency line as separate text pieces. The empty tags are just separators. We'll treat each competency as a list item? The original didn't have list markup; they are just separated by empty h3 tags. We could output them as a- list under Competencies heading. But the instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered a list. It's appropriate to make a list. However we must preserve original content word-for-word; converting to list items does not change the text. So we can output
- Action Oriented
- Balances Stakeholders ... etc. But we need to decide if we should keep them as paragraphs separated by line breaks. Since there is no explicit list markup, but we can still use
- as it's a list of items. The instruction says use
- for list items (duties, requirements, qualifications, skills). It doesn't forbid using for other lists. I'd use
- for competencies.
Thus after the heading
Competencies
, we output- Action Oriented
- Balances Stakeholders
- Builds Networks
- Collaborates
- Communicates Effectively
- Customer Focus
- Drives Results
- Ensures Accountability
Education
=> headingEducation
. 20. Then text: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". Note there are two spaces before "(Required)"? In the original: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)". There are two spaces before the opening parenthesis. We must preserve that exactly. 21. Then empty. 22. ThenClosing Date
=> headingClosing Date
. 23. Then text: "30 October 2026 , 23:59". Note there is a space before the comma after 2026? Actually it's "30 October 2026 , 23:59". There's a space before the comma. We must preserve that. 24. Then four emptytags. 25. Then
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 output...
? But we cannot use or ? The instruction only mentions,
,
- . It says No CSS classes, no inline styles, no s, no
tags. It doesn't forbid or . However to keep semantic HTML, we could just useand preserve the text without the italic/bold tags, as they are styling. The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove and tags, we are removing markup but not textual content. The textual content remains same. So it's acceptable to drop those tags as they are not required for semantic HTML. However we must not add any tags not allowed; and are allowed but not necessary. Safer to just output
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 text. 26. Then two emptytags. 27. Then
The Old Mutual Story!
. Text: "The Old Mutual Story!" with double tags and . We'll outputThe Old Mutual Story!
. Now we need to output the HTML in order, with appropriate tags. We must not include any emptytags? The instruction: If text has no clear sections, just wrap paragraphs in
tags. It doesn't say to omit empty paragraphs. But empty paragraphs have no content; we could omit them as they add no information. However preserving original content word-for-word: empty paragraphs have no textual content, so removing them doesn't remove any text. It's probably fine to omit them. But to be safe, we could keep them as
. However emptytags are allowed? They
- for competencies.
Thus after the heading
- for list items (duties, requirements, qualifications, skills). It doesn't forbid using for other lists. I'd use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered a list. It's appropriate to make a list. However we must preserve original content word-for-word; converting to list items does not change the text. So we can output
- list under Competencies heading. But the instruction: Use
for section headers like Responsibilities, Qualifications, etc. If there is no clear section header, we just wrap paragraphs in
. The list is under no heading; we could treat it as a list without a heading. That's okay. But we need to decide where to put headings: The original has bolded "Skills", "Competencies", "Education", "Closing Date". Those are headings. We should convert those to
. Also there is an initial bolded "Let's Write Africa's Story Together!" which is inside emphasis-2 and b. That seems like a title/intro. Should we treat that as a heading? It's not one of the listed section headers, but we could still treat as maybe? The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., but not limited to? It says use for section headers (e.g. ...). Likely any heading should be . So we can convert those bolded headings to . Also the initial "Let's Write Africa's Story Together!" maybe is a tagline; could be considered a heading but not in list. Safer to treat as
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., but not limited to? It says use for section headers (e.g. ...). Likely any heading should be . So we can convert those bolded headings to . Also the initial "Let's Write Africa's Story Together!" maybe is a tagline; could be considered a heading but not in list. Safer to treat as
. So we can convert those bolded headings to . Also the initial "Let's Write Africa's Story Together!" maybe is a tagline; could be considered a heading but not in list. Safer to treat as
? But it's bolded and emphasized. The instruction: preserve all original content word-for-word. Changing tags is allowed, but we must not change text. So we can wrap that text in
or
. Which is more appropriate? Since it's a title/intro, maybe
is okay. However the instruction says use for section headers (e.g. Responsibilities, Qualifications...). It doesn't forbid using for other headings. I'd treat it as as well.
But we need to be careful not to add extra text like colon or anything.
Now we need to strip all original tags and produce clean HTML.
Let's extract the text pieces in order as they appear in the raw HTML.
Raw HTML:
as well. But we need to be careful not to add extra text like colon or anything. Now we need to strip all original tags and produce clean HTML. Let's extract the text pieces in order as they appear in the raw HTML. Raw HTML:
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies.
The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions.
Skills
Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer RelationshipsCompetencies
Action Oriented Balances Stakeholders Builds Networks Collaborates Communicates Effectively Customer Focus Drives Results Ensures AccountabilityEducation
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)Closing Date
30 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 text nodes in order, ignoring tags. Let's go step by step. 1. First p: text: "Let's Write Africa's Story Together!" (note the HTML entity ' is apostrophe). We must preserve the original content word-for-word. The original had ' which is an HTML entity for apostrophe. Should we keep it as ' or convert to apostrophe? The instruction: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. The original content includes the entity '. So we must keep that exactly. Similarly " for quotes. So we must keep the entities as they appear. So we should not decode them. So we keep "Let's Write Africa's Story Together!". 2. Second p: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " Note there is a trailing space before closing span? The text includes a space after the period before closing span. We must preserve that space? Probably yes. We'll keep exactly as appears: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. " (including trailing space). However HTML collapses spaces but we must keep as is. 3. Third p: empty. 4. Fourth p: empty. 5. Fifth p: contains two spans with br between. The text: first span: "We are looking for self-motivated and dynamic individuals who have a passionate entrepreneurial spirit to join one of Africa's leading insurance companies." Thenthen second span: "The role at a glance is about championing our valued customers to achieve their lifetime goals by identifying their financial needs, providing sound financial advice, recommending and implementing "fit for purpose" financial plans and solutions." So combined with line breaks? The original had
which we must not use (
tags not allowed). We need to represent that as something else? Since we cannot use
, we must preserve the content word-for-word but we cannot include
tags. However the instruction says: No
tags. So we must omit them, but that would be removing content. However maybe we can treat the line break as just whitespace; we can replace
with a space or newline? But that would be altering content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove
tags, we are removing content. But the rule also says No
tags. There's a conflict. We need to interpret: The original content includes
tags, but we are not allowed to use
tags in output. So we must remove them, but that would be removing content. However maybe the intention is that the raw text already had
tags as formatting, but we should treat them as line breaks and represent them as separate paragraphs (
) instead. Since we cannot use
, we can convert the line break into a paragraph break. That would be adding a
tag, but not adding textual content. The instruction about preserving original content word-for-word likely refers to the textual content, not the markup. So we can change tags as needed, but must not alter the actual words. So we can treat the
as a paragraph separator, resulting in two
elements. That seems reasonable. Thus we will output two
elements: first containing the first sentence, second containing the second sentence. 6. Then a
empty. 7. Then the- with three
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.