Seasonal Aerial Application Specialist

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/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. Thus we need to decide which sections have real content. - About the role: Yes, we have prose. - Responsibilities: Yes, we have list of duties. - Requirements: Could be used for the "What We're Looking For" (soft requirements) but we also have Qualifications (hard requirements). The instruction lists both Requirements and Qualifications as possible headings. We need to decide how to split. Usually Requirements = mandatory qualifications; Qualifications = preferred or additional. But we can combine if content is thin. However we have both sets: Basic Qualifications (hard) and What We're Looking For (soft). Could map Basic Qualifications to Requirements, and What We're Looking For to Qualifications or Skills. But we also have Skills section for abilities like communication, attention to detail. We need to avoid thin sections. Let's see content: Basic Qualifications list: many items (certificates, experience, CDL, etc.) That's substantive. What We're Looking For list: passion for agriculture and technology, willingness to learn, ability to work independently/team, safety-focused mindset, compliance with drug-free policy. That's also substantive but could be considered Skills. Skills: Could include strong communication skills, attention to detail, ability to work independently/team, safety mindset, willingness to learn, etc. Benefits: "What You’ll Get Hands-on experience with cutting-edge drone tech Competitive seasonal pay Training and development to sharpen your skills A chance to be part of a forward-thinking team making a real impact" That's benefits. Pay: "Competitive seasonal pay" is mentioned under Benefits. Could be separate Pay section if we want, but instruction says prefer few substantive sections over many thin ones. Since Pay is just a phrase, maybe we include it within Benefits, not separate Pay section. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Competitive seasonal pay". So we could have a Pay section with that line. But we also have Benefits section with other benefits. Could combine Pay into Benefits? The instruction says prefer a few substantive sections over many thin ones. Having both Benefits and Pay might be thin. Better to have Benefits section that includes pay as one item. So we will have Benefits section with list: Hands-on experience with cutting-edge drone tech; Competitive seasonal pay; Training and development to sharpen your skills; A chance to be part of a forward-thinking team making a real impact. Schedule: The posting mentions "Willingness to work long seasonal hours outdoors in changing weather" and "Seasonal Position". No specific schedule like shift times. So we might not create a Schedule section because no specific schedule details (like hours per week, shift). The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state seasonal position and long seasonal hours, but not a schedule. Could we consider that as schedule content? It's vague. Better to omit Schedule section to avoid thin placeholder. Thus sections: About the role (prose), Responsibilities (list), Requirements (list of Basic Qualifications), Qualifications (list of What We're Looking For? Or Skills?), Benefits (list). We need to decide mapping to headings. We have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to pick which to use. Option: About the role (prose), Responsibilities (list of duties), Requirements (list of Basic Qualifications), Qualifications (list of What We're Looking For), Benefits (list of benefits). That's five sections. Could also combine Qualifications and Skills? But we have both sets. Alternatively, we could map What We're Looking For to Skills (since they are skills/attributes). Then we would have Requirements (Basic Qualifications), Skills (What We're Looking For). Qualifications heading could be omitted if we don't have separate qualifications beyond requirements. But we have Basic Qualifications as requirements; maybe we treat those as Requirements, and the "What We're Looking For" as Skills. Then we don't need Qualifications heading. That yields four sections: About the role, Responsibilities, Requirements, Skills, Benefits. That's five sections (including About). That seems reasonable. Check if any content for Qualifications separate from Requirements: Not really; we have Basic Qualifications which are requirements. So we can skip Qualifications heading. Thus final sections: - About the role: prose from opening paragraph. - Responsibilities: list of duties from "What You’ll Do" plus the detailed Flight Operations Essential Duties & Responsibilities list. We need to combine all duties into a single list? The instruction: Use

• for any list of duties/requirements/benefits. So we can combine all duty statements into one
  . Ensure we preserve all substantive information, not invent or summarize away detail. So we need to include each duty item exactly as stated. Let's extract duty items: From "What You’ll Do": - Apply crop protection and nutrients using precision drone technology - Operate advanced equipment and software to optimize flight paths and coverage - Monitor weather conditions to ensure safe and effective application - Support local agriculture by helping ensure healthy, productive fields From "Position Summary: The Aerial Application Specialist is responsible for operating drones to perform aerial spray applications, data collection, mapping, and other agricultural support tasks." This is a sentence; could be considered a duty but it's generic. Might be considered part of responsibilities but it's not a bullet. We could include as a prose

  maybe. But instruction says use

  • for any list of duties/requirements/benefits. This sentence is not a list item but could be a prose description. However we already have About the role prose; we could add a

    for position summary. But to avoid duplication, maybe we incorporate it into responsibilities as a list item? It's not a list but we could still make it a

  • . However the instruction says use
    • for any list of duties/requirements/benefits. If it's not a list, we could use

      . But we can also treat it as a duty item; it's okay. Then "Flight Operations Essential Duties & Responsibilities:" followed by a list: - Operate drones for aerial spray applications, photography, surveying, mapping, and data collection - Conduct pre-flight checks to ensure equipment functionality - Plan and coordinate flight missions based on weather, airspace restrictions, and safety protocols - Data Collection & Analysis - Capture images, video, and other data using specialized equipment - Process and analyze flight data for reporting and operational use - Equipment Maintenance - Perform routine maintenance and troubleshooting on drones and related equipment - Ensure all equipment is safe, clean, and operational - Communication & Coordination - Collaborate with ground teams, clients, and stakeholders during flight operations - Provide timely updates and report any issues or concerns - Documentation & Compliance - Maintain accurate flight logs, maintenance records, and incident reports - Training & Certification - Ensure compliance with FAA and other regulatory documentation requirements - Maintain current certifications and licenses required for drone operations - Assist in training team members or clients on drone protocols -