Diego Garcia: Harbor Pilot (Contingency)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info; remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove the EEO paragraph at end. Also remove "Belong, Connect and Grow at KBR" maybe it's not boilerplate but it's a tagline; but it's substantive? It's a statement about culture; we can keep as a section maybe "About KBR" but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should limit headings to those examples? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those headings where appropriate. So we need to map content to those headings.
We have:
- About the role: could include Program Summary and Job Summary.
- Responsibilities: Roles And Responsibilities.
- Requirements: Minimum experience, citizenship, clearance, retired Navy, leadership, driver's license, etc. Also maybe Education.
- Qualifications: maybe same as Requirements? Could combine.
- Skills: maybe leadership, management skills.
- Benefits: KBR Benefits.
- Pay: not specified, so we should NOT include Pay section.
- Schedule: not specified, so omit.
We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits is stated, so include Benefits.
We must not include headings with filler text. So we will include only those sections with real content.
We need to output only HTML fragment, no /, no markdown.
We'll produce something like:
About the role
Program Summary ...
Job Summary ...
Responsibilities
- Prepare and coordinate the Daily Harbor Schedule...
...
Requirements
- Minimum of three (3) years’ experience as an Unlimited Tonnage Harbor and Docking Pilot or Chief Harbor Pilot.
- Must be U.S. citizens.
- Must possess Special Background Investigation (SBI), secret clearance.
- Must be retired U.S. Navy, E-7 or above is preferred.
- Superior leadership and management skills.
- Must hold a valid driver’s license.
Maybe also Education as part of Requirements or Qualifications. Could add a Qualifications
with Education and Certifications.
But we have to avoid duplication. The posting includes "BASIC JOB QUALIFICATIONS: (Knowledge, Skills, and Abilities (KSAs):" and "JOB SPECIFICATIONS: SPECIAL CERTIFICATIONS OR TRAINING". Also Education.
We could combine into Requirements and Qualifications sections.
Let's decide:
- About the role: Program Summary + Job Summary.
- Responsibilities: Roles And Responsibilities.
- Requirements: Minimum experience, citizenship, clearance, retired Navy preference, leadership/management skills, driver's license.
- Qualifications: Education (Bachelor's Degree in Maritime Studies etc), Special certifications/training (USCG license, Unlimited Tonnage rating, NEC 0215, submit qualifications to COR).
- Skills: maybe leadership and management skills already covered; but we could keep Skills separate if we want. However we already have leadership in Requirements; maybe we can put Skills as leadership and management skills. But to avoid duplication, we could put Skills separate with leadership and management skills.
But we need to avoid thin sections. Perhaps combine Skills into Requirements.
Better: Use Requirements for experience, citizenship, clearance, retired Navy, driver's license. Use Qualifications for education and certifications. Use Skills for leadership and management skills.
But we have to ensure we don't create empty sections.
Let's extract content precisely.
Program Summary paragraph: "KBR provides full-spectrum base operations support to Naval Support Facility Diego Garcia, a remote location in the British Indian Ocean Territory. Our robust supply chain ensures on-time delivery of mission-critical supplies, and our team conducts essential port and airfield operations in this geographically complex environment. The KBR team is over 1,000 people strong, providing not only life support services such as water treatment, electricity, and telecom/antenna maintenance, but also quality of life services like Morale, Welfare, and Recreation (MWR) and an award-winning dining facility."
Job Summary: "The Harbor Pilot is responsible for the safe and efficient navigation, piloting, docking, and scheduling of all naval, civilian, and commercial vessels operating within Diego Garcia Harbor and surrounding waters. This role serves as a key liaison between military and civilian stakeholders and ensures harbor operations fully support mission-critical activities."
Now Responsibilities list: many bullet points. We'll capture each as - .
Let's list them:
- Prepare and coordinate the Daily Harbor Schedule for review and approval by the Port Operations Officer.
- Pilot U.S. Navy, Military Sealift Command, civilian, and foreign-flagged vessels of all classes and unlimited tonnage into and out of Diego Garcia Harbor.
- Operate in all environmental conditions, including darkness, reduced visibility, strong currents, heavy rain, and gale-force winds.
- Direct and coordinate the simultaneous operation of multiple tugboats, pusher boats, and support craft during vessel maneuvering, docking, unmooring, and anchoring.
- Consult nautical charts, maps, tide tables, weather reports, and navigation systems to determine safe vessel movements.
- Set vessel courses and speeds using expert knowledge of local waters, including depths, tides, currents, weather patterns, and navigational hazards.
- Ensure vessel movements avoid reefs, shoals, and other hazards by utilizing navigational aids such as sector lights, channel markers, buoys, and land-based navigation aids.
- Advise ship Masters on local harbor rules, safety procedures, and lagoon customs requirements.
- Supervise naval and civilian personnel engaged in docking, berthing, and mooring of vessels, floating docks, cranes, and barges.
- Serve as the primary liaison with:
- Naval Support Facility Diego Garcia
- Commander Squadron Two
- Military Sealift Command
- Tenant and supported commands
- Coordinate all harbor movements of ships, small craft, cargo barges, fuel barges, and LCM operations to ensure uninterrupted mission support.
- Act as Docking Master, developing and executing vessel-specific mooring plans for Deep Draft Wharf and POL Fueling Pier operations.
- Determine and supervise proper placement of pier fenders, docking camels, and mooring configurations based on vessel size and requirements.
We need to format the sublist under "Serve as the primary liaison with:" maybe as nested list? But spec says use
- for any list of duties/requirements/benefits. Could treat each liaison item as separate
- under a parent? Could just list them as separate items. We'll keep as separate
- items.
Now Requirements (BASIC JOB QUALIFICATIONS):
- Must be U.S. citizens.
- Must possess Special Background Investigation (SBI), secret clearance.
- Must be retired U.S. Navy, E-7 or above is preferred.
- Superior leadership and management skills.
- Must hold a valid driver’s license.
Also Minimum of three (3) years’ experience as an Unlimited Tonnage Harbor and Docking Pilot or Chief Harbor Pilot. That is a requirement.
Now Qualifications (Education and Certifications):
Education: Bachelor’s Degree in Maritime Studies (BS in Marine Transportation, Marine Engineering, Naval Architecture) or other related maritime fields, based on a four-year course of study from an accredited university or college.
Special Certifications or Training:
- Must be properly licensed by the USCG (or other recognized regulatory body) and be Unlimited Tonnage rated or have prior Navy experience with NEC 0215 qualifications and have had an exemplary record as a Navy Pilot.
- U.S. Navy Harbor and Docking Pilot (QM-0215)
- Submit qualifications to Contracting Officer Representative (COR) for approval prior to hiring.
We could combine into a list.
Now Benefits: KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development.
Also "Belong, Connect and Grow at KBR" is a tagline; maybe we can include as a short paragraph under About the role or separate section? But heading list does not include a specific heading for culture; we could incorporate into About the role as a paragraph.
We must not include EEO boilerplate.
Now produce HTML.
We'll need to ensure we don't include any extra text outside HTML.
Let's craft.
We'll start with
About the role
then two elements: program summary and job summary.
Then
Responsibilities
then with each responsibility as - .
Then
Requirements
then with each requirement.
Then Qualifications
then maybe two for education and certifications? Or
for certifications. We'll do for education, then
for certifications.
Then Benefits
then for benefits description.
We must not add Pay or Schedule.
Check for any duplicated lines: none.
Now ensure we preserve all substantive info: Did we miss anything? The phrase "Belong, Connect and Grow at KBR" and the following paragraph about Zero Harm culture etc. That's substantive but not covered by headings. Could we add a
About KBR
? Not in allowed headings but instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. However they say "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings where appropriate, but we could also use other headings if needed? 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 to be safe we should stick to those. The culture paragraph could be placed under About the role as a paragraph.
Thus we can add a third
under About the role containing that culture paragraph.
Let's extract that paragraph: "At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together."
We
for prose. We must include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info; remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove the EEO paragraph at end. Also remove "Belong, Connect and Grow at KBR" maybe it's not boilerplate but it's a tagline; but it's substantive? It's a statement about culture; we can keep as a section maybe "About KBR" but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should limit headings to those examples? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those headings where appropriate. So we need to map content to those headings.
We have:
- About the role: could include Program Summary and Job Summary.
- Responsibilities: Roles And Responsibilities.
- Requirements: Minimum experience, citizenship, clearance, retired Navy, leadership, driver's license, etc. Also maybe Education.
- Qualifications: maybe same as Requirements? Could combine.
- Skills: maybe leadership, management skills.
- Benefits: KBR Benefits.
- Pay: not specified, so we should NOT include Pay section.
- Schedule: not specified, so omit.
We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits is stated, so include Benefits.
We must not include headings with filler text. So we will include only those sections with real content.
We need to output only HTML fragment, no /, no markdown.
We'll produce something like:
About the role
About the role
Program Summary ...
Job Summary ...
Responsibilities
- Prepare and coordinate the Daily Harbor Schedule... ...
Requirements
- Minimum of three (3) years’ experience as an Unlimited Tonnage Harbor and Docking Pilot or Chief Harbor Pilot.
- Must be U.S. citizens.
- Must possess Special Background Investigation (SBI), secret clearance.
- Must be retired U.S. Navy, E-7 or above is preferred.
- Superior leadership and management skills.
- Must hold a valid driver’s license.
Qualifications
with Education and Certifications. But we have to avoid duplication. The posting includes "BASIC JOB QUALIFICATIONS: (Knowledge, Skills, and Abilities (KSAs):" and "JOB SPECIFICATIONS: SPECIAL CERTIFICATIONS OR TRAINING". Also Education. We could combine into Requirements and Qualifications sections. Let's decide: - About the role: Program Summary + Job Summary. - Responsibilities: Roles And Responsibilities. - Requirements: Minimum experience, citizenship, clearance, retired Navy preference, leadership/management skills, driver's license. - Qualifications: Education (Bachelor's Degree in Maritime Studies etc), Special certifications/training (USCG license, Unlimited Tonnage rating, NEC 0215, submit qualifications to COR). - Skills: maybe leadership and management skills already covered; but we could keep Skills separate if we want. However we already have leadership in Requirements; maybe we can put Skills as leadership and management skills. But to avoid duplication, we could put Skills separate with leadership and management skills. But we need to avoid thin sections. Perhaps combine Skills into Requirements. Better: Use Requirements for experience, citizenship, clearance, retired Navy, driver's license. Use Qualifications for education and certifications. Use Skills for leadership and management skills. But we have to ensure we don't create empty sections. Let's extract content precisely. Program Summary paragraph: "KBR provides full-spectrum base operations support to Naval Support Facility Diego Garcia, a remote location in the British Indian Ocean Territory. Our robust supply chain ensures on-time delivery of mission-critical supplies, and our team conducts essential port and airfield operations in this geographically complex environment. The KBR team is over 1,000 people strong, providing not only life support services such as water treatment, electricity, and telecom/antenna maintenance, but also quality of life services like Morale, Welfare, and Recreation (MWR) and an award-winning dining facility." Job Summary: "The Harbor Pilot is responsible for the safe and efficient navigation, piloting, docking, and scheduling of all naval, civilian, and commercial vessels operating within Diego Garcia Harbor and surrounding waters. This role serves as a key liaison between military and civilian stakeholders and ensures harbor operations fully support mission-critical activities." Now Responsibilities list: many bullet points. We'll capture each as- for any list of duties/requirements/benefits. Could treat each liaison item as separate
- under a parent? Could just list them as separate items. We'll keep as separate
- items.
Now Requirements (BASIC JOB QUALIFICATIONS):
- Must be U.S. citizens.
- Must possess Special Background Investigation (SBI), secret clearance.
- Must be retired U.S. Navy, E-7 or above is preferred.
- Superior leadership and management skills.
- Must hold a valid driver’s license.
Also Minimum of three (3) years’ experience as an Unlimited Tonnage Harbor and Docking Pilot or Chief Harbor Pilot. That is a requirement.
Now Qualifications (Education and Certifications):
Education: Bachelor’s Degree in Maritime Studies (BS in Marine Transportation, Marine Engineering, Naval Architecture) or other related maritime fields, based on a four-year course of study from an accredited university or college.
Special Certifications or Training:
- Must be properly licensed by the USCG (or other recognized regulatory body) and be Unlimited Tonnage rated or have prior Navy experience with NEC 0215 qualifications and have had an exemplary record as a Navy Pilot.
- U.S. Navy Harbor and Docking Pilot (QM-0215)
- Submit qualifications to Contracting Officer Representative (COR) for approval prior to hiring.
We could combine into a list.
Now Benefits: KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development.
Also "Belong, Connect and Grow at KBR" is a tagline; maybe we can include as a short paragraph under About the role or separate section? But heading list does not include a specific heading for culture; we could incorporate into About the role as a paragraph.
We must not include EEO boilerplate.
Now produce HTML.
We'll need to ensure we don't include any extra text outside HTML.
Let's craft.
We'll start with
About the role
then twoelements: program summary and job summary. Then
Responsibilities
then- with each responsibility as
- .
Then
Requirements
then- with each requirement.
Then
Qualifications
then maybe twofor education and certifications? Or
- for certifications. We'll do
for education, then
- for certifications.
Then
Benefits
thenfor benefits description. We must not add Pay or Schedule. Check for any duplicated lines: none. Now ensure we preserve all substantive info: Did we miss anything? The phrase "Belong, Connect and Grow at KBR" and the following paragraph about Zero Harm culture etc. That's substantive but not covered by headings. Could we add a
About KBR
? Not in allowed headings but instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. However they say "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings where appropriate, but we could also use other headings if needed? 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 to be safe we should stick to those. The culture paragraph could be placed under About the role as a paragraph. Thus we can add a third
under About the role containing that culture paragraph. Let's extract that paragraph: "At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." We
- .
Then