Job Description
for intro paragraphs and general text. Use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items (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 HTML.
We need to parse the given job description text (which includes HTML tags originally). We must output cleaned HTML with only allowed tags.
We must preserve content exactly as given, but we can reformat using allowed tags. Must not add or remove any text. Must keep original wording, punctuation, etc.
We need to identify sections: The original includes:
Why Airtel Africa?
At Airtel Africa, we act with passion, energy, and a can-do attitude. Innovation with an entrepreneurial spirit drive us. If you like “ordinary”, then we are not for you.
We champion diversity. We anticipate, adapt, and deliver solutions that enrich the lives of communities we serve. we roll up our sleeves to win with our customers.
By choosing Airtel, you choose to be part of a winning team. All this in addition to a brilliant opportunity to build a career in your field of expertise, across our different operating companies in Africa.
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Then Must have:
...
Then Skills critical to the role:
...
Then Purpose of the Job
Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner.
...
We need to convert to semantic HTML: Use for section headers. Which sections? "Why Airtel Africa?" maybe a header. Then "Must have:" maybe a header? Actually "Must have:" is a header for qualifications. "Skills critical to the role:" maybe a header for skills. "Purpose of the Job" maybe a header for responsibilities.
We need to decide which headers correspond to allowed list: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we can map:
- "Why Airtel Africa?" maybe "About the Role" or introductory. Could treat as About the Role
but we must preserve original content word-for-word. We cannot change the text. So we must keep "Why Airtel Africa?" exactly. But we can wrap it in tags? The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says use for section headers (e.g. those). It doesn't forbid using for other headers? It says use for section headers (e.g. Responsibilities, Qualifications...). Likely they expect we use for any section header we identify. So we can wrap "Why Airtel Africa?" in . That's okay as it's a section header.
Similarly "Airtel Africa is proud to be an equal opportunity employer..." maybe also a header? It's a statement; could be part of intro. Might be better to keep as
. But it's inside a . We could keep as with . However rule says preserve all original content word-for-word. So we must keep the exact text, including the tags? Actually we are to output HTML, we can replace the original markup with our own semantic HTML but must keep the text content unchanged. The original had tags; we can drop them if we replace with or
but we must keep the text inside. The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we cannot remove any characters from the original text. If we drop the tags, we are removing markup but not text content. The text content remains same. Is that allowed? Usually they mean the visible text content, not the markup. Since we are converting to clean HTML, we can change markup as long as we keep the textual content exactly. So we can drop , , etc. as long as we keep the words.
Thus we need to output something like:
Why Airtel Africa?
At Airtel Africa, we act with passion, energy, and a can-do attitude. Innovation with an entrepreneurial spirit drive us. If you like “ordinary”, then we are not for you.
We champion diversity. We anticipate, adapt, and deliver solutions that enrich the lives of communities we serve. we roll up our sleeves to win with our customers.
By choosing Airtel, you choose to be part of a winning team. All this in addition to a brilliant opportunity to build a career in your field of expertise, across our different operating companies in Africa.
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Then we have "Must have:" section. That is a header for qualifications. So:
Must have:
- Degree in IT, Computer Science or any other related field
- Post graduate in Data systems & Analysis
- 3 years working experience in related field
Note: original had after colon and after items. We need to preserve spaces? The text includes non-breaking spaces. We should keep them as spaces? Probably we can keep as regular spaces. The original text: "Must have: " includes a non-breaking space after colon. In output we can just have a normal space after colon? Might be considered altering content. Safer to keep the as is? But we are not allowed to add or remove characters. If we replace with a regular space, we are changing the character entity. That's a change. However the instruction likely expects we ignore HTML entities and just output plain text. Usually they'd accept normal spaces. But to be safe, we could keep the as is inside the text. However if we wrap in Must have:
that includes the entity. That's okay; we are preserving it. Similarly for list items: they have trailing after each item. We should preserve those.
Thus we need to keep the exact strings including entities.
Let's extract exact strings from original:
Original snippet:
Must have:
- Degree in IT, Computer Science or any other related field
- Post graduate in Data systems & Analysis
- 3 years working experience in related field
Note: first two items have no trailing ? Actually they have no . The third has before . Also the first line "Must have: " includes after colon.
Similarly skills section:
Skills critical to the role:
- Strong analytical, technical and reporting skills
- Proficient in querying a large amount of data using SQL queries
- In-depth knowledge of GSM Networks, IN and IT Billing & Provisioning Systems
- Good understanding of data models and various IT platforms/solutions
- Should be able to work and deliver under pressure and squeezed timelines
- Take ownership for the work assigned and have good follow-through skills
- Ability to consistently deliver accurate results on-time and hold others accountable
- Demonstrate ability to work in an ambiguous and fast paced environment
- Ability to successfully engage in multiple initiatives and manage multiple priorities
- Exceptional eye for details
- Ability to work effectively in a team environment as well as individually
- Quick learner to develop strong product knowledge and entire product lifecycle
- Build strong relationships in a matrix environment to help negotiate priorities and to resolve conflicts among project stakeholders
- Should be able to do risk analysis and document the business requirements and formulate the business processes
- Project management and planning skills
- High integrity is mandatory
Note: first item "Skills critical to the role: " includes after colon.
Purpose of the Job section:
Purpose of the Job
Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner.
- Maintain high levels of compliance above 95% for Airtel Money
- Implement, review, modify and manage Revenue Assurance SOPs & RA Manuals to cover emerging risks and better management of existing risks
- Roll out Group wide initiatives
- Project management for major system launches to do comprehensive risk analysis and ensure First Time Right
- Access knowledge base and key learning’s from across OpCos, standards UAT templates and already implemented processes for compliance
- Detect and plug revenue leakages
- Identify missed revenue opportunities
- Continuous review of service paths and revenue paths and contribute to evolve RA control environment to cover emerging risks and minimise the existing leakages
- Liaise with CFT to understand the complete architecture, end to end service path and revenue path, do risk analysis and formulate and perform UAT cases
- Highlight to business the emerging risks and liaise with CFT to develop new control environment (primary as well as secondary) to mitigate the same
- Develop relevant functional and technical RA skills and improve on the control environment by proactively reviewing the current control universe.
- Close loop with CFT for fast closure of issues
- Escalate appropriately when required through proper hierarchy
- Take ownership to get issues closed
- Ensure proper and correct RCA
- Provide weekly/monthly reports in a timely manner as required by business and Group RAFM
- Report on all revenue loss incidents to management
- Should strictly be satisfactory or above
- Any other reports that may arise
Note: first paragraph includes "Responsible for " with after for. Also first list item has trailing after "Money". Also note there’s an apostrophe in “key learning’s” (weird). We must preserve that exactly.
Also earlier intro sections had and
etc. We need to preserve those? We are to remove
tags and ? The rule says remove stray numbers or formatting artifacts. is a formatting artifact; we should remove it? It says "Remove all of the following: ... Stray numbers or formatting artifacts". is a formatting artifact (non-breaking space). So we should remove entities. Also
tags should be removed. Also we should remove empty divs etc. So we should strip out and
. However we must preserve the textual content; removing just removes a space character but we can replace with a normal space? The rule says remove formatting artifacts, so we can delete them. That likely means we should not keep in output. Similarly we should not keep
. So we need to produce HTML without those entities.
Thus we need to extract the plain text content, ignoring original markup, and then wrap in appropriate tags.
Thus we need to produce:
Why Airtel Africa?
At Airtel Africa, we act with passion, energy, and a can-do attitude. Innovation with an entrepreneurial spirit drive us. If you like “ordinary”, then we are not for you.
We champion diversity. We anticipate, adapt, and deliver solutions that enrich the lives of communities we serve. we roll up our sleeves to win with our customers.
By choosing Airtel, you choose to be part of a winning team. All this in addition to a brilliant opportunity to build a career in your field of expertise, across our different operating companies in Africa.
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Then qualifications:
Must have:
- Degree in IT, Computer Science or any other related field
- Post graduate in Data systems & Analysis
- 3 years working experience in related field
Note: we need to keep the "&" as it's part of the text "Data systems & Analysis". The original had & which is an HTML entity for &. We should preserve the ampersand character? The text originally had & which renders as &. If we output plain "&" that's same meaning. But to be safe we can keep & as it's part of the text. However the rule says remove formatting artifacts; & is also an HTML entity. Might be considered formatting artifact. But it's part of the actual phrase "Data systems & Analysis". If we remove the & we lose the ampersand. Better to output the ampersand character "&". That's preserving the meaning. The original text had & which is an entity; converting to & is still same character. I think it's fine.
Similarly other & in "SOPs & RA Manuals". We'll output "&".
Now skills section:
Skills critical to the role:
- Strong analytical, technical and reporting skills
- Proficient in querying a large amount of data using SQL queries
- In-depth knowledge of GSM Networks, IN and IT Billing & Provisioning Systems
- Good understanding of data models and various IT platforms/solutions
- Should be able to work and deliver under pressure and squeezed timelines
- Take ownership for the work assigned and have good follow-through skills
- Ability to consistently deliver accurate results on-time and hold others accountable
- Demonstrate ability to work in an ambiguous and fast paced environment
- Ability to successfully engage in multiple initiatives and manage multiple priorities
- Exceptional eye for details
- Ability to work effectively in a team environment as well as individually
- Quick learner to develop strong product knowledge and entire product lifecycle
- Build strong relationships in a matrix environment to help negotiate priorities and to resolve conflicts among project stakeholders
- Should be able to do risk analysis and document the business requirements and formulate the business processes
- Project management and planning skills
- High integrity is mandatory
Now purpose of job (responsibilities):
Purpose of the Job
Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner.
- Maintain high levels of compliance above 95% for Airtel Money
- Implement, review, modify and manage Revenue Assurance SOPs & RA Manuals to cover emerging risks and better management of existing risks
- Roll out
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 HTML. We need to parse the given job description text (which includes HTML tags originally). We must output cleaned HTML with only allowed tags. We must preserve content exactly as given, but we can reformat using allowed tags. Must not add or remove any text. Must keep original wording, punctuation, etc. We need to identify sections: The original includes:
Must have:
- ...
Skills critical to the role:
- ...
Purpose of the Job
Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner.
- ...
for section headers. Which sections? "Why Airtel Africa?" maybe a header. Then "Must have:" maybe a header? Actually "Must have:" is a header for qualifications. "Skills critical to the role:" maybe a header for skills. "Purpose of the Job" maybe a header for responsibilities.
We need to decide which headers correspond to allowed list: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we can map:
- "Why Airtel Africa?" maybe "About the Role" or introductory. Could treat as About the Role
but we must preserve original content word-for-word. We cannot change the text. So we must keep "Why Airtel Africa?" exactly. But we can wrap it in tags? The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says use for section headers (e.g. those). It doesn't forbid using for other headers? It says use for section headers (e.g. Responsibilities, Qualifications...). Likely they expect we use for any section header we identify. So we can wrap "Why Airtel Africa?" in . That's okay as it's a section header.
Similarly "Airtel Africa is proud to be an equal opportunity employer..." maybe also a header? It's a statement; could be part of intro. Might be better to keep as
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says use for section headers (e.g. those). It doesn't forbid using for other headers? It says use for section headers (e.g. Responsibilities, Qualifications...). Likely they expect we use for any section header we identify. So we can wrap "Why Airtel Africa?" in . That's okay as it's a section header.
Similarly "Airtel Africa is proud to be an equal opportunity employer..." maybe also a header? It's a statement; could be part of intro. Might be better to keep as
for other headers? It says use for section headers (e.g. Responsibilities, Qualifications...). Likely they expect we use for any section header we identify. So we can wrap "Why Airtel Africa?" in . That's okay as it's a section header.
Similarly "Airtel Africa is proud to be an equal opportunity employer..." maybe also a header? It's a statement; could be part of intro. Might be better to keep as
for any section header we identify. So we can wrap "Why Airtel Africa?" in . That's okay as it's a section header.
Similarly "Airtel Africa is proud to be an equal opportunity employer..." maybe also a header? It's a statement; could be part of intro. Might be better to keep as
. But it's inside a . We could keep as with . However rule says preserve all original content word-for-word. So we must keep the exact text, including the tags? Actually we are to output HTML, we can replace the original markup with our own semantic HTML but must keep the text content unchanged. The original had tags; we can drop them if we replace with but we must keep the text inside. The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we cannot remove any characters from the original text. If we drop the tags, we are removing markup but not text content. The text content remains same. Is that allowed? Usually they mean the visible text content, not the markup. Since we are converting to clean HTML, we can change markup as long as we keep the textual content exactly. So we can drop , , etc. as long as we keep the words.
Thus we need to output something like:
At Airtel Africa, we act with passion, energy, and a can-do attitude. Innovation with an entrepreneurial spirit drive us. If you like “ordinary”, then we are not for you. We champion diversity. We anticipate, adapt, and deliver solutions that enrich the lives of communities we serve. we roll up our sleeves to win with our customers. By choosing Airtel, you choose to be part of a winning team. All this in addition to a brilliant opportunity to build a career in your field of expertise, across our different operating companies in Africa. Must have: Skills critical to the role: Purpose of the Job Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner. At Airtel Africa, we act with passion, energy, and a can-do attitude. Innovation with an entrepreneurial spirit drive us. If you like “ordinary”, then we are not for you. We champion diversity. We anticipate, adapt, and deliver solutions that enrich the lives of communities we serve. we roll up our sleeves to win with our customers. By choosing Airtel, you choose to be part of a winning team. All this in addition to a brilliant opportunity to build a career in your field of expertise, across our different operating companies in Africa. Responsible for Performing and managing all internal controls for Airtel Money to ensure mitigation of revenue leakages, revenue exposure, fraud, errors and omissions. Institutionalize best in class RA processes in line with Group RAFM Governance Guidelines to achieve high levels of compliance, cash benefits by stopping revenue leakages and identifying missed revenue opportunities. Detect, report, close and take proactive steps to prevent further occurrence of issues by closely liaising with CFT strictly in a time-bound manner. or
Why Airtel Africa?
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Then we have "Must have:" section. That is a header for qualifications. So:
Must have:
Note: original had after colon and after items. We need to preserve spaces? The text includes non-breaking spaces. We should keep them as spaces? Probably we can keep as regular spaces. The original text: "Must have: " includes a non-breaking space after colon. In output we can just have a normal space after colon? Might be considered altering content. Safer to keep the as is? But we are not allowed to add or remove characters. If we replace with a regular space, we are changing the character entity. That's a change. However the instruction likely expects we ignore HTML entities and just output plain text. Usually they'd accept normal spaces. But to be safe, we could keep the as is inside the text. However if we wrap in Must have:
that includes the entity. That's okay; we are preserving it. Similarly for list items: they have trailing after each item. We should preserve those.
Thus we need to keep the exact strings including entities.
Let's extract exact strings from original:
Original snippet:
Note: first two items have no trailing ? Actually they have no . The third has before . Also the first line "Must have: " includes after colon.
Similarly skills section:
Note: first item "Skills critical to the role: " includes after colon.
Purpose of the Job section:
Note: first paragraph includes "Responsible for " with after for. Also first list item has trailing after "Money". Also note there’s an apostrophe in “key learning’s” (weird). We must preserve that exactly.
Also earlier intro sections had and
etc. We need to preserve those? We are to remove
tags and ? The rule says remove stray numbers or formatting artifacts. is a formatting artifact; we should remove it? It says "Remove all of the following: ... Stray numbers or formatting artifacts". is a formatting artifact (non-breaking space). So we should remove entities. Also
tags should be removed. Also we should remove empty divs etc. So we should strip out and
. However we must preserve the textual content; removing just removes a space character but we can replace with a normal space? The rule says remove formatting artifacts, so we can delete them. That likely means we should not keep in output. Similarly we should not keep
. So we need to produce HTML without those entities.
Thus we need to extract the plain text content, ignoring original markup, and then wrap in appropriate tags.
Thus we need to produce:
Why Airtel Africa?
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Then qualifications:
Must have:
Note: we need to keep the "&" as it's part of the text "Data systems & Analysis". The original had & which is an HTML entity for &. We should preserve the ampersand character? The text originally had & which renders as &. If we output plain "&" that's same meaning. But to be safe we can keep & as it's part of the text. However the rule says remove formatting artifacts; & is also an HTML entity. Might be considered formatting artifact. But it's part of the actual phrase "Data systems & Analysis". If we remove the & we lose the ampersand. Better to output the ampersand character "&". That's preserving the meaning. The original text had & which is an entity; converting to & is still same character. I think it's fine.
Similarly other & in "SOPs & RA Manuals". We'll output "&".
Now skills section:
Skills critical to the role:
Now purpose of job (responsibilities):
Purpose of the Job
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 📝Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.