Float Rotor Wing Pilot

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph about Life Flight Network (mission). Then description of Float Rotor Wing Pilot responsibilities: "The Float Rotor Wing Pilot is responsible for professionally and safely operating aircraft for LFN to facilitate care of critically ill and/or injured patients. Rotor Wing Pilots possess strong aviation skills, a keen sense of safety, superior customer service skills, and the ability to effectively communicate with a variety of people, one-on-one and in large groups, sometimes in highly stressful situations. The Float Rotor Wing Pilot will be required to work varied shifts, including days, nights, weekends, and holidays. Our float positions are full-time. The purpose of our float pilot is to cover open shifts on the schedule due to line pilot vacations, leave, etc. Seven shifts are guaranteed in the pay period, but may not be consecutive or all at the same base." Then "Qualifications & Skills" list: bullet points. Then "Benefits That Go Above and Beyond" with subsections: Compensation & Retention, Health & Wellness, Family & Lifestyle, Growth & Recognition. We need to decide sections: About the role (intro), Responsibilities (duties), Requirements (maybe qualifications), Skills (maybe separate), Benefits (list). Pay and Schedule: we have schedule info (varied shifts, days, nights, weekends, holidays, full-time, seven shifts guaranteed). Pay: "Competitive pay" mentioned under Benefits but not specific amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule info (varied shifts, etc.) and mentions "Competitive pay". So we can include Schedule section with details. Pay section: we have "Competitive pay" but no specifics; rule says never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is vague but maybe considered placeholder? It's not a specific number or range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay" which is a statement about pay, albeit vague. However the rule about filler text includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is not exactly those but still vague. Might be considered filler? Safer to not create Pay section if no concrete info. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Pay section. Schedule: we have specifics: varied shifts including days, nights, weekends, holidays; float positions full-time; purpose to cover open shifts; seven shifts guaranteed in pay period, may not be consecutive or all at same base. That's substantive. So include Schedule. Benefits: we have detailed benefits list. So include Benefits. About the role: intro paragraph about Life Flight Network and role description. Could be About the role. Responsibilities: duties like operating aircraft, pre/post-flight inspections, planning flights, loading, analyzing weather, maintaining logs, operating ground equipment, proficiency in MS Office, communication skills, travel, driver's license, etc. Requirements: qualifications like education, experience, flight hours, certificates, etc. Skills: maybe separate but could combine with qualifications. The posting has "Qualifications & Skills" heading. We could split into Requirements (education/experience) and Skills (specific abilities). But we need to avoid thin sections. Could combine into one section "Requirements & Skills". However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It allows us to choose which headings to use. We could use "Requirements" for the qualifications list and maybe not separate Skills. But we have many skill items (communication, MS Office, etc.) which could be under Skills. Might be better to have Requirements (education/experience/certificates) and Skills (abilities). That yields two substantive sections. Let's extract: About the role: Intro paragraph about Life Flight Network and the role's purpose. Responsibilities: list of duties: - Professionally and safely operating aircraft for LFN to facilitate care of critically ill and/or injured patients. - Perform pre- and post-flight inspections. - Plan flights. - Assist in loading of passengers, baggage and cargo. - Analyze weather conditions. - Maintain logs and records, as required, and prepare written reports. - Operate aircraft tug, tractor, and/or ground handling equipment. - Proficient in Microsoft Office Suite. - Excellent grammar; verbal and written communication, and customer service skills. - Travel by personal or company vehicle throughout LFN’s service area is required. - Must hold a valid driver’s license, have access to an automobile in good repair, be able to provide proof of auto insurance, meet LFN’s Driver’s Policy requirements and able to travel whenever or wherever business needs necessitate. Also mention strong aviation skills, keen sense of safety, superior customer service skills, ability to communicate with variety of people, one-on-one and in large groups, sometimes in highly stressful situations. Could be part of responsibilities or skills. Requirements (education/experience/certificates): - High School diploma or equivalent required. - Bachelor’s Degree preferred. - 5 years’ experience as a professional pilot preferred. - 2000 hours Total Time required. - 1500 hours Pilot in Command. - 1000 R/W Turbine hours required. - 100 hours instrument time preferred, 50 hours required. - 100 hours of nighttime required. - Pilots with air medical transportation experience preferred. - Pilots with NVG experience preferred. - Mountain experience preferred. - Experience evaluated on a case-by-case basis. - Must hold FAA Commercial Helicopter Certificate with Instrument Helicopter Rating. - Must have and maintain FAA second class flight physical. Skills: - Strong aviation skills. - Keen sense of safety. - Superior customer service skills. - Ability to effectively communicate with a variety of people, one-on-one and in large groups, sometimes in highly stressful situations. - Proficient in Microsoft Office Suite. - Excellent grammar; verbal and written communication. - Customer service skills (already). - Travel by personal or company vehicle throughout LFN’s service area. - Valid driver’s license, automobile, insurance, etc. (maybe more requirement than skill). But we can keep skills as communication, MS Office, customer service, etc. Schedule: - Varied shifts, including days, nights, weekends, and holidays. - Float positions are full-time. - Purpose: cover open shifts on the schedule due to line pilot vacations, leave, etc. - Seven shifts guaranteed in the pay period, but may not be consecutive or all at the same base. Benefits: list as given. We need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include boilerplate like EEO, drug screening, equal opportunity employer, etc. Remove those lines at end. Also remove navigation, cookie, legal, etc. Not present. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we don't repeat job title as heading. The job title is "Float Rotor Wing Pilot". Not used as heading. We must not put Job ID/requisition numbers as headings. Now craft HTML. Structure:

  About the role

  Life Flight Network is one of the most prominent not-for-profit air ambulance organizations. As the industry's trailblazers, we constantly raise the bar for safety, excellence, social justice, and innovation in the skies and on the ground. Being a member of our esteemed team means embarking on a career defined by distinction, pride, compassion, and unwavering service. We are a group of dedicated professionals who thrive in a high-octane, collaborative environment. Our collective brilliance shines as we come together to make a difference in the communities we serve. Here, you'll find the best and the brightest talents, who are second to none in their dedication and expertise. Are you ready to unleash your potential and make a real impact in your community? If you're seeking a rewarding and fulfilling path, then look no further - Life Flight Network is the place where your aspirations will take flight! The Float Rotor Wing Pilot is responsible for professionally and safely operating aircraft for LFN to facilitate care of critically ill and/or injured patients.

  But we might split responsibilities separate. Better: About the role: just the intro about organization and role purpose? Could include the first paragraph up to "The Float Rotor Wing Pilot is responsible for professionally and safely operating aircraft for LFN to facilitate care of critically ill and/or injured patients." Then Responsibilities section will list duties. Let's do that. About the role paragraph: includes description of organization and role purpose. Responsibilities: list of duties. Requirements: list of qualifications. Skills: list of abilities. Schedule: list. Benefits: list with subheadings? The benefits section has subheadings: Compensation & Retirement, Health & Wellness, Family & Lifestyle, Growth & Recognition. Should we create sub-sections? The instruction only mentions using

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings, but we should follow the pattern. Could keep Benefits as

  Benefits

  and then inside use

  for subcategories? Not specified. Safer to keep Benefits as one section with a list that includes all benefits items, maybe grouped with

  and
  • but we could also keep subheadings as or

    . However we must not invent headings not in the list? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It likely expects only those headings. So we should not add other heading levels like

    . We can keep Benefits as

    Benefits

    and then inside use

    or

    with benefit items. We can preserve the subcategories as within
    • or as separate

      paragraphs. We need to preserve all substantive information; we can keep the subheadings as inside

    • or as separate

      before a list. Simplify:

      Benefits

      Compensation & Retirement

      • Competitive pay
      • 401(k) with a 100% vested employer contribution — your future grows from day one
      • Tenure bonuses to reward your loyalty and long-term commitment

      Health & Wellness

      • Comprehensive Medical, Dental, and Vision coverage
      • Company-paid Life and AD&D Insurance
      • Company-paid Short & Long-Term Disability Insurance for peace of mind
      • Wellness Reimbursement Program to support your health goals
      • Complimentary Life Flight Network Membership for you and your household
      ... etc. That seems okay. Now ensure we don't include boilerplate: "All candidates are subject to drug screening and background investigation. Life Flight Network is an equal opportunity employer." Remove. Now produce final HTML. Check for any repeated content: ensure we didn't miss any duty. Duties list from text: - Professionally and safely operating aircraft for LFN to facilitate care of critically ill and/or injured patients. - Rotor Wing Pilots possess strong