Contracts Analyst (FPSO)

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Duration: 12 months, Schedule: 5/40, Location: The Woodlands, TX. Also description about role. Then "Requirements" section with bullet list. Then "About Airswift" maybe as About the role? Actually "About Airswift" is company description. Could be "About the role" maybe we can treat the paragraph after location as about the role. We'll need to include sections: About the role (maybe using the paragraph), Requirements (list), maybe Qualifications (but requirements already includes qualifications). Could combine. The instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. Do not put Job ID etc. We need to preserve all substantive info. Remove boilerplate (none). No application instructions. We need to decide which sections to include: About the role (the description after location). Responsibilities? Not explicitly listed but could be derived from description: leading supply chain and contracting activity for FPSO lease and operate agreements, exposure to complex procurement strategy, commercial negotiation, cross-functional collaboration. Could be considered responsibilities. However we must not invent content; we can only include if posting has real specific content. The posting says: "This opportunity is based within a major offshore development and focuses on leading supply chain and contracting activity for FPSO lease and operate agreements. The role offers exposure to complex procurement strategy, commercial negotiation, and cross-functional collaboration across project, engineering, legal, finance, and operations teams." That's responsibilities. So we can have a Responsibilities section with that content (maybe as

or

). Since it's prose, we can put in

. Could also bullet but not needed. Requirements: we have a list of requirements. Use

• . Qualifications: maybe we could separate education etc. But we can just keep Requirements as the qualifications. The instruction says prefer few substantive sections over many thin ones. So we could have About the role (or Responsibilities) and Requirements. Also Schedule and Duration and Location maybe as metadata; we could put them in a short

  under a heading like "Details" but not in list of allowed headings. The allowed headings include Schedule, Pay, Benefits. We have Schedule: 5/40. Duration: 12 months. Location: The Woodlands, TX. Should we include Schedule section? Yes, we have schedule info. Should we include Pay? No pay info not given. Benefits? Not given. So we include Schedule section with the schedule info. Also maybe Duration and Location could be included in same Schedule section? But better to have a separate "Details" but not allowed. Could embed Duration and Location in a

  under Schedule heading? Might be okay but schedule heading should contain schedule specifics. Could also add a separate "Details" but not in allowed list; better to avoid extra headings. Could put Duration and Location in a

  after the schedule heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g those). It doesn't say we cannot have other headings, but to be safe we stick to those. We could include Schedule heading and put schedule, duration, location inside as a

  . Or we could have separate headings for Duration and Location but they aren't in the list; better to avoid. Thus sections: About the role (maybe we call it About the role), Responsibilities, Requirements, Schedule. We need to preserve all substantive info: include description about role, responsibilities, requirements list, schedule, duration, location. Let's craft:

  About the role

  This opportunity is based within a major offshore development and focuses on leading supply chain and contracting activity for FPSO lease and operate agreements. The role offers exposure to complex procurement strategy, commercial negotiation, and cross‑functional collaboration across project, engineering, legal, finance, and operations teams.

  Responsibilities

  Lead supply chain and contracting activity for FPSO lease and operate agreements; develop and execute procurement plans and contracting strategies; manage end‑to‑end sourcing (market engagement, bidder pre‑qualification, RFI, RFP, ITT preparation, commercial bid evaluation, clarification, negotiation, award recommendation); negotiate complex, high‑value tenders with FPSO contractors, operators, fabrication yards, and offshore installation contractors; support newbuild or redeployment projects including topsides and hull interfaces, mooring, conversion, marine assurance, long‑term operating obligations; develop commercial models and contract terms for offshore scopes; manage commercial risk allocation, bid normalization, price escalation, schedule incentives and remedies, change and claims management, warranties, liabilities, performance security; work across international projects and multidisciplinary teams; use Ariba and SAP; apply strong commercial judgement and analytical capability; stakeholder management, document control, prioritisation in fast‑paced global environment.

  But we must not invent details; we need to ensure we only include what is in posting. The posting includes many specifics: leading supply chain and contracting activity for FPSO lease and operate agreements; exposure to complex procurement strategy, commercial negotiation, cross-functional collaboration; leading complex, high-value tenders and negotiations; experience supporting newbuild or redeployment projects including topsides and hull interfaces, mooring, conversion, marine assurance, long-term operating obligations; developing and executing procurement plans and contracting strategies aligned with project schedule, budget, execution strategy, risk profile; expertise in end-to-end sourcing activity including market engagement, bidder prequalification, RFI, RFP, ITT preparation, commercial bid evaluation, clarification, negotiation, award recommendation; understanding of commercial risk allocation, contracting strategy, bid normalization, price escalation, schedule incentives and remedies, change and claims management, warranties, liabilities, performance security; ability to develop commercial models and contract terms for complex offshore scopes including FPSO lease and operate, marine transportation and installation, commissioning support, long-term services; working knowledge of critical package interfaces across FPSO, SPS, SURF, drilling and completions, logistics, operations; experience using Ariba and SAP; fluency in English; strong commercial judgement; advanced analytical capability; excellent negotiation, stakeholder management, cross-functional collaboration, organisation, document control, ability to manage competing priorities; strong proficiency in Microsoft 365 and commercial data analysis; preferred: Icertis; certifications preferred. We need to capture all that in Responsibilities or Requirements. The posting has a "Requirements" heading with bullet list. So we should keep that as Requirements. The preceding paragraph before Requirements is more about the role and responsibilities. So we can have About the role (or Responsibilities) as that paragraph. Then Requirements as list. Thus we don't need to duplicate details in Responsibilities; we can keep the paragraph as About the role. Then Requirements list covers the bullet points. Thus sections: About the role (paragraph), Requirements (ul), Schedule (p with schedule, duration, location). Let's extract schedule info: Duration: 12 months, Schedule: 5/40, Location: The Woodlands, TX. We'll put in Schedule section:

  Duration: 12 months; Schedule: 5/40; Location: The Woodlands, TX.

  Now ensure we don't include boilerplate like "About Airswift". That's company description; is that substantive? It's about the employer, could be considered About the role? But it's not directly about the role; it's about Airswift. The instruction: preserve ALL substantive information. So we should include that as well. Where to put? Could be another section like "About the company" but not in allowed headings. Could we put it under About the role? Might be mixing. Better to add a section "About the company" but not in allowed list; maybe we can treat it as "About the role" extended? But the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use h3 for section headings (e.g those). It might be okay to add other headings as long as they are h3. However to be safe, we could incorporate the Airswift description into About the role section as additional paragraph. That would preserve info. Thus About the role section will have two paragraphs: first about the role responsibilities, second about Airswift. Let's craft final HTML:

  About the role

  This opportunity is based within a major offshore development and focuses on leading supply chain and contracting activity for FPSO lease and operate agreements. The role offers exposure to complex procurement strategy, commercial negotiation, and cross‑functional collaboration across project, engineering, legal, finance, and operations teams.

  Airswift is an international workforce solutions provider within the energy, process and infrastructure industries. Airswift serves as a strategic partner to clients, offering a turnkey workforce solution to capture and deliver the top talent needed to complete successful projects by aligning with unique project needs. With over 1000 employees and 9,000 contractors operating in over 60 countries, Airswift's geographical reach and pool of talent available is unmatched in the industry.

  Requirements

  • At least 12 years of recent experience in supply chain, contracts, or commercial roles supporting major oil and gas, offshore, or comparable capital projects.
  • Bachelor’s degree in Engineering, Supply Chain, Business, Law, Finance or a related discipline.
  • Demonstrated FPSO experience, including exposure to lease and operate, bareboat charter, and O&M structures.
  • Proven experience leading complex, high‑value tenders and negotiations with FPSO contractors, operators, fabrication yards, and offshore installation contractors.
  • Experience working across international projects and multidisciplinary teams.
  • Experience supporting newbuild or redeployment projects, including topsides and hull interfaces, mooring, conversion, marine assurance, and long‑term operating obligations.
  • Strong capability in developing and executing procurement plans and contracting strategies aligned with project schedule, budget, execution strategy, and risk profile.
  • Expertise in end‑to‑end sourcing activity including market engagement, bidder prequalification, RFI, RFP, ITT preparation, commercial bid evaluation, clarification, negotiation, and award recommendation.
  • Strong understanding of commercial risk allocation, contracting strategy, bid normalization, price escalation, schedule incentives and remedies, change and claims management, warranties, liabilities, and performance security.
  • Ability to develop commercial models and contract terms for complex offshore scopes including FPSO lease and operate, marine transportation and installation, commissioning support, and long‑term services.
  • Working knowledge of critical package interfaces across FPSO, SPS, SURF, drilling and completions, logistics, and operations.
  • Experience using Ariba and SAP; Icertis knowledge is listed separately as preferred.
  • Fluency in written and spoken English.
  • Strong commercial judgement with the ability to translate technical execution issues into clear contractual positions and risk‑adjusted recommendations.
  • Advanced analytical capability, including commercial evaluation, cost benchmarking, scenario analysis, and executive‑level reporting.
  • Excellent negotiation, stakeholder management, cross‑functional collaboration, organisation, document control, and ability to manage competing priorities in a fast‑paced global project environment.
  • Strong proficiency in Microsoft 365 applications and commercial data analysis.
  • Preferred: Experience with Icertis.
  • Preferred: PMP, CIPS, CPSM, CPCM