Job Description
We need to output clean semantic HTML per rules. Use for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use
for intro paragraphs and general text. Use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items. No CSS classes, no inline styles, no , no
. Preserve all original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text as given, but we need to strip out the HTML tags and formatting from the input, and then reformat using allowed tags.
We must not add or remove any content. So we need to extract the textual content from the input, preserving it exactly, then wrap in appropriate tags.
Let's parse the input:
Input is a string with HTML tags and some text.
We need to get the plain text content, preserving whitespace? Probably we just need to output the text with appropriate tags.
Let's extract the textual content ignoring tags.
We have:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Job Description
Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
PRINCIPAL ACCOUNTABILITIES.
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high level of integrity, determination, and personal commitment.
- Excellent communication and presentation skills.
SKILLS AND COMPETENCIES.
- Good interpersonal skills
- Thorough understanding of insurance
- Good communication and stakeholder management skills
- Good teaming and interpersonal skills
- Strong advocacy for collaborative working skills
na
Skills
Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management
Competencies
CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy
Education
Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)
Closing Date
07 September 2026 , 23:59
The Old Mutual Story!
We need to preserve all original content word-for-word. That includes the weird "na" line, the non-breaking space etc. Also there are some stray tags inside the Competencies section. Those are empty tags; we need to preserve content word-for-word, but we cannot keep tags because we cannot use etc but we can keep ? The rules say: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items. No CSS classes, no inline styles, no s, no
tags. It doesn't forbid other tags like , but we should probably not use them because they aren't specified. However we must preserve original content word-for-word, which includes those tags. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And earlier: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we must keep the exact original text, including any tags? But then we also need to format it as clean semantic HTML using only
,
, - . This is contradictory.
Interpretation: We need to extract the job information (the textual content) and then format it as clean semantic HTML using only those tags. So we discard the original markup and reformat. The phrase "Preserve ALL original content word-for-word" refers to the textual content, not the markup. So we should not add, remove, summarise, or rephrase the words themselves. So we need to keep the exact wording, punctuation, etc. But we can change formatting (tags). Also we need to keep things like "na" line as is.
Thus we need to output a cleaned version with only
,
, - . No other tags. Also we must not add any extra content.
We need to decide section headers. The original has bolded sections: "Job Description", "PRINCIPAL ACCOUNTABILITIES.", "Qualifications:", "SKILLS AND COMPETENCIES.", then later "Skills", "Competencies", "Education", "Closing Date". Also there is a line "Enthusiastic self-driven young talent..." which is likely the introductory paragraph after "Job Description". Also there are some introductory lines at top: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...".
We need to wrap introductory paragraphs in
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
. It might be a regular space. Hard to tell. We'll just keep a normal space.
Similarly "Works closely with systems analysts and customers to design and implement solutions.
" includes a non-breaking space.
"Facilitate end-user trainings." preceded by a non-breaking space? Actually " Facilitate end-user trainings." includes a leading non-breaking space.
We'll just keep a single space.
Now after that list, we have a blank then "Qualifications:
" -> Qualifications:
. Then list.
Then "SKILLS AND COMPETENCIES.
" -> SKILLS AND COMPETENCIES.
. Then list.
Then we have some empty paragraphs, then "na" line, then a paragraph with non-breaking space, then empty paragraphs, then "Skills
" -> Skills
. Then the line: "Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management". That's not a list; it's a sentence/comma-separated list. Should we treat as a paragraph? Probably .
Then "
Competencies
" -> Competencies
. Then the text: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". This includes empty tags between each competency. We need to preserve the original content word-for-word, but we cannot keep tags because we are only allowed to use
,
, - . However the instruction says preserve all original content word-for-word. This is contradictory. Likely we should strip those empty tags as they are not content. The content words are the competencies separated by those tags. The original likely intended each competency on its own line but got messed up. We need to output the competencies as they appear, but we cannot keep
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide.
Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string.
Similarly after that there are empty paragraphs.
Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)".
Then Closing Date header -> Closing Date
. Then paragraph: "07 September 2026 , 23:59".
Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph.
Now we need to output HTML with only ,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
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 📝
, no
. Preserve all original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text as given, but we need to strip out the HTML tags and formatting from the input, and then reformat using allowed tags. We must not add or remove any content. So we need to extract the textual content from the input, preserving it exactly, then wrap in appropriate tags. Let's parse the input: Input is a string with HTML tags and some text. We need to get the plain text content, preserving whitespace? Probably we just need to output the text with appropriate tags. Let's extract the textual content ignoring tags. We have: tags because we cannot use
. Preserve all original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact text as given, but we need to strip out the HTML tags and formatting from the input, and then reformat using allowed tags. We must not add or remove any content. So we need to extract the textual content from the input, preserving it exactly, then wrap in appropriate tags. Let's parse the input: Input is a string with HTML tags and some text. We need to get the plain text content, preserving whitespace? Probably we just need to output the text with appropriate tags. Let's extract the textual content ignoring tags. We have:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Job Description
Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.PRINCIPAL ACCOUNTABILITIES.
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high level of integrity, determination, and personal commitment.
- Excellent communication and presentation skills.
SKILLS AND COMPETENCIES.
- Good interpersonal skills
- Thorough understanding of insurance
- Good communication and stakeholder management skills
- Good teaming and interpersonal skills
- Strong advocacy for collaborative working skills
Skills
Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder ManagementCompetencies
CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational SavvyEducation
Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)Closing Date
07 September 2026 , 23:59The Old Mutual Story!
We need to preserve all original content word-for-word. That includes the weird "na" line, the non-breaking space etc. Also there are some stray tags inside the Competencies section. Those are empty tags; we need to preserve content word-for-word, but we cannot keep tags because we cannot use etc but we can keep ? The rules say: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items. No CSS classes, no inline styles, no s, no
tags. It doesn't forbid other tags like , but we should probably not use them because they aren't specified. However we must preserve original content word-for-word, which includes those tags. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And earlier: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we must keep the exact original text, including any tags? But then we also need to format it as clean semantic HTML using only
,
, - . This is contradictory.
Interpretation: We need to extract the job information (the textual content) and then format it as clean semantic HTML using only those tags. So we discard the original markup and reformat. The phrase "Preserve ALL original content word-for-word" refers to the textual content, not the markup. So we should not add, remove, summarise, or rephrase the words themselves. So we need to keep the exact wording, punctuation, etc. But we can change formatting (tags). Also we need to keep things like "na" line as is.
Thus we need to output a cleaned version with only
,
, - . No other tags. Also we must not add any extra content.
We need to decide section headers. The original has bolded sections: "Job Description", "PRINCIPAL ACCOUNTABILITIES.", "Qualifications:", "SKILLS AND COMPETENCIES.", then later "Skills", "Competencies", "Education", "Closing Date". Also there is a line "Enthusiastic self-driven young talent..." which is likely the introductory paragraph after "Job Description". Also there are some introductory lines at top: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...".
We need to wrap introductory paragraphs in
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
. It might be a regular space. Hard to tell. We'll just keep a normal space.
Similarly "Works closely with systems analysts and customers to design and implement solutions.
" includes a non-breaking space.
"Facilitate end-user trainings." preceded by a non-breaking space? Actually " Facilitate end-user trainings." includes a leading non-breaking space.
We'll just keep a single space.
Now after that list, we have a blank then "Qualifications:
" -> Qualifications:
. Then list.
Then "SKILLS AND COMPETENCIES.
" -> SKILLS AND COMPETENCIES.
. Then list.
Then we have some empty paragraphs, then "na" line, then a paragraph with non-breaking space, then empty paragraphs, then "Skills
" -> Skills
. Then the line: "Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management". That's not a list; it's a sentence/comma-separated list. Should we treat as a paragraph? Probably .
Then "
Competencies
" -> Competencies
. Then the text: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". This includes empty tags between each competency. We need to preserve the original content word-for-word, but we cannot keep tags because we are only allowed to use
,
, - . However the instruction says preserve all original content word-for-word. This is contradictory. Likely we should strip those empty tags as they are not content. The content words are the competencies separated by those tags. The original likely intended each competency on its own line but got messed up. We need to output the competencies as they appear, but we cannot keep
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide.
Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string.
Similarly after that there are empty paragraphs.
Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)".
Then Closing Date header -> Closing Date
. Then paragraph: "07 September 2026 , 23:59".
Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph.
Now we need to output HTML with only ,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
? The rules say: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items. No CSS classes, no inline styles, no s, no
tags. It doesn't forbid other tags like , but we should probably not use them because they aren't specified. However we must preserve original content word-for-word, which includes those tags. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And earlier: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we must keep the exact original text, including any tags? But then we also need to format it as clean semantic HTML using only
,
, - . This is contradictory.
Interpretation: We need to extract the job information (the textual content) and then format it as clean semantic HTML using only those tags. So we discard the original markup and reformat. The phrase "Preserve ALL original content word-for-word" refers to the textual content, not the markup. So we should not add, remove, summarise, or rephrase the words themselves. So we need to keep the exact wording, punctuation, etc. But we can change formatting (tags). Also we need to keep things like "na" line as is.
Thus we need to output a cleaned version with only
,
, - . No other tags. Also we must not add any extra content.
We need to decide section headers. The original has bolded sections: "Job Description", "PRINCIPAL ACCOUNTABILITIES.", "Qualifications:", "SKILLS AND COMPETENCIES.", then later "Skills", "Competencies", "Education", "Closing Date". Also there is a line "Enthusiastic self-driven young talent..." which is likely the introductory paragraph after "Job Description". Also there are some introductory lines at top: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...".
We need to wrap introductory paragraphs in
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
. It might be a regular space. Hard to tell. We'll just keep a normal space.
Similarly "Works closely with systems analysts and customers to design and implement solutions.
" includes a non-breaking space.
"Facilitate end-user trainings." preceded by a non-breaking space? Actually " Facilitate end-user trainings." includes a leading non-breaking space.
We'll just keep a single space.
Now after that list, we have a blank then "Qualifications:
" -> Qualifications:
. Then list.
Then "SKILLS AND COMPETENCIES.
" -> SKILLS AND COMPETENCIES.
. Then list.
Then we have some empty paragraphs, then "na" line, then a paragraph with non-breaking space, then empty paragraphs, then "Skills
" -> Skills
. Then the line: "Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management". That's not a list; it's a sentence/comma-separated list. Should we treat as a paragraph? Probably .
Then "
Competencies
" -> Competencies
. Then the text: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". This includes empty tags between each competency. We need to preserve the original content word-for-word, but we cannot keep tags because we are only allowed to use
,
, - . However the instruction says preserve all original content word-for-word. This is contradictory. Likely we should strip those empty tags as they are not content. The content words are the competencies separated by those tags. The original likely intended each competency on its own line but got messed up. We need to output the competencies as they appear, but we cannot keep
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide.
Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string.
Similarly after that there are empty paragraphs.
Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)".
Then Closing Date header -> Closing Date
. Then paragraph: "07 September 2026 , 23:59".
Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph.
Now we need to output HTML with only ,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
s, no
tags. It doesn't forbid other tags like,
tags. It doesn't forbid other tags like
, but we should probably not use them because they aren't specified. However we must preserve original content word-for-word, which includes those tags. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And earlier: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we must keep the exact original text, including any tags? But then we also need to format it as clean semantic HTML using only
,
, - . This is contradictory.
Interpretation: We need to extract the job information (the textual content) and then format it as clean semantic HTML using only those tags. So we discard the original markup and reformat. The phrase "Preserve ALL original content word-for-word" refers to the textual content, not the markup. So we should not add, remove, summarise, or rephrase the words themselves. So we need to keep the exact wording, punctuation, etc. But we can change formatting (tags). Also we need to keep things like "na" line as is.
Thus we need to output a cleaned version with only
,
, - . No other tags. Also we must not add any extra content.
We need to decide section headers. The original has bolded sections: "Job Description", "PRINCIPAL ACCOUNTABILITIES.", "Qualifications:", "SKILLS AND COMPETENCIES.", then later "Skills", "Competencies", "Education", "Closing Date". Also there is a line "Enthusiastic self-driven young talent..." which is likely the introductory paragraph after "Job Description". Also there are some introductory lines at top: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...".
We need to wrap introductory paragraphs in
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
. It might be a regular space. Hard to tell. We'll just keep a normal space.
Similarly "Works closely with systems analysts and customers to design and implement solutions.
" includes a non-breaking space.
"Facilitate end-user trainings." preceded by a non-breaking space? Actually " Facilitate end-user trainings." includes a leading non-breaking space.
We'll just keep a single space.
Now after that list, we have a blank then "Qualifications:
" -> Qualifications:
. Then list.
Then "SKILLS AND COMPETENCIES.
" -> SKILLS AND COMPETENCIES.
. Then list.
Then we have some empty paragraphs, then "na" line, then a paragraph with non-breaking space, then empty paragraphs, then "Skills
" -> Skills
. Then the line: "Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management". That's not a list; it's a sentence/comma-separated list. Should we treat as a paragraph? Probably .
Then "
Competencies
" -> Competencies
. Then the text: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". This includes empty tags between each competency. We need to preserve the original content word-for-word, but we cannot keep tags because we are only allowed to use
,
, - . However the instruction says preserve all original content word-for-word. This is contradictory. Likely we should strip those empty tags as they are not content. The content words are the competencies separated by those tags. The original likely intended each competency on its own line but got messed up. We need to output the competencies as they appear, but we cannot keep
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide.
Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string.
Similarly after that there are empty paragraphs.
Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)".
Then Closing Date header -> Closing Date
. Then paragraph: "07 September 2026 , 23:59".
Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph.
Now we need to output HTML with only ,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
,
, - . No other tags. Also we must not add any extra content.
We need to decide section headers. The original has bolded sections: "Job Description", "PRINCIPAL ACCOUNTABILITIES.", "Qualifications:", "SKILLS AND COMPETENCIES.", then later "Skills", "Competencies", "Education", "Closing Date". Also there is a line "Enthusiastic self-driven young talent..." which is likely the introductory paragraph after "Job Description". Also there are some introductory lines at top: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...".
We need to wrap introductory paragraphs in
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
. It might be a regular space. Hard to tell. We'll just keep a normal space.
Similarly "Works closely with systems analysts and customers to design and implement solutions.
. Section headers in
. List items in - .
We must preserve the exact text of headers, including punctuation and spacing. For example "PRINCIPAL ACCOUNTABILITIES." includes a period at end. We should keep that exactly.
Also "Qualifications:" includes colon.
"SKILLS AND COMPETENCIES." includes period.
"Skills" and "Competencies" are headers.
"Education" header.
"Closing Date" header.
Also there is a line "na" and a non-breaking space paragraph. Those appear as stray text; we should keep them as paragraphs? Probably they are part of original content; we must keep them. The "na" appears alone on a line. Also there is a paragraph with a non-breaking space ( ). We should keep them as
na
and
maybe.
Also there are empty tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them.
Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each.
Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
.
Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: each - content. We need to preserve the exact text inside each
- , including any trailing spaces or non-breaking spaces? The original had some spaces and a non-breaking space before "Facilitate". We need to keep them exactly. The
- text: "Investigates and defines requirements for business processes. " includes a non-breaking space after the period? Actually there is a (non-breaking space) after the period. We should keep that as a space? In HTML we can just keep a regular space; but to preserve exactly we could keep the non-breaking space as but that's adding an entity. Might be okay but maybe we just keep a normal space; but the instruction says preserve original content word-for-word. The non-breaking space is a character; we could represent it as a regular space? That would change the character. Safer to keep it as but that is adding an entity not originally present? Actually original had ? Let's look: In the source: "Investigates and defines requirements for business processes.
" There is a (non-breaking space) represented as a literal non-breaking space character? In the text we see a space after the period before the closing
na
andmaybe. Also there are empty
tags; we can ignore them as they have no content. But we must not add content; we can omit empty paragraphs because they have no content. The rule says preserve all original content word-for-word; empty paragraphs have no content, so we can drop them. Now we need to decide structure: The introductory text before "Job Description": two lines: "Lets Write Africa's Story Together!" and "Old Mutual is a firm believer...". Those could be wrapped in
each. Then there is a
Job Description
which is a header. According to rules, we should use for section headers. So we convert that to Job Description
. Then the following paragraph: "Enthusiastic self-driven young talent..." is introductory paragraph under Job Description, so
. Then we have "PRINCIPAL ACCOUNTABILITIES." header ->
PRINCIPAL ACCOUNTABILITIES.
. Then the list items: eachQualifications:
" ->Qualifications:
. Then list. Then "SKILLS AND COMPETENCIES.
" ->SKILLS AND COMPETENCIES.
. Then list. Then we have some empty paragraphs, then "na" line, then a paragraph with non-breaking space, then empty paragraphs, then "Skills
" ->Skills
. Then the line: "Communication, Database Administration, End Users, Information Technology Applications, Network Administration, Stakeholder Management". That's not a list; it's a sentence/comma-separated list. Should we treat as a paragraph? Probably. Then "
Competencies
" ->Competencies
. Then the text: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". This includes empty tags between each competency. We need to preserve the original content word-for-word, but we cannot keep tags because we are only allowed to use
,
, - . However the instruction says preserve all original content word-for-word. This is contradictory. Likely we should strip those empty tags as they are not content. The content words are the competencies separated by those tags. The original likely intended each competency on its own line but got messed up. We need to output the competencies as they appear, but we cannot keep
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide.
Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string.
Similarly after that there are empty paragraphs.
Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)".
Then Closing Date header -> Closing Date
. Then paragraph: "07 September 2026 , 23:59".
Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph.
Now we need to output HTML with only ,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
tags. Perhaps we should treat the text as a paragraph and keep the words exactly as they appear, ignoring the tags. The tags are not content; they are markup. So we can remove them. The phrase "Preserve ALL original content word-for-word" likely refers to the textual content, not the markup. So we can drop the tags.
Thus the competencies text becomes: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". But there is no spacing between them because the tags were removed. However there may have been no spaces originally; the tags were directly adjacent. In the source: "CollaboratesCommunicates EffectivelyDemonstrates Self-AwarenessDrives ResultsEnsures AccountabilityManages ComplexityOptimizes Work ProcessesOrganizational Savvy". There is no space between the closing
and the next word. So after removing tags, we get "CollaboratesCommunicates Effectively..." which seems odd. Probably the original intended each competency on separate line but got messed up. However we must preserve the content word-for-word; the content includes the words but not the tags. The tags are not content. So we should output the words exactly as they appear between tags, preserving any spaces that were present. There were no spaces between tags, so we get concatenated words. That seems wrong but it's what the original content is.
Maybe we should treat the line as a list of competencies each on its own line, but we cannot add structure not present. The safe approach: output that line as a paragraph
exactly as it appears after stripping tags? But we need to decide. Given the ambiguity, I think we should output the competencies as a paragraph, preserving the text exactly as it appears between the tags, but we cannot keep the tags. So we will output the concatenated string. Similarly after that there are empty paragraphs. Then Education header ->
Education
. Then the paragraph: "Bachelors Degree (B): Information Technology And Computer Science: Information Technology Management (Required)". Then Closing Date header ->Closing Date
. Then paragraph: "07 September 2026 , 23:59". Then final line: "The Old Mutual Story!
" -> The text: "The Old Mutual Story!". Should be a paragraph. Now we need to output HTML with only,
, - . No other tags.
We must ensure we don't add extra spaces or change punctuation.
Let's construct.
Start with introductory lines:
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Then Job Description
Then Enthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
Then PRINCIPAL ACCOUNTABILITIES.
Then
- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Note: I removed the trailing non-breaking spaces.
Then Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
Lets Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
ThenJob Description
ThenEnthusiastic self-driven young talent to join our IT department as a Graduate Trainee. Opportunity to gain the knowledge and experience required for promotion to a full-time position under the guidance of an experienced personnel.
ThenPRINCIPAL ACCOUNTABILITIES.
Then- Investigates and defines requirements for business processes.
- Analyses business processes to determine problems, risks, and opportunities for improvement.
- Works closely with systems analysts and customers to design and implement solutions.
- Conducts tests for system related changes.
- Facilitate end-user trainings.
- Document requirements including data modelling, process flows and report layouts.
Qualifications:
- Business Acumen
- Foundational knowledge of IT Applications, Infrastructure, Databases
- Must be innovative, creative, and teachable.
- Bachelor’s degree in computer science or a related field within the last 3 years.
- Must possess a high
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 📝My Job Concierge
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.
Almost there
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.
ECHO
Your MJC Assistant
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.