Livestock Officer – Uganda Climate Smart Agricultural Transformation Project (UCSATP)
Worldvision
Job Description
for intro paragraphs and general text. Use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use - for list items (duties, requirements, qualifications, skills). No CSS classes, no inline styles, no tags, no
tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in tags. Return ONLY the HTML. No markdown fences, no explanation.
We need to parse the given job description text (which already includes some HTML tags like
,
, , , etc). We must output clean semantic HTML, preserving content word-for-word. We must remove any tags that are not allowed:
, , , , style attributes, etc. We must replace them with appropriate semantic tags: headings for section headers,
for paragraphs,
- for lists.
We must preserve all original content word-for-word, meaning we cannot change the text itself, only the tags. So we need to extract the plain text content (including spaces, punctuation) and then wrap it in appropriate tags.
We need to identify sections: The original text includes:
- Intro paragraph: "With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith."
Then blank line? Then "Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!"
Then empty .
Then "Employee Contract Type:" then "Local - Fixed Term Employee (Fixed Term)" then then
Job Description:
then paragraph about World Vision Uganda seeking to partner...
Then blank .
Then paragraph about Uganda Climate Smart Agricultural Transformation Project...
Then blank .
Then "To implement this project, World Vision Uganda is prepositioning staffing needs, who will be on standby for hire, dependent on WVU being awarded the consultancy."
Then blank .
Then "Purpose of the role:" then paragraph about Livestock Officer.
Then "
" then paragraph about Livestock Officer will work closely...
Then blank .
Then "Reports to: Project Manager"
Then "Duty station: Adjumani / Lamwo (Refugee Settlement and Host Community Areas)."
Then blank .
Then "Key Result Areas: " then subsections with bold headings: "Technical Program Implementation" then list items.
Then "Animal Health and Disease Management" then list.
Then "Capacity Building and Community Engagement" then list.
Then "Refugee and Host Community Programming" then list.
Then "Monitoring, Evaluation and Reporting" then list.
Then "Stakeholder Coordination" then list.
Then "Compliance and Safeguarding" then list.
Then blank .
Then "Qualifications and Experience" then "Education" then paragraph "Applicants must possess:" then - A Bachelor of Science Degree in Agriculture from a recognized institution.
then "Additional training or certification in Animal Production, Animal Health, Veterinary Extension, Livestock Management, or Climate Smart Agriculture will be an added advantage. " then blank .
Then "Experience" then with items: first item has The ideal candidate should have:
then list items.
Then blank .
Then "Required Skills and Competencies" then "Technical Competencies" then list.
Then "Core Competencies" then list.
Then "Communication Skills" then list.
Then "Computer Skills" then list.
Then blank .
Then "Key Performance Indicators (KPIs)" then paragraph "The Livestock Officer shall be assessed based on:" then list.
Then blank .
Then "Equal Opportunity Statement" then paragraph about World Vision Uganda is an equal opportunity employer...
Then blank .
Then "Advert start date: 15th July, 2026." then "Advert end date: 20th July, 2026." then blank then then Applicant Types Accepted:
then "Local Applicants Only".
We need to produce HTML with for intro paragraphs and general text. Use
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). However, the original text uses various headings like "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", "Key Result Areas:", then subheadings like "Technical Program Implementation", etc. Also "Qualifications and Experience", "Education", "Experience", "Required Skills and Competencies", "Technical Competencies", "Core Competencies", "Communication Skills", "Computer Skills", "Key Performance Indicators (KPIs)", "Equal Opportunity Statement", "Advert start date:", "Advert end date:", "Applicant Types Accepted:".
We need to decide which of these should be . The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat headings that correspond to those categories as . Others like "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", maybe treat as
with bold? But we cannot use tags; we must preserve content word-for-word, but we cannot keep tags because they are not allowed? The instruction says: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we must keep the exact text, including any bold markup? But we also must not use tags because they are not allowed? The rules say: Use
for introductory paragraphs and general text. Use
for section headers. Use - for list items. No CSS classes, no inline styles, no s, no
tags. It does not explicitly forbid tags, but it says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid or . However, we are to return clean semantic HTML. Using is not semantic; better to avoid. But the instruction to preserve original content word-for-word could conflict. Usually in such tasks, we strip formatting tags and just keep the text, then apply semantic tags. The phrase "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" likely means we should not change the actual wording, but we can change tags. So we can remove , ,
, etc and just keep the text. That seems acceptable.
Thus we need to output plain text wrapped in appropriate tags.
We need to decide structure: Probably start with an introductory paragraph(s) about the organization. Then maybe a heading for "Employee Contract Type:"? Not sure if that qualifies as a section header. The examples given: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So "Employee Contract Type:" is not in that list; maybe treat as with bold? But we cannot keep bold. Could treat as
with the text "Employee Contract Type: Local - Fixed Term Employee (Fixed Term)". That's fine.
Similarly "Job Description:" could be a heading? Not in list; maybe treat as
.
But we could also treat "Job Description:" as a heading
because it's a section header. However the examples didn't include it, but it's still a section header. The instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The "e.g." suggests those are examples, not exhaustive. So we can treat any clear section header as . So we can treat "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", "Key Result Areas:", "Qualifications and Experience", "Education", "Experience", "Required Skills and Competencies", "Technical Competencies", "Core Competencies", "Communication Skills", "Computer Skills", "Key Performance Indicators (KPIs)", "Equal Opportunity Statement", "Advert start date:", "Advert end date:", "Applicant Types Accepted:" as . However, some are subheadings under "Key Result Areas:" like "Technical Program Implementation", "Animal Health and Disease Management", etc. Those could also be or maybe treat as as well. But we need to avoid too many headings; but it's okay.
We also need to wrap list items in - . The original already has
- for many lists. We'll keep the list items but remove any inside them? We must preserve text word-for-word, but we can strip tags inside list items as they are formatting. The text inside list items includes bold phrases like "Lead the implementation..."? Actually the list items have no bold inside except maybe some? Let's check: In the original, list items are like "
- Lead the implementation of climate-smart livestock production interventions within project target areas.
" no bold. In some lists, there are bold inside? For example under "Animal Health and Disease Management": "- Support livestock disease surveillance, prevention, and control activities.
" no bold. So fine.
In qualifications, there is "- A Bachelor of Science Degree in Agriculture from a recognized institution.
" That includes . We need to preserve the text word-for-word, but we can remove the tags and keep the text "A Bachelor of Science Degree in Agriculture". That would change the content? The bold is formatting, not content. The instruction says preserve original content word-for-word; bold is not content, it's markup. So we can drop it.
Similarly there is "Additional training or certification in Animal Production, Animal Health, Veterinary Extension, Livestock Management, or Climate Smart Agriculture will be an added advantage. " That's a sentence not in a list; we can drop .
Also there are tags around headings like "Purpose of the role:" etc. We'll drop them.
Also there is "Reports to: Project Manager" etc.
Also there is "Duty station: Adjumani / Lamwo (Refugee Settlement and Host Community Areas)."
Also there is "Key Result Areas: " etc.
Also there is "Qualifications and Experience" etc.
Also there is "Education" etc.
Also there is "Experience" etc.
Also there is "Required Skills and Competencies" etc.
Also there is "Technical Competencies" etc.
Also there is "Core Competencies" etc.
Also there is "Communication Skills" etc.
Also there is "Computer Skills" etc.
Also there is "Key Performance Indicators (KPIs)" etc.
Also there is "Equal Opportunity Statement" etc.
Also there is "Advert start date: 15th July, 2026." etc.
Also there is "Advert end date: 20th July, 2026." etc.
Also there is "Employee Contract Type:" etc.
Also there is "Job Description:" etc.
Also there is "Applicant Types Accepted:" etc.
We'll strip all those tags.
Now we need to decide which headings become . Let's treat any line that ends with a colon (:) as a heading, unless it's part of a sentence. For safety, we can treat the following as :
- Employee Contract Type:
- Job Description:
- Purpose of the role
- Reports to
- Duty station
- Key Result Areas:
- Technical Program Implementation
- Animal Health and Disease Management
- Capacity Building and Community Engagement
- Refugee and Host Community Programming
- Monitoring, Evaluation and Reporting
- Stakeholder Coordination
- Compliance and Safeguarding
- Qualifications and Experience
- Education
- Experience
- Required Skills and Competencies
- Technical Competencies
- Core Competencies
- Communication Skills
- Computer Skills
- Key Performance Indicators (KPIs)
- Equal Opportunity Statement
- Advert start date:
- Advert end date:
- Applicant Types Accepted:
But some of these are subheadings under Key Result Areas; maybe they should be as well. It's okay.
Now we need to wrap paragraphs in
. For text that is not a heading or list item, we wrap in
. For list items, we wrap in
- . Ensure we don't have stray
inside
- (the original had a
inside first experience item: "
The ideal candidate should have:
inside
- . We need to preserve content word-for-word, but we cannot have
inside
- because we are not allowed to add tags? Actually we can keep it if it's original, but we are to output clean semantic HTML; having a
inside
- is not semantic but maybe allowed? The instruction says use
- for list items. It doesn't forbid other tags inside, but we should avoid
inside
- because it's not needed. However we must preserve original content word-for-word; the original had a
tag inside the
- . If we remove it, we are removing original markup, but the content text remains same. The instruction says preserve original content word-for-word — do not add, remove, summarise, or rephrase. That likely refers to the textual content, not the markup. So we can change tags.
Thus we will treat "The ideal candidate should have:" as part of the list item text, not a separate
. So we will output
- The ideal candidate should have:
then subsequent - items.
But note the original structure:
The ideal candidate should have:
- A minimum of five (5) years of practical experience in Climate Smart Agriculture programming, with significant involvement in livestock production systems.
... So the first item is a paragraph inside li. We'll convert to - The ideal candidate should have:
. Then the rest as separate li items.
Now we need to ensure we don't lose any text.
Let's extract the textual content sequentially.
I'll copy the original text and manually extract.
Original:
With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith.
Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!
Employee Contract Type:
Local - Fixed Term Employee (Fixed Term)Job Description:
World Vision Uganda is seeking to partner with Ministry of Agriculture, Animal Industries and Fisheries(MAAIF) to implement the Uganda Climate Smart Agricultural Transformation Project (UCSATP) in the refugee settlements in northern Uganda (Adjumani or Lamwo).
The Uganda Climate Smart Agricultural Transformation Project seeks to transform agricultural production systems among refugee and host communities through climate-smart agriculture while strengthening resilience, livelihoods and food security.
To implement this project, World Vision Uganda is prepositioning staffing needs, who will be on standby for hire, dependent on WVU being awarded the consultancy.
Purpose of the role:
The Livestock Officer will provide technical leadership and field-level support in the implementation of climate-smart livestock production and management interventions under the Uganda Climate Smart Agricultural Transformation Project. The position will focus on improving livestock productivity, animal health, food security, nutrition, household incomes, and resilience among refugee and host communities through sustainable and climate-resilient livestock production systems.
The Livestock Officer will work closely with livestock farmers, community animal health workers, local authorities, and other stakeholders to promote good livestock husbandry practices, disease prevention and control, pasture management, and climate adaptation strategies.
Reports to: Project Manager
Duty station: Adjumani / Lamwo (Refugee Settlement and Host Community Areas).
<
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 ✍️
tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in
tags. Return ONLY the HTML. No markdown fences, no explanation. We need to parse the given job description text (which already includes some HTML tags like
, for paragraphs, Job Description: The ideal candidate should have: Applicant Types Accepted: for intro paragraphs and general text. Use with bold? But we cannot use tags; we must preserve content word-for-word, but we cannot keep tags because they are not allowed? The instruction says: Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we must keep the exact text, including any bold markup? But we also must not use tags because they are not allowed? The rules say: Use for introductory paragraphs and general text. Use with bold? But we cannot keep bold. Could treat as with the text "Employee Contract Type: Local - Fixed Term Employee (Fixed Term)". That's fine.
Similarly "Job Description:" could be a heading? Not in list; maybe treat as .
But we could also treat "Job Description:" as a heading . For text that is not a heading or list item, we wrap in . For list items, we wrap in inside inside first experience item: " The ideal candidate should have: inside inside inside inside tag inside the . So we will output The ideal candidate should have: With 75 years of experience, our focus is on helping the most vulnerable children overcome poverty and experience fullness of life. We help children of all backgrounds, even in the most dangerous places, inspired by our Christian faith. Employee Contract Type: Job Description: World Vision Uganda is seeking to partner with Ministry of Agriculture, Animal Industries and Fisheries(MAAIF) to implement the Uganda Climate Smart Agricultural Transformation Project (UCSATP) in the refugee settlements in northern Uganda (Adjumani or Lamwo). The Uganda Climate Smart Agricultural Transformation Project seeks to transform agricultural production systems among refugee and host communities through climate-smart agriculture while strengthening resilience, livelihoods and food security. To implement this project, World Vision Uganda is prepositioning staffing needs, who will be on standby for hire, dependent on WVU being awarded the consultancy. Purpose of the role: The Livestock Officer will provide technical leadership and field-level support in the implementation of climate-smart livestock production and management interventions under the Uganda Climate Smart Agricultural Transformation Project. The position will focus on improving livestock productivity, animal health, food security, nutrition, household incomes, and resilience among refugee and host communities through sustainable and climate-resilient livestock production systems. Reports to: Project Manager Duty station: Adjumani / Lamwo (Refugee Settlement and Host Community Areas). Get an instant AI match score for this role — free, takes 3 minutes. The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
, , , etc). We must output clean semantic HTML, preserving content word-for-word. We must remove any tags that are not allowed:
, , , for section headers,
" then paragraph about Livestock Officer will work closely...
Then blank .
Then "Reports to: Project Manager"
Then "Duty station: Adjumani / Lamwo (Refugee Settlement and Host Community Areas)."
Then blank .
Then "Key Result Areas: " then subsections with bold headings: "Technical Program Implementation" then list items.
Then "Animal Health and Disease Management" then list.
Then "Capacity Building and Community Engagement" then list.
Then "Refugee and Host Community Programming" then list.
Then "Monitoring, Evaluation and Reporting" then list.
Then "Stakeholder Coordination" then list.
Then "Compliance and Safeguarding" then list.
Then blank .
Then "Qualifications and Experience" then "Education" then paragraph "Applicants must possess:" then
then "Additional training or certification in Animal Production, Animal Health, Veterinary Extension, Livestock Management, or Climate Smart Agriculture will be an added advantage. " then blank .
Then "Experience" then with items: first item has
list.
Then "Core Competencies" then
list.
Then "Communication Skills" then
list.
Then "Computer Skills" then
list.
Then blank .
Then "Key Performance Indicators (KPIs)" then paragraph "The Livestock Officer shall be assessed based on:" then
list.
Then blank .
Then "Equal Opportunity Statement" then paragraph about World Vision Uganda is an equal opportunity employer...
Then blank .
Then "Advert start date: 15th July, 2026." then "Advert end date: 20th July, 2026." then blank then then
for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). However, the original text uses various headings like "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", "Key Result Areas:", then subheadings like "Technical Program Implementation", etc. Also "Qualifications and Experience", "Education", "Experience", "Required Skills and Competencies", "Technical Competencies", "Core Competencies", "Communication Skills", "Computer Skills", "Key Performance Indicators (KPIs)", "Equal Opportunity Statement", "Advert start date:", "Advert end date:", "Applicant Types Accepted:".
We need to decide which of these should be
. The instruction: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat headings that correspond to those categories as
. Others like "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", maybe treat as
for section headers. Use
tags. It does not explicitly forbid tags, but it says "No CSS classes, no inline styles, no
tags". It doesn't forbid or . However, we are to return clean semantic HTML. Using is not semantic; better to avoid. But the instruction to preserve original content word-for-word could conflict. Usually in such tasks, we strip formatting tags and just keep the text, then apply semantic tags. The phrase "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" likely means we should not change the actual wording, but we can change tags. So we can remove , ,
, because it's a section header. However the examples didn't include it, but it's still a section header. The instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The "e.g." suggests those are examples, not exhaustive. So we can treat any clear section header as
. So we can treat "Employee Contract Type:", "Job Description:", "Purpose of the role", "Reports to", "Duty station", "Key Result Areas:", "Qualifications and Experience", "Education", "Experience", "Required Skills and Competencies", "Technical Competencies", "Core Competencies", "Communication Skills", "Computer Skills", "Key Performance Indicators (KPIs)", "Equal Opportunity Statement", "Advert start date:", "Advert end date:", "Applicant Types Accepted:" as
. However, some are subheadings under "Key Result Areas:" like "Technical Program Implementation", "Animal Health and Disease Management", etc. Those could also be
or maybe treat as
as well. But we need to avoid too many headings; but it's okay.
We also need to wrap list items in
. Let's treat any line that ends with a colon (:) as a heading, unless it's part of a sentence. For safety, we can treat the following as
:
- Employee Contract Type:
- Job Description:
- Purpose of the role
- Reports to
- Duty station
- Key Result Areas:
- Technical Program Implementation
- Animal Health and Disease Management
- Capacity Building and Community Engagement
- Refugee and Host Community Programming
- Monitoring, Evaluation and Reporting
- Stakeholder Coordination
- Compliance and Safeguarding
- Qualifications and Experience
- Education
- Experience
- Required Skills and Competencies
- Technical Competencies
- Core Competencies
- Communication Skills
- Computer Skills
- Key Performance Indicators (KPIs)
- Equal Opportunity Statement
- Advert start date:
- Advert end date:
- Applicant Types Accepted:
But some of these are subheadings under Key Result Areas; maybe they should be
as well. It's okay.
Now we need to wrap paragraphs in
Come join our 31,000+ staff working in nearly 100 countries and share the joy of transforming vulnerable children’s life stories!
The Livestock Officer will work closely with livestock farmers, community animal health workers, local authorities, and other stakeholders to promote good livestock husbandry practices, disease prevention and control, pasture management, and climate adaptation strategies.How well do you match?
Tailor your CV for this role
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.