Job Description
We need to parse the raw job description and format it as clean semantic HTML per rules. The input is a plain-text job description with HTML tags already embedded (ul, ol, li, p, table, etc.). We need to extract actual job information and return clean HTML. But the instruction says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." So we need to transform the given text into clean HTML following rules.
The provided text includes:
- A list of responsibilities (bullet points)
- Then "MINIMUM POSITION QUALIFICATION REQUIREMENTS" header
- Academic & Professional section with a table
- Experience section with tables
We need to preserve all content word-for-word. So we should output HTML that represents the same structure but in clean semantic form.
Rules:
- Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)
- Use
for introductory paragraphs and general text - Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)
- Use - for list items (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.
So we need to identify sections:
1. Responsibilities (the bullet list) -> use
-
2. Minimum Position Qualification Requirements -> maybe
or ? The example says h4 for section headers. But they gave examples like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we can use for these. However, the original has "MINIMUM POSITION QUALIFICATION REQUIREMENTS" which could be an . Then subsections: Academic & Professional, Experience. Those could be as well.
But careful: The instructions say "Use for section headers". So we should use for all these headers.
Also, the tables need to be represented in semantic HTML. Since we cannot use tables? Actually we can use
, , , , , for tabular data. That's allowed because it's semantic HTML. The rule says no CSS classes, no inline styles, no s, no
tags. Tables are fine. We need to preserve all content word-for-word. So we should convert the tables into proper HTML tables.
But note: The original tables have complex styling attributes; we ignore those and just output clean table markup.
We need to extract the data from the tables. Let's parse each table.
First table under "Academic & Professional":
Rows:
- Education: Bachelor’s degree, Business or another related field, RQ
- Professional Qualifications: Banking, AA
- Master’s degree, Business or another related field, AA
Columns: Particulars, Detail, Specific Field or Qualification, Need Type.
Second table under "Experience":
First table: Total Minimum No of Years’ Experience Required: Team Leadership, Sales, Relationship Management, Credit, and Bank Operations: 10 years.
Then a table with rows:
Detail | Minimum No of Years | Need Type
Experience Area 1 – Sales and Relationship Management: Above 5 years, ES
Experience Area 2 – Credit Skills: Above 5 years, ES
Experience Area 3 - Banking Operations: Above 5 years, ES
Experience Area 4 – Leadership: Above 5 years, ES
Experience Area 5 – Business development track records: Above 3 years, ES
We need to include all this.
Also note there are empty
paragraphs; we can omit them or keep as empty ? Probably we can omit them since they are just spacing. But rule says preserve all original content word-for-word. The
contains a non-breaking space character. Should we include it? It's not meaningful content. I think we can drop them as they are just whitespace. But to be safe, we might include an empty ? However, the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". The
is a paragraph with a non-breaking space. That is content. But it's likely just formatting. In HTML output, we could output without the nbsp. But the instruction says no
tags, but is allowed. I think we can omit empty paragraphs. Usually such cleaning removes empty paragraphs. I'll omit them.
Now, we need to structure the whole thing.
Let's outline:
Responsibilities
- Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth;
... etc.
Then Minimum Position Qualification Requirements
Then Academic & Professional
Particulars Detail Specific Field or Qualification Need Type Education Bachelor’s degree Business or another related field RQ Professional Qualifications Banking Banking AA Master’s degree Business or another related field Business or another related field AA
Then Experience
First table:
Total Minimum No of Years’ Experience Required Team Leadership, Sales, Relationship Management, Credit, and Bank Operations 10 years
But wait, the first table has two columns: left column has label and detail, right column has value. Actually the structure: first cell width 360 contains two elements: one with "Total Minimum No of Years’ Experience Required", then a
with "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations". Second cell width 234 contains a
with "10 years". So it's essentially a two-column table where left column has two lines, right column has one line. We can represent as a table with two columns: first column has two rows (or we can combine). To preserve word-for-word, we could make a table with two columns: first column contains the label and the second column contains the detail. But the original has them as separate paragraphs inside the cell. For semantic HTML, we can make a table with two columns: first column row 1: "Total Minimum No of Years’ Experience Required", second column row 1: "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations". Then a row with only the right column: "10 years". That would be a table with three rows: first row has both cells, second row has only right cell. That's acceptable.
Alternatively, we could use a definition list, but the rule says use
- for lists, but tables are fine. I'll use a table.
Then the second experience table:
Detail Minimum No of Years Need Type Experience Area 1 – Sales and Relationship Management Above 5 years ES Experience Area 2 – Credit Skills Above 5 years ES Experience Area 3 - Banking Operations Above 5 years ES Experience Area 4 – Leadership Above 5 years ES Experience Area 5 – Business development track records Above 3 years ES
Note: There is also a footnote reference [1] and [2] in the Need Type cells. They are part of the original content. We should preserve them. In the first table, the Need Type cell for Education row has "[1]" superscript. In the second table, the Need Type cells have "[2]". We need to include them as superscript or just as text. Since we are preserving word-for-word, we can include them as [1] or just plain text. The original had [1]. I'll include them as plain text or as tags. Since we are writing clean HTML, we can use tags. But the rule doesn't forbid . It's semantic. I'll use [1] and [2].
Also note the "&" in "Academic & Professional" should be "&" in HTML to represent ampersand. So we write "Academic & Professional".
Similarly, " " we drop.
Now, about the heading levels: The examples say use for section headers. So we will use for all these.
But what about the top-level title? The job description doesn't have a title or company name explicitly. It starts with responsibilities. So maybe the job title is missing. We should not invent. Just output what's given.
Thus final HTML:
Responsibilities
- Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth;
- Manage the branch retail’s liability and assets portfolios with the ultimate aim of ensuring that it remains profitable, competitive and promptly reacts to the changes in both the internal and external environment;
- Drive a sales culture within the branch staff with the ultimate aim of growing the NFI, products per customer, share of wallet, quality customer base and at the same time ensure staff productivity.
- Oversee the branch operations in order to ensure superior service offering to all bank’s customers, reduction of operating costs through an efficient utilization of Bank’s resources and prevention of frauds & losses through implementation of first-class corporate governance and compliance with bank’s policies, procedures and processes
- Monitor and manage customer complaints, constantly review service delivery standards and manage branch human resources in a way, which ensures maintenance of the highest service standards.
- Coach, mentor and develop a high performing team and ensure an effective performance management framework;
- Ensure effective migration of customers to electronic business channels through promoting channels usage (Mobile Banking, Internet Banking and Cards) and a high performance of branch alternative channels such as Agency Banking and Merchant Business
- Ensure that branch processes are within agreed TAT in order to live customer satisfaction.
Minimum Position Qualification Requirements
Academic & Professional
Particulars Detail Specific Field or Qualification Need Type Education Bachelor’s degree Business or another related field RQ[1] Professional Qualifications Banking Banking AA Master’s degree Business or another related field Business or another related field AA
Experience
Total Minimum No of Years’ Experience Required Team Leadership, Sales, Relationship Management, Credit, and Bank Operations 10 years
Detail Minimum No of Years Need Type Experience Area 1 – Sales and Relationship Management Above 5 years ES[2] Experience Area 2 – Credit Skills Above 5 years ES Experience Area 3 - Banking Operations Above 5 years ES Experience Area 4 – Leadership Above 5 years ES Experience Area 5 – Business development track records Above 3 years ES
Check: The first experience table: The original had a table with two columns: left column had two paragraphs, right column had one paragraph. Our representation uses a table with two columns: first column has two rows (label and detail), second column has one row (value). That preserves the content.
But note: The original first experience table had a header row? Actually looking at the HTML: The first table under Experience has a single row with three cells? Wait, let's examine the raw HTML:
Total Minimum No of Years’ Experience Required
Team Leadership, Sales, Relationship Management, Credit, and Bank Operations
10 years
So it's a single row with two cells. The first cell contains three paragraphs: label, empty, detail. The second cell contains two paragraphs: empty, value. So effectively, the label and detail are stacked vertically within the first cell, and the value is stacked below the empty paragraph in the second cell. So our representation as a table with two columns and three rows (first row: both cells, second row: only right cell) is accurate.
But we need to ensure we don't lose the empty paragraphs. They are just spacing. I think it's fine to omit them.
Now, check for any other content: The original had "MINIMUM POSITION QUALIFICATION REQUIREMENTS" as a heading. We used . Good.
Also, the original had "Academic & Professional" and "Experience" as subheadings. We used for each.
All good.
One more thing: The bullet list items end with semicolons or periods. We keep them as is.
Also note the " " at the end of some items: we can keep them as ? But the rule says no inline styles, but is an entity, not a style. It's okay to keep to preserve the non-breaking space. However, the instruction says "No CSS classes, no inline styles, no s, no
tags". is not a tag, it's an entity. It's fine. But we might want to keep them to preserve exact content. I'll include where present.
In the first bullet: "...ensure sustainable business growth;" no nbsp.
Second: "...environment;" no nbsp.
Third: "...staff productivity. " has nbsp.
Fourth: "...processes " has nbsp.
Fifth: "...service standards. " has nbsp.
Sixth: "...framework;" no nbsp.
Seventh: "...Merchant Business " has nbsp.
Eighth: "...satisfaction
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.
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 - 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. So we need to identify sections: 1. Responsibilities (the bullet list) -> use
-
2. Minimum Position Qualification Requirements -> maybe
or
? The example says h4 for section headers. But they gave examples like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we can use
for these. However, the original has "MINIMUM POSITION QUALIFICATION REQUIREMENTS" which could be an
. Then subsections: Academic & Professional, Experience. Those could be
as well. But careful: The instructions say "Use
for section headers". So we should use
for all these headers. Also, the tables need to be represented in semantic HTML. Since we cannot use tables? Actually we can use
, , ,
, , for tabular data. That's allowed because it's semantic HTML. The rule says no CSS classes, no inline styles, no s, no
tags. Tables are fine. We need to preserve all content word-for-word. So we should convert the tables into proper HTML tables. But note: The original tables have complex styling attributes; we ignore those and just output clean table markup. We need to extract the data from the tables. Let's parse each table. First table under "Academic & Professional": Rows: - Education: Bachelor’s degree, Business or another related field, RQ - Professional Qualifications: Banking, AA - Master’s degree, Business or another related field, AA Columns: Particulars, Detail, Specific Field or Qualification, Need Type. Second table under "Experience": First table: Total Minimum No of Years’ Experience Required: Team Leadership, Sales, Relationship Management, Credit, and Bank Operations: 10 years. Then a table with rows: Detail | Minimum No of Years | Need Type Experience Area 1 – Sales and Relationship Management: Above 5 years, ES Experience Area 2 – Credit Skills: Above 5 years, ES Experience Area 3 - Banking Operations: Above 5 years, ES Experience Area 4 – Leadership: Above 5 years, ES Experience Area 5 – Business development track records: Above 3 years, ES We need to include all this. Also note there are empty
paragraphs; we can omit them or keep as empty ? Probably we can omit them since they are just spacing. But rule says preserve all original content word-for-word. The
contains a non-breaking space character. Should we include it? It's not meaningful content. I think we can drop them as they are just whitespace. But to be safe, we might include an empty ? However, the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". The
is a paragraph with a non-breaking space. That is content. But it's likely just formatting. In HTML output, we could output without the nbsp. But the instruction says no
tags, butis allowed. I think we can omit empty paragraphs. Usually such cleaning removes empty paragraphs. I'll omit them. Now, we need to structure the whole thing. Let's outline:
Responsibilities
- Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth; ... etc.
Minimum Position Qualification Requirements
ThenAcademic & Professional
ThenParticulars Detail Specific Field or Qualification Need Type Education Bachelor’s degree Business or another related field RQ Professional Qualifications Banking Banking AA Master’s degree Business or another related field Business or another related field AA Experience
First table:
But wait, the first table has two columns: left column has label and detail, right column has value. Actually the structure: first cell width 360 contains twoTotal Minimum No of Years’ Experience Required Team Leadership, Sales, Relationship Management, Credit, and Bank Operations 10 years elements: one with "Total Minimum No of Years’ Experience Required", then a
with "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations". Second cell width 234 contains a
with "10 years". So it's essentially a two-column table where left column has two lines, right column has one line. We can represent as a table with two columns: first column has two rows (or we can combine). To preserve word-for-word, we could make a table with two columns: first column contains the label and the second column contains the detail. But the original has them as separate paragraphs inside the cell. For semantic HTML, we can make a table with two columns: first column row 1: "Total Minimum No of Years’ Experience Required", second column row 1: "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations". Then a row with only the right column: "10 years". That would be a table with three rows: first row has both cells, second row has only right cell. That's acceptable. Alternatively, we could use a definition list, but the rule says use
- for lists, but tables are fine. I'll use a table.
Then the second experience table:
Note: There is also a footnote reference [1] and [2] in the Need Type cells. They are part of the original content. We should preserve them. In the first table, the Need Type cell for Education row has "[1]" superscript. In the second table, the Need Type cells have "[2]". We need to include them as superscript or just as text. Since we are preserving word-for-word, we can include them as [1] or just plain text. The original had [1]. I'll include them as plain text or as tags. Since we are writing clean HTML, we can use tags. But the rule doesn't forbid . It's semantic. I'll use [1] and [2]. Also note the "&" in "Academic & Professional" should be "&" in HTML to represent ampersand. So we write "Academic & Professional". Similarly, " " we drop. Now, about the heading levels: The examples say useDetail Minimum No of Years Need Type Experience Area 1 – Sales and Relationship Management Above 5 years ES Experience Area 2 – Credit Skills Above 5 years ES Experience Area 3 - Banking Operations Above 5 years ES Experience Area 4 – Leadership Above 5 years ES Experience Area 5 – Business development track records Above 3 years ES for section headers. So we will use
for all these. But what about the top-level title? The job description doesn't have a title or company name explicitly. It starts with responsibilities. So maybe the job title is missing. We should not invent. Just output what's given. Thus final HTML:
Responsibilities
- Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth;
- Manage the branch retail’s liability and assets portfolios with the ultimate aim of ensuring that it remains profitable, competitive and promptly reacts to the changes in both the internal and external environment;
- Drive a sales culture within the branch staff with the ultimate aim of growing the NFI, products per customer, share of wallet, quality customer base and at the same time ensure staff productivity.
- Oversee the branch operations in order to ensure superior service offering to all bank’s customers, reduction of operating costs through an efficient utilization of Bank’s resources and prevention of frauds & losses through implementation of first-class corporate governance and compliance with bank’s policies, procedures and processes
- Monitor and manage customer complaints, constantly review service delivery standards and manage branch human resources in a way, which ensures maintenance of the highest service standards.
- Coach, mentor and develop a high performing team and ensure an effective performance management framework;
- Ensure effective migration of customers to electronic business channels through promoting channels usage (Mobile Banking, Internet Banking and Cards) and a high performance of branch alternative channels such as Agency Banking and Merchant Business
- Ensure that branch processes are within agreed TAT in order to live customer satisfaction.
Minimum Position Qualification Requirements
Academic & Professional
Particulars Detail Specific Field or Qualification Need Type Education Bachelor’s degree Business or another related field RQ[1] Professional Qualifications Banking Banking AA Master’s degree Business or another related field Business or another related field AA Experience
Total Minimum No of Years’ Experience Required Team Leadership, Sales, Relationship Management, Credit, and Bank Operations 10 years
Check: The first experience table: The original had a table with two columns: left column had two paragraphs, right column had one paragraph. Our representation uses a table with two columns: first column has two rows (label and detail), second column has one row (value). That preserves the content. But note: The original first experience table had a header row? Actually looking at the HTML: The first table under Experience has a single row with three cells? Wait, let's examine the raw HTML:Detail Minimum No of Years Need Type Experience Area 1 – Sales and Relationship Management Above 5 years ES[2] Experience Area 2 – Credit Skills Above 5 years ES Experience Area 3 - Banking Operations Above 5 years ES Experience Area 4 – Leadership Above 5 years ES Experience Area 5 – Business development track records Above 3 years ES So it's a single row with two cells. The first cell contains three paragraphs: label, empty, detail. The second cell contains two paragraphs: empty, value. So effectively, the label and detail are stacked vertically within the first cell, and the value is stacked below the empty paragraph in the second cell. So our representation as a table with two columns and three rows (first row: both cells, second row: only right cell) is accurate. But we need to ensure we don't lose the empty paragraphs. They are just spacing. I think it's fine to omit them. Now, check for any other content: The original had "MINIMUM POSITION QUALIFICATION REQUIREMENTS" as a heading. We usedTotal Minimum No of Years’ Experience Required
Team Leadership, Sales, Relationship Management, Credit, and Bank Operations
10 years
. Good. Also, the original had "Academic & Professional" and "Experience" as subheadings. We used
for each. All good. One more thing: The bullet list items end with semicolons or periods. We keep them as is. Also note the " " at the end of some items: we can keep them as ? But the rule says no inline styles, but is an entity, not a style. It's okay to keep to preserve the non-breaking space. However, the instruction says "No CSS classes, no inline styles, no
s, no
tags". is not a tag, it's an entity. It's fine. But we might want to keep them to preserve exact content. I'll include where present. In the first bullet: "...ensure sustainable business growth;" no nbsp. Second: "...environment;" no nbsp. Third: "...staff productivity. " has nbsp. Fourth: "...processes " has nbsp. Fifth: "...service standards. " has nbsp. Sixth: "...framework;" no nbsp. Seventh: "...Merchant Business " has nbsp. Eighth: "...satisfaction
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 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.