Measurement Technician – Deepwater - 14/14

We need to output HTML fragment with sections: About the role (position summary), Responsibilities, Requirements (maybe combine Required Qualifications), Skills? The posting includes Required Qualifications, Preferred Qualifications, Education, Work Environment. We need to decide which sections to include based on content. Must not include sections with filler like "commensurate with experience". We have actual content for About the role (position summary), Responsibilities, Required Qualifications, Preferred Qualifications, Education, Work Environment. Also Schedule is given: 14 Days On / 14 Days Off Shift: 12-Hour Days. That's schedule info, so we should include a Schedule section. Pay not mentioned, so omit. Benefits not mentioned, omit. Skills maybe not separate; we could include Skills under Requirements or as separate if there is explicit skills list. There's mention of ability to use software etc. Could treat as Skills. But we need to follow rule: include a section ONLY when posting has real, specific content for it. We have content for Skills (knowledge of software, ability to troubleshoot, etc.) but those are also in qualifications. Might be redundant. Better to combine qualifications into Requirements section. Preferred qualifications could be part of Requirements or separate? Could make a Requirements section that includes both required and preferred? But rule: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements (including required and preferred qualifications, education, work environment), Schedule. That's four sections. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we list each duty as
• . For Requirements we list each qualification as
• . For Schedule we can just put a

  with the schedule text. We must preserve all substantive information, not invent or summarize away detail. Must not drop any detail. So we need to include all responsibilities listed, all qualifications, education, work environment, schedule. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Powered by JazzHR" at end - that's boilerplate, remove. We must not include Job ID/requisition numbers as headings; none present. We must not create Pay/Benefits sections unless posting actually states them; not present. Now craft HTML. Structure:

  About the role

  Position summary paragraph.

  Responsibilities

  • ...
  ...

  Requirements

  • Minimum 2 years of hands-on experience and/or technical training in Oil & Gas Allocation and Custody Transfer measurement systems.
  • Hands-on experience with both liquid and natural gas measurement is required.
  • Knowledge and experience with LACT meter proving and liquid measurement systems.
  • Knowledge and experience with sales gas meter calibration and gas measurement systems.
  • Knowledge of regulatory requirements and procedures related to: liquid and gas meter operation, meter calibration and proving, oil and gas sampling for custody transfer, oil and gas measurement and sampling for allocation.
  • Knowledge of single-phase oil and natural gas metering using positive displacement, helical turbine, orifice, and/or V-cone measurement technologies.
  • Ability to troubleshoot, test, calibrate, and maintain measurement equipment and associated instrumentation.
  • Ability to navigate and use Windows-based measurement programs such as OMNICOM, PCCU32, and MON2000, or similar measurement software.
  • Working knowledge of Microsoft Word, Excel, and Outlook.
  • Ability and willingness to travel offshore and work a 14/14 deepwater rotation with 12-hour shifts.
  • Ability to safely work around heavy equipment and in changing offshore environmental conditions.
  • Strong commitment to safety, accuracy, regulatory compliance, and documentation.
  • Preferred: Previous offshore or deepwater oil and gas experience.
  • Preferred: Experience independently maintaining and troubleshooting liquid and gas measurement systems in an oil and gas production environment.
  • Preferred: Experience with both allocation and custody transfer measurement.
  • Preferred: Current applicable offshore safety certifications and credentials.
  • Education: High school diploma or equivalent required. Associate or bachelor’s degree in instrumentation, measurement, electronics, engineering technology, or a related technical field is helpful but not required.
  • Work Environment: This position requires rotational work at a deepwater offshore facility. Employees must be capable of working 12-hour shifts, climbing stairs and ladders, working around operating production equipment, and performing duties in changing offshore environmental conditions while following all required safety procedures.
  But we have a lot of items; maybe we can group some. However we must preserve all detail; we can keep each as separate
• . That's okay. But note: The schedule is also mentioned in Requirements (Ability and willingness to travel offshore and work a 14/14 deepwater rotation with 12-hour shifts.) and also in Work Environment (Employees must be capable of working 12-hour shifts...). We also have a separate Schedule section from the posting: "Schedule: 14 Days On / 14 Days Off Shift: 12-Hour Days". To avoid duplication, we could still include Schedule section with that specific sentence, but we must not duplicate content? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should avoid redundant duplication? It says remove duplicated lines. So we should not duplicate the same sentence. The schedule appears in both the Requirements bullet and Work Environment bullet and also as a separate line. We need to decide how to handle. We could keep the schedule info only in the Schedule section, and remove it from Requirements and Work Environment to avoid duplication. However the requirement bullet about ability to work 14/14 is a substantive qualification; we could keep it there but then we would have duplication with Schedule section. The rule says remove duplicated lines. So we should avoid having the same exact sentence appear twice. We can rephrase or keep one instance. Better: Keep the schedule details in the Schedule section as a concise statement, and in Requirements we can mention ability to work offshore and 12-hour shifts but not repeat the 14/14 rotation? Actually the requirement bullet includes both ability to travel offshore and work a 14/14 deepwater rotation with 12-hour shifts. That's specific. If we move the schedule to its own section, we could keep the requirement bullet but maybe change to "Ability and willingness to travel offshore and work offshore rotations." But that would be summarizing away detail (removing 14/14). Not allowed. Thus we need to keep the detail somewhere. We could keep it in Requirements bullet and not have a separate Schedule section, but the posting explicitly has a Schedule line. The rule says include a section ONLY when the posting has real, specific content for it. It does have schedule content. So we should include Schedule section. To avoid duplication, we could keep the schedule bullet in Requirements but maybe we can note that the schedule is covered in the Schedule section and not repeat? But that would be omitting detail from Requirements (the ability to work 14/14). However the requirement bullet also includes ability to travel offshore; we could keep that but drop the 14/14 part? That would be summarizing away detail (the 14/14). Not allowed. Alternative: Keep schedule in Schedule section, and in Requirements we keep the ability to travel offshore but not mention the rotation; but we would be losing the 14/14 detail. However the schedule section already contains that detail, so overall the detail is preserved (just placed elsewhere). The requirement bullet would be less specific but still true. Is that considered summarizing away detail? We are removing the 14/14 from the requirement bullet but it's still present in schedule section. The requirement bullet originally said "Ability and willingness to travel offshore and work a 14/14 deepwater rotation with 12-hour shifts." If we change it to "Ability and willingness to travel offshore." we are removing the 14/14 and 12-hour shifts detail. Those details are still present in schedule section. The requirement bullet becomes less specific but not inaccurate. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail would be if we omitted the detail entirely. Since we keep it elsewhere, it's not omitted. However we are altering the original phrasing; is that allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid rephrasing, but we should avoid losing detail. Changing the bullet to a less specific version could be considered summarizing away detail (since we removed specifics). Safer to keep the original bullet unchanged and also have schedule section, but then we have duplication of the same sentence (the schedule line appears as a bullet and also as schedule section). That's duplicated lines, which we should remove. However we could keep the bullet as is and not have a separate schedule section; but then we lose the explicit schedule heading. The rule says include a section ONLY when posting has real, specific content for it. It does have schedule content, but we could argue that the schedule content is already covered in the Requirements bullet (ability to work 14/14). So we could omit a separate Schedule section to avoid duplication. The rule says "Prefer a few substantive sections over many thin ones." So maybe better to not have a separate Schedule section if the info is already captured elsewhere. However the schedule line is a distinct piece of metadata; but we can incorporate it into Requirements or Work Environment. The rule about sections: we should include a section only when the posting has real, specific content for it. It does have schedule content, but we could still include it as a subsection under Requirements? But they want headings like Schedule. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect Schedule as a possible heading. If we have schedule content, we should include a Schedule section. To avoid duplication, we could keep the schedule content only in the Schedule section and remove it from Requirements and Work Environment. But then we lose the explicit requirement about ability to work 14/14 from Requirements. However we could add a requirement bullet about ability to work offshore (without specifying rotation) and still keep the schedule detail in Schedule section. But that would be removing the 14/14 detail from the requirement bullet, which is summarizing away detail from that bullet. However the overall detail is still present in the schedule section. The rule about preserving ALL substantive information likely means we cannot omit any detail anywhere in the output. It doesn't say each detail must be in its original location. So moving the detail to a different section is acceptable as long as it's preserved. Changing the wording is okay as long as we don't lose meaning. If we change "Ability and willingness to travel offshore and work a 14/14 deepwater rotation with 12-hour shifts." to "Ability and willingness to travel offshore." we lose the 14/14 and 12-hour shifts detail from that sentence, but those details appear elsewhere. So overall we haven't lost any detail. However we have changed the original phrasing; is that allowed? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid rephrasing. So we could rephrase to avoid duplication. Thus we can have: Requirements bullet: "Ability and willingness to travel offshore." (but we lose the 14/14 and 12-hour shifts). To preserve that detail, we put it in Schedule section: "Schedule: 14 Days On / 14 Days Off Shift: 12-Hour Days." Thus the requirement bullet is less specific but the detail is preserved elsewhere. This seems