Health Systems Strengthening Lead

for section headers - Use

• for list items - No CSS classes, no inline styles, no
  s, no
  tags - Preserve ALL original content word-for-word Let me go through each section carefully. Introduction paragraph - keep as

  Contract type - keep as text Job Description header - h4 Key Responsibilities - h4, then list items Technical Quality Assurance - h4, then list items Leadership, Governance, Partnership & System Integration - h4 Monitoring, Evaluation, Accountability and Learning - h4 Grant, Finance and Compliance Management - h4 Documentation and Knowledge Management - h4 Required Education, Training, Certification - h4 Preferred Qualifications - h4 Required Professional Experience - h4 TECHNICAL COMPETENCIES - h4 CORE SKILLS - h4 About the Role - h4 (the World Vision statement) Applicant Types Accepted - h4 Wait, I need to be careful about the "Key Responsibilities" section. It has multiple subsections with percentages. Let me look at this more carefully. The "30% - Project Leadership and Coordination" is a subsection of Key Responsibilities. Then there's "20% - Technical Quality Assurance", etc. These are all under "KEY RESPONSIBILITIES" but with different percentage allocations. Actually, looking at the structure, these percentage allocations seem to be breakdown of responsibilities. They could be treated as sub-sections or just part of the Key Responsibilities list. Since they're all under "KEY RESPONSIBILITIES" and use bullet points, I think they should be treated as list items within the Key Responsibilities section. But the headers like "30% - Project Leadership and Coordination" are bold and seem like sub-headers. Hmm, but the instruction says to use

  for section headers. The bold text like "30% - Project Leadership and Coordination" could be treated as sub-section headers. But that might be overcomplicating it. Let me think about this differently. Actually, looking at the original text, these percentage breakdowns are part of the "Key Responsibilities" section. They appear to be sub-categories of responsibilities. I could either: 1. Treat them as sub-headers (

  or just bold text within the list) 2. Keep them as bold text within list items Since the instructions say to use

  for section headers and

  • for list items, and these percentage headers seem like they could be sub-section headers, I think the cleanest approach would be to treat them as sub-headers. But the instructions don't mention

    . Let me re-read... "Use

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

    is for main section headers. For sub-headers within a section, I should probably just use bold text or maybe

    . But the instructions don't specify

    . Let me just use bold text for the percentage sub-headers within the list, or treat them as separate list items. Actually, I think the cleanest approach is to treat each percentage block as a sub-header within the Key Responsibilities section. Since the instructions only mention

    , I'll use bold text for these sub-headers within the list, or I could make them

    elements. The instructions say "e.g." so they're examples, not exhaustive. Using

    for sub-sections seems reasonable. Wait, let me reconsider. The instructions say "Use

    for section headers". If I use

    for sub-sections, that might violate the spirit of the rule. Let me just use bold text for the percentage sub-headers and keep them as list items. Or I could make them their own list items with bold text. Actually, I think the best approach is: - "KEY RESPONSIBILITIES" →

    - Each percentage block like "30% - Project Leadership and Coordination" → bold text within a list item, or as a sub-header Let me go with treating the percentage blocks as sub-headers using bold text within list items. That keeps it simple and follows the rules. Hmm, but actually, looking more carefully, these percentage blocks ARE sub-sections of the responsibilities. They have their own content. So maybe I should structure them as:

    Key Responsibilities

    • 30% - Project Leadership and Coordination
    • • Lead overall planning...
    ...
    That seems reasonable. The bold text serves as a sub-header within the list. Now let me also handle the "Required Education, Training, Certification" section - this has both required and preferred qualifications mixed in. Looking at the text: "Required Education, Training, Certification" section contains: - MD requirement - Professional registration - Experience requirements - Technical experience - Working knowledge Then "Preferred Qualifications" has: - Partnership Management certification - Organizational Capacity Strengthening certification - Project Management certification - Related professional qualification Then "Required Professional Experience" has the rest. So I need to separate these into two lists under the education section, or keep them together. Actually, looking at the original, "Required Education, Training, Certification" includes both required and some preferred items. But then there's a separate "Preferred Qualifications" section. I'll keep them as they appear in the original text. Let me also note the "About the Role" section - the World Vision statement about safeguarding children. This seems like an important section about the role's values/ethics. I'll include it as a paragraph. And "Applicant Types Accepted: Local Applicants Only" - this is a small section. Let me now construct the HTML: ```html

    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:

    Key Responsibilities

    • 30% - Project Leadership and Coordination
    • • Lead overall planning, implementation, monitoring, and reporting of project activities.
    ...
    ``` Wait, I need to remove the `
    ` and `
    ` empty paragraphs. Also, the `
    ` tags should be removed since we can't use `
    ` tags. Also, I notice the original has `
    ` which is an empty paragraph with inline style. I should remove these. And `

    Job Description:

    ` - I should convert this to just `

    Job Description:

    ` or keep the underline. Actually, the instructions say to preserve content word-for-word. The `` tag is part of the original formatting. Should I keep it? The instructions say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I should keep the `` tags. But wait, the instructions also say "No CSS classes, no inline styles, no
    s, no
    tags". Inline styles are prohibited. So I need to remove `style="text-align:inherit"` and `style="text-align:left"`. Let me also check: the `

    ` is an empty paragraph - I should remove it entirely. OK let me also think about the "About the Role" section. The World Vision statement is quite long. Should I make it a heading? The instructions mention "About the Role" as an example of a section header. This World Vision statement seems to be about the organization's commitment, which could be considered "About the Role" or "Organization Values". I'll make it a paragraph since it's more of a statement than a structured section. Actually, looking at the structure again, after the Core Skills section, there's this long paragraph about World Vision's safeguarding policy. This could be a separate section. Let me call it "About the Role" based on the example given in the instructions. Let me now write out the full HTML: Actually, I realize I need to be more careful. Let me re-read the instructions: "Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" So "About the Role" is explicitly mentioned as an example. The World Vision safeguarding statement could be "About the Role" or "Organization Values". I'll use "About the Role" as the heading. Also, "Applicant Types Accepted" - this could be another section. I'll make it a heading too. Let me also consider: the "Required Education, Training, Certification" section mixes required and preferred items. But there's a separate "Preferred Qualifications" section. I'll keep them as separate sections as they appear in the original. Now, for the percentage sub-headers within Key Responsibilities, I'll use bold text within list items. This preserves the visual hierarchy without using additional heading levels. Let me draft the complete HTML now: ```html

    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:

    Key Responsibilities

    • 30% - Project Leadership and Coordination
    • • Lead overall planning, implementation, monitoring, and reporting of project activities.
    • • Develop annual work plans, procurement plans, and implementation schedules.
    • • Coordinate project implementation across all target districts.
    • • Supervise Project Officers and facilitate performance management.
    • • Ensure timely delivery of project outputs and outcomes.
    • • Coordinate quarterly review and reflection meetings.
    • • FCI hubs, spokes, FBO-owned facilities, government facilities, and community platforms function as a coordinated service delivery network.
    • • Readiness gaps in facilities and communities are systematically identified, ranked by priority, and addressed.
    • • MNCH & Nutrition and HIV & TB services are increasingly delivered through integrated platforms rather than parallel systems.
    • • Functional community–facility referral and back-referral mechanisms are established and used.
    • • Improved continuity of care from community to primary and referral-level facilities.
    • • Improved access to people-centered, equitable, integrated, and quality services.
    • • Continuous quality improvement has become part of routine service delivery.
    • • Facility, FBO, HEW/CHW, and community health workers have the competencies required to deliver integrated services.
    • • Workforce capacity gaps are systematically identified and addressed through targeted capacity development. Functional mentorship, coaching, and supportive supervision systems are established.
    • • Improved provider competency, performance, teamwork, and appropriate task sharing.
    • • Reduced duplication of training and technical support through integrated capacity-strengthening approaches.

    ``` Wait, I need to be careful about the "&" entities. The original text has "&" which is the HTML entity for "&". I should preserve these as-is since the instruction says "Preserve ALL original content word-for-word". Actually, let me reconsider. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". The "&" is part of the original content, so I should keep it. But when I write the HTML, I should write "&" as it appears in the original. Hmm, but actually, in the raw text provided, the "&" appears literally. When I output HTML, I should output "&" to represent the ampersand character. Let me keep them as "&" in the output. Wait, but the user said "You receive a plain-text job description." and then provided HTML-like content with `

    ` tags. So the input already has HTML entities. I should preserve them as they appear. Let me continue with the full structure. I need to handle the "20% - Technical Quality Assurance" section similarly. For the "Technical Quality Assurance" section, the first item is "• Ensure quality implementation of:" followed by sub-items. These sub-items are indented differently. In the original, they appear as separate `

    ` tags. I should treat them as list items under the "Ensure quality implementation of:" parent item. Actually, looking at the structure more carefully: ```

    • Ensure quality implementation of:

    • Support adaptation and contextualization of project materials.

    • Ensure safeguarding, disability inclusion, gender, and conflict sensitivity standards are maintained.

    ... ``` These are nested list items. In HTML, I could either: 1. Make them all top-level list items (losing the nesting) 2. Use nested lists Since the instructions don't mention nested lists, and the nesting is implied by indentation, I think making them all top-level list items is acceptable. The visual hierarchy is maintained through the bold sub-headers. Actually, let me reconsider. The "Ensure quality implementation of:" is a parent item, and the following bullets are its children. In HTML, I could represent this with nested `

    ` inside a `
    • `. But the instructions don't explicitly mention nested lists. Let me keep it simple and just make them all top-level list items. The bold text "Ensure quality implementation of:" will serve as a visual cue. Hmm, but that loses the nesting information. Let me think about what's cleaner. I think nested lists would be more semantically correct. Let me use: ```html
    • • Ensure quality implementation of:
    • • Support adaptation and contextualization of project materials.
    ...
    ``` This preserves the nesting. I think this is the right approach. Similarly, for the "Documentation and Knowledge Management" section, there are many sub-items. Some of them have "- " prefixes (like "- Reduced dependence on parallel project-funded systems." and "- Establish appropriate processes..."). I should strip the "- " prefix since it's just a formatting artifact. Wait, the instructions say "Stray numbers or formatting artifacts" should be REMOVED. The "- " prefix is a formatting artifact. Let me remove those. Actually, looking more carefully, some items start with "- " and others start with "• ". The "- " ones seem to be artifacts from copy-paste. I should remove the "- " prefixes. Let me also check for other formatting artifacts: - Empty `

    ` tags with styles → remove - `
    ` tags → remove (can't use `
    `) - `

    ` → remove - `
    ` → remove OK, let me now write the complete HTML. I'll be very careful to preserve all content. Let me also think about the "About the Role" section. The World Vision statement is quite long. I'll make it a paragraph. And the disclaimer at the end should probably be removed since it's promotional/legal text, not job information. Wait, the instructions say to remove "Advertisements or promotions". A disclaimer about not soliciting money could be considered promotional. But it's also part of the original content. H

  Translated by AI — may not be perfect

  Show original