Job Description
,
, - . No other tags like , , , etc. But we must preserve original content word-for-word, but we cannot add, remove, summarize, or rephrase. However we can wrap content in appropriate tags. The original includes , , etc. We need to keep the text content exactly as is, but we can wrap in tags. The instruction: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to identify sections and use headings. The original has headings like "Job Description", "Skills", "Competencies", "Education", "Closing Date". Also there are bolded items like Responsible for the processing... etc. Those are part of content; we should keep them as plain text, not as tags. But we need to preserve word-for-word, including the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes HTML tags? The original is plain-text job description with some HTML tags. We need to output clean semantic HTML, but we cannot add, remove, summarise, or rephrase. So we must keep the same text, including the tags? But we are to format it as clean semantic HTML using only
,
, - . So we can keep the tags? They are not allowed? The rule says no CSS classes, no inline styles, no s, no
tags. It doesn't forbid or . But they are not semantic; but maybe allowed as they are part of original content. However we might need to preserve them exactly as they appear. The original includes tags around some text. We should keep them as is, but we need to wrap sections with . The headings themselves are bolded maybe. For example "Job Description" is wrapped in in the original? Actually it's Job Description inside a
. So we need to output that as plain text? The instruction: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace those headings with tags. But we must preserve original content word-for-word. If we replace Job Description with Job Description
, we are changing the tag, but the content word is same. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to is not adding or removing words, just tag change. That might be acceptable. But we must not add or remove content. So we can convert the heading text to and keep the text inside. The original heading "Job Description" appears inside tags. We can output Job Description
. That seems okay.
Similarly "Skills" and "Competencies" and "Education" and "Closing Date" are headings. Use .
Now we need to output the whole thing as HTML with only
,
, - . No other tags. But the original includes
- already. We need to keep them but wrap list items in
- . The original already uses
- but also includes
inside
- . That's okay; we can keep
inside
- as they are allowed? The rule says use
- for list items. It doesn't forbid
inside
- . So we can keep
inside
- . But we must not add extra tags. So we can output the list items as
...content...
tags inside? The original list items have
around the text. For example:
Responsible for the processing...
wrapper. We can keep that
inside
- . That's okay.
We must not add any extra commentary. Just output the HTML.
We need to remove any stray tags like , maybe we keep them as they are part of content. But we need to ensure we only use allowed tags:
,
, , - . Using inside
- is not allowed? The rule didn't forbid , but it said use
- for list items. It didn't say we cannot use . But to be safe, we might keep as part of content because it's part of original text. However the instruction says "Use
for section headers". It doesn't say we cannot use . But we might want to avoid extra tags. However preserving original content word-for-word includes the tags. So we must keep them. But we also need to wrap headings with . So we can replace the surrounding with . For example original:
Job Description
. We can output Job Description
. That removes the tags but keeps the text. That's okay because we are not adding or removing words. The tags are not part of the visible text; they are markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does that include markup? Probably they mean the textual content, not the markup. But to be safe, we can keep the tags as they appear, but then we would have inside which is not allowed? The rule didn't forbid , but we are supposed to use only
,
, - . So we cannot use . So we must remove tags. But that would be removing markup, which might be considered removing content? The content inside is still there. The instruction is ambiguous. I think we can remove the tags because they are not part of the visible text; they are formatting. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing tags changes the markup but not the words. The words "Job Description" remain. So it's okay.
Thus we will output:
Job Description
then paragraphs.
We need to preserve all paragraphs as . The original has many
tags with text. Some are empty. We can output
maybe? But we should preserve empty paragraphs? They contain nothing. We can output but that adds empty content. Might be okay. But maybe we can just output
? The original has etc. Those are empty. We can output . That preserves emptiness.
We need to preserve the list items exactly as they appear, including the inside some list items. We can keep inside ...content...
Skills
Action Planning, Compliance Software, ... etc. So we need to output Skills
then a containing that comma-separated list. But we must preserve the exact text including the commas and spaces. So we output
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Similarly "Competencies" section includes headings with empty. The original has repeated. We need to preserve them? They are empty. We can output maybe but we are not allowed to use . The rule only allows for section headers. So we should not output . But the original contains tags. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must keep those tags? But we are limited to only
,
, - . So we cannot output
. This is a conflict. Perhaps we can ignore those empty tags because they contain no content. They are just placeholders. We could omit them, but that would be removing content. However they are empty, so removing them doesn't change visible content. The instruction says do not remove content. But empty tags maybe considered content? Might be okay to drop them. But to be safe, we could output them as but that violates allowed tags. The rule says "Use for section headers". It doesn't forbid other heading tags, but the instruction says use for section headers. So we should not use . So we can ignore those empty tags.
The "Closing Date" section includes Closing Date then text "17 July 2026 , 23:59". So we output Closing Date
then
17 July 2026 , 23:59
.
The "The Old Mutual Story!" part includes The Old Mutual Story!. That's text with tags. We need to preserve it. We can output The Old Mutual Story!
but we cannot use or or maybe? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid , , . But we might want to keep them as they appear. However we are supposed to use only ,
, - . So we cannot use or or . But we need to preserve them? This is contradictory. Probably they expect us to keep the textual content but not the markup tags. So we can output the text "The Old Mutual Story!" inside a
. The original includes formatting tags, but we can just output the text. That would be preserving the words but not the tags. That seems acceptable.
Thus final output: a series of
headings and
paragraphs and
- list items.
Let's construct:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
Ensure timeous monitoring and accurate management of mail count
Drive interdepartmental discussions on transactions and business issues and make recommendations
Participate in training and mentoring of junior underwriting support staff
In-depth understanding of specialty business, to fully understand the risk and impact to Specialty department
Ensure necessary authorisations are obtained to finalise transactions
Follow up on declarations, monthly/quarterly and annually
Work with various business partners to ensure that day-to-day administrative processes and procedures are fulfilled.
Continuous improvement to ensure effective service
Ensure statutory and legislative knowledge is always current in order to resolve customer complaints, to advise the business on corrective solutions to mitigate risks and to improve the customer experience whilst complying with governance requirements.
Ensure adherence to organisational policies, practices, and procedures.
Identify solutions to enhance cost effectiveness and increase operational efficiency
Service delivery to ensure customer satisfaction
Maintain service, quality, and desired outputs within a specific functional process through ensuring compliance to tactical policies, procedures, and standards.
Establish productive operational relationships with key stakeholders in the various channels and administrative teams.
Develop work routines in line with operational plans / schedules in order to manage achievement of service delivery goals.
Share knowledge on, and participate in the creation of new standards, control systems and procedures to maintain service delivery.
Cost control and governance adherence
Proactively ensure use of time, of resources, money, materials, or equipment is in line with policies and procedures.
Comply with corporate governance policies, procedures, and standards.
Operate within agreed mandates.
Quality people practices
Align own behaviour with the organisation culture and values.
Share and transfer product, process, and systems knowledge to colleagues.
Ensure achievement of own performance objectives.
Actively share information with other team members regarding successes, issues, trends, and ideas.
Actively participate in own professional development and career path.
Actively promote a culture of learning and high-performance culture amongst team members.
Diploma and/or equivalent NQF Level 6 qualification in general insurance.
More than 3 years’ experience within Engineering Insurance .
Candidate should be able to work independently, a great problem solver and live the company values.
Skills
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Competencies
Action Oriented
Business Insight
Collaborates
Communicates Effectively
Decision Quality
Ensures Accountability
Financial Acumen
Instills Trust
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent
Closing Date
17 July 2026 , 23:59
The Old Mutual Story!
But we have used , inside the last paragraph. That's not allowed? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid or . But we are supposed to use only ,
, - . So we should not use or . So we need to output just the text "The Old Mutual Story!" inside a
. So we output
The Old Mutual Story!
Thus final output should not contain any , , , , etc. Only
,
, , - . So we need to strip those tags but keep the text.
Thus final HTML:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
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 ✍️
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to identify sections and use headings. The original has headings like "Job Description", "Skills", "Competencies", "Education", "Closing Date". Also there are bolded items like Responsible for the processing... etc. Those are part of content; we should keep them as plain text, not as tags. But we need to preserve word-for-word, including the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes HTML tags? The original is plain-text job description with some HTML tags. We need to output clean semantic HTML, but we cannot add, remove, summarise, or rephrase. So we must keep the same text, including the tags? But we are to format it as clean semantic HTML using only
,
, - . So we can keep the tags? They are not allowed? The rule says no CSS classes, no inline styles, no s, no
tags. It doesn't forbid or . But they are not semantic; but maybe allowed as they are part of original content. However we might need to preserve them exactly as they appear. The original includes tags around some text. We should keep them as is, but we need to wrap sections with . The headings themselves are bolded maybe. For example "Job Description" is wrapped in in the original? Actually it's Job Description inside a
. So we need to output that as plain text? The instruction: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace those headings with tags. But we must preserve original content word-for-word. If we replace Job Description with Job Description
, we are changing the tag, but the content word is same. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to is not adding or removing words, just tag change. That might be acceptable. But we must not add or remove content. So we can convert the heading text to and keep the text inside. The original heading "Job Description" appears inside tags. We can output Job Description
. That seems okay.
Similarly "Skills" and "Competencies" and "Education" and "Closing Date" are headings. Use .
Now we need to output the whole thing as HTML with only
,
, - . No other tags. But the original includes
- already. We need to keep them but wrap list items in
- . The original already uses
- but also includes
inside
- . That's okay; we can keep
inside
- as they are allowed? The rule says use
- for list items. It doesn't forbid
inside
- . So we can keep
inside
- . But we must not add extra tags. So we can output the list items as
...content...
tags inside? The original list items have
around the text. For example:
Responsible for the processing...
wrapper. We can keep that
inside
- . That's okay.
We must not add any extra commentary. Just output the HTML.
We need to remove any stray tags like , maybe we keep them as they are part of content. But we need to ensure we only use allowed tags:
,
, , - . Using inside
- is not allowed? The rule didn't forbid , but it said use
- for list items. It didn't say we cannot use . But to be safe, we might keep as part of content because it's part of original text. However the instruction says "Use
for section headers". It doesn't say we cannot use . But we might want to avoid extra tags. However preserving original content word-for-word includes the tags. So we must keep them. But we also need to wrap headings with . So we can replace the surrounding with . For example original:
Job Description
. We can output Job Description
. That removes the tags but keeps the text. That's okay because we are not adding or removing words. The tags are not part of the visible text; they are markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does that include markup? Probably they mean the textual content, not the markup. But to be safe, we can keep the tags as they appear, but then we would have inside which is not allowed? The rule didn't forbid , but we are supposed to use only
,
, - . So we cannot use . So we must remove tags. But that would be removing markup, which might be considered removing content? The content inside is still there. The instruction is ambiguous. I think we can remove the tags because they are not part of the visible text; they are formatting. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing tags changes the markup but not the words. The words "Job Description" remain. So it's okay.
Thus we will output:
Job Description
then paragraphs.
We need to preserve all paragraphs as . The original has many
tags with text. Some are empty. We can output
maybe? But we should preserve empty paragraphs? They contain nothing. We can output but that adds empty content. Might be okay. But maybe we can just output
? The original has etc. Those are empty. We can output . That preserves emptiness.
We need to preserve the list items exactly as they appear, including the inside some list items. We can keep inside ...content...
Skills
Action Planning, Compliance Software, ... etc. So we need to output Skills
then a containing that comma-separated list. But we must preserve the exact text including the commas and spaces. So we output
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Similarly "Competencies" section includes headings with empty. The original has repeated. We need to preserve them? They are empty. We can output maybe but we are not allowed to use . The rule only allows for section headers. So we should not output . But the original contains tags. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must keep those tags? But we are limited to only
,
, - . So we cannot output
. This is a conflict. Perhaps we can ignore those empty tags because they contain no content. They are just placeholders. We could omit them, but that would be removing content. However they are empty, so removing them doesn't change visible content. The instruction says do not remove content. But empty tags maybe considered content? Might be okay to drop them. But to be safe, we could output them as but that violates allowed tags. The rule says "Use for section headers". It doesn't forbid other heading tags, but the instruction says use for section headers. So we should not use . So we can ignore those empty tags.
The "Closing Date" section includes Closing Date then text "17 July 2026 , 23:59". So we output Closing Date
then
17 July 2026 , 23:59
.
The "The Old Mutual Story!" part includes The Old Mutual Story!. That's text with tags. We need to preserve it. We can output The Old Mutual Story!
but we cannot use or or maybe? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid , , . But we might want to keep them as they appear. However we are supposed to use only ,
, - . So we cannot use or or . But we need to preserve them? This is contradictory. Probably they expect us to keep the textual content but not the markup tags. So we can output the text "The Old Mutual Story!" inside a
. The original includes formatting tags, but we can just output the text. That would be preserving the words but not the tags. That seems acceptable.
Thus final output: a series of
headings and
paragraphs and
- list items.
Let's construct:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
Ensure timeous monitoring and accurate management of mail count
Drive interdepartmental discussions on transactions and business issues and make recommendations
Participate in training and mentoring of junior underwriting support staff
In-depth understanding of specialty business, to fully understand the risk and impact to Specialty department
Ensure necessary authorisations are obtained to finalise transactions
Follow up on declarations, monthly/quarterly and annually
Work with various business partners to ensure that day-to-day administrative processes and procedures are fulfilled.
Continuous improvement to ensure effective service
Ensure statutory and legislative knowledge is always current in order to resolve customer complaints, to advise the business on corrective solutions to mitigate risks and to improve the customer experience whilst complying with governance requirements.
Ensure adherence to organisational policies, practices, and procedures.
Identify solutions to enhance cost effectiveness and increase operational efficiency
Service delivery to ensure customer satisfaction
Maintain service, quality, and desired outputs within a specific functional process through ensuring compliance to tactical policies, procedures, and standards.
Establish productive operational relationships with key stakeholders in the various channels and administrative teams.
Develop work routines in line with operational plans / schedules in order to manage achievement of service delivery goals.
Share knowledge on, and participate in the creation of new standards, control systems and procedures to maintain service delivery.
Cost control and governance adherence
Proactively ensure use of time, of resources, money, materials, or equipment is in line with policies and procedures.
Comply with corporate governance policies, procedures, and standards.
Operate within agreed mandates.
Quality people practices
Align own behaviour with the organisation culture and values.
Share and transfer product, process, and systems knowledge to colleagues.
Ensure achievement of own performance objectives.
Actively share information with other team members regarding successes, issues, trends, and ideas.
Actively participate in own professional development and career path.
Actively promote a culture of learning and high-performance culture amongst team members.
Diploma and/or equivalent NQF Level 6 qualification in general insurance.
More than 3 years’ experience within Engineering Insurance .
Candidate should be able to work independently, a great problem solver and live the company values.
Skills
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Competencies
Action Oriented
Business Insight
Collaborates
Communicates Effectively
Decision Quality
Ensures Accountability
Financial Acumen
Instills Trust
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent
Closing Date
17 July 2026 , 23:59
The Old Mutual Story!
But we have used , inside the last paragraph. That's not allowed? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid or . But we are supposed to use only ,
, - . So we should not use or . So we need to output just the text "The Old Mutual Story!" inside a
. So we output
The Old Mutual Story!
Thus final output should not contain any , , , , etc. Only
,
, , - . So we need to strip those tags but keep the text.
Thus final HTML:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
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 ✍️
tags. It doesn't forbid or . But they are not semantic; but maybe allowed as they are part of original content. However we might need to preserve them exactly as they appear. The original includes tags around some text. We should keep them as is, but we need to wrap sections with
. The headings themselves are bolded maybe. For example "Job Description" is wrapped in in the original? Actually it's Job Description inside a
. So we need to output that as plain text? The instruction: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should replace those headings with tags. But we must preserve original content word-for-word. If we replace Job Description with Job Description
, we are changing the tag, but the content word is same. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to is not adding or removing words, just tag change. That might be acceptable. But we must not add or remove content. So we can convert the heading text to and keep the text inside. The original heading "Job Description" appears inside tags. We can output Job Description
. That seems okay.
Similarly "Skills" and "Competencies" and "Education" and "Closing Date" are headings. Use .
Now we need to output the whole thing as HTML with only
Job Description
, we are changing the tag, but the content word is same. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to is not adding or removing words, just tag change. That might be acceptable. But we must not add or remove content. So we can convert the heading text to and keep the text inside. The original heading "Job Description" appears inside tags. We can output Job Description
. That seems okay.
Similarly "Skills" and "Competencies" and "Education" and "Closing Date" are headings. Use .
Now we need to output the whole thing as HTML with only
Job Description
. That seems okay. Similarly "Skills" and "Competencies" and "Education" and "Closing Date" are headings. Use. Now we need to output the whole thing as HTML with only
,
, - . No other tags. But the original includes
- already. We need to keep them but wrap list items in
- . The original already uses
- but also includes
inside
- . That's okay; we can keep
inside
- as they are allowed? The rule says use
- for list items. It doesn't forbid
inside
- . So we can keep
inside
- . But we must not add extra tags. So we can output the list items as
...content...
tags inside? The original list items have
around the text. For example:
Responsible for the processing...
wrapper. We can keep that
inside
- . That's okay.
We must not add any extra commentary. Just output the HTML.
We need to remove any stray tags like , maybe we keep them as they are part of content. But we need to ensure we only use allowed tags:
,
, , - . Using inside
- is not allowed? The rule didn't forbid , but it said use
- for list items. It didn't say we cannot use . But to be safe, we might keep as part of content because it's part of original text. However the instruction says "Use
for section headers". It doesn't say we cannot use . But we might want to avoid extra tags. However preserving original content word-for-word includes the tags. So we must keep them. But we also need to wrap headings with . So we can replace the surrounding with . For example original:
Job Description
. We can output Job Description
. That removes the tags but keeps the text. That's okay because we are not adding or removing words. The tags are not part of the visible text; they are markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does that include markup? Probably they mean the textual content, not the markup. But to be safe, we can keep the tags as they appear, but then we would have inside which is not allowed? The rule didn't forbid , but we are supposed to use only
,
, - . So we cannot use . So we must remove tags. But that would be removing markup, which might be considered removing content? The content inside is still there. The instruction is ambiguous. I think we can remove the tags because they are not part of the visible text; they are formatting. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing tags changes the markup but not the words. The words "Job Description" remain. So it's okay.
Thus we will output:
Job Description
then paragraphs.
We need to preserve all paragraphs as . The original has many
tags with text. Some are empty. We can output
maybe? But we should preserve empty paragraphs? They contain nothing. We can output but that adds empty content. Might be okay. But maybe we can just output
? The original has etc. Those are empty. We can output . That preserves emptiness.
We need to preserve the list items exactly as they appear, including the inside some list items. We can keep inside ...content...
Skills
Action Planning, Compliance Software, ... etc. So we need to output Skills
then a containing that comma-separated list. But we must preserve the exact text including the commas and spaces. So we output
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Similarly "Competencies" section includes headings with empty. The original has repeated. We need to preserve them? They are empty. We can output maybe but we are not allowed to use . The rule only allows for section headers. So we should not output . But the original contains tags. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must keep those tags? But we are limited to only
,
, - . So we cannot output
. This is a conflict. Perhaps we can ignore those empty tags because they contain no content. They are just placeholders. We could omit them, but that would be removing content. However they are empty, so removing them doesn't change visible content. The instruction says do not remove content. But empty tags maybe considered content? Might be okay to drop them. But to be safe, we could output them as but that violates allowed tags. The rule says "Use for section headers". It doesn't forbid other heading tags, but the instruction says use for section headers. So we should not use . So we can ignore those empty tags.
The "Closing Date" section includes Closing Date then text "17 July 2026 , 23:59". So we output Closing Date
then
17 July 2026 , 23:59
.
The "The Old Mutual Story!" part includes The Old Mutual Story!. That's text with tags. We need to preserve it. We can output The Old Mutual Story!
but we cannot use or or maybe? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid , , . But we might want to keep them as they appear. However we are supposed to use only ,
, - . So we cannot use or or . But we need to preserve them? This is contradictory. Probably they expect us to keep the textual content but not the markup tags. So we can output the text "The Old Mutual Story!" inside a
. The original includes formatting tags, but we can just output the text. That would be preserving the words but not the tags. That seems acceptable.
Thus final output: a series of
headings and
paragraphs and
- list items.
Let's construct:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
Ensure timeous monitoring and accurate management of mail count
Drive interdepartmental discussions on transactions and business issues and make recommendations
Participate in training and mentoring of junior underwriting support staff
In-depth understanding of specialty business, to fully understand the risk and impact to Specialty department
Ensure necessary authorisations are obtained to finalise transactions
Follow up on declarations, monthly/quarterly and annually
Work with various business partners to ensure that day-to-day administrative processes and procedures are fulfilled.
Continuous improvement to ensure effective service
Ensure statutory and legislative knowledge is always current in order to resolve customer complaints, to advise the business on corrective solutions to mitigate risks and to improve the customer experience whilst complying with governance requirements.
Ensure adherence to organisational policies, practices, and procedures.
Identify solutions to enhance cost effectiveness and increase operational efficiency
Service delivery to ensure customer satisfaction
Maintain service, quality, and desired outputs within a specific functional process through ensuring compliance to tactical policies, procedures, and standards.
Establish productive operational relationships with key stakeholders in the various channels and administrative teams.
Develop work routines in line with operational plans / schedules in order to manage achievement of service delivery goals.
Share knowledge on, and participate in the creation of new standards, control systems and procedures to maintain service delivery.
Cost control and governance adherence
Proactively ensure use of time, of resources, money, materials, or equipment is in line with policies and procedures.
Comply with corporate governance policies, procedures, and standards.
Operate within agreed mandates.
Quality people practices
Align own behaviour with the organisation culture and values.
Share and transfer product, process, and systems knowledge to colleagues.
Ensure achievement of own performance objectives.
Actively share information with other team members regarding successes, issues, trends, and ideas.
Actively participate in own professional development and career path.
Actively promote a culture of learning and high-performance culture amongst team members.
Diploma and/or equivalent NQF Level 6 qualification in general insurance.
More than 3 years’ experience within Engineering Insurance .
Candidate should be able to work independently, a great problem solver and live the company values.
Skills
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Competencies
Action Oriented
Business Insight
Collaborates
Communicates Effectively
Decision Quality
Ensures Accountability
Financial Acumen
Instills Trust
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent
Closing Date
17 July 2026 , 23:59
The Old Mutual Story!
But we have used , inside the last paragraph. That's not allowed? The rule only restricts CSS classes, inline styles, ,
. It doesn't forbid or . But we are supposed to use only ,
, - . So we should not use or . So we need to output just the text "The Old Mutual Story!" inside a
. So we output
The Old Mutual Story!
Thus final output should not contain any , , , , etc. Only
,
, , - . So we need to strip those tags but keep the text.
Thus final HTML:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
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 ✍️
- already. We need to keep them but wrap list items in
- . The original already uses
- but also includes
inside
- . That's okay; we can keep
inside
- as they are allowed? The rule says use
- for list items. It doesn't forbid
inside
- . So we can keep
inside
- . But we must not add extra tags. So we can output the list items as
...content...
maybe. But we need to preserve original content exactly, including the Responsible for the processing...
. That includes a - . That's okay.
We must not add any extra commentary. Just output the HTML.
We need to remove any stray tags like , maybe we keep them as they are part of content. But we need to ensure we only use allowed tags:
,
,
- ,
- . Using inside
- is not allowed? The rule didn't forbid , but it said use
- for list items. It didn't say we cannot use . But to be safe, we might keep as part of content because it's part of original text. However the instruction says "Use
for section headers". It doesn't say we cannot use . But we might want to avoid extra tags. However preserving original content word-for-word includes the tags. So we must keep them. But we also need to wrap headings with
. So we can replace the surrounding with
. For example original:
Job Description
. We can outputJob Description
. That removes the tags but keeps the text. That's okay because we are not adding or removing words. The tags are not part of the visible text; they are markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does that include markup? Probably they mean the textual content, not the markup. But to be safe, we can keep the tags as they appear, but then we would have insidewhich is not allowed? The rule didn't forbid , but we are supposed to use only
,
,
- . So we cannot use . So we must remove tags. But that would be removing markup, which might be considered removing content? The content inside is still there. The instruction is ambiguous. I think we can remove the tags because they are not part of the visible text; they are formatting. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing tags changes the markup but not the words. The words "Job Description" remain. So it's okay.
Thus we will output:
Job Description
then paragraphs. We need to preserve all paragraphs as. The original has many
tags with text. Some are empty. We can output
maybe? But we should preserve empty paragraphs? They contain nothing. We can output but that adds empty content. Might be okay. But maybe we can just output
? The original has etc. Those are empty. We can output . That preserves emptiness. We need to preserve the list items exactly as they appear, including the inside some list items. We can keep inside...content...
Skills
Action Planning, Compliance Software, ... etc. So we need to outputSkills
then acontaining that comma-separated list. But we must preserve the exact text including the commas and spaces. So we output
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Similarly "Competencies" section includes headings with empty. The original has repeated. We need to preserve them? They are empty. We can output maybe but we are not allowed to use. The rule only allows
for section headers. So we should not output
. But the original contains tags. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must keep those tags? But we are limited to only
,
,
- . So we cannot output
. This is a conflict. Perhaps we can ignore those empty
tags because they contain no content. They are just placeholders. We could omit them, but that would be removing content. However they are empty, so removing them doesn't change visible content. The instruction says do not remove content. But empty tags maybe considered content? Might be okay to drop them. But to be safe, we could output them as but that violates allowed tags. The rule says "Use
for section headers". It doesn't forbid other heading tags, but the instruction says use
for section headers. So we should not use
. So we can ignore those empty
tags. The "Closing Date" section includes Closing Date then text "17 July 2026 , 23:59". So we output
Closing Date
then17 July 2026 , 23:59
. The "The Old Mutual Story!" part includes The Old Mutual Story!. That's text with tags. We need to preserve it. We can outputThe Old Mutual Story!
but we cannot use or or maybe? The rule only restricts CSS classes, inline styles,,
. It doesn't forbid , , . But we might want to keep them as they appear. However we are supposed to use only,
,
- . So we cannot use or or . But we need to preserve them? This is contradictory. Probably they expect us to keep the textual content but not the markup tags. So we can output the text "The Old Mutual Story!" inside a
. The original includes formatting tags, but we can just output the text. That would be preserving the words but not the tags. That seems acceptable. Thus final output: a series of
headings and
paragraphs and
- list items.
Let's construct:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
Ensure timeous monitoring and accurate management of mail count
Drive interdepartmental discussions on transactions and business issues and make recommendations
Participate in training and mentoring of junior underwriting support staff
In-depth understanding of specialty business, to fully understand the risk and impact to Specialty department
Ensure necessary authorisations are obtained to finalise transactions
Follow up on declarations, monthly/quarterly and annually
Work with various business partners to ensure that day-to-day administrative processes and procedures are fulfilled.
Continuous improvement to ensure effective service
Ensure statutory and legislative knowledge is always current in order to resolve customer complaints, to advise the business on corrective solutions to mitigate risks and to improve the customer experience whilst complying with governance requirements.
Ensure adherence to organisational policies, practices, and procedures.
Identify solutions to enhance cost effectiveness and increase operational efficiency
Service delivery to ensure customer satisfaction
Maintain service, quality, and desired outputs within a specific functional process through ensuring compliance to tactical policies, procedures, and standards.
Establish productive operational relationships with key stakeholders in the various channels and administrative teams.
Develop work routines in line with operational plans / schedules in order to manage achievement of service delivery goals.
Share knowledge on, and participate in the creation of new standards, control systems and procedures to maintain service delivery.
Cost control and governance adherence
Proactively ensure use of time, of resources, money, materials, or equipment is in line with policies and procedures.
Comply with corporate governance policies, procedures, and standards.
Operate within agreed mandates.
Quality people practices
Align own behaviour with the organisation culture and values.
Share and transfer product, process, and systems knowledge to colleagues.
Ensure achievement of own performance objectives.
Actively share information with other team members regarding successes, issues, trends, and ideas.
Actively participate in own professional development and career path.
Actively promote a culture of learning and high-performance culture amongst team members.
Diploma and/or equivalent NQF Level 6 qualification in general insurance.
More than 3 years’ experience within Engineering Insurance .
Candidate should be able to work independently, a great problem solver and live the company values.
Skills
Action Planning, Compliance Software, Computer Literacy, Crisis Management, Data Compilation, Data Controls, Legal Practices, Management Reporting, Numerical Aptitude, Oral Communications, Professional Presentation, Regulatory Compliance Management, Risk Management, Underwriting Management
Competencies
Action Oriented
Business Insight
Collaborates
Communicates Effectively
Decision Quality
Ensures Accountability
Financial Acumen
Instills Trust
Education
NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent
Closing Date
17 July 2026 , 23:59
The Old Mutual Story!
But we have used , inside the last paragraph. That's not allowed? The rule only restricts CSS classes, inline styles,,
. It doesn't forbid or . But we are supposed to use only,
,
- . So we should not use or . So we need to output just the text "The Old Mutual Story!" inside a
. So we output
The Old Mutual Story!
Thus final output should not contain any , , ,, etc. Only
,
,
- ,
- . So we need to strip those tags but keep the text.
Thus final HTML:
Job Description
Responsible for the administration of complex transactions on policies such as new business, renewals, and midterm adjustments according to the guidelines. This position requires a team player who will manage the operations of the products and apply their expertise. The senior underwriting support will also handle day-to-day administrative functions.
Responsible for the processing of complex transactions such as new business, renewals, and midterm adjustments, correctly and within laid down timeframes.
Ensure all transactions including completed facultative reinsurance placement are processed accurately and correctly
Ensure documentation including Sasria is issued, checked, and authorised prior to dispatch as per regulations
Attend to complex accounts queries as per the Standard Operating Procedure and Service Level Agreements with necessary escalation as per the laid down rules
- . So we need to strip those tags but keep the text.
Thus final HTML:
- list items.
Let's construct:
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 ✍️ - . So we cannot use or or . But we need to preserve them? This is contradictory. Probably they expect us to keep the textual content but not the markup tags. So we can output the text "The Old Mutual Story!" inside a
- . So we cannot use . So we must remove tags. But that would be removing markup, which might be considered removing content? The content inside is still there. The instruction is ambiguous. I think we can remove the tags because they are not part of the visible text; they are formatting. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing tags changes the markup but not the words. The words "Job Description" remain. So it's okay.
Thus we will output:
- is not allowed? The rule didn't forbid , but it said use
- . Using inside
tags inside? The original list items have
around the text. For example:
wrapper. We can keep that
inside
- for list items. It doesn't forbid
- but also includes
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.