UG

CARGO STANDARDS OFFICER

Full-time Uganda, UG
Posted 11 hours, 36 minutes ago 7 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor. - I receive raw scraped text from a job website. - My job: extract ONLY actual job information, return clean, readable format. - Must REMOVE: social sharing text, author bylines, "you may also like", navigation, comments, ads/promotions, cookie/subscription notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts. - Must KEEP and STRUCTURE: job title, company/organization, location, job description/responsibilities, requirements/qualifications, how to apply, salary (if mentioned), deadline/closing date, job ID/reference number, contract type/level. - Return ONLY the cleaned job text. No commentary, no headers like "Here is the cleaned version", no markdown. Wait, the actual input provided is: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML. Rules: - Use

for introductory 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
    s, 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, no preamble. Job description: [big block of HTML-text with divs, spans, strong, ul, li, etc.]" So the task is: Take the provided "Job description" text, clean it according to the rules (but the rules are about formatting as clean semantic HTML, removing certain things, keeping others), and output ONLY the HTML. Let me re-read the initial prompt vs the actual input. Initial prompt: "You are a job listing editor... Your job is to extract ONLY the actual job information and return it in a clean, readable format. REMOVE all of the following: ... KEEP and STRUCTURE: ... Return ONLY the cleaned job text. Do not add any commentary..." Then the user says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then gives rules about HTML tags, and then provides the job description block. Actually, looking carefully, the user message is a mix of instructions and the actual job data. The core task is: format the given job description block as clean semantic HTML, following the specified rules. Rules given: - Use

    for introductory 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
      s, 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, no preamble. I need to parse the job description block and convert it to the specified HTML format, removing any stray formatting artifacts (the original has `

      `, ``, `style="...">` attributes, etc.), and keeping all content word-for-word. Let's examine the job description text structure. It's already somewhat structured with sections like "Job Purpose", "Key Accountabilities", "Key Performance Indicators (KPIs)", "Minimum Qualification and Experience", "Core Competencies", "HR Summary". There are also some dividers and horizontal rules represented as `
      `. Rules say: No
      s, no inline styles, no
      tags. So I need to strip those dividers and spans, and keep the text content. Also: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I must include all the text exactly as written, but format it into the HTML tags specified. Let's outline the structure I'll create: The text seems to have these main sections: - Job Purpose (introduced by `

      Job Purpose

      `) - Several paragraphs under `

      ...` - "Key Accountabilities" section with sub-items - "Key Performance Indicators (KPIs)" section - "Minimum Qualification and Experience" section - "Core Competencies" section - "HR Summary" section - Some trailing paragraphs and lists I need to map these to the HTML structure rules: - Use

      for section headers - Use
      • for list items - Use

        for introductory paragraphs and general text Since I must preserve all content word-for-word, I'll keep every sentence, every bullet point exactly as is. Let's go through the text carefully and extract/structure it. Original text block (I'll copy and analyze): ```

        Job Purpose

        The Cargo Standards Officer is responsible for monitoring, enforcing, and continuously improving UNACL cargo operational standards, cargo safety compliance, operational quality assurance, and third-party cargo handling conformity in alignment with IOSA, ISAGO, IATA Cargo Handling Manual (ICHM), Dangerous Goods Regulations (DGR), aviation security requirements, customs requirements, and UNACL operational standards.

        The role provides operational governance and quality oversight of outsourced cargo handling activities, Cargo GSAs, warehouse operators, cargo terminal providers, ground handling agents, and operational cargo partners to ensure standardized, safe, secure, compliant, and audit-ready cargo operations across UNACL network.

        The role supports UNACL IOSA compliance, operational risk management, safety reporting, corrective action monitoring, operational quality assurance, and continuous operational improvement within cargo operations.

        The role focuses heavily on operational oversight, service provider governance, operational compliance monitoring, and enforcement of standards across third-party cargo-handling environments.

        The Cargo Standards Officer works closely with Cargo Operations, Cargo GSAs, Ground Handling Agents, Airport Operations, Safety & Quality teams, Flight Operations, Security teams, and regulatory stakeholders to support operational compliance, cargo safety, and cargo service quality.

        Key Accountabilities

        1. Cargo Operational Standards Management

        • Monitor implementation of UNACL cargo operational standards across all cargo operations and stations.
        • Ensure compliance with cargo handling procedures, cargo acceptance standards, operational documentation requirements, shipment handling controls, and UNACL operational procedures.
        • Support standardization of cargo operational practices across all handling partners and operational locations.
        • Ensure cargo operational processes remain audit-ready and compliant with UNACL safety and quality management systems.

        2. IOSA, ISAGO and Operational Quality Compliance

        • Support UNACL compliance with IOSA operational standards, ISAGO handling oversight requirements, IATA Cargo Handling Manual (ICHM), IATA Dangerous Goods Regulations (DGR), and UNACL operational quality standards.
        • ... wait, let's look at original: original has `

          2. IOSA, ISAGO and Operational Quality Compliance

          ` then `
            ` with 5 `
          • ...
          `. I'll just count them.
        • (I'll handle carefully) ``` Let me copy the exact text from the user message to ensure I don't miss anything. I'll parse it mentally or textually. Actually, I'm the AI, I can just read the block. Let me re-read the user message's job description part carefully. It's long. I'll need to systematically convert it. Strategy: I'll go through the text, identify sections, headers, lists, paragraphs, and output HTML using

          ,

          ,

            ,
          • as appropriate, stripping all `
            `, ``, `style="..."`, `
            `, etc., but keeping all text content exactly. Important: The rule "Preserve ALL original content word-for-word" means I must include every word, including "1.", "2.", etc., and all the span text. But I need to format them properly. Also: "No CSS classes, no inline styles, no
            s, no
            tags" - so I must remove all those container divs and style attributes. "Use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" - so I'll use

            for each major section title. "Use

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?