Job Description
,
for section headers, - for list items. No other tags like
, , , , , etc. But we must preserve all original content word-for-word, not add, remove, summarize, or rephrase. However we must format using only allowed tags. The original includes many headings like Responsibilities
, Customer Service
, etc. We need to map these to section headers. The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace any heading tags with and keep the text inside. Also we need to wrap paragraphs in
. The original has many
tags with content, some empty. We need to preserve all original content word-for-word, but we cannot add or remove text. However we can wrap content in
tags as needed. The original already has
tags around some content, but also has
, , etc. We need to convert those to . Also there are , , , etc. The rule says no CSS classes, no inline styles, no s, no
tags. But we can keep and ? The rule didn't forbid or , only no CSS classes, no inline styles, no s, no
tags. So we can keep , , maybe? But they are styling tags; but not prohibited. However we might want to preserve them as they appear. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the exact text including tags? The original includes HTML tags. Should we preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. That includes the HTML tags? Probably yes, we must keep the same text, but we are allowed to wrap paragraphs in tags. However we cannot add new tags? We can add
for section headers, but we must replace existing headings with . The original headings are Responsibilities
, Customer Service
, etc. We need to output them as Responsibilities
etc. Also there are empty headings; we should output maybe? But they are empty; we can output but that would be empty header. Probably okay.
We must not add any extra text. So we need to output the cleaned HTML exactly as per rules.
Let's parse the original content:
```
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
Solutions Analysis
Assess compliance with established standards and protocols for routine inquiries.
Receiving Visitors
Receive visitors and assist with various requests for information, referring more complex matters to colleagues.
Customer Relationship Management (CRM) Data
Ensure that basic customer details held in the system are accurate, and make notes of follow-up actions that have been promised, together with notes of actions taken during each sales call.
Customer Needs Clarification
Interview the customer, following a multilevel sales script, to clarify the customer's requirements.
Customer Relationship Development / Prospecting
Make calls (by telephone or in person) to allocated potential customers to develop relationships. Provide a first point of contact for resolving customer queries and complaints.
Operational Compliance
Follow a range of mandatory procedures to ensure that work is carried out to the required quality standards and/or to ensure adherence to external regulatory codes and internal codes of conduct.
Business Development
Carry out routine business development support tasks and assist others by following established procedures.
Sales Opportunities Creation
Identify potential customers by obtaining information, referrals, and recommendations from existing customers.
Data Exploration
Select appropriate data from information provided by others and input that data into spreadsheets or standard formats.
Network of Influence
Demonstrate understanding of the value of networking by participating in and contributing to a network of people, technologies, and ideas both inside and outside the company.
Skills
Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships
Competencies
Balances Stakeholders
Builds Networks
Communicates Effectively
Customer Focus
Ensures Accountability
Instills Trust
Interpersonal Savvy
Manages Complexity
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)
Closing Date
30 August 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 output only HTML using ,
, - . No other tags. But we have , , , etc. Are we allowed to keep them? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , . So we can keep them. However we must not add new tags beyond allowed ones. But we can keep existing tags as they are part of content. However we must wrap paragraphs in tags. The original already has
tags around many pieces, but also there are plain text lines like "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" that are not inside a
tag but inside the document. We need to wrap them in
tags as well. Also there are empty
tags; we can keep them as empty
maybe? The rule says preserve all original content word-for-word, so we must keep empty paragraphs as they are. So we should output for empty paragraphs.
We need to convert headings: Responsibilities
-> Responsibilities
. Customer Service
-> Customer Service
. Similarly for other headings. Also there are empty headings; we should output maybe? But they are empty; we can output . However 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 use for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items (duties, requirements, qualifications, skills). The original content uses
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
. But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a after each heading? Or maybe we should create a single list for all duties? The instruction: "Use - for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
after the "Responsibilities" header and include each duty paragraph as - ...content...
. But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into - items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to . But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we could keep tags as they appear. But the instruction says "Use for section headers (e.g. ...)" implying that we should use for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change to something else. So we should keep them as . But the rule also says "Use for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
, , - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , , , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace with because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing to would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use for section headers. Perhaps the intention is to convert those headings to while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
, , - . So we must convert headings to
. That is allowed. So we can replace with , with , etc. That changes the tag name but not the visible text. That is permissible.
Thus we will convert all headings that are section headers to . For other headings like that are empty, we can keep them as or convert to ? The instruction says use for section headers
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 📝
, , , , , etc. But we must preserve all original content word-for-word, not add, remove, summarize, or rephrase. However we must format using only allowed tags. The original includes many headings like Responsibilities
, Customer Service
, etc. We need to map these to section headers. The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace any heading tags with and keep the text inside. Also we need to wrap paragraphs in
, , , etc. But we must preserve all original content word-for-word, not add, remove, summarize, or rephrase. However we must format using only allowed tags. The original includes many headings like Responsibilities
, Customer Service
, etc. We need to map these to section headers. The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace any heading tags with and keep the text inside. Also we need to wrap paragraphs in
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace any heading tags with and keep the text inside. Also we need to wrap paragraphs in
. The original has many
tags with content, some empty. We need to preserve all original content word-for-word, but we cannot add or remove text. However we can wrap content in
tags as needed. The original already has
tags around some content, but also has
, , etc. We need to convert those to . Also there are , , , etc. The rule says no CSS classes, no inline styles, no s, no
tags. But we can keep and ? The rule didn't forbid or , only no CSS classes, no inline styles, no s, no
tags. So we can keep , , maybe? But they are styling tags; but not prohibited. However we might want to preserve them as they appear. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the exact text including tags? The original includes HTML tags. Should we preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. That includes the HTML tags? Probably yes, we must keep the same text, but we are allowed to wrap paragraphs in tags. However we cannot add new tags? We can add
for section headers, but we must replace existing headings with . The original headings are Responsibilities
, Customer Service
, etc. We need to output them as Responsibilities
etc. Also there are empty headings; we should output maybe? But they are empty; we can output but that would be empty header. Probably okay.
We must not add any extra text. So we need to output the cleaned HTML exactly as per rules.
Let's parse the original content:
```
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
Solutions Analysis
Assess compliance with established standards and protocols for routine inquiries.
Receiving Visitors
Receive visitors and assist with various requests for information, referring more complex matters to colleagues.
Customer Relationship Management (CRM) Data
Ensure that basic customer details held in the system are accurate, and make notes of follow-up actions that have been promised, together with notes of actions taken during each sales call.
Customer Needs Clarification
Interview the customer, following a multilevel sales script, to clarify the customer's requirements.
Customer Relationship Development / Prospecting
Make calls (by telephone or in person) to allocated potential customers to develop relationships. Provide a first point of contact for resolving customer queries and complaints.
Operational Compliance
Follow a range of mandatory procedures to ensure that work is carried out to the required quality standards and/or to ensure adherence to external regulatory codes and internal codes of conduct.
Business Development
Carry out routine business development support tasks and assist others by following established procedures.
Sales Opportunities Creation
Identify potential customers by obtaining information, referrals, and recommendations from existing customers.
Data Exploration
Select appropriate data from information provided by others and input that data into spreadsheets or standard formats.
Network of Influence
Demonstrate understanding of the value of networking by participating in and contributing to a network of people, technologies, and ideas both inside and outside the company.
Skills
Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships
Competencies
Balances Stakeholders
Builds Networks
Communicates Effectively
Customer Focus
Ensures Accountability
Instills Trust
Interpersonal Savvy
Manages Complexity
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)
Closing Date
30 August 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 output only HTML using ,
, - . No other tags. But we have , , , etc. Are we allowed to keep them? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , . So we can keep them. However we must not add new tags beyond allowed ones. But we can keep existing tags as they are part of content. However we must wrap paragraphs in tags. The original already has
tags around many pieces, but also there are plain text lines like "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" that are not inside a
tag but inside the document. We need to wrap them in
tags as well. Also there are empty
tags; we can keep them as empty
maybe? The rule says preserve all original content word-for-word, so we must keep empty paragraphs as they are. So we should output for empty paragraphs.
We need to convert headings: Responsibilities
-> Responsibilities
. Customer Service
-> Customer Service
. Similarly for other headings. Also there are empty headings; we should output maybe? But they are empty; we can output . However 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 use for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items (duties, requirements, qualifications, skills). The original content uses
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
. But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a after each heading? Or maybe we should create a single list for all duties? The instruction: "Use - for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
after the "Responsibilities" header and include each duty paragraph as - ...content...
. But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into - items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to . But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we could keep tags as they appear. But the instruction says "Use for section headers (e.g. ...)" implying that we should use for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change to something else. So we should keep them as . But the rule also says "Use for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
, , - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , , , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace with because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing to would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use for section headers. Perhaps the intention is to convert those headings to while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
, , - . So we must convert headings to
. That is allowed. So we can replace with , with , etc. That changes the tag name but not the visible text. That is permissible.
Thus we will convert all headings that are section headers to . For other headings like that are empty, we can keep them as or convert to ? The instruction says use for section headers
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 📝
. Also there are , , , etc. The rule says no CSS classes, no inline styles, no s, no
tags. But we can keep and ? The rule didn't forbid or , only no CSS classes, no inline styles, no s, no
tags. So we can keep , , maybe? But they are styling tags; but not prohibited. However we might want to preserve them as they appear. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the exact text including tags? The original includes HTML tags. Should we preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. That includes the HTML tags? Probably yes, we must keep the same text, but we are allowed to wrap paragraphs in tags. However we cannot add new tags? We can add
for section headers, but we must replace existing headings with . The original headings are Responsibilities
, Customer Service
, etc. We need to output them as Responsibilities
etc. Also there are empty headings; we should output maybe? But they are empty; we can output but that would be empty header. Probably okay.
We must not add any extra text. So we need to output the cleaned HTML exactly as per rules.
Let's parse the original content:
```
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
Solutions Analysis
Assess compliance with established standards and protocols for routine inquiries.
Receiving Visitors
Receive visitors and assist with various requests for information, referring more complex matters to colleagues.
Customer Relationship Management (CRM) Data
Ensure that basic customer details held in the system are accurate, and make notes of follow-up actions that have been promised, together with notes of actions taken during each sales call.
Customer Needs Clarification
Interview the customer, following a multilevel sales script, to clarify the customer's requirements.
Customer Relationship Development / Prospecting
Make calls (by telephone or in person) to allocated potential customers to develop relationships. Provide a first point of contact for resolving customer queries and complaints.
Operational Compliance
Follow a range of mandatory procedures to ensure that work is carried out to the required quality standards and/or to ensure adherence to external regulatory codes and internal codes of conduct.
Business Development
Carry out routine business development support tasks and assist others by following established procedures.
Sales Opportunities Creation
Identify potential customers by obtaining information, referrals, and recommendations from existing customers.
Data Exploration
Select appropriate data from information provided by others and input that data into spreadsheets or standard formats.
Network of Influence
Demonstrate understanding of the value of networking by participating in and contributing to a network of people, technologies, and ideas both inside and outside the company.
Skills
Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships
Competencies
Balances Stakeholders
Builds Networks
Communicates Effectively
Customer Focus
Ensures Accountability
Instills Trust
Interpersonal Savvy
Manages Complexity
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)
Closing Date
30 August 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 output only HTML using ,
, - . No other tags. But we have , , , etc. Are we allowed to keep them? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , . So we can keep them. However we must not add new tags beyond allowed ones. But we can keep existing tags as they are part of content. However we must wrap paragraphs in tags. The original already has
tags around many pieces, but also there are plain text lines like "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" that are not inside a
tag but inside the document. We need to wrap them in
tags as well. Also there are empty
tags; we can keep them as empty
maybe? The rule says preserve all original content word-for-word, so we must keep empty paragraphs as they are. So we should output for empty paragraphs.
We need to convert headings: Responsibilities
-> Responsibilities
. Customer Service
-> Customer Service
. Similarly for other headings. Also there are empty headings; we should output maybe? But they are empty; we can output . However 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 use for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items (duties, requirements, qualifications, skills). The original content uses
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
. But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a after each heading? Or maybe we should create a single list for all duties? The instruction: "Use - for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
after the "Responsibilities" header and include each duty paragraph as - ...content...
. But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into - items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to . But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we could keep tags as they appear. But the instruction says "Use for section headers (e.g. ...)" implying that we should use for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change to something else. So we should keep them as . But the rule also says "Use for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
, , - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , , , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace with because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing to would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use for section headers. Perhaps the intention is to convert those headings to while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
, , - . So we must convert headings to
. That is allowed. So we can replace with , with , etc. That changes the tag name but not the visible text. That is permissible.
Thus we will convert all headings that are section headers to . For other headings like that are empty, we can keep them as or convert to ? The instruction says use for section headers
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 📝
tags. But we can keep and ? The rule didn't forbid or , only no CSS classes, no inline styles, no
tags. So we can keep , , maybe? But they are styling tags; but not prohibited. However we might want to preserve them as they appear. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the exact text including tags? The original includes HTML tags. Should we preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. That includes the HTML tags? Probably yes, we must keep the same text, but we are allowed to wrap paragraphs in
tags. However we cannot add new tags? We can add
for section headers, but we must replace existing headings with . The original headings are Responsibilities
, Customer Service
, etc. We need to output them as Responsibilities
etc. Also there are empty headings; we should output maybe? But they are empty; we can output but that would be empty header. Probably okay.
We must not add any extra text. So we need to output the cleaned HTML exactly as per rules.
Let's parse the original content:
```
Responsibilities
,Customer Service
, etc. We need to output them asResponsibilities
etc. Also there are empty headings; we should output maybe? But they are empty; we can output but that would be empty header. Probably okay. We must not add any extra text. So we need to output the cleaned HTML exactly as per rules. Let's parse the original content: ```Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
Solutions Analysis
Assess compliance with established standards and protocols for routine inquiries.
Receiving Visitors
Receive visitors and assist with various requests for information, referring more complex matters to colleagues.
Customer Relationship Management (CRM) Data
Ensure that basic customer details held in the system are accurate, and make notes of follow-up actions that have been promised, together with notes of actions taken during each sales call.
Customer Needs Clarification
Interview the customer, following a multilevel sales script, to clarify the customer's requirements.
Customer Relationship Development / Prospecting
Make calls (by telephone or in person) to allocated potential customers to develop relationships. Provide a first point of contact for resolving customer queries and complaints.
Operational Compliance
Follow a range of mandatory procedures to ensure that work is carried out to the required quality standards and/or to ensure adherence to external regulatory codes and internal codes of conduct.
Business Development
Carry out routine business development support tasks and assist others by following established procedures.
Sales Opportunities Creation
Identify potential customers by obtaining information, referrals, and recommendations from existing customers.
Data Exploration
Select appropriate data from information provided by others and input that data into spreadsheets or standard formats.
Network of Influence
Demonstrate understanding of the value of networking by participating in and contributing to a network of people, technologies, and ideas both inside and outside the company.
Skills
Consultative Selling, Customer Feedback Management, Customer-Focused, Customer Service, Customer Understanding, Evaluating Information, Identifying Customer Needs, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer RelationshipsCompetencies
Balances Stakeholders Builds Networks Communicates Effectively Customer Focus Ensures Accountability Instills Trust Interpersonal Savvy Manages ComplexityEducation
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)Closing Date
30 August 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 output only HTML using,
, - . No other tags. But we have , , , etc. Are we allowed to keep them? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , . So we can keep them. However we must not add new tags beyond allowed ones. But we can keep existing tags as they are part of content. However we must wrap paragraphs in tags. The original already has
tags around many pieces, but also there are plain text lines like "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" that are not inside a
tag but inside the document. We need to wrap them in
tags as well. Also there are empty
tags; we can keep them as empty
maybe? The rule says preserve all original content word-for-word, so we must keep empty paragraphs as they are. So we should output for empty paragraphs.
We need to convert headings: Responsibilities
-> Responsibilities
. Customer Service
-> Customer Service
. Similarly for other headings. Also there are empty headings; we should output maybe? But they are empty; we can output . However 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 use for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items (duties, requirements, qualifications, skills). The original content uses
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
. But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a after each heading? Or maybe we should create a single list for all duties? The instruction: "Use - for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
after the "Responsibilities" header and include each duty paragraph as - ...content...
. But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into - items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to . But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we could keep tags as they appear. But the instruction says "Use for section headers (e.g. ...)" implying that we should use for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change to something else. So we should keep them as . But the rule also says "Use for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
, , - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , , , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace with because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing to would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use for section headers. Perhaps the intention is to convert those headings to while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
, , - . So we must convert headings to
. That is allowed. So we can replace with , with , etc. That changes the tag name but not the visible text. That is permissible.
Thus we will convert all headings that are section headers to . For other headings like that are empty, we can keep them as or convert to ? The instruction says use for section headers
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 📝
tags". It doesn't forbid , , . So we can keep them. However we must not add new tags beyond allowed ones. But we can keep existing tags as they are part of content. However we must wrap paragraphs in
tags. The original already has
tags around many pieces, but also there are plain text lines like "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent (Required)" that are not inside a
tag but inside the document. We need to wrap them in
tags as well. Also there are empty
tags; we can keep them as empty
maybe? The rule says preserve all original content word-for-word, so we must keep empty paragraphs as they are. So we should output for empty paragraphs. We need to convert headings:Responsibilities
->Responsibilities
.Customer Service
->Customer Service
. Similarly for other headings. Also there are empty headings; we should output maybe? But they are empty; we can output . However 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 use for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
for any section header. So we can replace any heading tag with . So we will have many sections.
Now we need to structure the content: Use
sections. Now we need to structure the content: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items (duties, requirements, qualifications, skills). The original content uses
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
. But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a after each heading? Or maybe we should create a single list for all duties? The instruction: "Use - for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
after the "Responsibilities" header and include each duty paragraph as - ...content...
. But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into - items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to . But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we could keep tags as they appear. But the instruction says "Use for section headers (e.g. ...)" implying that we should use for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change to something else. So we should keep them as . But the rule also says "Use for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
, , - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use - for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid , , , , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace with because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing to would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use for section headers. Perhaps the intention is to convert those headings to while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
, , - . So we must convert headings to
. That is allowed. So we can replace with , with , etc. That changes the tag name but not the visible text. That is permissible.
Thus we will convert all headings that are section headers to . For other headings like that are empty, we can keep them as or convert to ? The instruction says use for section headers
for each duty, but they are not in a list. We could wrap them in
- if they are list items? The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert sequences of duties into list items. However we must preserve all original content word-for-word, but we can wrap them in
- tags. That is allowed. So we can take each duty paragraph and wrap its text in
- and wrap the list in
- . But we need to decide which paragraphs are duties. The headings like "Customer Service", "Solutions Analysis", etc. Probably each of those is a duty. So we can create a
- for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
- after the "Responsibilities" header and include each duty paragraph as
- ...content... . But we must preserve the order and content exactly. So we can take all duty paragraphs (those under various headings) and put them into a
- items? But we must preserve word-for-word, so we cannot split the comma-separated list into separate items; that would change content. So maybe we should keep it as a paragraph, not a list. But the instruction says use
- for list items (duties, requirements, qualifications, skills). So maybe we should treat the "Skills" section as a list of skills separated by commas; but we cannot split them. Could we wrap the whole text as a single
- ? That would be a list item containing the whole comma-separated list. That would be okay. Similarly "Competencies" section lists many competency phrases separated by headings; each competency phrase is preceded by a heading? Actually they are separate lines like "Balances Stakeholders" etc. The text after each heading is empty? Actually the pattern is: Balances Stakeholders etc. So the competency text is between tags? Actually the snippet shows:
```
Balances Stakeholders
Builds Networks
...
```
So the competency text is "Balances Stakeholders" etc, with empty before and after? Actually the pattern is: Balances Stakeholders. So the text "Balances Stakeholders" is between two tags. So we could treat each competency as a list item. But we need to preserve the exact text including the surrounding tags? The original includes those tags. We need to preserve them? The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. So we must keep the tags as they appear. But we are converting headings to
. However these are not headings but part of the content. The rule only says use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't say to convert all headings to
. But we need to preserve all original content word-for-word, so we cannot remove the tags. But we also cannot have them because we are limited to
for section headers. However these tags are not section headers; they are just empty tags used as separators. The instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using other heading tags elsewhere, but we might want to keep them as they are? The rule says "No CSS classes, no inline styles, no
s, no
tags". It doesn't forbid. So we could keep
tags as they appear. But the instruction says "Use
for section headers (e.g. ...)" implying that we should use
for those specific section headers, but other headings may remain as they are? However we must preserve all original content word-for-word, so we cannot change
to something else. So we should keep them as . But the rule also says "Use
for section headers (e.g. ...)" but doesn't say we cannot use other heading levels. So we can keep
as is. However we must not add any new tags beyond allowed ones? The allowed tags are
,
,
- ,
- . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text, Use
for section headers, Use
- for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid,
,
, , , etc. So we can keep them. However we must preserve all original content word-for-word, so we must keep the original tags exactly as they appear. So we cannot replace
with
because that would change the tag name, thus altering the content (the tag name is part of the content). The instruction says preserve all original content word-for-word, not add, remove, summarize, or rephrase. Changing
to
would be a change, thus not allowed. So we must keep the original tags exactly. But the rule also says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This seems contradictory: we must preserve original tags, but also we must use
for section headers. Perhaps the intention is to convert those headings to
while preserving the text inside. But that would change the tag name, which is part of the content. However maybe they consider the tag name not part of the "content"? Usually "content" refers to the visible text, not the markup. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That likely refers to the visible text, not the HTML tags. So we can change the tag names as long as the visible text remains the same. The example: they gave a job description with HTML tags; they want us to output clean semantic HTML using only
,
,
- ,
- . So we must convert headings to
. That is allowed. So we can replace
with
,
with
, etc. That changes the tag name but not the visible text. That is permissible. Thus we will convert all headings that are section headers to
. For other headings like that are empty, we can keep them as or convert to ? The instruction says use
for section headers
- . So we must convert headings to
- for list items". It doesn't explicitly forbid using other tags, but the overall instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no
- . It didn't say we cannot use other tags, but the instruction says "Use
- . However there are also other sections like "Skills", "Competencies" which also have text that should be list items? The "Skills" section contains a long list of skills separated by commas, not separate paragraphs. That could be considered a list of skills; we could split them into
- after each heading? Or maybe we should create a single list for all duties? The instruction: "Use
- for list items (duties, requirements, qualifications, skills)". So we should use list items for duties, requirements, qualifications, skills. So we can create a
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.