Job Description
for intro paragraphs and general text,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items (duties, requirements, qualifications, skills). No CSS classes, no inline styles, no s, no
tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble.
We have raw HTML input with
, , , , etc. We need to transform to semantic HTML per rules: use for section headers,
for intro paragraphs and general text,
- for list items. Also need to preserve content word-for-word. Must remove any tags not allowed: , tables, etc. But we must preserve the text content. So we need to extract the text and reformat.
We must not add or remove content. So we need to keep all textual content exactly as appears, but we can change tags to allowed ones. Must not add extra text. Must not remove any text. Must preserve spaces? Probably okay.
We need to convert:
- The initial paragraph: "
Job Description:
" then a paragraph with description. We need to keep "Job Description:" as part of text? The rule: Use for introductory paragraphs and general text. So we can have
Job Description: The Monitoring Analyst is responsible...
. The original had Job Description: separate line then paragraph. We need to preserve the text "Job Description:" exactly. So combine into one maybe? But we must not add or remove content. If we combine them into one
, we are not adding or removing text, just changing markup. That's allowed. However we must ensure we keep the colon and space. The original had a line break after the strong tag then a new
. We'll produce a single
containing "Job Description: The Monitoring Analyst is responsible...". That preserves the text.
- Then we have "
KEY RESPONSIBILITIES
" then a list. According to rules, section headers should be . So we need to change that to KEY RESPONSIBILITIES
. Then the list items should be - ... each item text. Need to preserve the text exactly, including any trailing spaces or etc. The original list items have at end of some lines. We must preserve them. So we need to keep the exact text inside each
- . The original had after some sentences. We'll keep them.
- Then there is a
(empty paragraph with a non-breaking space). According to rule, we should preserve content word-for-word. That is a paragraph containing a non-breaking space. We need to keep it. Should we wrap it in
? That's allowed ( for general text). So we keep
.
- Then "DAILY RESPONSIBILITIES
" then a . Convert header to DAILY RESPONSIBILITIES
. Keep list.
- Then another
.
- Then "ACADEMIC QUALIFICATIONS
" then a table. According to rules, we should use for section headers, and for content we need to use
for paragraphs and
- for list items. But the content is a table. We need to preserve the text word-for-word, but we cannot use
or etc because not allowed. However we must preserve the content exactly. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". It does not say we cannot change tags, but we must keep the textual content. So we can transform the table into something else as long as we keep the text. But we must not add or remove any text. We can represent the table data as paragraphs or list items, but we must keep the exact text. However we need to decide how to format: The rule says use for introductory paragraphs and general text,
- for list items. It doesn't forbid using other tags like
but says no CSS classes, no inline styles, no s, no
tags. It didn't explicitly forbid . However earlier they said "Use for introductory paragraphs and general text; Use
for section headers; Use - for list items". They didn't say we cannot use tables, but they likely expect us to avoid tables and use
or
. However the instruction "Preserve ALL original content word-for-word" suggests we should keep the exact text, but we can change markup. So we can convert the table into a series of paragraphs each containing the cell text separated maybe by spaces or line breaks? But we must not add or remove text. If we convert table to paragraphs, we need to decide how to separate cells. The original table had three columns: Detail, Specific Field or Qualification, Need Type. And rows with data. If we just output each cell as a paragraph, we would lose the table structure but keep the text. That's acceptable as we are not adding or removing text; we are just representing it differently. However we might inadvertently add extra spaces or line breaks not originally there. But line breaks are not part of the original text? The original had line breaks inside the HTML but not visible. Usually preserving text means the visible characters, not whitespace formatting. It's ambiguous.
Given typical tasks, they expect to convert tables into
paragraphs each line maybe. But we need to be safe: maybe we can keep the table as is? The rules didn't forbid
. They only said use for intro paragraphs and general text,
for section headers, - for list items. They didn't say you cannot use other tags like
. However they said "No CSS classes, no inline styles, no s, no
tags". They didn't forbid . So we could keep the markup as is, but we need to remove any inline styles (like style="margin-left:0.1pt") etc. The original table had inline styles on inside
. We must remove inline styles. Also we must remove any CSS classes (none). So we can keep , , , but we need to strip the tags and replace with just
(since
allowed). Also we need to remove the tags inside cells? The rule says use for section headers, but inside table we can keep ? It didn't forbid . However they said use for introductory paragraphs and general text; they didn't forbid . But to be safe, we could keep as it's not prohibited. However they said "Use for introductory paragraphs and general text". That doesn't forbid other tags. But they also said "No CSS classes, no inline styles, no
s, no
tags". So we can keep . However we need to remove inline styles from the inside
. So we replace with
. Also we need to remove the inside? No, we keep.
Also we need to remove the superscript tags like 4 and 5. Those are not prohibited but they are tags. They are not
,
, etc. They are allowed? The rule didn't forbid . However we might want to keep them as they are part of original content. The instruction: preserve ALL original content word-for-word. So we should keep the tags as they are. However we need to remove any inline styles; there are none on sup.
Thus we could keep the table structure but strip style attributes from tags. Also we need to ensure no
or
. There are none.
Similarly for the experience table.
Thus final HTML: start with Job Description: The Monitoring Analyst is responsible for supporting the monitoring infrastructure in delivering and maintaining system management and event monitoring capabilities. The role supports the Incident Manager by providing accurate system performance insights, timely reporting, and adherence to monitoring protocols to minimize business disruption. The position operates on a full-time basis within a 24x7 shift Rota.
Then KEY RESPONSIBILITIES
Then with each - containing the exact text from original list items (including at end). Need to copy each
- text.
Original list items:
1. "Constantly monitoring anomalous activities, events, and alerts and making interventions to avert possible service downtimes or minimise downtimes of IT services. "
2. "Working with technical teams to conduct root cause analysis to resolve the problem and prevent future incidents and issues. "
3. "Managing, coordinating, and resolving IT related incidents from monitoring "
4. "Share threat analysis, statistical analysis, event analysis and reports from the monitoring tool"
5. "Identification of areas for further investigation, improvement and/or correction based on reported metrics. "
6. "Performance reporting and improvement recommendations"
7. "Installations, troubleshooting and maintenance of the Monitoring software used by the bank."
8. "1st level support on the various bank systems, Network & Channels."
9. "Optimization and quality of service reporting"
Note: item 3 had double after monitoring. We'll keep that.
Item 8 includes st and &.
We need to preserve those tags.
Thus each
- will contain exactly that string.
Then after list, we have
(the empty paragraph). We'll keep that.
Then DAILY RESPONSIBILITIES
Then with list items:
1. "Perform real time monitoring of infrastructure and applications that ensures proactive interventions to avert possible service outages/downtimes"
2. "Managing and coordinating high Impact IT related incidents reported through the various channels including i.e Email, Social Media and Phone calls"
3. "Share daily threats, events , statistical analysis and reports from the monitoring tool"
4. "Identification of areas for further investigation, improvement and/or correction based on reported metrics. "
Note: item 2 has a space before Impact? original: "high Impact". We'll keep as is.
Item 3: "Share daily threats, events , statistical analysis and reports from the monitoring tool" includes a space before comma after events. Keep.
Item 4 ends with .
Then
Then ACADEMIC QUALIFICATIONS
Then we need to output the table. We'll keep etc. But we need to remove inline styles from inside
. Also we need to keep tags inside cells.
Original table:
Detail
Specific Field or Qualification
Need Type4
Bachelor’s Degree
Information Technology, Computer Science, or a related discipline
RQ
Professional Certification
ITIL Foundation
RQ
Professional Qualifications
Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/
AA
We need to strip style attributes from tags. So each
becomes
. Also note there is a after some text inside the
. We'll keep.
Also note the first row's third cell:
Need Type4 (no ). We'll keep as is.
Also note there is a trailing after some cells.
Thus final table HTML will be:
Detail
Specific Field or Qualification
Need Type4
Bachelor’s Degree
Information Technology, Computer Science, or a related discipline
RQ
Professional Certification
ITIL Foundation
RQ
Professional Qualifications
Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/
AA
Note: we removed the style attributes. Also we need to ensure we didn't add or remove any text. Check each cell: we kept the inner text exactly, including spaces and . For first cell: original had Detail
. We changed to Detail
. That's fine.
Second cell: same.
Third cell: original had Need Type4 . No . We kept same.
Second row first cell: original
Bachelor’s Degree
-> Bachelor’s Degree
. Good.
Second row second cell: Information Technology, Computer Science, or a related discipline
-> Information Technology, Computer Science, or a related discipline
. Good.
Second row third cell: RQ
-> RQ
. Good.
Third row first cell: Professional Certification
-> Professional Certification
. Good.
Third row second cell: ITIL Foundation
-> ITIL Foundation
. Good.
Third row third cell: RQ
-> RQ
. Good.
Fourth row first cell: Professional Qualifications
-> Professional Qualifications
. Good.
Fourth row second cell: Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/
-> same without style.
Fourth row third cell: AA
-> AA
. Good.
Now after that we have
(empty paragraph). Then EXPERIENCE
then experience table.
Experience table original:
EXPERIENCE
Detail
Minimum No of Years
Need Type5
Total Minimum No of Years Experience Required
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.
tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in
tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble. We have raw HTML input with
, , for intro paragraphs and general text, Job Description: for introductory paragraphs and general text. So we can have Job Description: The Monitoring Analyst is responsible... maybe? But we must not add or remove content. If we combine them into one , we are not adding or removing text, just changing markup. That's allowed. However we must ensure we keep the colon and space. The original had a line break after the strong tag then a new . We'll produce a single containing "Job Description: The Monitoring Analyst is responsible...". That preserves the text.
- Then we have " KEY RESPONSIBILITIES for general text). So we keep DAILY RESPONSIBILITIES ACADEMIC QUALIFICATIONS for paragraphs and for introductory paragraphs and general text, for introductory paragraphs and general text; Use or paragraphs each containing the cell text separated maybe by spaces or line breaks? But we must not add or remove text. If we convert table to paragraphs, we need to decide how to separate cells. The original table had three columns: Detail, Specific Field or Qualification, Need Type. And rows with data. If we just output each cell as a paragraph, we would lose the table structure but keep the text. That's acceptable as we are not adding or removing text; we are just representing it differently. However we might inadvertently add extra spaces or line breaks not originally there. But line breaks are not part of the original text? The original had line breaks inside the HTML but not visible. Usually preserving text means the visible characters, not whitespace formatting. It's ambiguous.
Given typical tasks, they expect to convert tables into paragraphs each line maybe. But we need to be safe: maybe we can keep the table as is? The rules didn't forbid for intro paragraphs and general text, inside tags and replace with just (since allowed). Also we need to remove the tags inside cells? The rule says use for introductory paragraphs and general text; they didn't forbid . But to be safe, we could keep as it's not prohibited. However they said "Use for introductory paragraphs and general text". That doesn't forbid other tags. But they also said "No CSS classes, no inline styles, no inside with . Also we need to remove the inside? No, we keep.
Also we need to remove the superscript tags like 4 and 5. Those are not prohibited but they are tags. They are not tags. Also we need to ensure no Job Description: The Monitoring Analyst is responsible for supporting the monitoring infrastructure in delivering and maintaining system management and event monitoring capabilities. The role supports the Incident Manager by providing accurate system performance insights, timely reporting, and adherence to monitoring protocols to minimize business disruption. The position operates on a full-time basis within a 24x7 shift Rota. inside Detail Specific Field or Qualification Bachelor’s Degree Information Technology, Computer Science, or a related discipline RQ Professional Certification ITIL Foundation RQ Professional Qualifications Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/ AA tags. So each becomes . Also note there is a after some text inside the . We'll keep.
Also note the first row's third cell: ). We'll keep as is.
Also note there is a trailing after some cells.
Thus final table HTML will be:
Detail Specific Field or Qualification Bachelor’s Degree Information Technology, Computer Science, or a related discipline RQ Professional Certification ITIL Foundation RQ Professional Qualifications Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/ AA Detail Detail . We kept same.
Second row first cell: original Bachelor’s Degree Bachelor’s Degree Information Technology, Computer Science, or a related discipline Information Technology, Computer Science, or a related discipline RQ RQ Professional Certification Professional Certification ITIL Foundation ITIL Foundation RQ RQ Professional Qualifications Professional Qualifications Microsoft Certified Desktop Support Technician (MCDST) certification/ Microsoft Office User Specialist (MOUS)/ MCP/ MCSE /MCITP/MCTS/A+/ AA AA EXPERIENCE Minimum No of Years Need Type5 Get an instant AI match score for this role — free, takes 3 minutes. The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste. Upload your CV and get a tailored cover letter in seconds — free, no account needed. Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call. 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. 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.,
, etc. We need to transform to semantic HTML per rules: use
for section headers,
list. According to rules, section headers should be
. So we need to change that to
KEY RESPONSIBILITIES
. Then the list items should be . Convert header to
DAILY RESPONSIBILITIES
. Keep list.
- Then another for section headers, and for content we need to use
or
etc because not allowed. However we must preserve the content exactly. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". It does not say we cannot change tags, but we must keep the textual content. So we can transform the table into something else as long as we keep the text. But we must not add or remove any text. We can represent the table data as paragraphs or list items, but we must keep the exact text. However we need to decide how to format: The rule says use but says no CSS classes, no inline styles, no
tags. It didn't explicitly forbid . However earlier they said "Use
for section headers; Use
. However the instruction "Preserve ALL original content word-for-word" suggests we should keep the exact text, but we can change markup. So we can convert the table into a series of
. They only said use
for section headers,
. However they said "No CSS classes, no inline styles, no
tags". They didn't forbid . So we could keep the
markup as is, but we need to remove any inline styles (like style="margin-left:0.1pt") etc. The original table had inline styles on
. We must remove inline styles. Also we must remove any CSS classes (none). So we can keep , ,
, but we need to strip the for section headers, but inside table we can keep ? It didn't forbid . However they said use
tags". So we can keep . However we need to remove inline styles from the . So we replace
, etc. They are allowed? The rule didn't forbid . However we might want to keep them as they are part of original content. The instruction: preserve ALL original content word-for-word. So we should keep the tags as they are. However we need to remove any inline styles; there are none on sup.
Thus we could keep the table structure but strip style attributes from
. There are none.
Similarly for the experience table.
Thus final HTML: start with KEY RESPONSIBILITIES
Then with each
DAILY RESPONSIBILITIES
Then with list items:
1. "Perform real time monitoring of infrastructure and applications that ensures proactive interventions to avert possible service outages/downtimes"
2. "Managing and coordinating high Impact IT related incidents reported through the various channels including i.e Email, Social Media and Phone calls"
3. "Share daily threats, events , statistical analysis and reports from the monitoring tool"
4. "Identification of areas for further investigation, improvement and/or correction based on reported metrics. "
Note: item 2 has a space before Impact? original: "high Impact". We'll keep as is.
Item 3: "Share daily threats, events , statistical analysis and reports from the monitoring tool" includes a space before comma after events. Keep.
Item 4 ends with .
Then
ACADEMIC QUALIFICATIONS
Then we need to output the table. We'll keep
etc. But we need to remove inline styles from . Also we need to keep tags inside cells.
Original table:
We need to strip style attributes from
Need Type4
Need Type4 (no
Note: we removed the style attributes. Also we need to ensure we didn't add or remove any text. Check each cell: we kept the inner text exactly, including spaces and . For first cell: original had
Need Type4
Need Type4 . No EXPERIENCE
then experience table.
Experience table original:
Detail
Total Minimum No of Years Experience Required
How well do you match?
Tailor your CV for this role
Free cover letter for this job
Let jobs find you
Add your CV for real matches
You're in.