BUSINESS SYSTEM SUPPORT ANALYST- VISIONFUND KENYA
Worldvision
Job Description
for intro paragraphs and general text,
for section headers like 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 s, no
. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in . Return ONLY the HTML. No markdown fences, no explanation.
We must parse the given job description and output HTML accordingly.
We need to identify sections: The raw text includes some headings like "About the Role", "Key Responsibilities", "Key Performance Indicators", "Qualifications and Experience", "Core Competencies", "Working Environment", "Application Instructions", "Applicant Types Accepted". 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 need to map appropriate headings to . The raw headings are About the Role
etc. We can extract the text inside and use . For example "About the Role" becomes About the Role
. Similarly "Key Responsibilities" becomes Key Responsibilities
. "Key Performance Indicators" maybe not listed as a header to keep? 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 should use for those headings. If a heading is not exactly one of those, maybe still use with the text? Probably yes.
We must preserve all original content word-for-word. That includes the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the same text including tags? But we cannot use tags? The instruction only says use
,
, - . It doesn't forbid but it's not a required tag. However preserving original content word-for-word includes the tags? The original text includes Employee Contract Type: etc. But we are to output clean semantic HTML using only allowed tags. We can keep the tags inside the text? The instruction says "Use
for introductory paragraphs and general text". It doesn't forbid other tags like , , . But it says "No CSS classes, no inline styles, no s, no
tags". So we can keep , , . However we must not add, remove, summarise, or rephrase. So we must keep the exact same inner text, including tags? The original includes tags around "Employee Contract Type:" and "Job Description:". Should we keep them? Probably yes, because they are part of the original content. But we need to wrap them in allowed tags? The tag is not disallowed. It's just not a structural tag. It's okay to keep it. However we must not add new tags beyond allowed ones. The allowed tags are ,
, , - . We can still include , , inside those? The instruction didn't forbid them, only said no CSS classes, no inline styles, no s, no
tags. So we can keep , , . But we must not add any new tags like . So we must replace headings with . The original headings are About the Role
. We need to output About the Role
maybe without the and ? But that would be removing content (the and tags). The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact same inner content, including the and tags? The original includes About the Role. That's part of the content. So we must output exactly that? But we are limited to for section headers. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot include other markup inside the . So we can output About the Role
? That would preserve the original content exactly. However the original had About the Role
. So we need to replace the with but keep the inner ... etc. So we output About the Role
. That preserves the inner content.
Similarly for "Key Responsibilities" heading: original is Key Responsibilities
. So we output Key Responsibilities
.
For "Key Performance Indicators": original is Key Performance Indicators
. So output Key Performance Indicators
.
For "Qualifications and Experience": original is Qualifications and Experience
. So output Qualifications and Experience
.
For "Core Competencies": original is Core Competencies
. So output Core Competencies
.
For "Working Environment": original is Working Environment
. So output Working Environment
.
For "Application Instructions": original is Application Instructions
. That's a paragraph with bold. Should we treat as section header? The instruction says use for section headers (e.g. ... How to Apply). So "Application Instructions" should be a header. So we output Application Instructions
. But we must preserve the original content word-for-word. The original had
Application Instructions
. So we need to output Application Instructions
. That preserves the bold but changes the tag from to
. That's okay because we are replacing the heading tag. The content inside remains same.
For "Applicant Types Accepted": original is
Applicant Types Accepted:
Local Applicants Only. That's a paragraph with Applicant Types Accepted: then "Local Applicants Only". We need to preserve that. Probably we can output Applicant Types Accepted: Local Applicants Only
. That's fine.
We also have some introductory paragraphs: The first part includes With 75 years of experience... etc. That's an intro paragraph. Then there is
empty. Then etc. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must output those empty paragraphs as maybe? But we cannot have empty paragraphs? It's okay to output . The original had and . We can output them as and (since style attribute not allowed). But we must not include style attributes. The instruction says no inline styles. So we must remove the style attribute. But that would be removing content? The style attribute is part of the original content. However the instruction says "No CSS classes, no inline styles, no s, no
tags". So we must not include style attributes. But we must preserve all original content word-for-word. There's a conflict: we cannot keep the style attribute because it's disallowed, but we must preserve it. However the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the style attribute. But also "No CSS classes, no inline styles, no s, no
tags". So we must remove the style attribute to comply with the no inline styles rule. This is a conflict. In such cases, we need to prioritize the higher-level instruction? The instruction hierarchy: The user gave explicit rules: "No CSS classes, no inline styles, no s, no
tags". Also "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Which takes precedence? The instruction to not use inline styles is a rule that overrides preserving the style attribute because we cannot output it. So we must remove it. But that would be removing content (the style attribute). However the instruction says "do not add, remove, summarise, or rephrase". Removing the style attribute is removing content. But the rule about no inline styles is more specific about allowed tags. I think we must obey the rule about no inline styles, which means we cannot output style attributes. So we must remove them, even though it removes content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But that conflicts with the rule about no inline styles. In such conflicts, the higher-level rule about allowed tags likely takes precedence. The instruction says "Your ONLY job is to format it as clean semantic HTML." and then lists rules, including "No CSS classes, no inline styles, no s, no
tags". So we must not output inline styles. So we must strip them. That means we are removing some content (the style attribute). But the instruction says preserve all original content word-for-word. However the style attribute is not "content" per se; it's a tag attribute. The instruction might consider that as part of the content to preserve? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That could be interpreted as preserving the textual content, not the markup attributes. So we can remove style attributes. That seems reasonable.
Thus we will output HTML with only allowed tags and no style attributes. We'll keep , , etc.
Now we need to produce the cleaned HTML.
Let's parse the original text step by step.
Original plain-text job description (including HTML tags). Let's copy it exactly as given:
With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith.
Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!
Employee Contract Type:
Local - Fixed Term Employee (Fixed Term)Job Description:
About the Role
We are seeking a proactive, analytical and customer-focused Business System Support Analyst to join our ICT team.
The successful candidate will provide first-line support for the Temenos Transact (T24) core banking system and related digital banking applications. The role will support the investigation and resolution of system issues, application monitoring, user support, testing and deployment, data validation, reporting and continuous improvement of business systems.
The role will also play a key part in driving the adoption of Artificial Intelligence (AI) to improve operational efficiency, strengthen data analysis and support fraud detection.
Key Responsibilities
1. Business Applications Support
- Provide first-level support to users of Temenos Transact (T24) and related business applications.
- Log, investigate and resolve application incidents within agreed Service Level Agreements (SLAs).
- Troubleshoot issues relating to customer accounts, loans, deposits and financial transactions.
- Monitor application availability and escalate complex issues to senior support teams or vendors.
- Provide timely guidance and technical support to business users.
2. AI Adoption and Innovation
- Support the adoption and effective use of AI across business operations.
- Identify opportunities where AI can improve efficiency, productivity and decision-making.
- Apply AI-driven tools and techniques to support fraud detection and risk management.
- Use AI to enhance data analysis and generate actionable business insights.
- Promote responsible AI awareness and best practices among users and ICT teams.
3. System Testing and Deployment
- Participate in User Acceptance Testing (UAT) for system enhancements.
- Assist in validating system fixes and enhancements before production deployment.
- Support post-deployment verification and monitoring.
- Document and report system defects identified during testing.
4. System Monitoring
- Monitor scheduled system jobs and batch processes.
- Support End-of-Day (COB) and End-of-Month processing.
- Identify and escalate system failures promptly.
- Support recovery activities to minimize disruption to business operations.
5. Data Validation and Reporting
- Conduct basic data validation and reconciliation.
- Use SQL queries to investigate and verify application data.
- Support preparation of operational and management reports.
- Ensure accuracy and integrity of information used for decision-making.
6. Documentation and Knowledge Management
- Maintain accurate records of incidents, resolutions and system issues.
- Develop user guides, knowledge-base articles and support documentation.
- Document recurring problems, root causes and recommended solutions.
- Contribute to continuous improvement of application support processes.
7. Stakeholder Collaboration
- Work closely with business users, ICT teams, software vendors and project teams.
- Support application implementations, upgrades and system improvement initiatives.
- Maintain effective working relationships with internal and external stakeholders.
Key Performance Indicators
Success in this role will be measured through:
- Timely resolution of application incidents within agreed SLAs.
- High availability and reliability of supported business applications.
- User satisfaction with ICT application support.
- Successful testing and deployment of system enhancements.
- Reduced post-deployment system defects.
- Timely identification and escalation of system and batch-processing failures.
- Accuracy of data validation and operational reports.
- Effective adoption and application of AI solutions.
- Improved efficiency and business insights through technology and data.
- Quality and completeness of system documentation.
Qualifications and Experience
The ideal candidate should have:
- A Bachelor's degree in Information Technology, Computer Science, Business Information Technology, Information Systems, or a related field.
- Experience in application support, core banking systems, business systems or ICT service support.
- Knowledge or experience working with Temenos Transact (T24) or similar core banking platforms will be an added advantage.
- Basic to intermediate SQL and database querying skills.
- Understanding of system testing,
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.
. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in
. Return ONLY the HTML. No markdown fences, no explanation. We must parse the given job description and output HTML accordingly. We need to identify sections: The raw text includes some headings like "About the Role", "Key Responsibilities", "Key Performance Indicators", "Qualifications and Experience", "Core Competencies", "Working Environment", "Application Instructions", "Applicant Types Accepted". 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 need to map appropriate headings to . The raw headings are About the Role
etc. We can extract the text inside and use . For example "About the Role" becomes About the Role
. Similarly "Key Responsibilities" becomes Key Responsibilities
. "Key Performance Indicators" maybe not listed as a header to keep? 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 should use for those headings. If a heading is not exactly one of those, maybe still use with the text? Probably yes.
We must preserve all original content word-for-word. That includes the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the same text including tags? But we cannot use tags? The instruction only says use
About the Role
etc. We can extract the text inside and use. For example "About the Role" becomes About the Role
. Similarly "Key Responsibilities" becomes Key Responsibilities
. "Key Performance Indicators" maybe not listed as a header to keep? 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 should use for those headings. If a heading is not exactly one of those, maybe still use with the text? Probably yes.
We must preserve all original content word-for-word. That includes the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the same text including tags? But we cannot use tags? The instruction only says use
for those headings. If a heading is not exactly one of those, maybe still use with the text? Probably yes.
We must preserve all original content word-for-word. That includes the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the same text including tags? But we cannot use tags? The instruction only says use
,
, - . It doesn't forbid but it's not a required tag. However preserving original content word-for-word includes the tags? The original text includes Employee Contract Type: etc. But we are to output clean semantic HTML using only allowed tags. We can keep the tags inside the text? The instruction says "Use
for introductory paragraphs and general text". It doesn't forbid other tags like , , . But it says "No CSS classes, no inline styles, no s, no
tags". So we can keep , , . However we must not add, remove, summarise, or rephrase. So we must keep the exact same inner text, including tags? The original includes tags around "Employee Contract Type:" and "Job Description:". Should we keep them? Probably yes, because they are part of the original content. But we need to wrap them in allowed tags? The tag is not disallowed. It's just not a structural tag. It's okay to keep it. However we must not add new tags beyond allowed ones. The allowed tags are ,
, , - . We can still include , , inside those? The instruction didn't forbid them, only said no CSS classes, no inline styles, no s, no
tags. So we can keep , , . But we must not add any new tags like . So we must replace headings with . The original headings are About the Role
. We need to output About the Role
maybe without the and ? But that would be removing content (the and tags). The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact same inner content, including the and tags? The original includes About the Role. That's part of the content. So we must output exactly that? But we are limited to for section headers. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot include other markup inside the . So we can output About the Role
? That would preserve the original content exactly. However the original had About the Role
. So we need to replace the with but keep the inner ... etc. So we output About the Role
. That preserves the inner content.
Similarly for "Key Responsibilities" heading: original is Key Responsibilities
. So we output Key Responsibilities
.
For "Key Performance Indicators": original is Key Performance Indicators
. So output Key Performance Indicators
.
For "Qualifications and Experience": original is Qualifications and Experience
. So output Qualifications and Experience
.
For "Core Competencies": original is Core Competencies
. So output Core Competencies
.
For "Working Environment": original is Working Environment
. So output Working Environment
.
For "Application Instructions": original is Application Instructions
. That's a paragraph with bold. Should we treat as section header? The instruction says use for section headers (e.g. ... How to Apply). So "Application Instructions" should be a header. So we output Application Instructions
. But we must preserve the original content word-for-word. The original had
Application Instructions
. So we need to output Application Instructions
. That preserves the bold but changes the tag from to
. That's okay because we are replacing the heading tag. The content inside remains same.
For "Applicant Types Accepted": original is
Applicant Types Accepted:
Local Applicants Only. That's a paragraph with Applicant Types Accepted: then "Local Applicants Only". We need to preserve that. Probably we can output Applicant Types Accepted: Local Applicants Only
. That's fine.
We also have some introductory paragraphs: The first part includes With 75 years of experience... etc. That's an intro paragraph. Then there is
empty. Then etc. We need to preserve them? The instruction says preserve ALL original content word-for-word. So we must output those empty paragraphs as maybe? But we cannot have empty paragraphs? It's okay to output . The original had and . We can output them as and (since style attribute not allowed). But we must not include style attributes. The instruction says no inline styles. So we must remove the style attribute. But that would be removing content? The style attribute is part of the original content. However the instruction says "No CSS classes, no inline styles, no s, no
tags". So we must not include style attributes. But we must preserve all original content word-for-word. There's a conflict: we cannot keep the style attribute because it's disallowed, but we must preserve it. However the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the style attribute. But also "No CSS classes, no inline styles, no s, no
tags". So we must remove the style attribute to comply with the no inline styles rule. This is a conflict. In such cases, we need to prioritize the higher-level instruction? The instruction hierarchy: The user gave explicit rules: "No CSS classes, no inline styles, no s, no
tags". Also "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Which takes precedence? The instruction to not use inline styles is a rule that overrides preserving the style attribute because we cannot output it. So we must remove it. But that would be removing content (the style attribute). However the instruction says "do not add, remove, summarise, or rephrase". Removing the style attribute is removing content. But the rule about no inline styles is more specific about allowed tags. I think we must obey the rule about no inline styles, which means we cannot output style attributes. So we must remove them, even though it removes content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But that conflicts with the rule about no inline styles. In such conflicts, the higher-level rule about allowed tags likely takes precedence. The instruction says "Your ONLY job is to format it as clean semantic HTML." and then lists rules, including "No CSS classes, no inline styles, no s, no
tags". So we must not output inline styles. So we must strip them. That means we are removing some content (the style attribute). But the instruction says preserve all original content word-for-word. However the style attribute is not "content" per se; it's a tag attribute. The instruction might consider that as part of the content to preserve? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That could be interpreted as preserving the textual content, not the markup attributes. So we can remove style attributes. That seems reasonable.
Thus we will output HTML with only allowed tags and no style attributes. We'll keep , , etc.
Now we need to produce the cleaned HTML.
Let's parse the original text step by step.
Original plain-text job description (including HTML tags). Let's copy it exactly as given:
With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith.
Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!
Employee Contract Type:
Local - Fixed Term Employee (Fixed Term)Job Description:
About the Role
We are seeking a proactive, analytical and customer-focused Business System Support Analyst to join our ICT team.
The successful candidate will provide first-line support for the Temenos Transact (T24) core banking system and related digital banking applications. The role will support the investigation and resolution of system issues, application monitoring, user support, testing and deployment, data validation, reporting and continuous improvement of business systems.
The role will also play a key part in driving the adoption of Artificial Intelligence (AI) to improve operational efficiency, strengthen data analysis and support fraud detection.
Key Responsibilities
1. Business Applications Support
- Provide first-level support to users of Temenos Transact (T24) and related business applications.
- Log, investigate and resolve application incidents within agreed Service Level Agreements (SLAs).
- Troubleshoot issues relating to customer accounts, loans, deposits and financial transactions.
- Monitor application availability and escalate complex issues to senior support teams or vendors.
- Provide timely guidance and technical support to business users.
2. AI Adoption and Innovation
- Support the adoption and effective use of AI across business operations.
- Identify opportunities where AI can improve efficiency, productivity and decision-making.
- Apply AI-driven tools and techniques to support fraud detection and risk management.
- Use AI to enhance data analysis and generate actionable business insights.
- Promote responsible AI awareness and best practices among users and ICT teams.
3. System Testing and Deployment
- Participate in User Acceptance Testing (UAT) for system enhancements.
- Assist in validating system fixes and enhancements before production deployment.
- Support post-deployment verification and monitoring.
- Document and report system defects identified during testing.
4. System Monitoring
- Monitor scheduled system jobs and batch processes.
- Support End-of-Day (COB) and End-of-Month processing.
- Identify and escalate system failures promptly.
- Support recovery activities to minimize disruption to business operations.
5. Data Validation and Reporting
- Conduct basic data validation and reconciliation.
- Use SQL queries to investigate and verify application data.
- Support preparation of operational and management reports.
- Ensure accuracy and integrity of information used for decision-making.
6. Documentation and Knowledge Management
- Maintain accurate records of incidents, resolutions and system issues.
- Develop user guides, knowledge-base articles and support documentation.
- Document recurring problems, root causes and recommended solutions.
- Contribute to continuous improvement of application support processes.
7. Stakeholder Collaboration
- Work closely with business users, ICT teams, software vendors and project teams.
- Support application implementations, upgrades and system improvement initiatives.
- Maintain effective working relationships with internal and external stakeholders.
Key Performance Indicators
Success in this role will be measured through:
- Timely resolution of application incidents within agreed SLAs.
- High availability and reliability of supported business applications.
- User satisfaction with ICT application support.
- Successful testing and deployment of system enhancements.
- Reduced post-deployment system defects.
- Timely identification and escalation of system and batch-processing failures.
- Accuracy of data validation and operational reports.
- Effective adoption and application of AI solutions.
- Improved efficiency and business insights through technology and data.
- Quality and completeness of system documentation.
Qualifications and Experience
The ideal candidate should have:
- A Bachelor's degree in Information Technology, Computer Science, Business Information Technology, Information Systems, or a related field.
- Experience in application support, core banking systems, business systems or ICT service support.
- Knowledge or experience working with Temenos Transact (T24) or similar core banking platforms will be an added advantage.
- Basic to intermediate SQL and database querying skills.
- Understanding of system testing,
Apply Now ↗
How well do you match?
Get an instant AI match score for this role — free, takes 3 minutes.
Tailor your CV for this role
The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
Tailor My CV to This Job ✍️
Free cover letter for this job
Upload your CV and get a tailored cover letter in seconds — free, no account needed.
Generate a Cover Letter 📝
My Job Concierge
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Almost there
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
ECHO
Your MJC Assistant
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
for introductory paragraphs and general text". It doesn't forbid other tags like , , . But it says "No CSS classes, no inline styles, no , Application Instructions Application Instructions to Applicant Types Accepted: Applicant Types Accepted: Local Applicants Only With 75 years of experience... etc. That's an intro paragraph. Then there is With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith. Employee Contract Type: Job Description: We are seeking a proactive, analytical and customer-focused Business System Support Analyst to join our ICT team. The successful candidate will provide first-line support for the Temenos Transact (T24) core banking system and related digital banking applications. The role will support the investigation and resolution of system issues, application monitoring, user support, testing and deployment, data validation, reporting and continuous improvement of business systems. The role will also play a key part in driving the adoption of Artificial Intelligence (AI) to improve operational efficiency, strengthen data analysis and support fraud detection. Success in this role will be measured through: The ideal candidate should have: 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. Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call. 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. 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.
tags". So we can keep , , . However we must not add, remove, summarise, or rephrase. So we must keep the exact same inner text, including tags? The original includes tags around "Employee Contract Type:" and "Job Description:". Should we keep them? Probably yes, because they are part of the original content. But we need to wrap them in allowed tags? The tag is not disallowed. It's just not a structural tag. It's okay to keep it. However we must not add new tags beyond allowed ones. The allowed tags are ,
,
tags. So we can keep , , . But we must not add any new tags like . So we must replace headings with
. The original headings are
About the Role
. We need to output About the Role
maybe without the and ? But that would be removing content (the and tags). The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the exact same inner content, including the and tags? The original includes About the Role. That's part of the content. So we must output exactly that? But we are limited to for section headers. The instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot include other markup inside the
. So we can output
About the Role
? That would preserve the original content exactly. However the original had About the Role
. So we need to replace the with
but keep the inner ... etc. So we output
About the Role
. That preserves the inner content.
Similarly for "Key Responsibilities" heading: original is Key Responsibilities
. So we output Key Responsibilities
.
For "Key Performance Indicators": original is Key Performance Indicators
. So output Key Performance Indicators
.
For "Qualifications and Experience": original is Qualifications and Experience
. So output Qualifications and Experience
.
For "Core Competencies": original is Core Competencies
. So output Core Competencies
.
For "Working Environment": original is Working Environment
. So output Working Environment
.
For "Application Instructions": original is for section headers (e.g. ... How to Apply). So "Application Instructions" should be a header. So we output
Application Instructions
. But we must preserve the original content word-for-word. The original had Application Instructions
. That preserves the bold but changes the tag from . That's okay because we are replacing the heading tag. The content inside remains same.
For "Applicant Types Accepted": original is
tags". So we must not include style attributes. But we must preserve all original content word-for-word. There's a conflict: we cannot keep the style attribute because it's disallowed, but we must preserve it. However the instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the style attribute. But also "No CSS classes, no inline styles, no
tags". So we must remove the style attribute to comply with the no inline styles rule. This is a conflict. In such cases, we need to prioritize the higher-level instruction? The instruction hierarchy: The user gave explicit rules: "No CSS classes, no inline styles, no
tags". Also "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Which takes precedence? The instruction to not use inline styles is a rule that overrides preserving the style attribute because we cannot output it. So we must remove it. But that would be removing content (the style attribute). However the instruction says "do not add, remove, summarise, or rephrase". Removing the style attribute is removing content. But the rule about no inline styles is more specific about allowed tags. I think we must obey the rule about no inline styles, which means we cannot output style attributes. So we must remove them, even though it removes content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But that conflicts with the rule about no inline styles. In such conflicts, the higher-level rule about allowed tags likely takes precedence. The instruction says "Your ONLY job is to format it as clean semantic HTML." and then lists rules, including "No CSS classes, no inline styles, no
tags". So we must not output inline styles. So we must strip them. That means we are removing some content (the style attribute). But the instruction says preserve all original content word-for-word. However the style attribute is not "content" per se; it's a tag attribute. The instruction might consider that as part of the content to preserve? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That could be interpreted as preserving the textual content, not the markup attributes. So we can remove style attributes. That seems reasonable.
Thus we will output HTML with only allowed tags and no style attributes. We'll keep , , etc.
Now we need to produce the cleaned HTML.
Let's parse the original text step by step.
Original plain-text job description (including HTML tags). Let's copy it exactly as given:
Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!About the Role
Key Responsibilities
1. Business Applications Support
2. AI Adoption and Innovation
3. System Testing and Deployment
4. System Monitoring
5. Data Validation and Reporting
6. Documentation and Knowledge Management
7. Stakeholder Collaboration
Key Performance Indicators
Qualifications and Experience
How well do you match?
Tailor your CV for this role
Free cover letter for this job
Let jobs find you
Add your CV for real matches
You're in.