Transportation Officer UG

for intro paragraphs and general text,

for section headers like Responsibilities, Qualifications, etc. Use

• for list items. No
  , no CSS, no inline styles, no
  . Preserve all original content word-for-word, do not add, remove, summarise, or rephrase. Must keep original text exactly as given, including stray tags like

  .

  etc. But we need to output HTML only. The original includes some stray

  .

  etc. We need to preserve them? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the stray

  .

  tags? They are part of the raw text. Should we keep them as is? Probably yes, but we need to output HTML. The raw text includes HTML tags like

  .

  which are not valid HTML but we can keep them? The instruction says preserve all original content word-for-word, so we must keep the characters exactly as they appear, including the stray

  .

  . However we also need to output clean semantic HTML using

  etc. There's a conflict: we must preserve original content word-for-word, but also we must format it as clean semantic HTML using

  ,

  ,

  • . The instruction says "Use

    for introductory paragraphs and general text". So we need to replace the raw

    tags? But preserving word-for-word would mean we cannot change them. However the instruction hierarchy: "Your ONLY job is to format it as clean semantic HTML." and "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we must output the same characters, but also wrap them in appropriate tags? That seems contradictory. Perhaps we need to keep the original text exactly as is, but embed it within the required tags. So we should output the same text, but wrap sections with

    etc. The original includes headings like Upstream Forecasts etc. We need to use

    for section headers. So we need to replace Upstream Forecasts with

    Upstream Forecasts

    . But that would be changing the text (removing and adding

  ). That would be a modification, not preserving word-for-word. However the instruction says preserve all original content word-for-word, but also use

  for section headers. Possibly we can keep the original Upstream Forecasts as is, but also add

  around it? That would add extra tags, but not change the content? Adding tags would be adding characters, which might violate preserving word-for-word. But maybe we can wrap the existing Upstream Forecasts with

  tags, like

  Upstream Forecasts

  . That would preserve the original content inside, but adds extra tags. The instruction didn't forbid adding tags, only said use

  for section headers. So we can wrap the existing Upstream Forecasts with

  tags, preserving the inner content exactly. That would be adding

  and

  around it, which is adding characters, but maybe acceptable because we are formatting, not altering the content. The instruction "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Adding tags might be considered adding content, but maybe it's okay because we are not altering the text itself, just wrapping it. However "do not add" could be interpreted as not adding any new text, but tags are not text? They are markup. The instruction is ambiguous. Usually these tasks require to output the cleaned HTML while preserving the original text content exactly, but you can add tags around it. I think we can wrap sections with

  and keep the inner content unchanged, including the tags. That would preserve the original content word-for-word inside the tags. We need to output only HTML, no markdown fences. Use

  for intro paragraphs and general text. Use

  for section headers. Use

  • for list items. We need to identify sections: There's a header "Transportation Officer UG

    .

    " maybe that's the job title? Actually "Transportation Officer UG

    .

    " seems like job title with stray

    .

    . We can treat that as part of intro paragraph? Probably we just output as is, but wrap in

    maybe? The instruction: Use

    for introductory paragraphs and general text. So we can output the job title line as a paragraph? It includes

    .

    after it. That is weird. The raw text: "Transportation Officer UG

    .

    The Transportation Officer is responsible..." So there is a

    .

    after "UG". That seems like stray. We need to preserve it exactly. So we should output that exact string, but we need to wrap in

    tags? The instruction says use

    for introductory paragraphs and general text. So we can output the whole thing as a

    ... but we must preserve the original content word-for-word, including the stray

    .

    . If we wrap the whole thing in a

    , we would be adding extra

    tags around it, but the content inside would be "Transportation Officer UG

    .

    The Transportation Officer is responsible...". That would preserve the inner content exactly. So we can output a

    that contains that text. That would be okay. Then there are sections with Upstream Forecasts etc. We need to wrap those with

    . So we can output

    Upstream Forecasts

    then the following
    ...
    . That preserves the tags inside. We need to preserve all list items exactly as given, including bullet points with
  • items. The original uses
  • Develop with Operations department templates for production forecasting
  etc. We need to keep them exactly. We need to preserve all other paragraphs, including stray

  .

  etc. So we just output them as they appear, but within appropriate tags. We must not add any extra commentary. Thus final output will be a series of tags containing the original text. Let's reconstruct step by step. Original text: Transportation Officer UG

  .

  The Transportation Officer is responsible for coordinating upstream production forecasting, tariff invoicing, commercial agreements, and transportation operations to ensure the efficient and compliant movement of crude oil through the East African Crude Oil Pipeline (EACOP). The role serves as the key liaison between EACOP, upstream shippers, finance, and operations teams, ensuring accurate forecasting, timely invoicing, payment reconciliation, and adherence to transportation and tariff agreements.

  .

  Upstream Forecasts

  • Develop with Operations department templates for production forecasting
  • Participate to planning committees with Upstream
  • Coordinate with Deputy Offtake and transportation Manager for generation of upstream forecasts: upstream nominations and capacity forecasts. Sharing with Upstream Shippers.

  Business and Commercial

  • Contribute to the finalisation of commercial agreements in relation to Tariff and Transportation Agreement and Operations at PS1 / Kabaale Shared Facilities.
  • Provide feedback on effectiveness of these agreements and KPIs over the operations phase
  • Provide assistance to contract engineers for closure of PS1 / Kabaale Shared facilities construction contracts and final cost allocation

  Invoicing

  • Develop templates for follow up of all monthly Tariff invoice inputs and develop invoicing template with finance
  • Issue monthly statements
  • Follow up with the Finance department for payment tracking.
  • Monthly reconciliation

  Reporting

  • Ensure all reporting requirement on Upstream matters as per agreements are complied with. Coordination with operations departement
  • Maintain all recurrent production forecasts up to date.

  Operations

  • Provide operational follow‑up as needed.
  • Commercial focal point for matters related to Upstream/EACOP operations and cost sharing at PS1 / Kabaale Shared facilities

  HSE

  • Apply EACOP HSE rules in all tasks.
  • Ensure operational instructions comply with HSE requirements.

  .

  Qualifications and experience:

  ·     Master’s degree (Engineering, Finance, Commercial & Business).

  ·     Minimum 4 years experience including 2 in commercial activities and negociations

  ·     2 years of experience in: Oil and Gas contracts / business development / Trading Operations / Production-Operations / material balance and accounting

  ·     Experience in financing matters is a plus

   

  Technical competencies:

  ·     Excellent Microsoft Office skills and Excel in particular. Power BI type analysis application

  ·     Any experience in additional  technical areas of Oil and Gas is a plus.

   

  Behavioral competencies:

  ·     Strong analytical skills, high numeracy, problem‑solving mindset.

  ·     Proactive, diplomatic, team‑oriented

  ·     Strong communication skills, considering the variety of stakeholders with different expectations

  ·     Fluent English

  ·     Ability to work in a multicultural environment

  ·     High availability: week end regular duties

  ·     Reactivity and a sense of respect for deadlines.

  .

  If you like working with happy, enthusiastic over-achievers, you'll enjoy your career with us!

  We need to output HTML only, using

  for paragraphs,

  for section headers,

  • for list items. No other tags. We need to decide which parts are section headers. The original uses Upstream Forecasts, Business and Commercial, Invoicing, Reporting, Operations , HSE, then later Qualifications and experience: and Technical competencies: and Behavioral competencies:. Those could be considered 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 wrap those headings with

    . The original headings are bolded with . We can wrap them with

    ...preserving the inside. So we output

    Upstream Forecasts

    etc. But note that there is also a

    at the end:

    If you like working with happy, enthusiastic over-achievers, you'll enjoy your career with us!

    . The instruction only mentions

    for section headers, but we have an

    present. Should we preserve it? The instruction says preserve all original content word-for-word, so we must keep the

    tag as is. However we also need to use

    for section headers. The

    is not a section header per the list, but it's a heading tag. The instruction didn't forbid other heading levels, but says use

    for section headers. It doesn't say we cannot have other tags. So we can keep the

    as is. But we must not add any new tags beyond required. So we can output the

    line exactly as is. Thus we will output:

    Transportation Officer UG

    .

    The Transportation Officer is responsible for coordinating upstream production forecasting, tariff invoicing, commercial agreements, and transportation operations to ensure the efficient and compliant movement of crude oil through the East African Crude Oil Pipeline (EACOP). The role serves as the key liaison between EACOP, upstream shippers, finance, and operations teams, ensuring accurate forecasting, timely invoicing, payment reconciliation, and adherence to transportation and tariff agreements.

    .

    Then for each section:

    Upstream Forecasts

    • Develop with Operations department templates for production forecasting
    • Participate to planning committees with Upstream
    • Coordinate with Deputy Offtake and transportation Manager for generation of upstream forecasts: upstream nominations and capacity forecasts. Sharing with Upstream Shippers.

    Similarly for Business and Commercial, Invoicing, Reporting, Operations, HSE. After HSE section, there is

    .

    then

    Qualifications and experience:

    etc. That is a heading? It is a bold with span. We can treat it as a section header, so wrap with

    . So output

    Qualifications and experience:

    Then the following paragraphs are qualifications etc. They are not list items but paragraphs with spans and bullet points using · etc. Those are part of the content; we need to preserve them exactly. They are not list items, but they contain bullet characters within spans. The instruction says use

    • for list items (duties, requirements, qualifications, skills). However these bullet points are not in
    • tags; they are within · .... So they are not list items. Should we convert them to
    • ? The instruction says use
      • for list items (duties, requirements, qualifications, skills). But the original does not have
        • for those sections; they are just paragraphs with bullet characters. The instruction says preserve all original content word-for-word, so we cannot change them to
        • . But also we need to use
          • for list items. This is contradictory. However maybe we should treat those bullet points as list items and wrap them in
          • tags, but that would be altering the content (adding
          • and
          ). That would be adding characters, which might violate preserving word-for-word. But the instruction says "use
          • for list items (duties, requirements, qualifications, skills)". So we must output them as
            • items. That means we need to convert the bullet points to
            • items, which changes the markup but not the text content? It adds tags, but the text inside remains same. That might be acceptable because we are not altering the text content, just wrapping with tags. However the instruction "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" might be interpreted as not altering the textual content, but adding markup is okay. Usually these tasks allow adding tags around content. So we can wrap each bullet point in
            • tags, but we need to keep the bullet character inside. So we can output
              • Develop with Operations department templates for production forecasting
              etc. That would be adding
              • and
              but not altering the inner text. That seems permissible. Thus for the Qualification section, we have paragraphs with bullet points using ·     etc. Those are not simple
              • items; they have extra spans. We could extract the text after the bullet and wrap in
              • . But that would be altering the content (removing the span tags). The instruction says preserve all original content word-for-word, so we must keep the span tags as they are. So we cannot strip them. So maybe we should treat the whole paragraph as a paragraph, not a list item. But