Senior Manager Ground Operations

,

,

• . No divs, no classes, no inline styles, no
  . Must preserve all original content word-for-word. The input includes some HTML tags already:

   

  ,

  ... etc. We need to output HTML only, preserving content. We must strip out the existing tags? The instruction: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." It says we receive plain-text job description, but the given input includes HTML tags. We must preserve all original content word-for-word, but we need to format as clean semantic HTML using only

  ,

  ,

  • . So we need to convert the given content into that format, preserving the text content exactly (including spaces? but we can ignore   maybe). We must not add or remove content. So we need to extract the textual content and wrap appropriately. We need to identify sections: Title, department etc table, then job purpose, key accountabilities (with subpoints a-l), qualifications, knowledge skills. We must use

    for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. In this text, we have headings like "1. Job purpose", "2. Key accountabilities", then subpoints like "(a) Ground operations leadership and readiness", etc. Also "3. Minimum qualifications and experience", "4. Knowledge, skills and competencies". Also there is a table with Department, Reports To, Duty Station, Job Level, Direct Reports, Operational Scope. Those could be considered as details; we could treat each row as a

    maybe? But we need to use

    for section headers. The table rows have labels like Department:, Reports To:, etc. Those are not section headers per the list, but we could still wrap them in

    . The instruction: "Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using

    for other headings, but we should follow the pattern. Probably we should treat "1. Job purpose", "2. Key accountabilities", "3. Minimum qualifications and experience", "4. Knowledge, skills and competencies" as

    . Also subpoints like "(a) Ground operations leadership and readiness" maybe also

    ? They are not in the example list but could be considered section headers. Safer to treat them as

    as well. We need to wrap paragraphs in

    . List items in

    • . The existing
      • already present; we should keep them but ensure they are proper HTML. The input already has
        and
        • with inside. We need to preserve content word-for-word, but we can strip the extra tags? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That suggests we must keep the exact text, including any existing tags? But we also must output only

          ,

          ,

          • . So we cannot keep or etc. That would be adding tags not allowed. However we could keep the text content inside those tags, but we would be removing the and tags, which is removing content (the tags). The instruction says preserve original content word-for-word. Does "content" refer to the textual content, not the markup? Usually in such tasks, they mean the textual content, not the formatting tags. So we can strip away existing tags and reformat using allowed tags. We must not add any extra words or omit any words. Thus we need to extract the plain text from the given HTML, preserving spaces and punctuation exactly. Then we need to wrap sections appropriately. Let's extract the text. First line:

             

            => a non-breaking space, basically empty paragraph. We can ignore or keep as

             

            ? But we cannot use  ? It's a character entity; we could keep it as is inside

            . But we are not allowed to add tags besides p, h4, ul li. We can keep   as text inside

            . That's fine. Then title:

                                                       Senior Manager Ground Operations

            That includes many spaces before the text. We need to preserve them? Probably we should keep the spaces as they are. The text includes many leading spaces. We'll keep them. Then table rows: each row has Department: Customer Services. So the text includes "Department:" and "Customer Services". We need to preserve them. We could represent each row as a

            containing the label and value separated by maybe a space? The original had them in separate table cells. We need to preserve the content word-for-word, but we can't keep the table tags. We could output each row as a

            with the label and value separated by a space (or maybe keep the colon and space). The original had "Department:" in strong, then a cell with "Customer Services". If we just concatenate "Department: Customer Services" that changes the formatting but not the textual content? The original had them separated by table cell boundaries, but the textual content if we flatten would be "Department: Customer Services". That's essentially the same words and punctuation, just missing the table structure. I think acceptable. Similarly for other rows. Then after table, we have

            1. Job purpose

            etc. We'll convert each

            containing heading to

            with the text inside (including the strong etc). We'll strip the tags but keep the text. Then the paragraph after that:

            The Senior Manager Ground Operations is accountable ...

            =>

            with that text. Then heading "2. Key accountabilities" =>

            . Then subheading "(a) Ground operations leadership and readiness" => maybe

            as well. Then the list under it: each

            with ... . We'll output

            • with the text. We need to ensure we preserve all text exactly, including punctuation, spaces inside the lines. We must be careful with special characters like & in "Systems & World Tracer". That's an HTML entity for &. We need to preserve it as "&"? The original content includes the entity. If we output plain text, we should convert to "&"? But preserving word-for-word would keep the entity as "&". However the instruction says preserve original content word-for-word. If we change & to &, that's a change. So we should keep "&" as is. Similarly other entities. Thus we need to extract the text including entities exactly as they appear in the source. That means we should not decode them. So we need to keep the literal characters "&", "a", "m", "p", ";". So we will output them as they appear. Thus we need to parse the given HTML string and extract the text nodes, preserving entities. That's tricky manually. But we can approximate by copying the visible text and keeping entities as they appear. Given the complexity, maybe we can output the HTML as is but replace tags with allowed ones? But we cannot keep , , , Inner text of first cell: "Department:" (with strong). Second cell: "Customer Services". We'll output as

              Department: Customer Services

              (preserving the colon and space). There's a space after colon in original? The strong includes "Department:" then closing tag, then cell ends. The second cell starts with Customer Services. Likely there is a space between cells due to table formatting, but not in text. We'll just put a space. Row2: Reports To: Chief Customer Services Officer Row3: Duty Station: Entebbe International Airport, with oversight and travel across the network as assigned Row4: Job Level: Senior Manager Row5: Direct Reports: Coordinator Standards, Systems & World Tracer; Station Manager - Entebbe Hub; Manager Ground Support Equipment; Administrative Assistant Note the & entity. Row6: Operational Scope: Passenger processing; station and hub operations; ramp and turnaround; baggage tracing; travel-document verification; passenger check-in; flight monitoring; cabin grooming; transport support; ground support equipment; contracted ground handling oversight. We'll output each as

              . Now after table, we have blank line? There's a

               

              after table? Actually after table closing

              , etc. We must remove them. But we can keep the inner text. Given the time, we can produce a reasonable approximation: produce headings and paragraphs with the text as we read it, preserving entities like &. Let's manually extract sections. I'll copy the text from the input, ignoring tags. Start: First empty paragraph: just a space? We'll output   maybe. Then title line: many spaces then "Senior Manager Ground Operations". We'll keep leading spaces. Let's count spaces: The snippet shows many spaces before the text. Hard to replicate exactly. We'll just keep the spaces as they appear in the source: there are many spaces. We'll copy the exact string from the source: "                                         Senior Manager Ground Operations". Actually the source:                                            Senior Manager Ground Operations So inside strong there is a series of   entities separated by spaces? Actually it's "      ..." each entity followed by a space? The pattern: "  " repeated many times then the text. We'll keep that exactly. Thus we output followed by that exact string then . But we are not allowed to use or . So we will output then the inner text (including the   entities and spaces) then . That means we strip the tags but keep their inner text. Thus the line becomes:                                            Senior Manager Ground Operations Now table rows. We'll process each row: Row1: Department: Customer Services Original:

              Department:

              Customer Services

              there is a

              1. Job purpose

              . No blank. We'll output heading

              1. Job purpose

              Then paragraph: The Senior Manager Ground Operations is accountable for the safe, secure, compliant, punctual and customer-focused delivery of Uganda Airlines' ground operations at Entebbe Hub and for the consistent application of approved ground-handling standards across the network. The role leads passenger processing, travel-document verification, ramp and turnaround activities, baggage services and tracing, cabin grooming, transport support, ground support equipment and contracted ground-handling oversight. The job holder converts the operating schedule into station readiness, coordinates all parties involved in an aircraft turnaround, protects customers and aircraft, and ensures that operational irregularities are controlled, communicated, recorded and resolved. We need to keep apostrophe as is. Then heading

              2. Key accountabilities

              Then subheading "(a) Ground operations leadership and readiness" =>

              (a) Ground operations leadership and readiness

              Then list items: - Develop and execute the ground operations plan, station readiness programme, manpower requirements and budget in line with the approved schedule and Customer Services objectives. - Ensure each operating day is supported by adequate qualified staff, service providers, equipment, facilities, permits, systems and escalation arrangements. - Lead daily operational briefings and performance reviews, identifying risks, constraints, special flights, VIP movements, disruptions and corrective actions. - Provide the Chief Customer Services Officer with timely reports on safety, compliance, punctuality, baggage, passenger processing, supplier performance and material operational risks. Each as
            • . Then subheading "(b) Entebbe Hub and station operations" =>

              (b) Entebbe Hub and station operations

              List items similarly. Then subheading "© Passenger check-in, acceptance and boarding" Note: The original shows "(c)" but with a copyright symbol? Actually it shows "© Passenger check-in, acceptance and boarding" That's a copyright symbol then space then text. We need to preserve that exactly: the copyright symbol is the entity ©? In source it's literally the character ©? It appears as © (the character). We'll keep as is. Thus heading:

              © Passenger check-in, acceptance and boarding

              Then list. Then subheading "(d) Travel-document verification and regulatory controls" =>

              (d) Travel-document verification and regulatory controls

              Then list. Then subheading "(e) Ramp, turnaround and aircraft handling" =>

              (e) Ramp, turnaround and aircraft handling

              List. Then subheading "(f) Baggage services and World Tracer" =>

              (f) Baggage services and World Tracer

              List. Then subheading "(g) Ground support equipment and transport" =>

              (g) Ground support equipment and transport

              List. Then subheading "(h) Ground handling standards, systems and quality" =>

              (h) Ground handling standards, systems and quality

              List. Then subheading "(i) Disruption and emergency response" =>

              (i) Disruption and emergency response

              List. Then subheading "(j). Safety, security and compliance" Note there is a period after j). Original: "(j). Safety, security and compliance" So heading:

              (j). Safety, security and compliance

              List. Then subheading "(k). Supplier, financial and resource management" =>

              (k). Supplier, financial and resource management

              List. Then subheading "(l). People leadership and performance" =>

              (l). People leadership and performance

              List. Then heading "

              3. Minimum qualifications and experience

              " =>

              3. Minimum qualifications and experience

              Then list items (each
            • ). Then heading "

              4. Knowledge, skills and competencies

              " =>

              4. Knowledge, skills and competencies

              Then list items (simple phrases). Finally there is a trailing

               

              at end. We'll output that as

               

              . Now we need to ensure we didn't miss any text. Also need to preserve any punctuation like periods, commas. Let's craft the HTML. We'll start with the empty p:

               

              Then title p. Then each table row p. Then headings and paragraphs. We'll need to be careful to not accidentally add extra spaces. Let's write it out. I'll produce:

               

                                                         Senior Manager Ground Operations

              Department: Customer Services

              Reports To: Chief Customer Services Officer

              Duty Station: Entebbe International Airport, with oversight and travel across the network as assigned

              Job Level: Senior Manager

              Direct Reports: Coordinator Standards, Systems & World Tracer; Station Manager - Entebbe Hub; Manager Ground Support Equipment; Administrative Assistant

              Operational Scope: Passenger processing; station and hub operations; ramp and turnaround; baggage tracing; travel-document verification; passenger check-in; flight monitoring; cabin grooming; transport support; ground support equipment; contracted ground handling oversight.

              1. Job purpose

              The Senior Manager Ground Operations is accountable for the safe, secure, compliant, punctual and customer-focused delivery of Uganda Airlines' ground operations at Entebbe Hub and for the consistent application of approved ground-handling standards across the network. The role leads passenger processing, travel-document verification, ramp and turnaround activities, baggage services and tracing, cabin grooming, transport support, ground support equipment and contracted ground-handling oversight. The job holder converts the operating schedule into station readiness, coordinates all parties involved in an aircraft turnaround, protects customers and aircraft, and ensures that operational irregularities are controlled, communicated, recorded and resolved.

              2. Key accountabilities

              (a) Ground operations leadership and readiness

              • Develop and execute the ground operations plan, station readiness programme, manpower requirements and budget in line with the approved schedule and Customer Services objectives.
              • Ensure each operating day is supported by adequate qualified staff, service providers