Wildlife Biologist.

We need to output HTML fragment with sections: Duties (maybe "Responsibilities"? The posting uses "Duties" heading. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map "Duties" to maybe "Responsibilities". The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we need headings for sections present: Duties, Requirements, Qualifications. Possibly also "Conditions of employment" is part of Requirements? The posting includes "Requirements Conditions of employment". We'll treat that as part of Requirements. Also "Qualifications" includes many subparts: Who May Apply, Basic Education Requirement, etc. We'll keep as Qualifications. We need to use

• for any list of duties/requirements/benefits. So for duties list, we need bullet list. For requirements list (conditions of employment) also bullet list. For qualifications maybe not a list but paragraphs; but we can still use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes many paragraphs about benefits, etc. Those are not specifically listed as Benefits, Pay, Schedule sections. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting includes generic benefits description but not specific benefits like health insurance, retirement, etc. It says "A career with the U.S. government provides employees with a comprehensive benefits package." That's generic; not specific. So we should NOT create a Benefits section because no specific benefits listed. Similarly Pay: posting says "Salary includes applicable locality pay or Local Market Supplement." That's specific? It mentions salary includes locality pay. That's somewhat specific but not a numeric value. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Salary includes applicable locality pay or Local Market Supplement." is somewhat specific but still vague. Might be considered not specific enough? The instruction: "Prefer a few substantive sections over many thin ones." Probably we can include a Pay section with that sentence. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state something about salary includes locality pay. So we can include Pay section with that sentence. Schedule: posting mentions TDY up to 5% of time. That's schedule info (travel). So we can include Schedule section with that. Thus sections: Responsibilities (from Duties), Requirements (conditions of employment), Qualifications (who may apply, education, experience, etc.), Pay, Schedule. We need to ensure we don't include headings with empty content. Now extract duties bullet points: From "Duties Serve as lead field biologist, providing general oversight and continuing analysis of the daily operations of an installation-wide fishery/wildlife management program. Take a lead role in the development and implementation of a program covering a 61,000 acre installation that serves as a habitat for numerous flora, fauna, threatened or endangered species. Plan, coordinate, oversee, and/or conduct fish and wildlife management activities Prepare contract specifications and statements of work for fish and wildlife management requirements. Exercise considerable initiative and professional judgment to adapt guidelines to fit local circumstances. Make recommendations concerning the impact of programs and projects such as military training, construction, livestock grazing, and multiple land use activities. Utilize a computer to develop and maintain geographic information system (GIS) files and automated databases. Prepare articles on fish and wildlife species and other wildlife management topics for publishing. Serve as Team Leader and Subject Matter Expert (SME) on matters relating to waters of the United States. Assist in developing budget and funding requests." We'll make each as

• . Now Requirements: "Conditions of employment Appointment may be subject to a suitability or fitness determination, as determined by a completed background investigation. The duties of this position require the incumbent to possess or obtain and maintain a valid state Driver's License in one of the 50 U.S. states or possessions to operate vehicles. This position requires the employee drive a motor vehicle and successfully pass an Army approved defensive driving certification course. This position has a Temporary Duty (TDY) or business travel requirement of up to 5% of the time." We'll bullet those. Now Qualifications: large block. We need to preserve all substantive info. We'll break into paragraphs maybe but keep as

  . Could also use

  for subpoints like "Who May Apply:" list but that's huge. The instruction: Use
  • for any list of duties/requirements/benefits. For qualifications, not required but could still use list if it's a list. However the qualifications section includes many enumerated categories (Who May Apply: list). That is a list; we could make it a
    . But the instruction says for any list of duties/requirements/benefits. It doesn't forbid using lists elsewhere, but we can. However to be safe, we can keep as

    with line breaks? Better to use

    for the Who May Apply list because it's a list. Also the Basic Education Requirement could be a list. But we risk over-sectioning. The instruction: "Prefer a few substantive sections over many thin ones." So maybe keep Qualifications as a few paragraphs, not many lists. We'll preserve the text as is, but we need to ensure we don't include boilerplate like "See Current Department of Army Civilian Employees" etc. That's part of Qualifications; we should keep it. We'll need to strip out duplicated lines and application instructions. The posting includes many lines about "You will be asked to identify which category..." etc. That's part of Qualifications; we keep. We also need to remove EEO etc. Not present. Now Pay section: "Salary includes applicable locality pay or Local Market Supplement." Schedule section: "This position has a Temporary Duty (TDY) or business travel requirement of up to 5% of the time." Actually that's already in Requirements; but we might duplicate. However we already have that in Requirements as condition of employment. The instruction: do not repeat content? It didn't say not to repeat, but we should preserve all substantive information; duplication may be okay but better to avoid redundancy. Since the TDY is already in Requirements, we could still include Schedule section referencing that. But maybe better to keep Schedule separate with that sentence. However that would duplicate. The instruction didn't forbid duplication but we should aim to avoid filler. I'd keep Schedule section with that sentence (maybe rephrase). But we already have it in Requirements; maybe we can move it to Schedule and remove from Requirements? However Requirements includes other items like background investigation, driver's license, defensive driving. The TDY is also a condition of employment; it's fine to keep there. Having it also in Schedule would be duplication. I'd keep it only in Requirements and not create Schedule section if it's just same sentence. But the instruction says include Schedule section only if posting actually states them. It does state TDY requirement. So we could include Schedule section with that sentence, but we would then have duplicate. To avoid duplication, we could keep Schedule section and remove that sentence from Requirements? But then we lose that info in Requirements. However the requirement of TDY is also a condition of employment; but we could still keep it in Requirements as part of conditions; duplication may be okay but not ideal. The instruction didn't forbid duplication; it said preserve ALL substantive information; do NOT invent or summarize away detail. Duplication preserves detail, not summarizing away. So it's okay to have it in both sections. However they said "Prefer a few substantive sections over many thin ones." Duplication adds thin sections. Might be better to keep only one. I'd keep it in Requirements and not create Schedule section, because the schedule info is minimal and already captured. But then we would not have a Schedule section despite the posting stating it. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must create them if stated; it's optional but we should if we want to include that info. Since we already have it in Requirements, we could still create Schedule section but it's thin. I'd choose to not create Schedule section to avoid thin section. However the instruction also says "Prefer a few substantive sections over many thin ones." So better to omit Schedule. Thus sections: Responsibilities, Requirements, Qualifications, Pay. Now Pay: we have sentence about salary includes locality pay. We'll put that in

    . Now we need to output only HTML fragment, no /. Use

    for each section heading. Let's craft:

    Responsibilities

    • Serve as lead field biologist, providing general oversight and continuing analysis of the daily operations of an installation-wide fishery/wildlife management program.
    • Take a lead role in the development and implementation of a program covering a 61,000 acre installation that serves as a habitat for numerous flora, fauna, threatened or endangered species.
    • Plan, coordinate, oversee, and/or conduct fish and wildlife management activities
    • Prepare contract specifications and statements of work for fish and wildlife management requirements.
    • Exercise considerable initiative and professional judgment to adapt guidelines to fit local circumstances.
    • Make recommendations concerning the impact of programs and projects such as military training, construction, livestock grazing, and multiple land use activities.
    • Utilize a computer to develop and maintain geographic information system (GIS) files and automated databases.
    • Prepare articles on fish and wildlife species and other wildlife management topics for publishing.
    • Serve as Team Leader and Subject Matter Expert (SME) on matters relating to waters of the United States.
    • Assist in developing budget and funding requests.

    Requirements

    • Appointment may be subject to a suitability or fitness determination, as determined by a completed background investigation.
    • The duties of this position require the incumbent to possess or obtain and maintain a valid state Driver's License in one of the 50 U.S. states or possessions to operate vehicles.
    • This position requires the employee drive a motor vehicle and successfully pass an Army approved defensive driving certification course.
    • This position has a Temporary Duty (TDY) or business travel requirement of up to 5% of the time.

    Qualifications

    Who May Apply: Only applicants who meet one of the employment authority categories below are eligible to apply for this job. You will be asked to identify which category or categories you meet, and to provide documents which prove you meet the category or categories you selected. See Current Department of Army Civilian EmployeesCurrent Department of Defense (DOD) Civilian Employee (non-Army)Defense Civilian Intelligence Personnel System (DCIPS) Interchange AgreementDomestic Defense Industrial Base/Major Range and Test Facilities Base Civilian Personnel WorkforceInteragency Career Transition Assistance PlanLand Management Workforce Flexibility ActMilitary Spouses, under Executive Order (E.O.) 13473Non-Appropriated Fund Instrumentality (NAFI)Non-Department of Defense (DoD) TransferPriority Placement Program, DoD Military Reserve (MR) and National Guard (NG) Technician EligiblePriority Placement Program, DoD Military Spouse Preference (MSP) EligiblePriority Placement Program, DoD MR and NG Preference Eligible Tech Receiving Disability RetirementPriority Placement Program, DoD Retained Grade Preference EligibleReinstatementVeterans Employment Opportunity Act (VEOA) of 1998 In order to qualify, you must meet the education and experience requirements described below. Experience refers to paid and unpaid experience, including volunteer work done through National Service