Job Description
for intro paragraphs and general text. Use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items (duties, requirements, qualifications, skills). No CSS classes, no inline styles, no s, no
tags.
We must preserve all original content word-for-word. That includes the text inside tags, but we must strip out HTML tags and replace with semantic HTML as per rules. However we must keep the content exactly same words, punctuation, etc. We cannot add or remove anything. So we need to parse the raw text and output HTML with same textual content.
We have a large job description with many sections: Introduction, Organizational Context and Scope, Required Qualifications and Experience (with subsections Education, Experience, Skills, Languages, Required Competencies, Values, Core Competencies, Managerial Competencies, Notes). Then after that there is an ordered list () with list items that appear to be duties/responsibilities (maybe under Responsibilities). Those list items have some weird formatting with spans etc. We need to preserve the text inside those list items exactly.
We must not add any extra content, not remove any. So we need to output the same textual content, just wrapped in appropriate tags.
We must not use or
. Use for paragraphs,
for section headers, - for list items. For the ordered list at the end, we need to decide if it's a list of duties; we should use
- (unordered) as per instruction: Use
- for list items (duties, requirements, qualifications, skills). So we should convert the
to - . However we must preserve the content word-for-word; changing ordered list to unordered list changes the markup but not the content. The instruction says use
- for list items. So we should output
- for those duty items. The original had
with numeric ordering; but we must follow instruction to use - . That is acceptable as we are not adding or removing content; we are just changing list type. The content inside each
- must be preserved exactly.
We also need to handle nested lists like the sublist under the fourth duty item (the one with "Support and oversee end-to-end procurement and logistics processes..." which includes a sublist with items o AVRR operations; o Reintegration as ...). The original had a
then a with "o AVRR operations;" then a
then another with "o Reintegration as". This seems like a list within a paragraph. We need to preserve the text exactly. The instruction says use - for list items. So we should treat those as list items as well. However the original content includes "o " as bullet-like. We must keep that exactly. So we could wrap the whole block in a
- for the main duty, and then inside that maybe a nested
- for the subitems. But we must not add any extra content; we can add tags but not change text. Adding
and - tags is allowed as per instruction. So we can structure.
We also need to handle the earlier lists: under Education, Experience, Skills, Languages, Required Competencies, Values, Core Competencies, Managerial Competencies. Those are already
- in original. We should keep them as
- . Also there are some
for first-tier candidates list (internal candidates, then list of countries). That is a list; we should convert to - as per instruction (list items). Also there is a second tier candidates paragraph (plain text). We'll keep as
.
We also need to handle headings: The original has Introduction, Organizational Context and Scope, Required Qualifications and Experience, then subheadings like Education, Experience, Skills, Languages, Required Competencies, Values , Core Competencies, Managerial Competencies, Notes. According to instruction, use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should wrap each of those headings in . Also maybe "Introduction" and "Organizational Context and Scope" are also section headers; we can treat them as as well.
We must not add any extra text like "Responsibilities". The headings should be exactly the original strong text. So we will output Introduction
, etc.
We must preserve all original content word-for-word, including spaces, line breaks? We can ignore line breaks as they are not content; but we must not add or remove characters. We'll output HTML tags around the text; the text itself remains same.
We must not use or
. So we need to replace
with nothing? But we must preserve content word-for-word;
is a tag, not content. The instruction says no
tags. So we should omit them, but that would be removing a tag, not content. The content is the text; the
is not content. So it's okay to omit
tags. However we must ensure that removing
does not change the textual content (i.e., we don't lose a line break that is part of the text). Since
is just a formatting tag, removing it does not affect the textual content (the visible characters). So it's fine.
Similarly, we must remove any tags? The instruction didn't forbid tags. It only said no CSS classes, no inline styles, no s, no
tags. It didn't say we cannot keep tags. However we should preserve all original content word-for-word, which includes the tags and their href etc. But the instruction says return ONLY the cleaned job text. In the first task, they wanted to remove ads etc. In this second task, they want to format as clean semantic HTML. It seems we should keep the links as tags but without classes, inline styles. The original tags have target="_blank" rel="noopener noreferrer" href="..." and sometimes nested tags (like ... ). That's malformed (nested ). We need to preserve content word-for-word, but we also need to output clean semantic HTML. The nested is invalid HTML; but we must preserve the content word-for-word, which includes the nested tags. However we cannot keep invalid HTML? The instruction says return ONLY the HTML. It didn't say we must fix malformed markup. But we should output valid HTML? Usually they'd expect us to strip the nested and keep only one with the href and the inner text. However that would be changing content (removing a tag). The inner tag's content is the same as the outer's? Let's examine: In the introduction: "IOM workplace culture | International Organization for Migration" So outer has href to iom.int/iom-workplace-culture, inner has rel="nofollow" and no href? Actually inner has rel="nofollow" but no href attribute, which is invalid. The inner text is "IOM workplace culture | International Organization for Migration". So the nested is pointless. If we keep both, we have nested which is invalid. If we remove the inner and keep outer with same href and inner text, we preserve the visible text and the link. That changes the markup but not the visible content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That refers to text content, not tags? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Usually "content" means the textual content, not the markup. So we can change tags as needed to produce clean semantic HTML, as long as we don't alter the textual content. So we can fix the nested by removing the inner tag and keeping the outer with href and the text. That does not add or remove any textual content; we just removed a tag. That's acceptable.
Similarly, there are many tags with target="_blank" rel="noopener noreferrer" href="..." and sometimes nested with rel="nofollow". We'll need to flatten them: keep the outermost that has an href, and use its text content (which may be inside inner ). We'll need to extract the text.
Also there are some tags with class etc. We'll need to strip those and keep the text.
We also have some tags with inline styles (like style="margin-left: 0px;"). We must remove inline styles per instruction (no inline styles). So we strip style attributes.
We also have some
with inline style attribute huge; we will replace with (or ? but instruction says use - for list items). So we will change to
- . We'll strip the style attribute.
We also have some
- with inline style attributes; we will strip them.
We also have some
with class "ck-list-bogus-paragraph". We'll strip class.
We also have some with class "ck-list-bogus-paragraph". We'll strip.
We also have some with style attributes (font-family, font-size, line-height). We'll strip.
We also have some
tags; we will remove them.
We also have some entities; we should keep them as is? They are part of content. We'll keep them.
We also have some "o " bullet characters inside spans; we will keep them.
We also have some text like "o AVRR operations;" and "o Reintegration as". The second seems truncated: "o Reintegration as". Probably the original text continues but got cut off. We must preserve exactly as given.
Now we need to produce final HTML with only ,
, - , and tags (if we keep them). Also we may keep ? The instruction didn't forbid . It said use
for section headers,
for introductory paragraphs and general text,
- for list items. It didn't say we cannot use for bold text within paragraphs. However to keep it clean semantic HTML, we could keep as it's semantic. But 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 forbid other tags. However to be safe, we could keep as is, but we need to remove any inline styles/classes. The original tags have no attributes, just . So we can keep them.
But we also have some with trailing spaces like "Values " includes inside. We'll keep that.
Now we need to produce the final HTML.
Let's extract the textual content and structure.
We'll go through the original HTML and produce a cleaned version.
Original snippet:
Introduction
Established in 1951, IOM is a Related Organization of the United Nations and the leading UN agency in the field of migration. Working closely with governmental, intergovernmental and non-governmental partners, IOM promotes humane and orderly migration for the benefit of all. It saves lives and protects people on the move, drives solutions to displacement, and facilitates pathways for regular migration, while providing services and advice to governments and migrants.
IOM is committed to fostering a respectful, inclusive and supportive workplace where all employees can thrive professionally and feel valued. By creating such an environment, IOM aims to better harness the full potential of migration and strengthen its support to people on the move.
IOM invites candidates from diverse backgrounds to apply and provides reasonable accommodation throughout the recruitment process when required. Learn more about IOM’s workplace culture at IOM workplace culture | International Organization for Migration
Applications are welcome from first- and second-tier candidates, particularly qualified female candidates as well as applications from the non-represented member countries of IOM. For all IOM vacancies, applications from qualified and eligible first-tier candidates are considered before those of qualified and eligible second-tier candidates in the selection process.
For the purpose of this vacancy, the following are considered first-tier candidates:
- Internal candidates
- Candidates from the following IOM Member States that are not represented among staff members in the Professional and higher categories:
Bahamas, Barbados, Cabo Verde, Comoros, Congo (the), Cook Islands, Dominica, Federated States of Micronesia, Grenada, Guinea-Bissau, Holy See, Iceland, Israel, Kiribati, Marshall Islands, Namibia, Nauru, Palau, Saint Kitts and Nevis, Saint Lucia, Samoa, Sao Tome and Principe, Seychelles, Solomon Islands, Suriname, Timor-Leste, Tonga, Trinidad and Tobago, Tuvalu, Vanuatu
Second tier candidates include:
All external candidates, except candidates from non-represented member states of IOM.
Organizational Context and Scope
Under the overall supervision of the Chief of Mission (CoM) with coordination functions, and the direct supervision of the Resources Management Officer (RMO), and in close coordination with the Regional Office (RO) for West and Central Africa (WCA) in Dakar, the Central Coordination Unit (CCU) of the Migrant Protection, Return and Reintegration for Sub-Saharan Africa (MPRR-SSA) programme, relevant programme units, implementing Country Offices (COs), and the Supply Chain Division at Headquarters (HQ), the Supply Chain Officer will be responsible and accountable for leading, coordinating, and monitoring supply chain activities in support of programme and operational objectives, ensuring the timely, efficient, compliant, and cost-effective delivery of quality goods and services to beneficiaries in accordance with the International Organization for Migration (IOM) policies, donor requirements, and Supply Chain Management (SCM) standards.
As Senegal serves as a Country Office with Coordinating Functions (COCF), the role will also provide technical supply chain guidance, coordination, and support, as required, to COs within the assigned Area of Responsibility (AoR), currently comprising The Gambia, Sierra Leone, Cabo Verde, and Guinea-Bissau, in line with delegated institutional responsibilities.
Required Qualifications and Experience
Education
- Master’s degree in Business Administration, Supply Chain Management, Logistics, Procurement, or a related field from an accredited academic institution with five years of relevant professional experience; or,
- University degree in the above fields with seven years of relevant professional experience.
Accredited Universities are those listed in the UNESCO World Higher Education Database.
Experience
- Experience in managing diverse procurement and logistics operations; and,
- Demonstrated experience in training and managing large teams of co-workers, managing vendors and suppliers.
Skills
- Extensive knowledge of IOM/UN internal procurement and financial rules, as well as IOM's system and processes as they apply to procurement and logistics; and,
- Excellent level of computer literacy and good knowledge of Oracle is an advantage.
Languages
For this position, fluency in English and French is required (oral and written).
Working knowledge of another official UN languages (Arabic, Chinese, Russian, and Spanish) is an advantage.
Proficiency of language(s) required will be specifically evaluated during the selection process, which may include written and/or oral assessments.
Required Competencies
IOM’s competency framework can be found at this link. Competencies will be assessed during the selection process.
Values - all IOM staff members must abide by and demonstrate these five values:
- Inclusion and respect for diversity: Respects and promotes individual and cultural differences. Encourages diversity and inclusion.
- Integrity and transparency: Maintains high ethical standards and acts
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 📝
tags. We must preserve all original content word-for-word. That includes the text inside tags, but we must strip out HTML tags and replace with semantic HTML as per rules. However we must keep the content exactly same words, punctuation, etc. We cannot add or remove anything. So we need to parse the raw text and output HTML with same textual content. We have a large job description with many sections: Introduction, Organizational Context and Scope, Required Qualifications and Experience (with subsections Education, Experience, Skills, Languages, Required Competencies, Values, Core Competencies, Managerial Competencies, Notes). Then after that there is an ordered list (
- ) with list items that appear to be duties/responsibilities (maybe under Responsibilities). Those list items have some weird formatting with spans etc. We need to preserve the text inside those list items exactly.
We must not add any extra content, not remove any. So we need to output the same textual content, just wrapped in appropriate tags.
We must not use
- for list items. For the ordered list at the end, we need to decide if it's a list of duties; we should use
- (unordered) as per instruction: Use
- for list items (duties, requirements, qualifications, skills). So we should convert the
- to
- . However we must preserve the content word-for-word; changing ordered list to unordered list changes the markup but not the content. The instruction says use
- for list items. So we should output
- for those duty items. The original had
- with numeric ordering; but we must follow instruction to use
- . That is acceptable as we are not adding or removing content; we are just changing list type. The content inside each
- must be preserved exactly.
We also need to handle nested lists like the sublist under the fourth duty item (the one with "Support and oversee end-to-end procurement and logistics processes..." which includes a sublist with items o AVRR operations; o Reintegration as ...). The original had a
then a with "o AVRR operations;" then a
then another with "o Reintegration as". This seems like a list within a paragraph. We need to preserve the text exactly. The instruction says use- for list items. So we should treat those as list items as well. However the original content includes "o " as bullet-like. We must keep that exactly. So we could wrap the whole block in a
- for the main duty, and then inside that maybe a nested
- for the subitems. But we must not add any extra content; we can add tags but not change text. Adding
- and
- tags is allowed as per instruction. So we can structure.
We also need to handle the earlier lists: under Education, Experience, Skills, Languages, Required Competencies, Values, Core Competencies, Managerial Competencies. Those are already
- in original. We should keep them as
- . Also there are some
- for first-tier candidates list (internal candidates, then list of countries). That is a list; we should convert to
- as per instruction (list items). Also there is a second tier candidates paragraph (plain text). We'll keep as
. We also need to handle headings: The original has Introduction, Organizational Context and Scope, Required Qualifications and Experience, then subheadings like Education, Experience, Skills, Languages, Required Competencies, Values , Core Competencies, Managerial Competencies, Notes. According to instruction, use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should wrap each of those headings in
. Also maybe "Introduction" and "Organizational Context and Scope" are also section headers; we can treat them as
as well. We must not add any extra text like "Responsibilities". The headings should be exactly the original strong text. So we will output
Introduction
, etc. We must preserve all original content word-for-word, including spaces, line breaks? We can ignore line breaks as they are not content; but we must not add or remove characters. We'll output HTML tags around the text; the text itself remains same. We must not useor
. So we need to replace
with nothing? But we must preserve content word-for-word;
is a tag, not content. The instruction says no
tags. So we should omit them, but that would be removing a tag, not content. The content is the text; the
is not content. So it's okay to omit
tags. However we must ensure that removing
does not change the textual content (i.e., we don't lose a line break that is part of the text). Since
is just a formatting tag, removing it does not affect the textual content (the visible characters). So it's fine. Similarly, we must remove any tags? The instruction didn't forbid tags. It only said no CSS classes, no inline styles, nos, no
tags. It didn't say we cannot keep tags. However we should preserve all original content word-for-word, which includes the tags and their href etc. But the instruction says return ONLY the cleaned job text. In the first task, they wanted to remove ads etc. In this second task, they want to format as clean semantic HTML. It seems we should keep the links as tags but without classes, inline styles. The original tags have target="_blank" rel="noopener noreferrer" href="..." and sometimes nested tags (like ... ). That's malformed (nested ). We need to preserve content word-for-word, but we also need to output clean semantic HTML. The nested is invalid HTML; but we must preserve the content word-for-word, which includes the nested tags. However we cannot keep invalid HTML? The instruction says return ONLY the HTML. It didn't say we must fix malformed markup. But we should output valid HTML? Usually they'd expect us to strip the nested and keep only one with the href and the inner text. However that would be changing content (removing a tag). The inner tag's content is the same as the outer's? Let's examine: In the introduction: "IOM workplace culture | International Organization for Migration" So outer has href to iom.int/iom-workplace-culture, inner has rel="nofollow" and no href? Actually inner has rel="nofollow" but no href attribute, which is invalid. The inner text is "IOM workplace culture | International Organization for Migration". So the nested is pointless. If we keep both, we have nested which is invalid. If we remove the inner and keep outer with same href and inner text, we preserve the visible text and the link. That changes the markup but not the visible content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That refers to text content, not tags? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Usually "content" means the textual content, not the markup. So we can change tags as needed to produce clean semantic HTML, as long as we don't alter the textual content. So we can fix the nested by removing the inner tag and keeping the outer with href and the text. That does not add or remove any textual content; we just removed a tag. That's acceptable. Similarly, there are many tags with target="_blank" rel="noopener noreferrer" href="..." and sometimes nested with rel="nofollow". We'll need to flatten them: keep the outermost that has an href, and use its text content (which may be inside inner ). We'll need to extract the text. Also there are some tags with class etc. We'll need to strip those and keep the text. We also have sometags with inline styles (like style="margin-left: 0px;"). We must remove inline styles per instruction (no inline styles). So we strip style attributes. We also have some
- with inline style attribute huge; we will replace with
- for list items). So we will change to
- . We'll strip the style attribute. We also have some
- with inline style attributes; we will strip them.
We also have some
with class "ck-list-bogus-paragraph". We'll strip class. We also have some with class "ck-list-bogus-paragraph". We'll strip. We also have some with style attributes (font-family, font-size, line-height). We'll strip. We also have some
tags; we will remove them. We also have some entities; we should keep them as is? They are part of content. We'll keep them. We also have some "o " bullet characters inside spans; we will keep them. We also have some text like "o AVRR operations;" and "o Reintegration as". The second seems truncated: "o Reintegration as". Probably the original text continues but got cut off. We must preserve exactly as given. Now we need to produce final HTML with only,
,
- , and tags (if we keep them). Also we may keep ? The instruction didn't forbid . It said use
for section headers,
for introductory paragraphs and general text,
- for list items. It didn't say we cannot use for bold text within paragraphs. However to keep it clean semantic HTML, we could keep as it's semantic. But 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 forbid other tags. However to be safe, we could keep as is, but we need to remove any inline styles/classes. The original tags have no attributes, just . So we can keep them. But we also have some with trailing spaces like "Values " includes inside. We'll keep that. Now we need to produce the final HTML. Let's extract the textual content and structure. We'll go through the original HTML and produce a cleaned version. Original snippet:
Introduction
Established in 1951, IOM is a Related Organization of the United Nations and the leading UN agency in the field of migration. Working closely with governmental, intergovernmental and non-governmental partners, IOM promotes humane and orderly migration for the benefit of all. It saves lives and protects people on the move, drives solutions to displacement, and facilitates pathways for regular migration, while providing services and advice to governments and migrants.
IOM is committed to fostering a respectful, inclusive and supportive workplace where all employees can thrive professionally and feel valued. By creating such an environment, IOM aims to better harness the full potential of migration and strengthen its support to people on the move.
IOM invites candidates from diverse backgrounds to apply and provides reasonable accommodation throughout the recruitment process when required. Learn more about IOM’s workplace culture at IOM workplace culture | International Organization for Migration
Applications are welcome from first- and second-tier candidates, particularly qualified female candidates as well as applications from the non-represented member countries of IOM. For all IOM vacancies, applications from qualified and eligible first-tier candidates are considered before those of qualified and eligible second-tier candidates in the selection process.
For the purpose of this vacancy, the following are considered first-tier candidates:
- Internal candidates
- Candidates from the following IOM Member States that are not represented among staff members in the Professional and higher categories:
Bahamas, Barbados, Cabo Verde, Comoros, Congo (the), Cook Islands, Dominica, Federated States of Micronesia, Grenada, Guinea-Bissau, Holy See, Iceland, Israel, Kiribati, Marshall Islands, Namibia, Nauru, Palau, Saint Kitts and Nevis, Saint Lucia, Samoa, Sao Tome and Principe, Seychelles, Solomon Islands, Suriname, Timor-Leste, Tonga, Trinidad and Tobago, Tuvalu, Vanuatu
Second tier candidates include:
All external candidates, except candidates from non-represented member states of IOM.Organizational Context and Scope
Under the overall supervision of the Chief of Mission (CoM) with coordination functions, and the direct supervision of the Resources Management Officer (RMO), and in close coordination with the Regional Office (RO) for West and Central Africa (WCA) in Dakar, the Central Coordination Unit (CCU) of the Migrant Protection, Return and Reintegration for Sub-Saharan Africa (MPRR-SSA) programme, relevant programme units, implementing Country Offices (COs), and the Supply Chain Division at Headquarters (HQ), the Supply Chain Officer will be responsible and accountable for leading, coordinating, and monitoring supply chain activities in support of programme and operational objectives, ensuring the timely, efficient, compliant, and cost-effective delivery of quality goods and services to beneficiaries in accordance with the International Organization for Migration (IOM) policies, donor requirements, and Supply Chain Management (SCM) standards.
As Senegal serves as a Country Office with Coordinating Functions (COCF), the role will also provide technical supply chain guidance, coordination, and support, as required, to COs within the assigned Area of Responsibility (AoR), currently comprising The Gambia, Sierra Leone, Cabo Verde, and Guinea-Bissau, in line with delegated institutional responsibilities.
Required Qualifications and Experience
Education
- Master’s degree in Business Administration, Supply Chain Management, Logistics, Procurement, or a related field from an accredited academic institution with five years of relevant professional experience; or,
- University degree in the above fields with seven years of relevant professional experience.
Accredited Universities are those listed in the UNESCO World Higher Education Database.
Experience
- Experience in managing diverse procurement and logistics operations; and,
- Demonstrated experience in training and managing large teams of co-workers, managing vendors and suppliers.
Skills
- Extensive knowledge of IOM/UN internal procurement and financial rules, as well as IOM's system and processes as they apply to procurement and logistics; and,
- Excellent level of computer literacy and good knowledge of Oracle is an advantage.
Languages
For this position, fluency in English and French is required (oral and written).
Working knowledge of another official UN languages (Arabic, Chinese, Russian, and Spanish) is an advantage.
Proficiency of language(s) required will be specifically evaluated during the selection process, which may include written and/or oral assessments.
Required Competencies
IOM’s competency framework can be found at this link. Competencies will be assessed during the selection process.
Values - all IOM staff members must abide by and demonstrate these five values:
- Inclusion and respect for diversity: Respects and promotes individual and cultural differences. Encourages diversity and inclusion.
- Integrity and transparency: Maintains high ethical standards and acts
- for list items. It didn't say we cannot use for bold text within paragraphs. However to keep it clean semantic HTML, we could keep as it's semantic. But the instruction says "Use
- , and tags (if we keep them). Also we may keep ? The instruction didn't forbid . It said use
- (or
- ? but instruction says use
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 📝 - for list items). So we will change to
- as per instruction (list items). Also there is a second tier candidates paragraph (plain text). We'll keep as
- . Also there are some
- in original. We should keep them as
- tags is allowed as per instruction. So we can structure.
We also need to handle the earlier lists: under Education, Experience, Skills, Languages, Required Competencies, Values, Core Competencies, Managerial Competencies. Those are already
- for the subitems. But we must not add any extra content; we can add tags but not change text. Adding
- for the main duty, and then inside that maybe a nested
- for list items. So we should treat those as list items as well. However the original content includes "o " as bullet-like. We must keep that exactly. So we could wrap the whole block in a
- for those duty items. The original had
- for list items. So we should output
- . However we must preserve the content word-for-word; changing ordered list to unordered list changes the markup but not the content. The instruction says use
- for list items (duties, requirements, qualifications, skills). So we should convert the
- (unordered) as per instruction: Use
. Use
for paragraphs,
for section headers,
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.