Job Description
for intro paragraphs,
for section headers, - for list items. No CSS classes, no inline styles, no , no
. Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. Must not add commentary. Must output only HTML.
We have raw text with some HTML tags originally. We need to extract content and format accordingly.
Let's parse the given job description:
Original snippet:
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.
Must have:
- Bachelor's degree in business, sales, or equivalent training in business or sales management.
- Strong computer literacy with proficiency in MS office and other business applications.
- Excellent communication, influencing, and negotiation skills, with the ability to build and maintain strong customer relationships.
- Minimum 2 years of proven sales experience in the telecommunications or fast-moving consumer goods (FMCG) industry.
- Demonstrated commitment to delivering exceptional customer service and creating positive customer experiences
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
- Develop and maintain strong, long-term relationships with corporate clients, serving as their primary point of contact.
- Conduct regular client meetings to understand business needs, gather feedback, and identify opportunities for service improvement.
- Ensure high levels of client satisfaction by addressing queries, concerns, and service issues promptly.
- Achieve monthly, quarterly, and annual sales targets through the acquisition of new clients and the retention and expansion of existing accounts.
- Identify and pursue upselling and cross-selling opportunities for Airtel Business products and services, including data solutions, internet services, managed services, and IoT solutions.
- Prepare and present tailored product proposals, quotations, and presentations to clients based on their unique business requirements.
- Develop and implement account strategies in line with Airtel Business’s Go-To-Market plan to maximize revenue potential.
- Work closely with the marketing and product teams to develop campaigns and initiatives targeting the corporate segment.
- Pipeline and sales activity management.
We need to produce HTML with for intro paragraphs and general text,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items.
We must preserve all original content word-for-word. So we cannot change wording, but we can wrap in tags.
We need to decide sections: The content includes:
- Intro: "Why Airtel Africa?" (strong) then paragraphs about Airtel Africa, then equal opportunity statement.
- Then "Must have:" paragraph (already
Must have:
) then list of requirements.
- Then a paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." (with after period). Then list of responsibilities/duties.
Thus we can treat sections: maybe "About the Role" for intro, "Requirements" for Must have list, "Responsibilities" for the second list.
But we must use for section headers. We need to decide appropriate header names based on content. The instruction says: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we can pick those that match.
We have:
- Intro paragraphs: could be under About the Role
(or maybe no header if not clear sections? But we have clear sections: requirements and responsibilities). The intro could be considered "About the Role". We'll wrap intro paragraphs in
tags under that header.
- Then
Requirements
(or Qualifications). The "Must have:" paragraph is introductory to the list; we could keep that as a then list.
- Then
Responsibilities
(or Key Duties). The paragraph before list: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." That's an intro to responsibilities. Then list.
We must preserve all original content word-for-word, including the " " spaces. In HTML, is an entity; we can keep it as is. The instruction says preserve all original content word-for-word, do not add, remove, summarise, or rephrase. So we must keep the exact text, including entities. However, we cannot use
tags. The original had
and for spacing; we must keep them? The instruction says preserve all original content word-for-word. But also says: Use for introductory paragraphs and general text,
- for list items. No CSS classes, no inline styles, no s, no
tags. So we must not use
tags. However, we must preserve original content word-for-word. There's a conflict: if we remove
tags, we are not preserving original content exactly. But the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Yet also says "No ...
tags". So we need to interpret: we should not include
tags in output, but we must keep the textual content, ignoring the
tags as formatting artifacts that we can remove? The earlier instruction in the first part said to remove stray numbers or formatting artifacts. Here they explicitly say no
tags. So we should strip out
tags and maybe? But is a character entity representing a non-breaking space; it's part of content. If we remove it, we are altering content. However, we could keep as is; it's not a tag. The instruction says no
tags, but is okay. So we should keep entities.
Thus we need to strip out
tags but keep .
Also we need to strip out tags and tags? The instruction says no s, but we can keep ? It didn't forbid . It said use for introductory paragraphs and general text,
for section headers, - for list items. No CSS classes, no inline styles, no s, no
tags. It didn't say we cannot use other tags like . However, to keep semantic HTML, we could keep for emphasis. But the instruction says "Preserve ALL original content word-for-word". If we keep tags, we are preserving them. That's okay. However, the earlier part said to remove author bylines etc. Not relevant.
Thus we can keep tags as they are.
But we need to wrap paragraphs in tags. The original had
tags around paragraphs. We'll replace those with tags, preserving the inner content (including etc). Also we need to handle the Must have:
already present; we can keep it as is (it's already a ). The list items are already in
- . We'll keep them.
We also need to add
headers for sections. Where to place them? We'll insert About the Role
before the intro paragraphs. Then Requirements
before the "Must have:" paragraph and list. Then Responsibilities
before the paragraph about She/He and the second list.
We must ensure we don't duplicate content. We'll output:
About the Role
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 Requirements
Must have:
- Bachelor's degree in business, sales, or equivalent training in business or sales management.
- Strong computer literacy with proficiency in MS office and other business applications.
- Excellent communication, influencing, and negotiation skills, with the ability to build and maintain strong customer relationships.
- Minimum 2 years of proven sales experience in the telecommunications or fast-moving consumer goods (FMCG) industry.
- Demonstrated commitment to delivering exceptional customer service and creating positive customer experiences
Then Responsibilities
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
- Develop and maintain strong, long-term relationships with corporate clients, serving as their primary point of contact.
- Conduct regular client meetings to understand business needs, gather feedback, and identify opportunities for service improvement.
- Ensure high levels of client satisfaction by addressing queries, concerns, and service issues promptly.
- Achieve monthly, quarterly, and annual sales targets through the acquisition of new clients and the retention and expansion of existing accounts.
- Identify and pursue upselling and cross-selling opportunities for Airtel Business products and services, including data solutions, internet services, managed services, and IoT solutions.
- Prepare and present tailored product proposals, quotations, and presentations to clients based on their unique business requirements.
- Develop and implement account strategies in line with Airtel Business’s Go-To-Market plan to maximize revenue potential.
- Work closely with the marketing and product teams to develop campaigns and initiatives targeting the corporate segment.
- Pipeline and sales activity management.
We need to ensure we kept all original content word-for-word. Let's verify:
Original intro paragraphs:
- Why Airtel Africa? => we have Why Airtel Africa?
(good)
-
=> we omitted this entirely (it was just blank line with spaces). Should we preserve? It's formatting artifact; we can drop as per instruction to remove stray numbers or formatting artifacts. The instruction says remove stray numbers or formatting artifacts. So we can drop empty divs.
- 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 have 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.
Note we removed the leading (non-breaking space) before the sentence. That is a formatting artifact; we removed it. Is that allowed? The instruction says preserve ALL original content word-for-word. The is a character entity; removing it changes content. However, the earlier instruction said to remove stray numbers or formatting artifacts. could be considered a formatting artifact (non-breaking space). The instruction in this part says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That's contradictory with earlier. But the overarching task: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The given input includes HTML tags. We need to output clean semantic HTML. 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. If text has no clear sections, just wrap paragraphs in tags. Return ONLY the HTML.
Thus we must keep the exact textual content, including any entities, but we cannot use
tags. However, we can keep as is. The leading before the sentence is part of the text node; we should keep it. But we removed it. We need to keep it.
Similarly, there is a trailing after the period in the responsibilities paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment. " We kept that after the period inside the
. Good.
Also there is a
with
after the intro paragraphs; we omitted that entirely. That div contains only a line break and a non-breaking space; it's basically whitespace. If we remove it, we are removing content (the ). But maybe it's considered formatting artifact and can be removed. The instruction says preserve ALL original content word-for-word. However, the earlier part said to remove stray numbers or formatting artifacts. The is a formatting artifact (non-breaking space). I'd lean to keep it if it's not inside a visible text? But it's just a space; preserving it won't affect visual output much. However, to strictly follow "preserve ALL original content word-for-word", we should keep it. But we cannot use
tags, but we can keep . The div containing
: we could replace the div with a containing ? But that would be a paragraph with just a non-breaking space, which is odd. Better to just keep the as a text node somewhere? But we cannot have free text not inside a tag? We could wrap it in a
but that would add a paragraph that is just a space. That might be considered adding structure but not adding content. The instruction says do not add, remove, summarise, or rephrase. Adding a
tag is adding markup, but we are allowed to add tags for formatting as per rules. The original had a
with
. We are replacing that with nothing? That's removing content (the and
tags). But we are allowed to remove tags? The instruction says preserve ALL original content word-for-word. Does that refer to textual content only, not markup? Usually in such tasks, they mean preserve the textual content, not the exact markup. The earlier part said remove navigation text, social sharing, etc. So we are allowed to remove certain tags and replace with semantic tags. So I think it's okay to discard the empty div.
Thus we can proceed as earlier.
Now check the equal opportunity paragraph: original: Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
. We have Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
. We omitted the trailing with
. That's fine.
Now check the "Must have:" paragraph: original: Must have:
. We kept that.
Now the list items: original had with - items. We kept them.
Now the responsibilities paragraph: original:
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
. We kept that.
Now the second list: original with - items. We kept them.
Now we need to ensure we didn't lose any spaces or punctuation. Let's verify each paragraph text exactly.
Paragraph 1: "Why Airtel Africa?" with strong tags. We have
Why Airtel Africa?
. Good.
Paragraph 2: original: " 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." Note there is a leading (non-breaking space). We omitted it. Should we keep it? Let's decide to keep it as a leading inside the . So we would have
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.
. Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. Must not add commentary. Must output only HTML. We have raw text with some HTML tags originally. We need to extract content and format accordingly. Let's parse the given job description: Original snippet:
Must have:
- Bachelor's degree in business, sales, or equivalent training in business or sales management.
- Strong computer literacy with proficiency in MS office and other business applications.
- Excellent communication, influencing, and negotiation skills, with the ability to build and maintain strong customer relationships.
- Minimum 2 years of proven sales experience in the telecommunications or fast-moving consumer goods (FMCG) industry.
- Demonstrated commitment to delivering exceptional customer service and creating positive customer experiences
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
- Develop and maintain strong, long-term relationships with corporate clients, serving as their primary point of contact.
- Conduct regular client meetings to understand business needs, gather feedback, and identify opportunities for service improvement.
- Ensure high levels of client satisfaction by addressing queries, concerns, and service issues promptly.
- Achieve monthly, quarterly, and annual sales targets through the acquisition of new clients and the retention and expansion of existing accounts.
- Identify and pursue upselling and cross-selling opportunities for Airtel Business products and services, including data solutions, internet services, managed services, and IoT solutions.
- Prepare and present tailored product proposals, quotations, and presentations to clients based on their unique business requirements.
- Develop and implement account strategies in line with Airtel Business’s Go-To-Market plan to maximize revenue potential.
- Work closely with the marketing and product teams to develop campaigns and initiatives targeting the corporate segment.
- Pipeline and sales activity management.
for intro paragraphs and general text,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items.
We must preserve all original content word-for-word. So we cannot change wording, but we can wrap in tags.
We need to decide sections: The content includes:
- Intro: "Why Airtel Africa?" (strong) then paragraphs about Airtel Africa, then equal opportunity statement.
- Then "Must have:" paragraph (already
Must have:
) then list of requirements.
- Then a paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." (with after period). Then list of responsibilities/duties.
Thus we can treat sections: maybe "About the Role" for intro, "Requirements" for Must have list, "Responsibilities" for the second list.
But we must use for section headers. We need to decide appropriate header names based on content. The instruction says: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we can pick those that match.
We have:
- Intro paragraphs: could be under About the Role
(or maybe no header if not clear sections? But we have clear sections: requirements and responsibilities). The intro could be considered "About the Role". We'll wrap intro paragraphs in
tags under that header.
- Then
Requirements
(or Qualifications). The "Must have:" paragraph is introductory to the list; we could keep that as a then list.
- Then
Responsibilities
(or Key Duties). The paragraph before list: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." That's an intro to responsibilities. Then list.
We must preserve all original content word-for-word, including the " " spaces. In HTML, is an entity; we can keep it as is. The instruction says preserve all original content word-for-word, do not add, remove, summarise, or rephrase. So we must keep the exact text, including entities. However, we cannot use
tags. The original had
and for spacing; we must keep them? The instruction says preserve all original content word-for-word. But also says: Use for introductory paragraphs and general text,
- for list items. No CSS classes, no inline styles, no s, no
tags. So we must not use
tags. However, we must preserve original content word-for-word. There's a conflict: if we remove
tags, we are not preserving original content exactly. But the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Yet also says "No ...
tags". So we need to interpret: we should not include
tags in output, but we must keep the textual content, ignoring the
tags as formatting artifacts that we can remove? The earlier instruction in the first part said to remove stray numbers or formatting artifacts. Here they explicitly say no
tags. So we should strip out
tags and maybe? But is a character entity representing a non-breaking space; it's part of content. If we remove it, we are altering content. However, we could keep as is; it's not a tag. The instruction says no
tags, but is okay. So we should keep entities.
Thus we need to strip out
tags but keep .
Also we need to strip out tags and tags? The instruction says no s, but we can keep ? It didn't forbid . It said use for introductory paragraphs and general text,
for section headers, - for list items. No CSS classes, no inline styles, no s, no
tags. It didn't say we cannot use other tags like . However, to keep semantic HTML, we could keep for emphasis. But the instruction says "Preserve ALL original content word-for-word". If we keep tags, we are preserving them. That's okay. However, the earlier part said to remove author bylines etc. Not relevant.
Thus we can keep tags as they are.
But we need to wrap paragraphs in tags. The original had
tags around paragraphs. We'll replace those with tags, preserving the inner content (including etc). Also we need to handle the Must have:
already present; we can keep it as is (it's already a ). The list items are already in
- . We'll keep them.
We also need to add
headers for sections. Where to place them? We'll insert About the Role
before the intro paragraphs. Then Requirements
before the "Must have:" paragraph and list. Then Responsibilities
before the paragraph about She/He and the second list.
We must ensure we don't duplicate content. We'll output:
About the Role
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 Requirements
Must have:
- Bachelor's degree in business, sales, or equivalent training in business or sales management.
- Strong computer literacy with proficiency in MS office and other business applications.
- Excellent communication, influencing, and negotiation skills, with the ability to build and maintain strong customer relationships.
- Minimum 2 years of proven sales experience in the telecommunications or fast-moving consumer goods (FMCG) industry.
- Demonstrated commitment to delivering exceptional customer service and creating positive customer experiences
Then Responsibilities
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
- Develop and maintain strong, long-term relationships with corporate clients, serving as their primary point of contact.
- Conduct regular client meetings to understand business needs, gather feedback, and identify opportunities for service improvement.
- Ensure high levels of client satisfaction by addressing queries, concerns, and service issues promptly.
- Achieve monthly, quarterly, and annual sales targets through the acquisition of new clients and the retention and expansion of existing accounts.
- Identify and pursue upselling and cross-selling opportunities for Airtel Business products and services, including data solutions, internet services, managed services, and IoT solutions.
- Prepare and present tailored product proposals, quotations, and presentations to clients based on their unique business requirements.
- Develop and implement account strategies in line with Airtel Business’s Go-To-Market plan to maximize revenue potential.
- Work closely with the marketing and product teams to develop campaigns and initiatives targeting the corporate segment.
- Pipeline and sales activity management.
We need to ensure we kept all original content word-for-word. Let's verify:
Original intro paragraphs:
- Why Airtel Africa? => we have Why Airtel Africa?
(good)
-
=> we omitted this entirely (it was just blank line with spaces). Should we preserve? It's formatting artifact; we can drop as per instruction to remove stray numbers or formatting artifacts. The instruction says remove stray numbers or formatting artifacts. So we can drop empty divs.
- 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 have 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.
Note we removed the leading (non-breaking space) before the sentence. That is a formatting artifact; we removed it. Is that allowed? The instruction says preserve ALL original content word-for-word. The is a character entity; removing it changes content. However, the earlier instruction said to remove stray numbers or formatting artifacts. could be considered a formatting artifact (non-breaking space). The instruction in this part says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That's contradictory with earlier. But the overarching task: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The given input includes HTML tags. We need to output clean semantic HTML. 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. If text has no clear sections, just wrap paragraphs in tags. Return ONLY the HTML.
Thus we must keep the exact textual content, including any entities, but we cannot use
tags. However, we can keep as is. The leading before the sentence is part of the text node; we should keep it. But we removed it. We need to keep it.
Similarly, there is a trailing after the period in the responsibilities paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment. " We kept that after the period inside the
. Good.
Also there is a
with
after the intro paragraphs; we omitted that entirely. That div contains only a line break and a non-breaking space; it's basically whitespace. If we remove it, we are removing content (the ). But maybe it's considered formatting artifact and can be removed. The instruction says preserve ALL original content word-for-word. However, the earlier part said to remove stray numbers or formatting artifacts. The is a formatting artifact (non-breaking space). I'd lean to keep it if it's not inside a visible text? But it's just a space; preserving it won't affect visual output much. However, to strictly follow "preserve ALL original content word-for-word", we should keep it. But we cannot use
tags, but we can keep . The div containing
: we could replace the div with a containing ? But that would be a paragraph with just a non-breaking space, which is odd. Better to just keep the as a text node somewhere? But we cannot have free text not inside a tag? We could wrap it in a
but that would add a paragraph that is just a space. That might be considered adding structure but not adding content. The instruction says do not add, remove, summarise, or rephrase. Adding a
tag is adding markup, but we are allowed to add tags for formatting as per rules. The original had a
with
. We are replacing that with nothing? That's removing content (the and
tags). But we are allowed to remove tags? The instruction says preserve ALL original content word-for-word. Does that refer to textual content only, not markup? Usually in such tasks, they mean preserve the textual content, not the exact markup. The earlier part said remove navigation text, social sharing, etc. So we are allowed to remove certain tags and replace with semantic tags. So I think it's okay to discard the empty div.
Thus we can proceed as earlier.
Now check the equal opportunity paragraph: original: Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
. We have Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
. We omitted the trailing with
. That's fine.
Now check the "Must have:" paragraph: original: Must have:
. We kept that.
Now the list items: original had with - items. We kept them.
Now the responsibilities paragraph: original:
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
. We kept that.
Now the second list: original with - items. We kept them.
Now we need to ensure we didn't lose any spaces or punctuation. Let's verify each paragraph text exactly.
Paragraph 1: "Why Airtel Africa?" with strong tags. We have
Why Airtel Africa?
. Good.
Paragraph 2: original: " 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." Note there is a leading (non-breaking space). We omitted it. Should we keep it? Let's decide to keep it as a leading inside the . So we would have
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.
Must have:
) then list of requirements. - Then a paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." (with after period). Then list of responsibilities/duties. Thus we can treat sections: maybe "About the Role" for intro, "Requirements" for Must have list, "Responsibilities" for the second list. But we must use for section headers. We need to decide appropriate header names based on content. The instruction says: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we can pick those that match.
We have:
- Intro paragraphs: could be under About the Role
(or maybe no header if not clear sections? But we have clear sections: requirements and responsibilities). The intro could be considered "About the Role". We'll wrap intro paragraphs in
About the Role
(or maybe no header if not clear sections? But we have clear sections: requirements and responsibilities). The intro could be considered "About the Role". We'll wrap intro paragraphs intags under that header. - Then
Requirements
(or Qualifications). The "Must have:" paragraph is introductory to the list; we could keep that as athen list. - Then
Responsibilities
(or Key Duties). The paragraph before list: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment." That's an intro to responsibilities. Then list. We must preserve all original content word-for-word, including the " " spaces. In HTML, is an entity; we can keep it as is. The instruction says preserve all original content word-for-word, do not add, remove, summarise, or rephrase. So we must keep the exact text, including entities. However, we cannot usetags. The original had
and for spacing; we must keep them? The instruction says preserve all original content word-for-word. But also says: Use
for introductory paragraphs and general text,
- for list items. No CSS classes, no inline styles, no s, no
tags. So we must not use
tags. However, we must preserve original content word-for-word. There's a conflict: if we remove
tags, we are not preserving original content exactly. But the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Yet also says "No ...
tags". So we need to interpret: we should not include
tags in output, but we must keep the textual content, ignoring the
tags as formatting artifacts that we can remove? The earlier instruction in the first part said to remove stray numbers or formatting artifacts. Here they explicitly say no
tags. So we should strip out
tags and maybe? But is a character entity representing a non-breaking space; it's part of content. If we remove it, we are altering content. However, we could keep as is; it's not a tag. The instruction says no
tags, but is okay. So we should keep entities. Thus we need to strip out
tags but keep . Also we need to strip outtags and tags? The instruction says nos, but we can keep ? It didn't forbid . It said usefor introductory paragraphs and general text,
for section headers,
- for list items. No CSS classes, no inline styles, no s, no
tags. It didn't say we cannot use other tags like . However, to keep semantic HTML, we could keep for emphasis. But the instruction says "Preserve ALL original content word-for-word". If we keep tags, we are preserving them. That's okay. However, the earlier part said to remove author bylines etc. Not relevant. Thus we can keep tags as they are. But we need to wrap paragraphs intags. The original had
tags around paragraphs. We'll replace those withtags, preserving the inner content (including etc). Also we need to handle the
Must have:
already present; we can keep it as is (it's already a). The list items are already in
- . We'll keep them.
We also need to add
headers for sections. Where to place them? We'll insert
About the Role
before the intro paragraphs. ThenRequirements
before the "Must have:" paragraph and list. ThenResponsibilities
before the paragraph about She/He and the second list. We must ensure we don't duplicate content. We'll output:About the Role
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.
ThenRequirements
Must have:
- Bachelor's degree in business, sales, or equivalent training in business or sales management.
- Strong computer literacy with proficiency in MS office and other business applications.
- Excellent communication, influencing, and negotiation skills, with the ability to build and maintain strong customer relationships.
- Minimum 2 years of proven sales experience in the telecommunications or fast-moving consumer goods (FMCG) industry.
- Demonstrated commitment to delivering exceptional customer service and creating positive customer experiences
Responsibilities
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
- Develop and maintain strong, long-term relationships with corporate clients, serving as their primary point of contact.
- Conduct regular client meetings to understand business needs, gather feedback, and identify opportunities for service improvement.
- Ensure high levels of client satisfaction by addressing queries, concerns, and service issues promptly.
- Achieve monthly, quarterly, and annual sales targets through the acquisition of new clients and the retention and expansion of existing accounts.
- Identify and pursue upselling and cross-selling opportunities for Airtel Business products and services, including data solutions, internet services, managed services, and IoT solutions.
- Prepare and present tailored product proposals, quotations, and presentations to clients based on their unique business requirements.
- Develop and implement account strategies in line with Airtel Business’s Go-To-Market plan to maximize revenue potential.
- Work closely with the marketing and product teams to develop campaigns and initiatives targeting the corporate segment.
- Pipeline and sales activity management.
Why Airtel Africa?=> we haveWhy Airtel Africa?
(good) -=> we omitted this entirely (it was just blank line with spaces). Should we preserve? It's formatting artifact; we can drop as per instruction to remove stray numbers or formatting artifacts. The instruction says remove stray numbers or formatting artifacts. So we can drop empty divs. -
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 haveAt 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.
Note we removed the leading (non-breaking space) before the sentence. That is a formatting artifact; we removed it. Is that allowed? The instruction says preserve ALL original content word-for-word. The is a character entity; removing it changes content. However, the earlier instruction said to remove stray numbers or formatting artifacts. could be considered a formatting artifact (non-breaking space). The instruction in this part says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That's contradictory with earlier. But the overarching task: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The given input includes HTML tags. We need to output clean semantic HTML. 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. If text has no clear sections, just wrap paragraphs intags. Return ONLY the HTML. Thus we must keep the exact textual content, including any entities, but we cannot use
tags. However, we can keep as is. The leading before the sentence is part of the text node; we should keep it. But we removed it. We need to keep it. Similarly, there is a trailing after the period in the responsibilities paragraph: "She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment. " We kept that after the period inside the. Good. Also there is a
with
after the intro paragraphs; we omitted that entirely. That div contains only a line break and a non-breaking space; it's basically whitespace. If we remove it, we are removing content (the ). But maybe it's considered formatting artifact and can be removed. The instruction says preserve ALL original content word-for-word. However, the earlier part said to remove stray numbers or formatting artifacts. The is a formatting artifact (non-breaking space). I'd lean to keep it if it's not inside a visible text? But it's just a space; preserving it won't affect visual output much. However, to strictly follow "preserve ALL original content word-for-word", we should keep it. But we cannot use
tags, but we can keep . The div containing
: we could replace the div with acontaining ? But that would be a paragraph with just a non-breaking space, which is odd. Better to just keep the as a text node somewhere? But we cannot have free text not inside a tag? We could wrap it in a
but that would add a paragraph that is just a space. That might be considered adding structure but not adding content. The instruction says do not add, remove, summarise, or rephrase. Adding a
tag is adding markup, but we are allowed to add tags for formatting as per rules. The original had a
with
. We are replacing thatwith nothing? That's removing content (theand
tags). But we are allowed to remove tags? The instruction says preserve ALL original content word-for-word. Does that refer to textual content only, not markup? Usually in such tasks, they mean preserve the textual content, not the exact markup. The earlier part said remove navigation text, social sharing, etc. So we are allowed to remove certain tags and replace with semantic tags. So I think it's okay to discard the empty div. Thus we can proceed as earlier. Now check the equal opportunity paragraph: original:. We haveAirtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
Airtel Africa is proud to be an equal opportunity employer and remain fully committed to diversity and inclusion in the workplace.
. We omitted the trailingwith
. That's fine. Now check the "Must have:" paragraph: original:Must have:
. We kept that. Now the list items: original had- with
- items. We kept them.
Now the responsibilities paragraph: original:
She/He will be responsible for managing and developing relationships with key corporate clients to drive revenue growth and customer satisfaction within the corporate segment.
. We kept that. Now the second list: original- with
- items. We kept them.
Now we need to ensure we didn't lose any spaces or punctuation. Let's verify each paragraph text exactly.
Paragraph 1: "Why Airtel Africa?" with strong tags. We have
Why Airtel Africa?
. Good. Paragraph 2: original: " 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." Note there is a leading (non-breaking space). We omitted it. Should we keep it? Let's decide to keep it as a leading inside the. So we would have
- items. We kept them.
Now we need to ensure we didn't lose any spaces or punctuation. Let's verify each paragraph text exactly.
Paragraph 1: "Why Airtel Africa?" with strong tags. We have
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.
- items. We kept them.
Now the responsibilities paragraph: original:
- . We'll keep them.
We also need to add
- for list items. No CSS classes, no inline styles, no