Program Monitoring, Evaluation and Accountability Manager

for intro paragraphs and general text,

for section headers like Responsibilities, Qualifications, etc. Use

• for list items. No
  , no inline styles, no
  . Must not add any extra commentary. Must keep original content exactly as given, including line breaks? We can output HTML with paragraphs and lists. Need to map sections: The job description includes headings like "Purpose of the Position", "MAJOR RESPONSIBILITIES", then subheadings within bold tags etc. We need to use

  for section headers such as Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. The given text uses various bold headings; we need to convert them to

  . Probably each major heading should be wrapped in

  . The instruction: Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to identify those sections in the text and wrap them in

  . The text includes headings like "Purpose of the Position" and "MAJOR RESPONSIBILITIES" etc. Those are not exactly the listed header names but we can treat them as section headers. The instruction says use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should map the headings we have to these categories. For example, "MAJOR RESPONSIBILITIES" corresponds to Responsibilities. "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" corresponds to Requirements? Actually "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" is a header for qualifications/requirements. "Work/Travel requirements" maybe is a separate header. Also "Applicant Types Accepted:" maybe part of How to Apply. The instruction says we must use

  for section headers, but does not require to map exactly; we can just wrap any heading text in

  . Probably we should wrap the headings that are clearly section titles. The text includes many headings. We can wrap each of those in

  . For example:

  Purpose of the Position

  But we need to preserve the original content word-for-word, including the and tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. However we are allowed to wrap headings in

  tags, which adds tags but not change the text. The original content includes the tags like Purpose of the Position. If we wrap that in

  , we are adding a new tag but not altering the inner text. That's permissible because we are not removing or altering the content. The content inside remains same. So we can do

  Purpose of the Position

  . That adds

  around it, but the inner tags remain. That's okay. We must not use

  or
  or inline styles. The original text includes

  etc. Those are style attributes; we must not keep them because we cannot use inline styles. The rule says no inline styles. So we must remove style attributes. But we must preserve content word-for-word? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing style attributes would be removing content? The style attribute is part of the tag, but the textual content inside is empty. The style attribute is not text content; it's an attribute. The instruction about preserving content likely refers to the textual content, not HTML markup. However we must not add or remove content. Removing style attributes might be considered removing markup, but it's not textual content. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we should keep the exact same characters, including tags? But we are required to output clean semantic HTML with specific tags, which may require modifying the markup. There's a conflict. Usually we should keep the textual content but can change tags to meet rules. The instruction says "Use

  for introductory paragraphs and general text". So we need to wrap paragraphs in

  . The original has

  tags already, but also includes

  etc. We can just output

  for empty paragraphs? That would be preserving the empty paragraph? The original has

  which is an empty paragraph. We can output

  as well. That preserves the empty paragraph. But we must not use style attributes. The original has

  . That includes style attribute. If we output

  , we are removing the style attribute, which is part of the markup but not the textual content. The instruction about preserving content likely refers to the textual nodes, not attributes. However to be safe, we could keep the style attribute? But rule says no inline styles. So we must remove it. That would be removing part of the markup, but not textual content. I think it's acceptable. We need to output only HTML, no markdown fences. Let's parse the original text:

  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:

  Purpose of the Position

  Purpose of the Position

  Wait there is duplication? Actually after

  Purpose of the Position

  there is another

  Purpose of the Position

  maybe a mistake. Let's read carefully: The snippet:

  Purpose of the Position

  Purpose of the Position

  Communicate World Vision's Christian ethos and demonstrate a quality of spiritual life that is an example to others.

  MAJOR RESPONSIBILITIES

  Strategic Programme Design, Planning and Quality Assurance

  ... list items ...

  So there are two consecutive

  Purpose of the Position

  lines. We'll keep both. Then after that, there is

  Communicate World Vision's Christian ethos and demonstrate a quality of spiritual life that is an example to others.

  Then

  Then

  MAJOR RESPONSIBILITIES

  Then

  Strategic Programme Design, Planning and Quality Assurance

  (note trailing space). That is a subheading. Then

  ... list items ...

  Then

  Monitoring Systems Strengthening and Performance Measurement

  etc. We need to output HTML with

  for paragraphs and

  for section headers. Which headings should be

  ? The instruction lists examples: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. In the text, we have "MAJOR RESPONSIBILITIES" which is responsibilities. Also "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" maybe qualifications. "Work/Travel requirements" maybe not a listed header but could be "How to Apply"? Not exactly. "Applicant Types Accepted:" maybe part of How to Apply. But we can just wrap headings that are clearly section titles in

  . Let's identify: - "Purpose of the Position" maybe "About the Role"? Could be "About the Role". So we can wrap that in

  . - "MAJOR RESPONSIBILITIES" -> Responsibilities, so

  . - "Strategic Programme Design, Planning and Quality Assurance" maybe a duty category, but not a top-level header. Could be part of responsibilities. Might not need

  . - "Monitoring Systems Strengthening and Performance Measurement" etc. These are subheadings within responsibilities. Probably not need

  . - "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" -> Requirements, so

  . - "Work/Travel requirements" maybe "How to Apply"? Not exactly. Could be "Key Duties"? Not exactly. Might just leave as paragraph. - "Applicant Types Accepted:" maybe part of "How to Apply". Could wrap in

  . But the instruction says use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should map the headings we have to these categories. Let's map: - "Purpose of the Position" -> About the Role (or could be "About the Role"). So wrap in

  . - "MAJOR RESPONSIBILITIES" -> Responsibilities. So wrap in

  . - "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" -> Requirements. So wrap in

  . - "Work/Travel requirements" maybe "How to Apply"? Not exactly; it's more about requirements. Could be "Requirements" but we already have that. Might just leave as paragraph. - "Applicant Types Accepted:" maybe "How to Apply". So wrap in

  . But the instruction says "e.g." meaning these are examples; we can use

  for any section header we deem appropriate. So we can wrap headings that are clearly section titles. Thus we will output:

  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:

  Purpose of the Position

  Communicate World Vision's Christian ethos and demonstrate a quality of spiritual life that is an example to others.

  MAJOR RESPONSIBILITIES

  Strategic Programme Design, Planning and Quality Assurance

  ... list items ...

  ... continue with other headings and lists ... We need to preserve all content exactly, including the duplicate

  Purpose of the Position

  line. So after the first

  Job Description:

  we have two

  Purpose of the Position

  paragraphs. We'll output both before the "Communicate..." paragraph? Actually the original order: after

  Job Description:

  there is

  Purpose of the Position

  then another

  Purpose of the Position

  then

  Communicate ...

  . So we need to keep that order. Thus we will output:

  Job Description:

  Purpose of the Position

  Purpose of the Position

  Communicate World Vision's Christian ethos and demonstrate a quality of spiritual life that is an example to others.

  MAJOR RESPONSIBILITIES

  Strategic Programme Design, Planning and Quality Assurance

  ... list items ...

  But we need to wrap "MAJOR RESPONSIBILITIES" in

  . The original heading is

  MAJOR RESPONSIBILITIES

  . We'll replace that with

  MAJOR RESPONSIBILITIES

  . That adds

  around it, but the inner tags remain. Similarly, "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE" is inside

  REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE

  . We'll wrap that in

  . Also "Work/Travel requirements" is inside

  Work/Travel requirements

  . Could wrap in

  as well? It's a heading but not one of the listed categories. Could be "How to Apply"? Not exactly. Might just leave as

  ... but maybe we should wrap it in

  as it's 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). "Work/Travel requirements" is not exactly one of those, but it's a header. Could treat it as "Requirements". But we already have a requirements header for "REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE". Might not need another. But it's still a heading; we could wrap it in

  as well. However we must not add extra headings that are not present. The original has that heading; we can wrap it in

  to follow rule of using

  for section headers. It's safe. Similarly "Applicant Types Accepted:" is inside

  Applicant Types Accepted:

  . That's a heading; we could wrap in

  . But the instruction says "Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So we should only use

  for those categories. "Applicant Types Accepted:" is not exactly one of those, but it's part of application instructions. Could be considered "How to Apply". So we could wrap it in

  . That seems appropriate. Thus we will wrap headings that correspond to those categories. Let's list all headings in order: 1. Employee Contract Type: (not a job section, just a label) 2. Job Description: (label) 3. Purpose of the Position (duplicate) 4. Communicate ... (paragraph) 5. MAJOR RESPONSIBILITIES (Responsibilities) 6. Strategic Programme Design, Planning and Quality Assurance (maybe a subheading, but part of responsibilities) 7. Monitoring Systems Strengthening and Performance Measurement 8. Evaluation, Research and Evidence Generation 9. Data Quality Management and Information Systems 10. Reporting, Analysis and Evidence Utilization 11. Accountability, Community Feedback and Safeguarding 12. Learning, Adaptive Programming and Improvement 13. Capacity Development and Staff Leadership 14. REQUIRED KNOWLEDGE, SKILL AND EXPERIENCE (Requirements) 15. Work/Travel requirements 16. All successful candidates will be required to undergo a police (criminal background) check... (maybe part of requirements) 17. World Vision International also participates in the Inter-Agency Misconduct Disclosure Scheme... 18. By applying for this role, applicants confirm their understanding... 19. WOMEN ARE STRONGLY ENCOURAGED TO APPLY 20. Applicant Types Accepted: (How to Apply) We need to wrap headings that are section headers: "MAJOR RES

  Translated by AI — may not be perfect

  Show original