Scaling & Innovation Officer I
International Livestock Research Institute (ILRI)
Job Description
for intro paragraphs and general text,
for section headers, - for list items. No , no CSS classes, no inline styles, no
. Must not add any extra text. Must keep original content exactly as given, including HTML tags that are present? The original job description includes some HTML tags like , , , etc. We need to output clean semantic HTML, but we must preserve all original content word-for-word. That includes the existing HTML tags? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the same text exactly, including any HTML tags that are part of the content? The original text includes HTML tags like , , etc. Those are part of the content. We should output them as is? But we also need to format it as clean semantic HTML using ,
, - . The original already uses
, , , - . We need to transform section headers to
. The original uses for headings like "Key Responsibilities:", "Requirements", "Post location", "Terms of Appointment", "How to apply:". We need to replace those with tags. But we must preserve the content word-for-word, meaning we cannot change the text inside the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to would be adding a tag and removing . That might be considered a change. However the rule also says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So we must use for section headers. The original uses tags around headings. We need to replace them with tags, but that would be altering the markup. Is that allowed? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to is adding a tag and removing , which is a change. But maybe we can keep the inside the ? Like Key Responsibilities:
? That would preserve the text "Key Responsibilities:" but adds wrapper. That adds a tag but not altering the text. The rule says do not add, remove, summarise, or rephrase. Adding a wrapper tag might be considered adding, but it's required by the formatting rules. Probably acceptable because we must output clean semantic HTML with for section headers. So we can wrap the heading text in tags, but keep the inner if present. That adds but not change the text. That seems permissible.
We must not add any extra commentary. Just output the HTML.
Let's parse the original content:
It starts with:
The International Livestock Research Institute (ILRI) seeks to recruit a Scaling & Innovation Officer I to support the day-to-day delivery of scaling and innovation activities across CGIAR Initiatives, with a focus on livestock. This is a hands-on, implementation-focused role: the postholder takes ambiguous, half-formed inputs and turns them into usable products, reducing the load on senior staff rather than adding to it. The work spans carrying out scaling activities in the field, working closely with partners, analysing data and evidence, holding quality and evidence standards, and presenting clear plans that move the work forward.
Then:
ILRI is an international organisation working for better lives and better planet through livestock. ILRI’s mission emphasises the interconnections between people, animals, and the environment, aiming to improve the lives of more than 300 million people in low- and middle-income countries through livestock science that supports equitable and resilient livestock systems, ultimately contributing to food systems transformation with climate and environmental benefits. This mission is delivered through two core strategic objectives: co-designing and deploying sustainable, science-based livestock solutions, and leveraging science to inform and influence policy and investment decisions.
ILRI is a member of the CGIAR, a global research alliance that works to transform food, land and water systems in a climate crisis and is the only CGIAR centre dedicated to addressing multiple development challenges through sustainable livestock solutions.
Key Responsibilities:
- Carry out and support the implementation of scaling and innovation activities across the relevant CGIAR Initiatives, in the field and remotely
- Support the preparation and delivery of scaling studies and assessments, applying ILRI and CGIAR scaling tools and frameworks
- Collect, organize, and analyse data from a range of sources, and assess the evidence behind scaling decisions
- Prepare briefs, reports, presentations, and plans of work, and present scaling plans and recommendations to teams and partners
- Build and maintain effective working relationships with project teams, partners, and other stakeholders, and travel regularly to project and partner sites to support delivery and facilitate workshops
- Maintain trackers and documentation, follow up with teams, and ensure activities are completed on time
- Perform any other related duties as may be required
Requirements
- Masters degree in agriculture, development, social or business sciences, data analytics, or relevant field
- Three years relevant experience
- Experience in project delivery, scaling, innovation, stakeholder engagement, or data analysis
- Experience in agricultural or development settings
- Strong, transferable skill set and the ability to learn quickly, rather than deep prior expertise in livestock or a specific scaling method, which will be developed on the job
- Sound organizational and delivery skills, with the ability to manage tasks reliably and meet deadlines with limited supervision
- Sound judgment and the ability to work independently, while knowing when to seek guidance or escalate
- Good analytical skills and attention to detail when working with data and evidence, including the ability to tell strong evidence from weak
- Clear, well-structured writing and confident presentation skills
- Strong interpersonal and communication skills, including in multicultural settings
- Adaptability and a willingness to learn and adjust as priorities and tools evolve
- A practical, hands-on attitude and a strong team orientation
- Proficiency with common digital, presentation, and data tools, and good judgment in using AI tools to accelerate work without weakening accuracy
- Excellent written and spoken English
- Willingness and ability to travel regularly to project and partner sites
Post location: The position will be based in Nairobi, Kenya
Terms of Appointment
This position is at job level HG13 and it is only open to Kenyan nationals. The position is a 3-year contract, renewable subject to satisfactory performance and availability of funding. ILRI offers a competitive salary and benefits package which includes pension, medical and other insurances.
How to apply: Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The position title and reference number REF: IS/2278/2026 should be clearly marked on the subject line of the cover letter.
We thank all applicants for their interest in working for ILRI. Due to the volume of applications, only shortlisted candidates will be contacted.
ILRI does not charge a fee at any stage of the recruitment process (application, interview meeting, processing or training). ILRI also does not concern itself with information on applicants' bank accounts.
To find out more about ILRI, visit our websites at http://www.ilri.org/
We need to output clean semantic HTML. Use for intro paragraphs and general text. Use
for section headers. Use - for list items. No , no inline styles, no
. We must preserve all original content word-for-word. So we cannot change any text. We can wrap headings in but must keep the inner if present. That adds but not change text. That's okay.
We need to decide which paragraphs are intro vs section headers. The original uses for headings. We'll replace each ... with ...
? Actually we need to wrap the heading text in tags. The heading text includes the wrapper. So we can output Key Responsibilities:
. That preserves the tag and its content. That is adding but not removing anything. That's okay.
Similarly for "Requirements", "Post location", "Terms of Appointment", "How to apply:". Also maybe "Key Responsibilities:" is a heading. Also "Requirements" is a heading. "Post location" is a heading. "Terms of Appointment" is a heading. "How to apply:" is a heading.
We also have a
at the end. That's a paragraph with inline style, which is not allowed (no inline styles). The rule says no inline styles. So we must remove that
? But we must preserve all original content word-for-word. That includes the style attribute. However the rule also says "No CSS classes, no inline styles, no s, no
tags". So we cannot keep inline style. But we must preserve content word-for-word. Conflict. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But also "No CSS classes, no inline styles, no s, no
tags". So we must remove the inline style but that would be removing content (the style attribute). However the higher priority might be the formatting rules. The instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no s, no
tags". So we must remove the inline style. That is removing part of the content (the style attribute). But the instruction says preserve all original content word-for-word. This is contradictory. In such conflicts, we need to prioritize the explicit formatting rules? The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That seems absolute. But then they also say "No CSS classes, no inline styles, no s, no
tags". So we must remove inline style but that would be removing content. Perhaps we can keep the with the style but that violates "no inline styles". So we must remove the style attribute but keep the rest of the content. That is removing part of the content (the style attribute). But maybe we can keep the
with the style but that is an inline style, which is not allowed. So we must remove it. That means we are removing the style attribute, which is part of the original content. That violates the preserve rule. However the instruction likely expects us to remove it because they explicitly forbid inline styles. So we must remove it, even though it changes content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But they also say "No CSS classes, no inline styles, no
s, no
tags". So we must remove the inline style, which is a removal. This is contradictory. In such cases, we need to follow the higher-level instruction: "Your ONLY job is to format it as clean semantic HTML." The formatting rules include no inline styles. So we must remove it. The preserve rule might be interpreted as preserving the textual content, not the markup attributes? But they said "word-for-word". The style attribute is part of the markup, not text. The textual content inside the is just a non-breaking space? Actually the
contains a non-breaking space character inside. The text content is just a space. That is preserved if we output
(just a space). That would preserve the text content (the space). The style attribute is not text content; it's an attribute. So we can remove the attribute while preserving the text content. That might be acceptable. So we can output
(just a space). That preserves the space character. The style attribute is removed, which is not part of the text content. So we are not removing text, just an attribute. That might be okay.
Thus we will output:
- For each heading, wrap the heading text (including any inner ) in ...
. Keep the inside.
- For list items, keep - items inside
. The original uses with - items indented with tabs. We need to output
then each - item. The content inside
- must be exactly as original, including any inside? In the original, the
- items do not have any inner tags except maybe none. They are plain text. So we output
- Carry out and support the implementation of scaling and innovation activities across the relevant CGIAR Initiatives, in the field and remotely
etc.
- For paragraphs that are not headings, we output ...
as is, preserving the content exactly.
- For the final
, we output
(just a space). That preserves the space character.
- Also there is a line: More ILRI jobs. That's a link with inside. We need to preserve it. Should we keep it as is? The rule says use for intro paragraphs and general text. Use
for section headers. Use - for list items. It doesn't say we cannot use tags. So we can keep tags. The content inside is More ILRI jobs. That is fine.
- The line http://www.ilri.org/ also should be preserved.
- The line
we will output
.
- Also there is a line: How to apply: Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The position title and reference number REF: IS/2278/2026 should be clearly marked on the subject line of the cover letter.
This paragraph contains tags inside. We need to keep them. The heading "How to apply:" is a heading, so we should wrap it in . The original has How to apply: . So we output How to apply:
then the following paragraph? Actually the paragraph includes the tag at the start, then the rest of the text. The heading is part of the paragraph? In the original, they used How to apply: Applicants should send... So the heading is part of the paragraph content. But we need to treat "How to apply:" as a section header, so we should output
How to apply:
followed by the rest of the paragraph? But that would split the paragraph. The original has the heading and then the paragraph text in the same element. The heading is just the tag, then the rest of the text. We could output How to apply:
Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The
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 ✍️
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.
. Must not add any extra text. Must keep original content exactly as given, including HTML tags that are present? The original job description includes some HTML tags like
, , , , etc. Those are part of the content. We should output them as is? But we also need to format it as clean semantic HTML using , , , The International Livestock Research Institute (ILRI) seeks to recruit a Scaling & Innovation Officer I to support the day-to-day delivery of scaling and innovation activities across CGIAR Initiatives, with a focus on livestock. This is a hands-on, implementation-focused role: the postholder takes ambiguous, half-formed inputs and turns them into usable products, reducing the load on senior staff rather than adding to it. The work spans carrying out scaling activities in the field, working closely with partners, analysing data and evidence, holding quality and evidence standards, and presenting clear plans that move the work forward. ILRI is an international organisation working for better lives and better planet through livestock. ILRI’s mission emphasises the interconnections between people, animals, and the environment, aiming to improve the lives of more than 300 million people in low- and middle-income countries through livestock science that supports equitable and resilient livestock systems, ultimately contributing to food systems transformation with climate and environmental benefits. This mission is delivered through two core strategic objectives: co-designing and deploying sustainable, science-based livestock solutions, and leveraging science to inform and influence policy and investment decisions. ILRI is a member of the CGIAR, a global research alliance that works to transform food, land and water systems in a climate crisis and is the only CGIAR centre dedicated to addressing multiple development challenges through sustainable livestock solutions. Key Responsibilities: Requirements Post location: The position will be based in Nairobi, Kenya Terms of Appointment This position is at job level HG13 and it is only open to Kenyan nationals. The position is a 3-year contract, renewable subject to satisfactory performance and availability of funding. ILRI offers a competitive salary and benefits package which includes pension, medical and other insurances. How to apply: Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The position title and reference number REF: IS/2278/2026 should be clearly marked on the subject line of the cover letter. We thank all applicants for their interest in working for ILRI. Due to the volume of applications, only shortlisted candidates will be contacted. ILRI does not charge a fee at any stage of the recruitment process (application, interview meeting, processing or training). ILRI also does not concern itself with information on applicants' bank accounts. To find out more about ILRI, visit our websites at http://www.ilri.org/ for intro paragraphs and general text. Use with the style but that violates "no inline styles". So we must remove the style attribute but keep the rest of the content. That is removing part of the content (the style attribute). But maybe we can keep the with the style but that is an inline style, which is not allowed. So we must remove it. That means we are removing the style attribute, which is part of the original content. That violates the preserve rule. However the instruction likely expects us to remove it because they explicitly forbid inline styles. So we must remove it, even though it changes content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But they also say "No CSS classes, no inline styles, no is just a non-breaking space? Actually the ... for intro paragraphs and general text. Use How to apply: Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The position title and reference number REF: IS/2278/2026 should be clearly marked on the subject line of the cover letter. How to apply: Applicants should send... So the heading is part of the paragraph content. But we need to treat "How to apply:" as a section header, so we should output element. The heading is just the tag, then the rest of the text. We could output Applicants should send a cover letter and CV expressing their interest in the position, what they can bring to the job and the names and addresses (including telephone and email) of three referees who are knowledgeable about the candidate’s professional qualifications and work experience to the Head of People and Culture through our recruitment portal by clicking on "Apply Now" on or before 28 July 2026. The 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. Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call. Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper. We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge. I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa., etc. We need to output clean semantic HTML, but we must preserve all original content word-for-word. That includes the existing HTML tags? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must keep the same text exactly, including any HTML tags that are part of the content? The original text includes HTML tags like
,
,
. The original uses for headings like "Key Responsibilities:", "Requirements", "Post location", "Terms of Appointment", "How to apply:". We need to replace those with
tags. But we must preserve the content word-for-word, meaning we cannot change the text inside the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to
would be adding a tag and removing . That might be considered a change. However the rule also says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So we must use
for section headers. The original uses tags around headings. We need to replace them with
tags, but that would be altering the markup. Is that allowed? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Changing to
is adding a tag and removing , which is a change. But maybe we can keep the inside the
? Like
Key Responsibilities:
? That would preserve the text "Key Responsibilities:" but adds wrapper. That adds a tag but not altering the text. The rule says do not add, remove, summarise, or rephrase. Adding a wrapper tag might be considered adding, but it's required by the formatting rules. Probably acceptable because we must output clean semantic HTML with
for section headers. So we can wrap the heading text in
tags, but keep the inner if present. That adds
but not change the text. That seems permissible.
We must not add any extra commentary. Just output the HTML.
Let's parse the original content:
It starts with:
for section headers. Use
. We must preserve all original content word-for-word. So we cannot change any text. We can wrap headings in but must keep the inner if present. That adds
but not change text. That's okay.
We need to decide which paragraphs are intro vs section headers. The original uses for headings. We'll replace each ... with
...
? Actually we need to wrap the heading text in tags. The heading text includes the wrapper. So we can output
Key Responsibilities:
. That preserves the tag and its content. That is adding but not removing anything. That's okay.
Similarly for "Requirements", "Post location", "Terms of Appointment", "How to apply:". Also maybe "Key Responsibilities:" is a heading. Also "Requirements" is a heading. "Post location" is a heading. "Terms of Appointment" is a heading. "How to apply:" is a heading.
We also have a
tags". So we cannot keep inline style. But we must preserve content word-for-word. Conflict. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But also "No CSS classes, no inline styles, no
tags". So we must remove the inline style but that would be removing content (the style attribute). However the higher priority might be the formatting rules. The instruction says "Your ONLY job is to format it as clean semantic HTML." and "No CSS classes, no inline styles, no
tags". So we must remove the inline style. That is removing part of the content (the style attribute). But the instruction says preserve all original content word-for-word. This is contradictory. In such conflicts, we need to prioritize the explicit formatting rules? The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That seems absolute. But then they also say "No CSS classes, no inline styles, no
tags". So we must remove inline style but that would be removing content. Perhaps we can keep the
tags". So we must remove the inline style, which is a removal. This is contradictory. In such cases, we need to follow the higher-level instruction: "Your ONLY job is to format it as clean semantic HTML." The formatting rules include no inline styles. So we must remove it. The preserve rule might be interpreted as preserving the textual content, not the markup attributes? But they said "word-for-word". The style attribute is part of the markup, not text. The textual content inside the ...
. Keep the inside.
- For list items, keep . The original uses
with
then each
for section headers. Use
. The original has How to apply: . So we output
How to apply:
then the following paragraph? Actually the paragraph includes the tag at the start, then the rest of the text. The heading is part of the paragraph? In the original, they used How to apply:
followed by the rest of the paragraph? But that would split the paragraph. The original has the heading and then the paragraph text in the same How to apply:
How well do you match?
Tailor your CV for this role
Let jobs find you
Add your CV for real matches
You're in.