Job Description
for paragraphs,
for section headers, - for list items. No CSS classes, no inline styles, no , no
. Must preserve original content word-for-word, no addition/removal. The input already contains some HTML tags like , , , - , , , etc. We need to output only HTML, preserving content but we must reformat according to rules: 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. No CSS classes, no inline styles, no , no
. Must preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase.
Thus we need to parse the given job description and output HTML with appropriate tags. The original includes tags already, but we must ensure we follow rules: Use
for paragraphs,
for section headers, - for list items. Also we must not keep any other tags like , , ? The rules say preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we must keep the original text exactly, but we can change tags? The instruction: "Your ONLY job is to format it as clean semantic HTML." So we need to output HTML that represents the content, preserving the text but using appropriate tags. It likely expects we replace the existing markup with the required tags, but keep the text content unchanged. However, we must not add or remove any text. So we need to keep all words, punctuation, etc. We can change tags but must keep the inner text same.
Thus we need to produce HTML where:
- Intro paragraphs: The first few paragraphs before "Values" etc. Should be wrapped in
tags.
- Section headers: "Values" maybe? Actually there is a bold "Values" line. Also "Education:", "Experience:", "Skills:" lines. Also maybe "The Senior Manager - Software Developer will be accountable to achieve the following objectives:" is a header? Could be considered a section header. The rules say use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat "Education:", "Experience:", "Skills:" as headers. Also maybe "Values" as a header? Not in list but could be considered "About the Role"? Actually "Values" is a section about culture. Could be considered "About the Role"? Not exactly. But we can still treat as header if it's a section header. The rule says use for section headers (e.g., ...). It doesn't forbid using for other headers. So we can use for any section header we identify.
- Lists: The bullet lists under Values, Education, Experience, Skills, and the objectives list should be - .
- Links: The original includes tags with URLs. We must preserve them word-for-word, meaning we should keep the tags as they are? The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we change the tags to something else, we would be removing or altering content. So we must keep the tags exactly as they appear. Similarly , tags inside them? The original includes , inside . We must keep them.
Thus we cannot strip those tags; we must keep them. However the instruction also says use
for introductory paragraphs and general text,
for section headers, - for list items. It doesn't forbid other tags like , , . So we can keep them.
Thus we need to output HTML where we wrap paragraphs in
, headings in
, lists in - , but keep existing inline tags like , , inside.
We must also remove any stray formatting like maybe? The rule says preserve ALL original content word-for-word. So we must keep as is. Also we must not remove empty
maybe? It says preserve all original content word-for-word. So we should keep that empty paragraph with as is. However we might need to wrap it in tags? It already is
. That's fine.
We must not add any extra tags beyond those needed for structure? We can add ,
, , - as needed, but must not remove existing tags. So we need to take the original HTML and maybe replace some tags with appropriate ones while preserving inner text and other tags.
Simplify: We can just output the original HTML but ensure that paragraphs are
, headings are
, lists are - . The original already uses
for paragraphs,
- for lists, and for bold. It also uses for "Values". That's not an
. So we need to change that to . Also "Education:", "Experience:", "Skills:" are currently
with bold? Actually they are
Education:
then . So we need to change the Education:
to Education:
. Similarly for Experience and Skills. Also "The Senior Manager - Software Developer will be accountable to achieve the following objectives:" is a followed by
. Should we make that a header? Possibly "Key Duties" style. Could treat as Objectives:
but the text is longer. The rule says use for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). The phrase "will be accountable to achieve the following objectives:" could be considered a header for responsibilities. We could wrap it in . But we must preserve the exact text. So we can change the
to
.
Also "Values" line currently is
Values (Our Culture)
. We need to make that a header: Values (Our Culture)
. Keep the bold inside.
Also there is a paragraph after values describing culture etc. Those are paragraphs.
Also there are links after values: three each containing an with ... etc. Those are paragraphs; we keep them as .
Also after that there is a blank
then Education:
etc.
Thus we need to modify certain tags to
where they act as section headers.
We must not add or remove any text, including the tags we change? Changing a tag from
to
is altering the markup but not the text content. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does changing a tag count as adding/removing? It changes the markup but not the content. Likely acceptable because we are formatting as clean semantic HTML. The instruction: "Your ONLY job is to format it as clean semantic HTML." So we are allowed to change tags to achieve semantic HTML. The content (text) must stay same.
Thus we will produce HTML where we replace appropriate
with
. Also ensure that list items are
- inside
. They already are.
We must not add any extra tags like . Keep existing , , .
We must also ensure we don't have any stray
tags; there are none.
We must not add CSS classes or inline styles.
Thus final output: a series of elements.
Let's reconstruct.
Start with first paragraph:
As a member of the squad, the Senior Manager – Software Developer will be responsible to design, develop, and maintain reliable and innovative software solutions. They will help enable MTN to deliver cutting-edge telecommunications services to customers by ensuring high quality software designs.
Second paragraph:
The Senior Manager – Software Developer will closely work with engineering manager and cross-functional teams within the squad to understand business requirements, identify opportunities for optimization, and build scalable software solutions that support the company's growth objectives.
Third:
They will collaborate with DevSecOps engineer, tester etc. to address issues and drive continuous improvement. They will gain an understanding and adopt emerging technologies to ensure that MTN remains competitive in the market.
Fourth:
As developers, they will leverage technical expertise and skills to develop solutions that drives innovation and enhance customer experience supporting overall growth and success of MTN.
Fifth:
(keep)
Now Values section: currently Values (Our Culture)
. Change to Values (Our Culture)
Then paragraph after that:
We at MTN are a purpose and value-led organization. At MTN, we believe that understanding our people’s needs and aspirations is key to creating experiences that delight you at work, everyday. We are committed to fostering an environment where every member of our Y’ello Family is heard, understood and empowered to live an inspired life.
Next:
Our values keep us grounded and moving in the right direction. Most importantly, they keep us honest. It is not something we claim to be. It is in our DNA.
Next:
As an organisation, we consider it our mission to create an exciting and rewarding place to work, where our people can be themselves, thrive in positivity and ignite their full potential. A workplace that boosts creativity and innovation, improves productivity, and ultimately drives meaningful results. A workplace that is built on relationships and achieving a purpose that is bigger than us.
Next:
Our commitments go beyond an organisational promise. It is in our leadership and managerial ethos to meaningfully partner with our employees, customers and stakeholders with a vision to realise our shared goals.
Next:
Live Y’ello
Then the list:
- Lead with Care
- Can-do with Integrity
- Collaborate with Agility
- Serve with Respect
- Act with Inclusion
Then three link paragraphs:
Click here to find out more about Living an Inspired Life @ MTN
Click here to learn more about MTN Software Solutions
Click here to find out more about MTN’s uniquely crafted Inspired Rewards
Then blank? Actually after that there is Education:
originally. We need to change to Education:
Then the education list:
- Bachelor’s degree in Computer Science/Information Technology/Electronics and Communication
- Post graduate degree in Computer Science /Networks and /or equivalent professional qualification (Preferred)
Then Experience:
change to Experience:
Then experience list:
- 7+ years of relevant working experience
- 4-5 years of experience in either as a full stack developer or as a frontend/backend developer
- Experience in emerging telecom-based software technology (Preferred to have)
- Expertise in software development methodologies, design patterns, and best practices
- Experience with cloud platforms (AWS, Azure, Google Cloud) is a plus
Then Skills:
change to Skills:
Then skills list:
- Proficiency in entire Java technology stack backed by multiple projects and visible accomplishments
- Strong knowledge of telecom systems, protocols, and industry standards (Preferred)
- Solid understanding of web technologies, APIs, and web services
- Detailed knowledge of database management systems, SQL, and NoSQL databases
- Excellent problem-solving and analytical skills, with a focus on delivering robust and scalable solution
Then the objectives paragraph: currently The Senior Manager - Software Developer will be accountable to achieve the following objectives:
We need to change to The Senior Manager - Software Developer will be accountable to achieve the following objectives:
(remove the style attribute? The rule says no inline styles. So we must remove the style attribute. However preserving original content word-for-word would keep the style attribute. But we cannot have inline styles per rules. Conflict: preserve original content word-for-word vs no inline styles. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. But also says no CSS classes, no inline styles, no s, no
tags. So we must remove the inline style attribute to comply with no inline styles. However that would be removing content (the style attribute). Which rule takes precedence? The overall task: format as clean semantic HTML. The rules include no inline styles. So we must strip the style attribute. The preservation rule likely refers to the textual content, not the markup. Usually in such tasks, we keep the text but can change tags and remove styling. So we will remove the style attribute.
Thus we output The Senior Manager - Software Developer will be accountable to achieve the following objectives:
Then the objectives list:
- Deliver high-quality software solutions that meets the requirements and expectations of stakeholders
- Ensure projects/software solutions adhere to established software development lifecycles (e.g., Agile, Waterfall) by contributing to project planning, requirements analysis, design, coding, testing, deployment, and maintenance
- Actively participate in agile development practices such as sprint planning, daily stand-ups, and retrospectives
- Collaborate with the team to estimate and prioritize user stories, ensure that work is completed within sprint timelines, and adapt to changing requirements
- Proficiency in various common data structures, their performance characteristics, and assembling them into complex programs within the frontend stack
- Understanding of (asymptotic and practical) performance characteristics with regards to fundamental algorithms in the language and standard library
- Ability to architect, develop and implement new microservices in a container environment
- Leverage knowledge of version control, incremental delivery of software, frequent releases, automation, testing and breakdown of work to meet stakeholder requirements effectively
- Work on multiple cloud platform and leverage cloud native components for a full-stack application
- Translate architecture requirements into software specifications by using emerging technologies
- Foster effective collaboration and communication within development team
- Take leadership roles within development team by promoting best practices, sharing knowledge and helping the team grow and improve their skills
- Excel in problem-solving and troubleshooting complex technical issues by identifying the root causes of problems, proposing and implementing effective solutions, and resolving issues in a timely manner
- Drive continuous improvement and innovation in software development processes by adopting automation tools, optimizing development workflows, or introducing innovative features or solutions
- Deliver software solutions that meet customer needs, adds value, and aligns with business goals, which in turn drives the success of the organization and its products or services
- Adhere to security and compliance standards while developing software solutions. Ensure that data privacy, protection, and regulatory requirements are met within the software solutions
We must ensure we keep the inside text where present.
Now we need to output the HTML as a single string, no extra explanation.
Let's construct final HTML.
We'll start with the intro paragraphs.
Note: The original had a paragraph with after the intro paragraphs. We'll keep that.
Let's write:
As a member of the squad, the Senior Manager – Software Developer will be responsible to design, develop, and maintain reliable and innovative software solutions. They will help enable MTN to
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 📝
. Must preserve original content word-for-word, no addition/removal. The input already contains some HTML tags like
, , for introductory paragraphs and general text. Use tags already, but we must ensure we follow rules: Use for paragraphs, tags.
- Section headers: "Values" maybe? Actually there is a bold "Values" line. Also "Education:", "Experience:", "Skills:" lines. Also maybe "The Senior Manager - Software Developer will be accountable to achieve the following objectives:" is a header? Could be considered a section header. The rules say use for introductory paragraphs and general text, , headings in tags? It already is , , headings are for paragraphs, with bold? Actually they are Education: Education: followed by to Values (Our Culture) each containing an with ... etc. Those are paragraphs; we keep them as .
Also after that there is a blank Education: tags to to with As a member of the squad, the Senior Manager – Software Developer will be responsible to design, develop, and maintain reliable and innovative software solutions. They will help enable MTN to deliver cutting-edge telecommunications services to customers by ensuring high quality software designs. The Senior Manager – Software Developer will closely work with engineering manager and cross-functional teams within the squad to understand business requirements, identify opportunities for optimization, and build scalable software solutions that support the company's growth objectives. They will collaborate with DevSecOps engineer, tester etc. to address issues and drive continuous improvement. They will gain an understanding and adopt emerging technologies to ensure that MTN remains competitive in the market. As developers, they will leverage technical expertise and skills to develop solutions that drives innovation and enhance customer experience supporting overall growth and success of MTN. Values (Our Culture) We at MTN are a purpose and value-led organization. At MTN, we believe that understanding our people’s needs and aspirations is key to creating experiences that delight you at work, everyday. We are committed to fostering an environment where every member of our Y’ello Family is heard, understood and empowered to live an inspired life. Our values keep us grounded and moving in the right direction. Most importantly, they keep us honest. It is not something we claim to be. It is in our DNA. As an organisation, we consider it our mission to create an exciting and rewarding place to work, where our people can be themselves, thrive in positivity and ignite their full potential. A workplace that boosts creativity and innovation, improves productivity, and ultimately drives meaningful results. A workplace that is built on relationships and achieving a purpose that is bigger than us. Our commitments go beyond an organisational promise. It is in our leadership and managerial ethos to meaningfully partner with our employees, customers and stakeholders with a vision to realise our shared goals. Live Y’ello Click here to find out more about Living an Inspired Life @ MTN Click here to learn more about MTN Software Solutions Click here to find out more about MTN’s uniquely crafted Inspired Rewards Education: Experience: Skills: The Senior Manager - Software Developer will be accountable to achieve the following objectives: As a member of the squad, the Senior Manager – Software Developer will be responsible to design, develop, and maintain reliable and innovative software solutions. They will help enable MTN to Get an instant AI match score for this role — free, takes 3 minutes. The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste. Upload your CV and get a tailored cover letter in seconds — free, no account needed.,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use
. Must preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase.
Thus we need to parse the given job description and output HTML with appropriate tags. The original includes for section headers,
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat "Education:", "Experience:", "Skills:" as headers. Also maybe "Values" as a header? Not in list but could be considered "About the Role"? Actually "Values" is a section about culture. Could be considered "About the Role"? Not exactly. But we can still treat as header if it's a section header. The rule says use
for section headers (e.g., ...). It doesn't forbid using for other headers. So we can use
for any section header we identify.
- Lists: The bullet lists under Values, Education, Experience, Skills, and the objectives list should be
for section headers,
, lists in
,
,
, lists are
. So we need to change that to
. Also "Education:", "Experience:", "Skills:" are currently
. So we need to change the
Education:
. Similarly for Experience and Skills. Also "The Senior Manager - Software Developer will be accountable to achieve the following objectives:" is a . Should we make that a header? Possibly "Key Duties" style. Could treat as
Objectives:
but the text is longer. The rule says use for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). The phrase "will be accountable to achieve the following objectives:" could be considered a header for responsibilities. We could wrap it in
. But we must preserve the exact text. So we can change the
.
Also "Values" line currently is
Values (Our Culture)
. Keep the bold inside.
Also there is a paragraph after values describing culture etc. Those are paragraphs.
Also there are links after values: three where they act as section headers.
We must not add or remove any text, including the tags we change? Changing a tag from
is altering the markup but not the text content. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Does changing a tag count as adding/removing? It changes the markup but not the content. Likely acceptable because we are formatting as clean semantic HTML. The instruction: "Your ONLY job is to format it as clean semantic HTML." So we are allowed to change tags to achieve semantic HTML. The content (text) must stay same.
Thus we will produce HTML where we replace appropriate
. Also ensure that list items are
. They already are.
We must not add any extra tags like
tags; there are none.
We must not add CSS classes or inline styles.
Thus final output: a series of elements.
Let's reconstruct.
Start with first paragraph:
Values (Our Culture)
Then paragraph after that:
Then three link paragraphs:
Education:
Then the education list:
Then Experience:
Then experience list:
Then Skills:
Then skills list:
Then the objectives paragraph: currently The Senior Manager - Software Developer will be accountable to achieve the following objectives:
(remove the style attribute? The rule says no inline styles. So we must remove the style attribute. However preserving original content word-for-word would keep the style attribute. But we cannot have inline styles per rules. Conflict: preserve original content word-for-word vs no inline styles. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. But also says no CSS classes, no inline styles, no
tags. So we must remove the inline style attribute to comply with no inline styles. However that would be removing content (the style attribute). Which rule takes precedence? The overall task: format as clean semantic HTML. The rules include no inline styles. So we must strip the style attribute. The preservation rule likely refers to the textual content, not the markup. Usually in such tasks, we keep the text but can change tags and remove styling. So we will remove the style attribute.
Thus we output The Senior Manager - Software Developer will be accountable to achieve the following objectives:
Then the objectives list:
We must ensure we keep the inside text where present.
Now we need to output the HTML as a single string, no extra explanation.
Let's construct final HTML.
We'll start with the intro paragraphs.
Note: The original had a paragraph with after the intro paragraphs. We'll keep that.
Let's write:
How well do you match?
Tailor your CV for this role
Free cover letter for this job
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.