PILATUS PC-12 PILOT IN COMMAND

We need to produce HTML fragment with sections: About the role? The posting includes "THE ROLE" and "IDEAL CANDIDATE". Also "Compensation & Benefits". Also "WHY RIDGELINE". Also maybe "Pay" and "Benefits" sections but we already have compensation & benefits. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting has: - About the role? Not explicitly but "THE ROLE" is a heading. Could map to "About the role" or "Responsibilities". The content under THE ROLE is a list of duties. So we can have

  About the role

  with
  • items. - IDEAL CANDIDATE: could be "Requirements" or "Qualifications". We'll use

    Requirements

    with list. - Compensation & Benefits: includes salary range, health/dental/vision, 401(k), company-paid recurrent training, full-time, variable schedule with occasional overnight travel. Also later "Pay: $105,000.00 - $140,000.00 per year Benefits 401(k)Dental insuranceEmployee discountPaid time off". There's duplication. We need to preserve all substantive info. We'll combine. We need separate sections for Pay and Benefits? The instruction says we can use headings like Pay, Benefits, Schedule. But we prefer few substantive sections. Could combine compensation and benefits into one section "Compensation & Benefits". That's acceptable as a heading? The allowed headings list includes Benefits, Pay, Schedule. But we can also use other headings? 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. Likely we should stick to those examples. However "Compensation & Benefits" is not in list but could be considered as Benefits? Might be okay to use Benefits heading and include pay inside? But they said never create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state pay and benefits, so we can have separate Pay and Benefits sections. However we want few sections; maybe we can have Pay and Benefits separate but that's two sections. Could also have a single "Compensation & Benefits" but that's not in the examples; risk of being considered not following instruction. Safer to follow examples: Use Pay and Benefits headings. Also we have Schedule info: variable schedule with occasional overnight travel. So we can have Schedule section. Thus sections: About the role (or Responsibilities), Requirements, Pay, Benefits, Schedule, Why Ridgeline (maybe "About the company"? Not in list but could be "About the role"? Not exactly. Could omit? But we should preserve substantive info. The "WHY RIDGELINE" is a description of company culture. Could be placed under a heading like "About the company" but not in list. However we could incorporate into "About the role" or maybe omit? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include that info somewhere. Could add a

    after sections without a heading? But they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to add a heading like "About Ridgeline" maybe not in list but still a heading. However they said 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. So we can use other headings as long as they are

    . We'll include a section "Why Ridgeline" as

    Why Ridgeline

    with paragraph. Now we need to remove boilerplate: "APPLY Please submit your resume to: Amanda Monger at a.monger@flyridgelinemt.com" is application instruction, remove. Also "Work Location: In person" maybe minor metadata; we could fold into a short

    or drop. It's not essential but could be kept as a short paragraph under maybe "About the role"? But it's location. Could drop as minor metadata? The instruction says fold minor metadata into a short

    or drop it. We'll drop it. Also duplicate lines: Pay appears twice; we will include once. Now construct HTML. We'll start with

    About the role

    then
    with items from THE ROLE. List items: - Serve as PIC for Pilatus PC-12 operations. - Conduct Part 91 and Part 135 charter and on-demand operations. - Operate safely and professionally in single- and dual-pilot environments. - Serve as SIC when operationally appropriate. - Deliver a consistently professional passenger and customer experience. - Maintain accurate flight, aircraft, and operational documentation. - Exercise sound aeronautical judgment and uphold a strong safety culture. - Represent Ridgeline Aviation with professionalism both in the aircraft and on the ground. Now

    Requirements

    (or Qualifications). Use list: - Previous Pilatus PC-12 experience strongly preferred. - Part 135 instrument minimums required. - FAA First Class Medical required. - Mountain flying experience preferred. - Strong customer-service and communication skills. - Professional, dependable, self-sufficient, and safety-minded. - Takes ownership of the aircraft, the mission, and the passenger experience. Now

    Pay

    then

    with salary range: $105,000–$140,000 base salary (or $120,000–$140,000? The posting shows both: earlier "$105,000–$140,000 Base Salary" then later "Compensation & Benefits $120,000–$140,000 annual base salary" then "Pay: $105,000.00 - $140,000.00 per year". We need to preserve ALL substantive information; we should not invent or summarize away detail. So we need to include both mentions? They are overlapping but slightly different. To preserve all, we could include both statements. But that might be redundant. However we must not invent or summarize away detail; we can include both as separate sentences. Let's include: "Base salary range: $105,000–$140,000 per year." and also "Compensation & Benefits lists annual base salary of $120,000–$140,000." Might be confusing. Better to combine: state that the base salary range is $105,000–$140,000 per year, with a noted range of $120,000–$140,000 in the compensation section. But that's summarizing. The instruction says do NOT invent or summarize away detail. Summarizing is not allowed? It says "do NOT invent or summarize away detail". So we should not combine ranges into a single range if that loses detail. We need to keep both statements exactly as they appear. So we can have two

    sentences: one from the top line: "$105,000–$140,000 Base Salary". Another from Compensation & Benefits: "$120,000–$140,000 annual base salary". And later "Pay: $105,000.00 - $140,000.00 per year". That's three statements. We'll keep them all. Now

    Benefits

    then
    list: - Health, dental & vision insurance - 401(k) with company contributions - Company-paid recurrent training - Full-time position - Variable schedule with occasional overnight travel (maybe schedule) - Employee discount - Paid time off But variable schedule with occasional overnight travel is schedule info; maybe move to Schedule section. We'll keep schedule separate. Thus Benefits list: Health, dental & vision insurance; 401(k) with company contributions; Company-paid recurrent training; Employee discount; Paid time off. Now

    Schedule

    then

    variable schedule with occasional overnight travel. Now

    Why Ridgeline

    then

    with the paragraph: "At Ridgeline Aviation, we're building a flight department around people who care about the job and the people they serve. We value pilots who are professional without being pretentious, confident without being complacent, and capable of operating independently while being a dependable member of a small team. If you take pride in your flying, care about the passenger experience, and hold yourself to a high professional standard, we'd like to hear from you." Now ensure no application instructions. Also remove duplicated lines like "Full-time position" appears in Benefits and also maybe elsewhere; we kept it in Benefits but also we have schedule separate. It's okay. Now produce HTML fragment. Check for any leftover boilerplate: "RIDGELINE AVIATION | BELGRADE, MONTANA Full-Time | $105,000–$140,000 Base Salary" - we have not included that as heading; we could incorporate location and employment type as a short

    maybe under About the role? But it's minor metadata; we can drop or fold into a short

    . The instruction says fold minor metadata into a short

    or drop it. We'll drop it to keep concise. Now output only HTML. Let's craft:

    About the role

    • Serve as PIC for Pilatus PC-12 operations.
    • Conduct Part 91 and Part 135 charter and on-demand operations.
    • Operate safely and professionally in single- and dual-pilot environments.
    • Serve as SIC when operationally appropriate.
    • Deliver a consistently professional passenger and customer experience.
    • Maintain accurate flight, aircraft, and operational documentation.
    • Exercise sound aeronautical judgment and uphold a strong safety culture.
    • Represent Ridgeline Aviation with professionalism both in the aircraft and on the ground.

    Requirements

    • Previous Pilatus PC-12 experience strongly preferred.
    • Part 135 instrument minimums required.
    • FAA First Class Medical required.
    • Mountain flying experience preferred.