AF
Communication & Multimedia Officer
African Population and Health Research Center (APHRC)
Job Description
Here's a thinking process:
1. **Analyze User Input:**
- **Role:** Job listing editor
- **Task:** Extract ONLY actual job information, return clean, readable format
- **Remove:** Social sharing text, author bylines, "You may also like", navigation, comments, ads, cookie notices, duplicate text, category labels, stray numbers/formatting artifacts
- **Keep/Structure:** Job title, company, location, description, requirements, how to apply, salary, deadline, job ID, contract type
- **Output:** ONLY the cleaned job text, no commentary, no markdown fences, no headers/explanations
Wait, the user actually provided a specific instruction set and then a "Job description" section. The prompt says:
"You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML."
Then there are rules for HTML formatting.
Then: "Job description:" followed by the actual text.
Then: "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
But earlier in the prompt, it said: "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."
There's a conflict: one part says return clean text, another says return clean semantic HTML with specific tags (,
,
, - ). The latter part seems to override/be the actual task, as it gives detailed HTML formatting rules.
Let re-read carefully:
- First paragraph: "You are a job listing editor... Your job is to extract ONLY the actual job information and return it in a clean, readable format." Then lists what to remove/keep.
- Then: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Gives rules for
,
, - , no CSS/inline/styles//
, preserve ALL original content word-for-word, no summarization.
- Then: "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
- Then: "Job description:" with the text.
- Then: "Return ONLY the cleaned job text. Do not add any commentary..." Wait, this seems like a repeat or conflicting instruction.
Actually, the very last line says: "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." But the preceding section says to format as HTML. I need to resolve this.
Looking at the structure: The user prompt starts with a role description, then gives rules, then the job text, then says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then at the very end, it says "Return ONLY the cleaned job text. Do not add any commentary..." This might be a copy-paste artifact.
Given the explicit rules: "format it as clean semantic HTML", "Use for introductory paragraphs...", "Use
for section headers", "Use - for list items", "No CSS classes, no inline styles, no s, no
tags", "Preserve ALL original content word-for-word", "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
I should follow the HTML formatting rules. The last line might be a remnant. I'll output clean semantic HTML as specified, without markdown fences, just raw HTML. But wait: "No markdown fences" means I shouldn't wrap it in ```html ```. I should just output the HTML text directly.
However, there's also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word from the job description, but structured into HTML tags as specified.
Let's examine the job description text. It has:
- Intro about APHRC
- Job title/role: "Communication & Multimedia Officer"
- Location: "Dakar, Senegal" (implied, "Based in Dakar")
- Responsibilities section with bullet points
- Qualifications, Experience, and Skills section with bullet points
- Language Requirements
I need to structure this into HTML using ,
, - . I should identify section headers. The text has "Key Responsibilities:", "Qualifications, Experience, and Skills:", "Language Requirements:". The rules say to use
for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So I should map the existing headers to these, or create appropriate ones.
Important: "Preserve ALL original content word-for-word". So I must not paraphrase, but I can wrap text in tags. The text content inside tags must be exact.
Let's outline the structure:
- Intro paragraph(s) about APHRC
- Job title: should be prominent. Maybe as or first line. The rules say use for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
. To be safe, I'll use
for "Communication & Multimedia Officer" as the title, then
for intro, then
for "Key Responsibilities", then - for each bullet. Then
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
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 📝
,
, - , no CSS/inline/styles//
, preserve ALL original content word-for-word, no summarization.
- Then: "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
- Then: "Job description:" with the text.
- Then: "Return ONLY the cleaned job text. Do not add any commentary..." Wait, this seems like a repeat or conflicting instruction.
Actually, the very last line says: "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." But the preceding section says to format as HTML. I need to resolve this.
Looking at the structure: The user prompt starts with a role description, then gives rules, then the job text, then says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then at the very end, it says "Return ONLY the cleaned job text. Do not add any commentary..." This might be a copy-paste artifact.
Given the explicit rules: "format it as clean semantic HTML", "Use for introductory paragraphs...", "Use
for section headers", "Use - for list items", "No CSS classes, no inline styles, no s, no
tags", "Preserve ALL original content word-for-word", "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
I should follow the HTML formatting rules. The last line might be a remnant. I'll output clean semantic HTML as specified, without markdown fences, just raw HTML. But wait: "No markdown fences" means I shouldn't wrap it in ```html ```. I should just output the HTML text directly.
However, there's also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word from the job description, but structured into HTML tags as specified.
Let's examine the job description text. It has:
- Intro about APHRC
- Job title/role: "Communication & Multimedia Officer"
- Location: "Dakar, Senegal" (implied, "Based in Dakar")
- Responsibilities section with bullet points
- Qualifications, Experience, and Skills section with bullet points
- Language Requirements
I need to structure this into HTML using ,
, - . I should identify section headers. The text has "Key Responsibilities:", "Qualifications, Experience, and Skills:", "Language Requirements:". The rules say to use
for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So I should map the existing headers to these, or create appropriate ones.
Important: "Preserve ALL original content word-for-word". So I must not paraphrase, but I can wrap text in tags. The text content inside tags must be exact.
Let's outline the structure:
- Intro paragraph(s) about APHRC
- Job title: should be prominent. Maybe as or first line. The rules say use for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
. To be safe, I'll use
for "Communication & Multimedia Officer" as the title, then
for intro, then
for "Key Responsibilities", then - for each bullet. Then
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
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 📝
/
, preserve ALL original content word-for-word, no summarization. - Then: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." - Then: "Job description:" with the text. - Then: "Return ONLY the cleaned job text. Do not add any commentary..." Wait, this seems like a repeat or conflicting instruction. Actually, the very last line says: "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." But the preceding section says to format as HTML. I need to resolve this. Looking at the structure: The user prompt starts with a role description, then gives rules, then the job text, then says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then at the very end, it says "Return ONLY the cleaned job text. Do not add any commentary..." This might be a copy-paste artifact. Given the explicit rules: "format it as clean semantic HTML", "Use for section headers", "Use
, preserve ALL original content word-for-word, no summarization. - Then: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." - Then: "Job description:" with the text. - Then: "Return ONLY the cleaned job text. Do not add any commentary..." Wait, this seems like a repeat or conflicting instruction. Actually, the very last line says: "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." But the preceding section says to format as HTML. I need to resolve this. Looking at the structure: The user prompt starts with a role description, then gives rules, then the job text, then says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then at the very end, it says "Return ONLY the cleaned job text. Do not add any commentary..." This might be a copy-paste artifact. Given the explicit rules: "format it as clean semantic HTML", "Use
for introductory paragraphs...", "Use
for section headers", "Use - for list items", "No CSS classes, no inline styles, no s, no
tags", "Preserve ALL original content word-for-word", "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
I should follow the HTML formatting rules. The last line might be a remnant. I'll output clean semantic HTML as specified, without markdown fences, just raw HTML. But wait: "No markdown fences" means I shouldn't wrap it in ```html ```. I should just output the HTML text directly.
However, there's also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word from the job description, but structured into HTML tags as specified.
Let's examine the job description text. It has:
- Intro about APHRC
- Job title/role: "Communication & Multimedia Officer"
- Location: "Dakar, Senegal" (implied, "Based in Dakar")
- Responsibilities section with bullet points
- Qualifications, Experience, and Skills section with bullet points
- Language Requirements
I need to structure this into HTML using ,
, - . I should identify section headers. The text has "Key Responsibilities:", "Qualifications, Experience, and Skills:", "Language Requirements:". The rules say to use
for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So I should map the existing headers to these, or create appropriate ones.
Important: "Preserve ALL original content word-for-word". So I must not paraphrase, but I can wrap text in tags. The text content inside tags must be exact.
Let's outline the structure:
- Intro paragraph(s) about APHRC
- Job title: should be prominent. Maybe as or first line. The rules say use for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
. To be safe, I'll use
for "Communication & Multimedia Officer" as the title, then
for intro, then
for "Key Responsibilities", then - for each bullet. Then
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
s, no
tags", "Preserve ALL original content word-for-word", "Return ONLY the HTML. No markdown fences, no explanation, no preamble." I should follow the HTML formatting rules. The last line might be a remnant. I'll output clean semantic HTML as specified, without markdown fences, just raw HTML. But wait: "No markdown fences" means I shouldn't wrap it in ```html ```. I should just output the HTML text directly. However, there's also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word from the job description, but structured into HTML tags as specified. Let's examine the job description text. It has: - Intro about APHRC - Job title/role: "Communication & Multimedia Officer" - Location: "Dakar, Senegal" (implied, "Based in Dakar") - Responsibilities section with bullet points - Qualifications, Experience, and Skills section with bullet points - Language Requirements I need to structure this into HTML using,
tags", "Preserve ALL original content word-for-word", "Return ONLY the HTML. No markdown fences, no explanation, no preamble." I should follow the HTML formatting rules. The last line might be a remnant. I'll output clean semantic HTML as specified, without markdown fences, just raw HTML. But wait: "No markdown fences" means I shouldn't wrap it in ```html ```. I should just output the HTML text directly. However, there's also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word from the job description, but structured into HTML tags as specified. Let's examine the job description text. It has: - Intro about APHRC - Job title/role: "Communication & Multimedia Officer" - Location: "Dakar, Senegal" (implied, "Based in Dakar") - Responsibilities section with bullet points - Qualifications, Experience, and Skills section with bullet points - Language Requirements I need to structure this into HTML using
,
, - . I should identify section headers. The text has "Key Responsibilities:", "Qualifications, Experience, and Skills:", "Language Requirements:". The rules say to use
for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So I should map the existing headers to these, or create appropriate ones.
Important: "Preserve ALL original content word-for-word". So I must not paraphrase, but I can wrap text in tags. The text content inside tags must be exact.
Let's outline the structure:
- Intro paragraph(s) about APHRC
- Job title: should be prominent. Maybe as or first line. The rules say use for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
. To be safe, I'll use
for "Communication & Multimedia Officer" as the title, then
for intro, then
for "Key Responsibilities", then - for each bullet. Then
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So I should map the existing headers to these, or create appropriate ones.
Important: "Preserve ALL original content word-for-word". So I must not paraphrase, but I can wrap text in tags. The text content inside tags must be exact.
Let's outline the structure:
- Intro paragraph(s) about APHRC
- Job title: should be prominent. Maybe as or first line. The rules say use for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
for section headers. Job title might be or just text. Since it's not a section header per se, but I could use for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
for "Communication & Multimedia Officer". Or keep it as paragraph. The rules: "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
for those named sections. Job title could be too, but not required. I'll make the job title an or maybe the first
or maybe the first
. To be safe, I'll use
for "Communication & Multimedia Officer" as the title, then
for intro, then
for "Key Responsibilities", then - for each bullet. Then
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
for "Qualifications, Experience, and Skills", then - . Then
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
... etc.
But the rule says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so Key Responsibilities
is fine.
Similarly, "Qualifications, Experience, and Skills:" is a header. I'll use Qualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe as Qualifications, Experience, and Skills
.
"Language Requirements:" - Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in
.
Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it.
Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe . The rules don't specify where to put title, but say use
for section headers. I'll use for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as .
Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
Qualifications, Experience, and Skills
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
Language Requirements
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
Wait, the rule says "No CSS classes, no inline styles, no s, no
tags". I'm not using any of those. I'm using ,
,
, - . Good.
"Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash.
Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases.
Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly.
One thing: the source has "3-5 years". I'll keep as is.
Also, the source has "(an added advantage)." I'll keep.
Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence.
But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow?
Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble."
Then "Job description: [text]". Then "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."
This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences.
However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML.
Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded.
I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
for "Language Requirements", then
or
- for the three language points.
But the rule says "Preserve ALL original content word-for-word". So I need to include the bullet points exactly as they are, including dashes or not? The text has "- Support the implementation..." etc. I should keep the dashes or remove them? The rule says preserve content word-for-word, but also "Use
- for list items (duties, requirements, qualifications, skills)". So I should convert the bullet points to
- items, and the text inside should be the original text without the dash, or with it? "Preserve ALL original content word-for-word" suggests I shouldn't omit any words, but the dash might be considered formatting. I'll include the text after the dash, or keep the dash as part of the text. To be safe, I'll include the exact text as given, maybe without the leading dash if it's not part of the content, but the rule says word-for-word. I think including the text content exactly as is, and the dash is a formatting artifact. The prompt earlier said "Remove... Stray numbers or formatting artifacts". So I should remove dashes, bullets, etc. that are not part of the actual job content. But the bullet list items' text should be preserved. I'll remove the dash and any leading whitespace, and just put the sentence content.
Let's check the exact text:
"Key Responsibilities:
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
..."
I'll structure as:
Key Responsibilities
- Support the implementation of WARO's communications and visibility strategy. ... etc. But the rule says "Use
- Support the implementation of WARO's communications and visibility strategy.
- Assist in executing communication plans for research projects, events, and institutional milestones.
- Draft and edit communication materials primarily in French and, where required, in English, including press releases, blog posts, website content, newsletters, and social media messaging.
- Support preparation of media kits and assist in responding to press inquiries.
- Assist in maintaining relationships with local and regional media contacts.
- Ensure that all communication materials comply with APHRC brand guidelines and project donor visibility requirements.
- Develop and produce high-quality multimedia content, including: end-to-end video production, high-quality photography, infographics and data visualizations, animations and motion graphics, design of PowerPoint presentations and branded merchandise.
- Design visually compelling materials for digital and print use, including brochures, banners, reports, social media graphics, and project briefs.
- Adapt and optimize content for multiple platforms (LinkedIn, X/Twitter, YouTube, websites, newsletters).
- Support webinar production and digital knowledge-sharing products.
- Provide multimedia, audiovisual and branding support for project activities, high-level meetings and stakeholder events.
- Maintain and organize multimedia archives (photo/video databases) for institutional knowledge management.
- Coordinate with vendors (printers, designers, event service providers) when necessary.
- Collaborate closely with WARO researchers, program teams, and APHRC HQ Policy, Engagement, and Communications (PEC) teams.
- Contribute to documentation of major initiatives and communication reporting.
- Bachelor's degree in Communications, Journalism, Multimedia, Graphic Design, Digital Media, Visual Arts, or a related field.
- Additional certification in photography, videography, digital storytelling, or multimedia production, and an accompanying portfolio.
- 3-5 years of relevant professional experience in communication, multimedia production, digital media, or a related field.
- Demonstrated experience in producing communication materials for diverse audiences (technical, policy, public).
- Experience in media engagement and institutional visibility initiatives is an advantage.
- Proficiency in Adobe Creative Suite (Photoshop, Illustrator, InDesign, Premiere Pro, After Effects or similar tools).
- Strong skills in photography and videography, including equipment handling and post-production editing.
- Ability to design visually engaging materials for digital and print formats, and strong PowerPoint design and presentation formatting skills.
- Familiarity with social media content creation, digital publishing tools, social media insights, and web metrics.
- Basic understanding of web content management systems (an added advantage).
- Excellent professional proficiency in French (written and spoken) – required.
- Functional working proficiency in English (written and spoken) – required.
- Ability to support the production and adaptation of communication materials for Francophone and Anglophone audiences in West and Central Africa.
- . Good. "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". I need to make sure I didn't change any words. I need to check each bullet and ensure the text inside
- is exactly as in the source, minus the dash. The source has "- Support the implementation...". I'll put "Support the implementation..." without the dash. Is the dash considered part of the content? The prompt earlier said "Remove... Stray numbers or formatting artifacts". So removing dashes is fine. But "word-for-word" might mean the textual content, not formatting characters. I think it's safe to remove the dash. Also, the source has "– required." with an en dash. I'll keep it as is, or normalize to hyphen? "Preserve ALL original content word-for-word" suggests I should keep the exact characters. I'll keep the en dash or replace with a regular hyphen? To be safe, I'll keep the text exactly as is, including punctuation. But in HTML, I can just type the text. I'll copy-paste the exact phrases. Let's check the exact text for language requirements: "Excellent professional proficiency in French (written and spoken) – required." I'll include that exactly. One thing: the source has "3-5 years". I'll keep as is. Also, the source has "(an added advantage)." I'll keep. Now, about the "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should output just the HTML code, no ```html fence. But wait: the prompt also says at the very end: "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." This is confusing. Which one to follow? Let's read the very beginning of the prompt: "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." Then it lists remove/keep. Then "REMOVE all of the following... KEEP and STRUCTURE: ..." Then "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 next section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules for HTML tags. Then "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then "Job description: [text]". Then "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." This is likely a test where the final instruction overrides, or they want HTML. Given the detailed HTML rules, I think they want HTML output. The last "Return ONLY the cleaned job text..." might be a leftover from a previous iteration. I'll follow the HTML formatting rules, as they are more specific and include the job description text. I'll output pure HTML without markdown fences. However, to cover bases, I could output just the cleaned text without HTML tags, but the rules explicitly say "format it as clean semantic HTML" and give tag rules. I'll go with HTML. Let's structure the HTML carefully, ensuring all content is preserved word-for-word. I'll avoid adding any "Job Title:" or "Company:" labels unless they are in the text. The text already has the organization name and role info embedded. I need to make sure I don't include any remove-listed items. The text doesn't seem to have social sharing, bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It lists "Key Responsibilities" as an example, so
Key Responsibilities
is fine. Similarly, "Qualifications, Experience, and Skills:" is a header. I'll useQualifications, Experience and Skills
or keep exact wording. The rule says preserve content word-for-word, but the header itself is part of the structure. I think I should keep the header text as given, maybe asQualifications, Experience, and Skills
. "Language Requirements:" -Language Requirements
Intro text: "The African Population and Health Research Center (APHRC) is a premier research-to-policy institution..." etc. This is introductory paragraph(s). I'll wrap in. Location: "Based in Dakar, Senegal" is mentioned. I should include location. The rules say "Keep and Structure: Location". I'll add it or include it in the text. The text already says "Based in Dakar". I might need to explicitly state location, but the rule says preserve all original content word-for-word. So I shouldn't add "Location: Dakar" if it's not there, but I can include the existing location info. The text has "Based in Dakar, the Communication and Multimedia Officer will contribute...". I'll keep it. Job title: "Communication & Multimedia Officer". I'll make it
Communication & Multimedia Officer
or maybe. The rules don't specify where to put title, but say use
for section headers. I'll use
for the title as it's common, but if it causes conflict with "section headers", I'll use
. To be safe, I'll put it as a paragraph or as
. Given the examples include "Key Duties", "About the Role", I'll treat the title as
. Let's map out the full HTML structure mentally:
Communication & Multimedia Officer
The African Population and Health Research Center (APHRC) is a premier research-to-policy institution that generates evidence, strengthens research and related capacity in the African Research and Development (R&D) ecosystem, and engages policymakers to inform action on health and development. APHRC is African-founded, African-led, and Africa-based, with headquarters in Nairobi, Kenya, and a West Africa Regional Office (WARO) in Dakar, Senegal. APHRC seeks to drive change by developing strong African research leadership and promoting evidence-informed decision-making (EIDM) across sub-Saharan Africa. WARO plays a strategic role in generating policy-relevant evidence, strengthening research capacity, and engaging governments and regional institutions in West and Central Africa.
Key Responsibilities
Qualifications, Experience, and Skills
Language Requirements
s, no
tags". I'm not using any of those. I'm using,
,
- ,
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.