RE

Programme Coordinator - Youth Engagement

Fixed_term Kampala, UG
Posted 6 days, 10 hours ago 22 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User wants me to format a raw scraped job description into clean semantic HTML. - Rules are strict: use `

` for paragraphs, `

` for section headers, `
  • ` for lists, no CSS classes/inline styles/
    /
    , preserve ALL original content word-for-word, no summarizing/rephrasing, return ONLY HTML, no markdown fences/explanation/preamble. 2. **Identify the Source Text:** - The text is a job listing for "Programme Coordinator - Youth Engagement" at Restless Development Uganda. - It contains various sections: About Restless Development, approach, role description, job details (title, location, salary, contract, etc.), key responsibilities (numbered 1-6), skills and experience (essential list), equal opportunities statement. - There are `

    `, `` tags with inline styles, `

      `, `
    • ` already in the raw text, but I need to strip the styles and restructure into clean semantic HTML per the rules. 3. **Deconstruct and Reconstruct Rules:** - **Remove**: All inline styles (color, font-size, font-weight), `` tags, `
      ` tags, any decorative or tracking text. But wait - the rules say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". However, the HTML rules say: "No CSS classes, no inline styles, no
      s, no
      tags". There's a conflict: preserve content word-for-word vs. remove inline styles/
      . I need to interpret this carefully. The intent is likely: keep the text content, but strip the presentation markup (styles, spans, brs) and re-wrap in the required semantic tags. The "word-for-word" means don't change the actual words/text, but the markup tags (span, br, style) are not "content" - they're formatting. I'll strip styles and brs, and keep only the text nodes, wrapping them in `

      `, `

      `, `
        `, `
      • ` as appropriate. - Actually, re-reading: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This probably applies to the visible text. The inline styles and br tags are not "content" in the human-readable sense. I need to extract the plain text and re-markup semantically. - Rules also: "If text has no clear sections, just wrap paragraphs in

        tags". Here we have clear sections: Responsibilities, Skills and Experience, etc. - Use `

        ` for section headers: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. I need to map the actual section headers from the text to these. The text has: "About the Role", "Key responsibilities", "5. People Management", "6. Safeguarding...", "5. Others responsibilities", "Skills and Experience", "Essential", etc. I'll use `

        ` for major section breaks. - Use `
        • ` for list items (duties, requirements, qualifications, skills). The text already has `
          • ` with `` inside. I'll keep the `
          • ` structure but strip spans/styles. - No markdown fences, no explanation, just raw HTML output. Let's map the structure: - Job title: "Programme Coordinator - Youth Engagement" - this appears multiple times. I'll keep it once, maybe as `

            ` or start of text. The rules say "Remove duplicate text (if the title appears multiple times, keep it once)". - Company: "Restless Development" / "Restless Development Uganda" - Location: "Kampala, Uganda" - Salary: "UGX 73,299,474 Gross Per Annum" - Apply by: "10th September 2026 at 5:00 PM (E.A.T)" - Contract length: "2 years" - Preferred start date: "October 2026" - Reports to: "Programme manager youth employment and market systems." - Expected travel: "Fairly regular international and domestic travel" - About Restless Development paragraph(s) - Approach to safeguarding - About Youth Employment Work - About the Role (multiple paragraphs) - Key responsibilities (sections 1-6, plus "Others responsibilities") - Skills and Experience (Essential list items) - Equal Opportunities statement I need to decide on section headers. The rules list specific allowed headers: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". I should use `

            ` for these where applicable. The text has "Key responsibilities", "Skills and Experience", "About the Role". I'll map: - "Key responsibilities" -> `

            Key responsibilities

            ` or just use the text as header. - "Skills and Experience" -> `

            Skills and Experience

            ` - "About the Role" -> `

            About the Role

            ` - Maybe "About Restless Development" -> could be `

            ` or `

            `, but rules say use `

            ` for section headers. I'll treat major divisions as `

            ` if they look like section headers, otherwise `

            `. - Actually, 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 any of these that appear. I'll use `

            ` for: Key responsibilities, Skills and Experience, About the Role. Others might be `

            ` or integrated. Important: "No CSS classes, no inline styles, no

            s, no
            tags". So I must strip all `style` attributes, `color` spans, `font-size`, `font-weight`, `
            ` tags. The `
              ` and `
            • ` tags from the original should be preserved, but I'll need to wrap their content properly. The original has `
              • ...`. I'll keep `
                • ` and put the text inside `
                • ` without spans. Let's plan the HTML output structure: ```

                  Programme Coordinator - Youth Engagement

                  Restless Development Uganda

                  Kampala, Uganda

                  Salary: UGX 73,299,474 Gross Per Annum

                  Apply by 10th September 2026 at 5:00 PM (E.A.T)

                  Length of contract: 2 years

                  Preferred start date: October 2026

                  Reports to: Programme manager youth employment and market systems.

                  Expected travel: Fairly regular international and domestic travel

                  About the Role

                  . But I need to strip spans. I'll just put the plain text in

                  .

                  Wait, the rule "Preserve ALL original content word-for-word" is tricky. If I strip spans and styles, am I preserving word-for-word? Yes, the textual content is preserved, just markup changes. I think that's the intent. Let's carefully extract and reformat each part, stripping spans and brs, but keeping all visible text exactly as is. I'll go through the text node by node, identify text content, and rewrap. Original text blocks (simplified, removing the noisy span attributes in analysis, but I'll process the actual given text): The given text is already HTML-ish with

                  . I need to output clean HTML with

                  ,

                  ,
                    ,
                  • , no styles, no br, no spans. Strategy: I'll parse the text, extract the plain text content of each element, and re-markup semantically. I'll keep the exact string of visible text. Let's list all visible text segments in order, noting where sections start/end: 1. "Programme Coordinator - Youth Engagement" (appears in ... twice? Actually once as title, then repeated later. I'll keep once.) 2. "Apply by 10th September 2026 at 5:00 PM (E.A.T)" 3. "About Restless Development" 4. Restless Development Uganda description paragraph. 5. "Our approach to safeguarding:" 6. Safeguarding paragraph. 7. "About our Youth Employment Work:" 8. Youth Employment Work paragraph. 9. "About the Role" 10. About the Role paragraph 1. 11. About the Role paragraph 2. 12. About the Role paragraph 3. 13. "Job title: Programme Coordinator - Youth Engagement" (duplicate, skip) 14. "Location: Kampala, Uganda" 15. "Salary: UGX 73,299,474 Gross Per Annum" 16. "Preferred start date: October 2026" 17. "Length of contract: 2 years" 18. "Reports to: Programme manager youth employment and market systems." 19. "Expected travel: Fairly regular international and domestic travel" 20. "Key responsibilities" -> "Key responsibilities" 21. "1. Youth engagement and Programme Implementation" -> maybe keep as text, but under responsibilities. Actually, the responsibilities are numbered list items under headings like "1. Youth engagement and Programme Implementation", "2. Capacity strengthening and partnerships", etc. The rules say use
                    • for list items. I'll make each bullet point an
                    • , and the main headings (1., 2., etc.) might be part of the
                    • text or I could use

                      for each section header, but rules only list specific headers. I'll treat the numbered sections as
                    • items, possibly keeping the number and text. Let's re-examine the responsibilities section: - "Key responsibilities" (bold, underlined) - "1. Youth engagement and Programme Implementation" with sub-bullets (li items) - "2. Capacity strengthening and partnerships" with sub-bullets - "3. Cost-effective and transparent financial management" with sub-bullets - "4. Monitoring and Reporting" with sub-bullets - "5. People Management" with sub-bullets - "6. Safeguarding, Compliance and Organisational Responsibilities" with sub-bullets - "5. Others responsibilities" with one bullet The rules say: "Use
                      • for list items (duties, requirements, qualifications, skills)". So I'll make each bullet point an
                      • . The main section headings (1., 2., etc.) I'll either include as text within
                      • or as

                        if they match. Since "Key Duties" is in the allowed header list, but the text uses "Key responsibilities", I'll use

                        Key responsibilities

                        before the
                          . For the numbered sections, I'll just put the text as
                        • items, maybe keeping the number. But the rules say preserve word-for-word. So I'll keep "1. Youth engagement and Programme Implementation" as the text inside
                        • , but the "1." might be part of the original. I'll keep it. Actually, looking at the original, each responsibility section has a heading like "1. Youth engagement and Programme Implementation" followed by `
                          • ...
                          `. So the structure is:

                          1. Youth engagement ...

                          • text
                          Wait, looking at the raw text: ```

                          1. Youth engagement  and Programme  Implementation

                          • Coordinate the implementation...
                          • ...
                          ``` So the "1. Youth engagement..." is in a

                          with bold span, then a

                          • list. I'll convert the bold heading to

                            or just keep it as

                            ? Rules say use

                            for section headers. "Key responsibilities" is listed as an example header. I'll use

                            Key responsibilities

                            and then the
                            • list. But the "1. Youth engagement..." is a sub-heading for the first group. I could either include it as part of the
                            • text, or as a nested

                              . To keep it simple and preserve content, I'll make each
                            • start with the duty text, and maybe keep the "1." outside or inside. Since the rule says preserve word-for-word, I'll include "1. Youth engagement and Programme Implementation" as the first
                            • text, but then the actual bullet points follow. Actually, the original has the numbered heading in a

                              , then separate

                              • list. I'll restructure:

                                Key responsibilities

                                • 1. Youth engagement and Programme Implementation: [but the text says "1. Youth engagement..." as a heading, then sub-bullets]. This is getting messy. Let's look at the exact original snippet for responsibilities: ```

                                  Key responsibilities

                                  1. Youth engagement  and Programme  Implementation

                                  • Coordinate the implementation...
                                  • ...

                                  2. Capacity strengthening and partnerships

                                  • ...>
                                  • ... ``` So each responsibility section has a heading paragraph, then a
                                    • list. I need to preserve the text. I'll do:

                                      Key responsibilities

                                      • 1. Youth engagement and Programme Implementation
                                        • Coordinate the implementation...
                                        • ...
                                      But that nested ul might be overcomplicating. The rules say "Use
                                      • for list items (duties, requirements, qualifications, skills)". It doesn't forbid nested lists, but says if no clear sections, just wrap in

                                        . I think the simplest is to treat each bullet point as an

                                      • , and the main section headings (1., 2., etc.) as part of the
                                      • text or as

                                        . Given the strict "preserve word-for-word", I'll keep the exact text flow. Maybe better: I'll output the responsibilities as

                                        Key responsibilities

                                        followed by
                                        • 1. Youth engagement and Programme Implementation
                                        • Coordinate the implementation...
                                        • ... but that loses the grouping. The original groups duties under sub-headings. I could nest:
                                          • 1. Youth engagement and Programme Implementation
                                            • Coordinate...
                                            • ...
                                          . But rules say no ? Actually rules only say no CSS classes, inline styles, no
                                          , no
                                          . They don't forbid or , but to be safe and semantic, I might use them or just keep text. The rule "Preserve ALL original content word-for-word" means I should keep the text exactly, but markup can change. I'll use or just keep as text. Actually, I'll just put the main heading "Key responsibilities" as

                                          , then for each section, I'll put the numbered heading as a

                                          or

                                          ? The allowed headers are listed: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". "Key responsibilities" maps to "Key Duties". I'll use

                                          Key responsibilities

                                          at the top. Then the numbered sections: I'll just include the text "1. Youth engagement and Programme Implementation" as the first
                                        • item, but then the sub-bullets follow. This is ambiguous. Let's rethink: The user wants me to format the raw text as clean semantic HTML. The raw text has a certain structure. I need to output HTML that represents that structure using only

                                          ,

                                          ,
                                            ,
                                          • . I should not nest beyond
                                            • unless necessary, but I can nest
                                                inside
                                              • if the original has sub-bullets. The original has: a heading (e.g., "1. Youth engagement...") then a
                                                • list of duties. So the structure is: - Heading "1. Youth engagement..." - List of duties (each a bullet)

      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 📝

MJC
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.

How was your experience with ECHO?