Job Description
` for paragraphs, `
` for section headers, `- ` for lists, no CSS classes/inline styles//
, preserve ALL original content word-for-word, no summarizing/rephrasing, if no clear sections just wrap in ``, return ONLY HTML, no markdown fences/explanation/preamble.
2. **Identify the Source Text:**
- The text is a job listing for a "Support Manager" position at "Forum des ONG en Afrique de l’Ouest et centrale (FONGA)".
- It contains various formatting tags from the original website (`
`, ``, ``, ``, etc.), French language content, lists, etc.
- I need to extract the actual job content and reformat it into the specified HTML structure, preserving all text word-for-word but removing the original formatting artifacts (like inline CSS, `` maybe kept? Rule says preserve ALL original content word-for-word. But also says no inline styles, no ``, no `
`. It doesn't say remove ``, ``, etc. But the output format specifies `` for headers, `- ` for lists, `
` for intro/general text. I need to decide how to handle ``, ``, etc. The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This means the text content inside tags must be preserved exactly. The tags themselves can be replaced per the new schema. So I should keep the text, but use the new tags (``, `
`, `
`, ``, `- `). I'll need to handle `` and `` - probably keep them as inline text formatting, but the rule says "no inline styles". `` and `` are not styles, they're semantic HTML tags. I think it's okay to keep them or maybe just keep the text as-is without them? But the rule says preserve ALL original content word-for-word. If I remove ``, I'm removing markup but keeping the text. The intent is probably to keep the visible text. I'll keep `` and `` as they are valid semantic HTML and not "inline styles". Actually, the rule says "No CSS classes, no inline styles, no s, no
tags". So ``, `` are fine. I'll use them sparingly or as needed to preserve emphasis, but the main structure must follow the rules.
Let me re-read carefully: "Use for introductory paragraphs and general text. Use
- for list items... Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in
tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble."
So I need to transform the given text into:
- `
` for section headers (Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - but the text might not have exact section headers labeled as such. I need to identify natural sections and label them with ``. The rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This implies I should create those sections if they exist, or use what's there. The original text has sections like "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", etc. I'll map them to the suggested headers, but must preserve all content word-for-word. I should not rename or rephrase, but I can wrap section titles as `` and then the content below in `
` or `
- `. The content text itself must remain exactly as original.
- Actually, the rule: "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This might mean I should use those exact headers if those sections exist, or similar. I'll interpret it as: when there's a natural section break, use `` for the heading, and then the content below in appropriate tags. The headings themselves should be the section labels, but I must preserve original content. There's a tension: "Preserve ALL original content word-for-word" vs "Use for section headers". I think the intent is: the text content inside must not be changed, but I can structure it with headers. The headers themselves might be derived from the text, but I should probably use the exact phrases that serve as section dividers, or create reasonable ones. Looking at the text, it has "Contexte", "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", "En complément", "Compétences souhaitées". I'll use those as `` text, or map to the suggested ones. But the rule says "Preserve ALL original content word-for-word". If I change "Ce que nous recherchons" to "Responsibilities", that's rephrasing. So I should keep the original heading text exactly, but wrap it in ``. That makes sense.
- Let's outline the structure I'll create:
- The job title isn't explicitly given at the very top, but there's context. I might need to infer or just start from the text. The text starts with "Contexte". There's no explicit "Job Title" line, but I can treat the whole thing as a job listing. I'll perhaps add a `` for the role if I can identify it, but must preserve content. Actually, the instruction says "Keep and Structure: Job title, Company/Organisation name, Location, Job description and responsibilities, Requirements/qualifications, How to apply / application instructions, Salary (if mentioned), Deadline / closing date, Job ID / reference number, Contract type / level". But then it says "Your job is to extract ONLY the actual job information and return it in a clean, readable format." and later "Return ONLY the cleaned job text. Do not add any commentary...". The rules section says "Rules: Use
... Use
... Use - ... No CSS classes... Preserve ALL original content word-for-word... If text has no clear sections, just wrap paragraphs in
tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Wait, there's a conflict between the very first user prompt and the later "Rules" section. The first prompt says: "You are a job listing editor. You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format. REMOVE all of the following: ... KEEP and STRUCTURE: - Job title - Company/Organisation name - Location - Job description and responsibilities - Requirements/qualifications - How to apply / application instructions - Salary (if mentioned) - Deadline / closing date - Job ID / reference number - Contract type / level - Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text."
Then the user says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML. 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 (duties, requirements, qualifications, skills) - No CSS classes, no inline styles, no s, no
tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble."
And then provides the job description text.
I need to follow the most specific rules. The second set seems to be the actual formatting task rules, while the first is a general description. The rules say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is very strict. It also says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This implies I should structure the content into those sections using ``, but the actual header text should probably be the original section titles, or the suggested ones. Given "Preserve ALL original content word-for-word", I think I should keep the original section headings as they appear in the text, but wrap them in ``. However, the original text has headings like "Contexte", "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", "En complément", "Compétences souhaitées". These are in French. The suggested headers are in English: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". There's a mismatch. I need to decide: do I translate/rephrase headers to English, or keep French? The rule says "Preserve ALL original content word-for-word". That likely includes the heading text. So I should keep the French headings exactly, but mark them as ``. However, the example gives English headers. This is tricky.
Let me re-read carefully: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The "e.g." means "for example". It's suggesting what kinds of headers to use, not that I must exactly use those English terms. Given the preservation rule, I should use the actual section headers from the text, wrapped in ``. But the text's headers are in French. I'll keep them in French, as translating would be removing/rephrasing.
Another issue: the original text has a lot of inline CSS (`style="line-height: normal; margin-bottom: 0cm;"`, `style="text-align: justify;"`, `style="font-size: 11pt;"`, `style="color: black;"`, `style="background-color: yellow;"`). The rules say "No CSS classes, no inline styles, no s, no
tags". I must strip all `style` attributes. Also remove ``, ``? The rule says "Preserve ALL original content word-for-word". I think the visible text must be preserved, but the markup can be restructured. I'll keep `` and `` as they are semantic HTML and not "inline styles". Actually, `` is deprecated/obsolete in HTML5, but still valid. The rule says "No CSS classes, no inline styles". `` has no style by default, so it's fine. I'll keep them. But the `style` attributes on ``, ``, `- ` etc. must be removed. Also `` etc. I need to decide what to do with ``. The rule doesn't forbid ``, but it says "No CSS classes, no inline styles". `` has no style attribute, so it might be okay. However, the rule says "Preserve ALL original content word-for-word". If I remove ``, I'm removing markup but the text inside remains. I think it's safer to keep `` tags if they don't have inline styles, but the original has `style="font-size: 11pt;"` etc. I'll strip all `style` attributes, and keep the tags that don't have styles, or just remove `` entirely and keep the text. The simplest approach: extract all visible text, and re-markup using only `
`, `
`, ``, ``, `- `, ``, ``. I'll strip ``, `` maybe keep, `` keep. Actually, the rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't say no ``, but `` with `lang` might be okay. To be safe, I'll remove all `` tags and keep their inner text. I'll also remove `style` attributes from all tags. I'll keep `` and `` as they are not inline styles. I'll keep ``, `
`, ``, ``, `- `.
Let's parse the original text mentally and structure it:
Original text chunks (simplified):
- `
Contexte
` -> "Contexte"
- `L’Afrique de l’Ouest et centrale fait face...
` -> long paragraph
- `...
` (empty/nbsp)
- `...Créé en 2025, le Forum des ONG en Afrique de l’Ouest et centrale (FONGA)...
`
- `...
` (empty)
- `...Afin d'accompagner son développement...
`
- `...Ce que nous recherchons :
`
- `...Le/la Support Manager joue un rôle central...
`
- `...Ce que vous ferez :
`
- `...- ...L'administration, la conformité et la gestion des risques ;
...
`
- `...
` (some empty)
- `...Compétences professionnelles:
`
- `...- ...Gestion financière, budgétaire et conformité (expertise essentielle)
...
`
- `...- ...Expertise confirmée en gestion financière...
...
`
- `...- ...Pilotage des fonctions support
...
`
- `...- ...Expérience dans la supervision...
...
`
- `...- ...Développement institutionnel
...
`
- `...- ...Expérience dans le développement...
...
`
- `...
` -> "
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, no summarizing/rephrasing, if no clear sections just wrap in `
`, return ONLY HTML, no markdown fences/explanation/preamble. 2. **Identify the Source Text:** - The text is a job listing for a "Support Manager" position at "Forum des ONG en Afrique de l’Ouest et centrale (FONGA)". - It contains various formatting tags from the original website (`
`, ``, ``, ``, etc.), French language content, lists, etc.
- I need to extract the actual job content and reformat it into the specified HTML structure, preserving all text word-for-word but removing the original formatting artifacts (like inline CSS, `` maybe kept? Rule says preserve ALL original content word-for-word. But also says no inline styles, no ` ` for intro/general text. I need to decide how to handle ``, ``, etc. The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This means the text content inside tags must be preserved exactly. The tags themselves can be replaced per the new schema. So I should keep the text, but use the new tags (` `, ` for introductory paragraphs and general text. Use tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble."
So I need to transform the given text into:
- ` ` or ` ... Use tags. Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Wait, there's a conflict between the very first user prompt and the later "Rules" section. The first prompt says: "You are a job listing editor. You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format. REMOVE all of the following: ... KEEP and STRUCTURE: - Job title - Company/Organisation name - Location - Job description and responsibilities - Requirements/qualifications - How to apply / application instructions - Salary (if mentioned) - Deadline / closing date - Job ID / reference number - Contract type / level - Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text."
Then the user says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML. Rules: - Use for introductory paragraphs and general text - Use tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble."
And then provides the job description text.
I need to follow the most specific rules. The second set seems to be the actual formatting task rules, while the first is a general description. The rules say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is very strict. It also says "Use `, ``, ` `, ` `, ` Contexte L’Afrique de l’Ouest et centrale fait face... ... ...Créé en 2025, le Forum des ONG en Afrique de l’Ouest et centrale (FONGA)... ... ...Afin d'accompagner son développement... ...Ce que nous recherchons : ...Le/la Support Manager joue un rôle central... ...Ce que vous ferez : ... ...Compétences professionnelles: ... 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.
`. It doesn't say remove ``, ``, etc. But the output format specifies `` for headers, `
`, `
`, `
`, `
tags". So ``, `` are fine. I'll use them sparingly or as needed to preserve emphasis, but the main structure must follow the rules.
Let me re-read carefully: "Use ` for section headers (Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - but the text might not have exact section headers labeled as such. I need to identify natural sections and label them with `
`. The rule says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This implies I should create those sections if they exist, or use what's there. The original text has sections like "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", etc. I'll map them to the suggested headers, but must preserve all content word-for-word. I should not rename or rephrase, but I can wrap section titles as `
` and then the content below in `
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This might mean I should use those exact headers if those sections exist, or similar. I'll interpret it as: when there's a natural section break, use `
` for the heading, and then the content below in appropriate tags. The headings themselves should be the section labels, but I must preserve original content. There's a tension: "Preserve ALL original content word-for-word" vs "Use
for section headers". I think the intent is: the text content inside must not be changed, but I can structure it with headers. The headers themselves might be derived from the text, but I should probably use the exact phrases that serve as section dividers, or create reasonable ones. Looking at the text, it has "Contexte", "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", "En complément", "Compétences souhaitées". I'll use those as `
` text, or map to the suggested ones. But the rule says "Preserve ALL original content word-for-word". If I change "Ce que nous recherchons" to "Responsibilities", that's rephrasing. So I should keep the original heading text exactly, but wrap it in `
`. That makes sense.
- Let's outline the structure I'll create:
- The job title isn't explicitly given at the very top, but there's context. I might need to infer or just start from the text. The text starts with "Contexte". There's no explicit "Job Title" line, but I can treat the whole thing as a job listing. I'll perhaps add a `
` for the role if I can identify it, but must preserve content. Actually, the instruction says "Keep and Structure: Job title, Company/Organisation name, Location, Job description and responsibilities, Requirements/qualifications, How to apply / application instructions, Salary (if mentioned), Deadline / closing date, Job ID / reference number, Contract type / level". But then it says "Your job is to extract ONLY the actual job information and return it in a clean, readable format." and later "Return ONLY the cleaned job text. Do not add any commentary...". The rules section says "Rules: Use
... Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - Use
tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This implies I should structure the content into those sections using `
`, but the actual header text should probably be the original section titles, or the suggested ones. Given "Preserve ALL original content word-for-word", I think I should keep the original section headings as they appear in the text, but wrap them in `
`. However, the original text has headings like "Contexte", "Ce que nous recherchons", "Ce que vous ferez", "Compétences professionnelles", "En complément", "Compétences souhaitées". These are in French. The suggested headers are in English: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". There's a mismatch. I need to decide: do I translate/rephrase headers to English, or keep French? The rule says "Preserve ALL original content word-for-word". That likely includes the heading text. So I should keep the French headings exactly, but mark them as `
`. However, the example gives English headers. This is tricky.
Let me re-read carefully: "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The "e.g." means "for example". It's suggesting what kinds of headers to use, not that I must exactly use those English terms. Given the preservation rule, I should use the actual section headers from the text, wrapped in `
`. But the text's headers are in French. I'll keep them in French, as translating would be removing/rephrasing.
Another issue: the original text has a lot of inline CSS (`style="line-height: normal; margin-bottom: 0cm;"`, `style="text-align: justify;"`, `style="font-size: 11pt;"`, `style="color: black;"`, `style="background-color: yellow;"`). The rules say "No CSS classes, no inline styles, no
tags". I must strip all `style` attributes. Also remove ``, ``? The rule says "Preserve ALL original content word-for-word". I think the visible text must be preserved, but the markup can be restructured. I'll keep `` and `` as they are semantic HTML and not "inline styles". Actually, `` is deprecated/obsolete in HTML5, but still valid. The rule says "No CSS classes, no inline styles". `` has no style by default, so it's fine. I'll keep them. But the `style` attributes on ``, `
`, `
`, `
tags". It doesn't say no ``, but `` with `lang` might be okay. To be safe, I'll remove all `` tags and keep their inner text. I'll also remove `style` attributes from all tags. I'll keep `` and `` as they are not inline styles. I'll keep ``, `
` -> long paragraph
- ``, `
`, `
...
`
- `...
`
- `...
`
- `...
`
- `...
`
- `...
`
- `...
`
- `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.