Job Description
We need to output clean semantic HTML with ,
,
, - . Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. So we need to extract the text content from the given HTML snippet, preserving it exactly, then wrap appropriate parts with tags.
We have a job description with sections: KEY RESPONSIBILITIES (list items), then MINIMUM POSITION QUALIFICATION REQUIREMENTS (with sub-sections Academic & Professional, Experience, etc). There's a table with details. We must preserve all content word-for-word, including the table content, notes, etc. We need to format as semantic HTML: use
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). Use
for introductory paragraphs and general text.
We must not add or remove content. So we need to output the exact same textual content, but wrapped in tags.
We need to decide what constitutes a section header. The original text includes:
- "
- KEY RESPONSIBILITIES:
" => This is a header for responsibilities.
- Then a list of responsibilities.
- Then "
" (non-breaking space) maybe just a blank line.
- Then "- MINIMUM POSITION QUALIFICATION REQUIREMENTS
" => header for qualifications.
- Then "
" blank.
- Then "- Academic & Professional
" => subheader.
- Then "
" blank.
- Then a figure with a table (Academic & Professional details). We need to preserve the table content exactly. The instruction says use for introductory paragraphs and general text,
- for list items,
for section headers. It does not say we cannot use tables; but we should avoid etc. It didn't forbid tables. It only said no CSS classes, no inline styles, no s, no
tags. It didn't say we cannot use tables. However, we should aim to use semantic HTML: tables are okay if needed to preserve content. But we must not include inline styles. The original table has inline styles (style attributes). We must strip those? The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we cannot remove the style attributes because they are part of original content. However, the instruction also says: "No CSS classes, no inline styles, no s, no
tags". This is a conflict: we must preserve original content word-for-word, but also must not include inline styles. Which takes precedence? The instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." The rules: "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. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is contradictory if original content includes inline styles. We need to interpret: we should strip away the styling and just keep the textual content, because we cannot include inline styles per rule. The rule to preserve original content likely refers to the textual content, not the markup. Usually in such tasks, we strip formatting and keep the text. So we should output the plain text content, wrapped in appropriate semantic tags, without any inline styles.
Thus we need to extract the plain text from the given HTML, preserving spaces and line breaks? We need to preserve the content word-for-word, meaning we should not change any characters of the textual content. We can ignore the tags and just output the text. However, we need to add semantic tags around sections.
Thus we need to parse the given snippet and produce:
- A header KEY RESPONSIBILITIES:
- Then a with each responsibility as - ...
- Then maybe a for any blank lines? Probably ignore blank lines.
- Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
- Then Academic & Professional
(note the original had & which is HTML entity for &. We need to preserve that exactly? The original text includes "Academic & Professional". If we output as plain text, we should output "Academic & Professional"? The rule says preserve original content word-for-word. The original content includes the entity &. If we output as plain text, we would change it to &, which is not word-for-word. However, the instruction to not include inline styles may conflict. Usually we would decode entities to plain text. But "preserve ALL original content word-for-word" suggests we should keep the entity as is. But then we would have & in the output, which is okay as it's plain text. However, the output is HTML, so & would be interpreted as an ampersand. If we want to display the literal string "Academic & Professional", we would need to escape it as "Academic & Professional". That's messy.
Probably the intention is to keep the readable text, not the HTML entities. So we should convert & to &. Similarly for other entities like & in responsibilities list (e.g., "cheques, EFTs, direct debits & and unpaid"). That should become "cheques, EFTs, direct debits and unpaid". The original had "& and". Actually the text: "cheques, EFTs, direct debits & and unpaid". That seems odd: they likely meant "cheques, EFTs, direct debits and unpaid". The & is an HTML entity for &. So we should output "cheques, EFTs, direct debits and unpaid". Similarly other occurrences.
Thus we will decode HTML entities.
Now we need to extract all text content from the snippet, preserving order.
Let's manually extract.
First part: KEY RESPONSIBILITIES:
Then list items:
1. "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits & and unpaid) to customer’s accounts as per approved system limits and laid down procedures."
We need to decode & to &.
So: "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures."
Note there is an apostrophe in customer’s (Unicode right single quote). We'll keep as is.
2. "Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions."
3. "Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts."
4. "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties."
=> "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties."
5. "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank."
=> "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank."
6. "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns."
=> "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns."
7. "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
We need to handle the rd tag. The content includes "3rd". We should preserve the text "3rd" maybe? The original includes superscript tags. We should output "3rd". The rule: preserve original content word-for-word. The original includes the markup rd. If we strip it, we change content. But we cannot include tags because they are not allowed? The rule didn't forbid . It only forbids , inline styles, CSS classes,
. It didn't forbid . However, we are supposed to use only ,
, - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text. Use
for section headers ... Use - for list items". It doesn't explicitly forbid other tags, but to be safe, we should stick to those tags only. However, we need to preserve the content. The superscript is just formatting; we can represent as "3rd". That's essentially same meaning. I think it's acceptable.
Thus: "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
8. "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
=> "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
9. "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
=> "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
10. "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments"
Note there is a trailing period after the assessments? In the original: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments." So the period is separate but same sentence. So we should include the period: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments."
11. "Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency."
12. "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
=> "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
13. "Query management and ECRM case closure as per set SLA."
Now after responsibilities, we have blank lines (
) then MINIMUM POSITION QUALIFICATION REQUIREMENTS header.
Then blank line.
Then Academic & Professional subheader.
Then blank line.
Then a table with Academic & Professional details.
We need to preserve the table content exactly (text). The table includes:
Header row: Particulars | Detail | Specific Field or Qualification | Need Type
Then rows:
Education | Bachelor’s Degree | (empty) | RQ
Professional Qualifications | (empty) | (empty) | (empty)
Master’s Degree | (empty) | (empty) | (empty)
Then after table, a paragraph: "Notes:
" => "Notes:"
Then "4. Need Types are: RQ = Required, AA = Added Advantage
" => "4. Need Types are: RQ = Required, AA = Added Advantage"
Then blank lines.
Then "- Experience
" => subheader Experience.
Then blank line.
Then a figure with a table: "Total Minimum No of Years’ Experience Required" | "4 years"
Then blank lines.
Then another figure with a table: header row: Detail | Area | Minimum No of Years | Need Type
Rows:
Experience Area 1 | Branch banking | 1 | ES
Experience Area 2 | BOU clearing | 3 | DE
Then after that, there is a stray "KEY RESPONSIBILITIES:
- Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures.
- Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions.
- Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts.
- Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties.
- Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank.
- Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns.
- Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines.
- Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place.
- Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS.
- Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments.
- Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency.
- Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools.
- Query management and ECRM case closure as per set SLA.
Then maybe a for any blank lines? Not needed.
Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
Then Academic & Professional
Then we need to represent the table. Since we cannot use or inline styles, but we can use without style attributes. The rule didn't forbid tables. It only forbade CSS classes, inline styles, ,
. So we can output a plain with and maybe, but we should keep it simple: ... etc. However, using is okay. The rule didn't forbid . We'll output a table with the exact text.
We need to preserve the text exactly, including the header names: "Particulars", "Detail", "Specific Field or Qualification", "Need Type". Then rows.
We need to include the empty cells as empty.
We also need to include the Notes paragraph and the Need Types paragraph.
Thus after the Academic & Professional table, we output:
Notes:
4. Need Types are: RQ = Required, AA = Added Advantage
Then Experience
Then we need to output the table for Total Minimum No of Years’ Experience Required.
We can output a simple table with two columns: left cell: "Total Minimum No of Years’ Experience Required", right cell: "4 years". The original had a table with two columns, left wide, right narrow. We'll just output a table.
Then the next table for Experience Areas.
We'll output a table with header: Detail, Area, Minimum No of Years, Need Type.
Rows: Experience Area 1, Branch banking, 1, ES; Experience Area 2, BOU clearing, 3, DE.
We must ensure we
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.
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). Use
for introductory paragraphs and general text.
We must not add or remove content. So we need to output the exact same textual content, but wrapped in tags.
We need to decide what constitutes a section header. The original text includes:
- "
- KEY RESPONSIBILITIES:
" => This is a header for responsibilities.
- Then a list of responsibilities.
- Then "
" (non-breaking space) maybe just a blank line.
- Then "- MINIMUM POSITION QUALIFICATION REQUIREMENTS
" => header for qualifications.
- Then "
" blank.
- Then "- Academic & Professional
" => subheader.
- Then "
" blank.
- Then a figure with a table (Academic & Professional details). We need to preserve the table content exactly. The instruction says use for introductory paragraphs and general text,
- for list items,
for section headers. It does not say we cannot use tables; but we should avoid etc. It didn't forbid tables. It only said no CSS classes, no inline styles, no s, no
tags. It didn't say we cannot use tables. However, we should aim to use semantic HTML: tables are okay if needed to preserve content. But we must not include inline styles. The original table has inline styles (style attributes). We must strip those? The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we cannot remove the style attributes because they are part of original content. However, the instruction also says: "No CSS classes, no inline styles, no s, no
tags". This is a conflict: we must preserve original content word-for-word, but also must not include inline styles. Which takes precedence? The instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." The rules: "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. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is contradictory if original content includes inline styles. We need to interpret: we should strip away the styling and just keep the textual content, because we cannot include inline styles per rule. The rule to preserve original content likely refers to the textual content, not the markup. Usually in such tasks, we strip formatting and keep the text. So we should output the plain text content, wrapped in appropriate semantic tags, without any inline styles.
Thus we need to extract the plain text from the given HTML, preserving spaces and line breaks? We need to preserve the content word-for-word, meaning we should not change any characters of the textual content. We can ignore the tags and just output the text. However, we need to add semantic tags around sections.
Thus we need to parse the given snippet and produce:
- A header KEY RESPONSIBILITIES:
- Then a with each responsibility as - ...
- Then maybe a for any blank lines? Probably ignore blank lines.
- Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
- Then Academic & Professional
(note the original had & which is HTML entity for &. We need to preserve that exactly? The original text includes "Academic & Professional". If we output as plain text, we should output "Academic & Professional"? The rule says preserve original content word-for-word. The original content includes the entity &. If we output as plain text, we would change it to &, which is not word-for-word. However, the instruction to not include inline styles may conflict. Usually we would decode entities to plain text. But "preserve ALL original content word-for-word" suggests we should keep the entity as is. But then we would have & in the output, which is okay as it's plain text. However, the output is HTML, so & would be interpreted as an ampersand. If we want to display the literal string "Academic & Professional", we would need to escape it as "Academic & Professional". That's messy.
Probably the intention is to keep the readable text, not the HTML entities. So we should convert & to &. Similarly for other entities like & in responsibilities list (e.g., "cheques, EFTs, direct debits & and unpaid"). That should become "cheques, EFTs, direct debits and unpaid". The original had "& and". Actually the text: "cheques, EFTs, direct debits & and unpaid". That seems odd: they likely meant "cheques, EFTs, direct debits and unpaid". The & is an HTML entity for &. So we should output "cheques, EFTs, direct debits and unpaid". Similarly other occurrences.
Thus we will decode HTML entities.
Now we need to extract all text content from the snippet, preserving order.
Let's manually extract.
First part: KEY RESPONSIBILITIES:
Then list items:
1. "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits & and unpaid) to customer’s accounts as per approved system limits and laid down procedures."
We need to decode & to &.
So: "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures."
Note there is an apostrophe in customer’s (Unicode right single quote). We'll keep as is.
2. "Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions."
3. "Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts."
4. "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties."
=> "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties."
5. "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank."
=> "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank."
6. "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns."
=> "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns."
7. "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
We need to handle the rd tag. The content includes "3rd". We should preserve the text "3rd" maybe? The original includes superscript tags. We should output "3rd". The rule: preserve original content word-for-word. The original includes the markup rd. If we strip it, we change content. But we cannot include tags because they are not allowed? The rule didn't forbid . It only forbids , inline styles, CSS classes,
. It didn't forbid . However, we are supposed to use only ,
, - . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text. Use
for section headers ... Use - for list items". It doesn't explicitly forbid other tags, but to be safe, we should stick to those tags only. However, we need to preserve the content. The superscript is just formatting; we can represent as "3rd". That's essentially same meaning. I think it's acceptable.
Thus: "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
8. "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
=> "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
9. "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
=> "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
10. "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments"
Note there is a trailing period after the assessments? In the original: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments." So the period is separate but same sentence. So we should include the period: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments."
11. "Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency."
12. "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
=> "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
13. "Query management and ECRM case closure as per set SLA."
Now after responsibilities, we have blank lines (
) then MINIMUM POSITION QUALIFICATION REQUIREMENTS header.
Then blank line.
Then Academic & Professional subheader.
Then blank line.
Then a table with Academic & Professional details.
We need to preserve the table content exactly (text). The table includes:
Header row: Particulars | Detail | Specific Field or Qualification | Need Type
Then rows:
Education | Bachelor’s Degree | (empty) | RQ
Professional Qualifications | (empty) | (empty) | (empty)
Master’s Degree | (empty) | (empty) | (empty)
Then after table, a paragraph: "Notes:
" => "Notes:"
Then "4. Need Types are: RQ = Required, AA = Added Advantage
" => "4. Need Types are: RQ = Required, AA = Added Advantage"
Then blank lines.
Then "- Experience
" => subheader Experience.
Then blank line.
Then a figure with a table: "Total Minimum No of Years’ Experience Required" | "4 years"
Then blank lines.
Then another figure with a table: header row: Detail | Area | Minimum No of Years | Need Type
Rows:
Experience Area 1 | Branch banking | 1 | ES
Experience Area 2 | BOU clearing | 3 | DE
Then after that, there is a stray "KEY RESPONSIBILITIES:
- Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures.
- Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions.
- Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts.
- Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties.
- Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank.
- Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns.
- Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines.
- Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place.
- Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS.
- Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments.
- Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency.
- Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools.
- Query management and ECRM case closure as per set SLA.
Then maybe a for any blank lines? Not needed.
Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
Then Academic & Professional
Then we need to represent the table. Since we cannot use or inline styles, but we can use without style attributes. The rule didn't forbid tables. It only forbade CSS classes, inline styles, ,
. So we can output a plain with and maybe, but we should keep it simple: ... etc. However, using is okay. The rule didn't forbid . We'll output a table with the exact text.
We need to preserve the text exactly, including the header names: "Particulars", "Detail", "Specific Field or Qualification", "Need Type". Then rows.
We need to include the empty cells as empty.
We also need to include the Notes paragraph and the Need Types paragraph.
Thus after the Academic & Professional table, we output:
Notes:
4. Need Types are: RQ = Required, AA = Added Advantage
Then Experience
Then we need to output the table for Total Minimum No of Years’ Experience Required.
We can output a simple table with two columns: left cell: "Total Minimum No of Years’ Experience Required", right cell: "4 years". The original had a table with two columns, left wide, right narrow. We'll just output a table.
Then the next table for Experience Areas.
We'll output a table with header: Detail, Area, Minimum No of Years, Need Type.
Rows: Experience Area 1, Branch banking, 1, ES; Experience Area 2, BOU clearing, 3, DE.
We must ensure we
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.
for introductory paragraphs and general text. We must not add or remove content. So we need to output the exact same textual content, but wrapped in tags. We need to decide what constitutes a section header. The original text includes: - "
- KEY RESPONSIBILITIES:
- list of responsibilities.
- Then "
- MINIMUM POSITION QUALIFICATION REQUIREMENTS
- Academic & Professional
- for list items,
for section headers. It does not say we cannot use tables; but we should avoid
etc. It didn't forbid tables. It only said no CSS classes, no inline styles, nos, no
tags. It didn't say we cannot use tables. However, we should aim to use semantic HTML: tables are okay if needed to preserve content. But we must not include inline styles. The original table has inline styles (style attributes). We must strip those? The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we cannot remove the style attributes because they are part of original content. However, the instruction also says: "No CSS classes, no inline styles, nos, no
tags". This is a conflict: we must preserve original content word-for-word, but also must not include inline styles. Which takes precedence? The instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." The rules: "Usefor introductory paragraphs and general text. Use
for section headers ... Use
- for list items ... No CSS classes, no inline styles, no s, no
tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is contradictory if original content includes inline styles. We need to interpret: we should strip away the styling and just keep the textual content, because we cannot include inline styles per rule. The rule to preserve original content likely refers to the textual content, not the markup. Usually in such tasks, we strip formatting and keep the text. So we should output the plain text content, wrapped in appropriate semantic tags, without any inline styles. Thus we need to extract the plain text from the given HTML, preserving spaces and line breaks? We need to preserve the content word-for-word, meaning we should not change any characters of the textual content. We can ignore the tags and just output the text. However, we need to add semantic tags around sections. Thus we need to parse the given snippet and produce: - A headerKEY RESPONSIBILITIES:
- Then a- with each responsibility as
- ... - Then maybe a
- . It didn't say we cannot use other tags, but the instruction says "Use
for introductory paragraphs and general text. Use
for section headers ... Use
- for list items". It doesn't explicitly forbid other tags, but to be safe, we should stick to those tags only. However, we need to preserve the content. The superscript is just formatting; we can represent as "3rd". That's essentially same meaning. I think it's acceptable.
Thus: "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
8. "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
=> "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
9. "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
=> "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
10. "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments"
Note there is a trailing period after the assessments? In the original: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments." So the period is separate but same sentence. So we should include the period: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments."
11. "Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency."
12. "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
=> "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
13. "Query management and ECRM case closure as per set SLA."
Now after responsibilities, we have blank lines (
) then MINIMUM POSITION QUALIFICATION REQUIREMENTS header. Then blank line. Then Academic & Professional subheader. Then blank line. Then a table with Academic & Professional details. We need to preserve the table content exactly (text). The table includes: Header row: Particulars | Detail | Specific Field or Qualification | Need Type Then rows: Education | Bachelor’s Degree | (empty) | RQ Professional Qualifications | (empty) | (empty) | (empty) Master’s Degree | (empty) | (empty) | (empty) Then after table, a paragraph: "Notes:
" => "Notes:" Then "4. Need Types are: RQ = Required, AA = Added Advantage
" => "4. Need Types are: RQ = Required, AA = Added Advantage" Then blank lines. Then "- Experience
KEY RESPONSIBILITIES:
- Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures.
- Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions.
- Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts.
- Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties.
- Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank.
- Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns.
- Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines.
- Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place.
- Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS.
- Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments.
- Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency.
- Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools.
- Query management and ECRM case closure as per set SLA.
for any blank lines? Not needed. Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
ThenAcademic & Professional
Then we need to represent the table. Since we cannot useor inline styles, but we can usewithout style attributes. The rule didn't forbid tables. It only forbade CSS classes, inline styles,
,
. So we can output a plainwith and maybe, but we should keep it simple:
... etc. However, using is okay. The rule didn't forbid . We'll output a table with the exact text. We need to preserve the text exactly, including the header names: "Particulars", "Detail", "Specific Field or Qualification", "Need Type". Then rows. We need to include the empty cells as empty. We also need to include the Notes paragraph and the Need Types paragraph. Thus after the Academic & Professional table, we output: Notes:
4. Need Types are: RQ = Required, AA = Added Advantage
ThenExperience
Then we need to output the table for Total Minimum No of Years’ Experience Required. We can output a simple table with two columns: left cell: "Total Minimum No of Years’ Experience Required", right cell: "4 years". The original had a table with two columns, left wide, right narrow. We'll just output a table. Then the next table for Experience Areas. We'll output a table with header: Detail, Area, Minimum No of Years, Need Type. Rows: Experience Area 1, Branch banking, 1, ES; Experience Area 2, BOU clearing, 3, DE. We must ensure weApply 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 ConciergeLet 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 thereAdd 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.
ECHOYour MJC AssistantI'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
- for list items". It doesn't explicitly forbid other tags, but to be safe, we should stick to those tags only. However, we need to preserve the content. The superscript is just formatting; we can represent as "3rd". That's essentially same meaning. I think it's acceptable.
Thus: "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines."
8. "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
=> "Monitoring instant card printing to ensure timely delivery to branches & compliance to the control processes in place."
9. "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
=> "Close monitoring of BOU running balances to ensure that all accounts are sufficiently funded before approving payments in swift & RTGS."
10. "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments"
Note there is a trailing period after the assessments? In the original: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments." So the period is separate but same sentence. So we should include the period: "Drive a high performance and career development culture through offering leadership, coaching, mentoring and routine staff performance assessments."
11. "Develop and maintain up-to-date procedures and guidelines for processing transactions in the unit and implement initiatives that enhance operational efficiency."
12. "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
=> "Identify, mitigate and report on risks associated with tasks in the unit through appropriate channels & tools."
13. "Query management and ECRM case closure as per set SLA."
Now after responsibilities, we have blank lines (
for any blank lines? Probably ignore blank lines. - Then
MINIMUM POSITION QUALIFICATION REQUIREMENTS
- ThenAcademic & Professional
(note the original had & which is HTML entity for &. We need to preserve that exactly? The original text includes "Academic & Professional". If we output as plain text, we should output "Academic & Professional"? The rule says preserve original content word-for-word. The original content includes the entity &. If we output as plain text, we would change it to &, which is not word-for-word. However, the instruction to not include inline styles may conflict. Usually we would decode entities to plain text. But "preserve ALL original content word-for-word" suggests we should keep the entity as is. But then we would have & in the output, which is okay as it's plain text. However, the output is HTML, so & would be interpreted as an ampersand. If we want to display the literal string "Academic & Professional", we would need to escape it as "Academic & Professional". That's messy. Probably the intention is to keep the readable text, not the HTML entities. So we should convert & to &. Similarly for other entities like & in responsibilities list (e.g., "cheques, EFTs, direct debits & and unpaid"). That should become "cheques, EFTs, direct debits and unpaid". The original had "& and". Actually the text: "cheques, EFTs, direct debits & and unpaid". That seems odd: they likely meant "cheques, EFTs, direct debits and unpaid". The & is an HTML entity for &. So we should output "cheques, EFTs, direct debits and unpaid". Similarly other occurrences. Thus we will decode HTML entities. Now we need to extract all text content from the snippet, preserving order. Let's manually extract. First part: KEY RESPONSIBILITIES: Then list items: 1. "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits & and unpaid) to customer’s accounts as per approved system limits and laid down procedures." We need to decode & to &. So: "Timely & accurate processing inward clearing items (cheques, EFTs, direct debits and unpaid) to customer’s accounts as per approved system limits and laid down procedures." Note there is an apostrophe in customer’s (Unicode right single quote). We'll keep as is. 2. "Monitoring all RTGS transactions on hold and unauthorized transactions to ensure timely completion of transaction exceptions." 3. "Monitoring all Clearing and RTGs reconciliations to ensure timely closure of outstanding items in related suspense accounts." 4. "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties." => "Accurate authorization & remittance of clearing transactions in sybrin and KACH systems to avoid regulatory penalties." 5. "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank." => "Accurate & timely processing of transactions in T24, mobile portals, sybrin, Direct credit engine & Sopra systems to mitigate against frauds and losses to the bank." 6. "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns." => "Timely preparation and submission of both internal & regulatory reports to stakeholders as per set frequency ie NPSM, Telecom returns, operational payment statistics, RCSA & contingency returns." 7. "Ensure timely actioning of URA 3rd party agency notices to avoid regulatory fines." We need to handle the rd tag. The content includes "3rd". We should preserve the text "3rd" maybe? The original includes superscript tags. We should output "3rd". The rule: preserve original content word-for-word. The original includes the markup rd. If we strip it, we change content. But we cannot include tags because they are not allowed? The rule didn't forbid . It only forbids, inline styles, CSS classes,
. It didn't forbid . However, we are supposed to use only,
,
- for list items ... No CSS classes, no inline styles, no
" (non-breaking space) maybe just a blank line. - Then "
" blank. - Then "
" blank. - Then a figure with a table (Academic & Professional details). We need to preserve the table content exactly. The instruction says use
for introductory paragraphs and general text,