Experienced Biologist
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. 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 to include based on content.
We have content for About the role (first paragraph). Responsibilities (Your Impact...). Qualifications (required and preferred). Skills (maybe part of qualifications). Benefits (explicit). Pay (explicit). Schedule none.
We could combine Required and Preferred Qualifications into a Qualifications section with sublists? But we must use
- for any list of duties/requirements/benefits. Could have separate lists for Required and Preferred under Qualifications.
Skills: Could be extracted from required qualifications: Strong analytical and problem-solving skills, Excellent written and oral communication skills, Substantial biological field survey knowledge, Ability to work in remote conditions, Valid driver's license, Travel willingness, Safety track record. Those are more like qualifications/requirements. Might be better to keep them under Qualifications rather than separate Skills section to avoid thin sections.
Thus we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
But the instruction gave examples of possible headings; we can choose subset.
We need to ensure we preserve all substantive info. Let's extract each piece.
About the role: The first paragraph includes location, role description, detail-oriented candidate, ability to work independently/team, history completing botanical and wildlife surveys, supporting wetland inventories, experience to complete and manage biological field surveys including avian, wildlife, vegetation, wetland/waterway, sensitive species and T&E species, effective communication skills important for success especially while completing field work and working as part of larger team.
We should preserve that.
Responsibilities: The "Your Impact" paragraph: Support and help build the environmental project team working on transmission lines, fire hardening, renewable energy, oil and gas pipelines, transportation projects, environmental surveys, NEPA analyses, and permitting services. Support biological field survey efforts throughout the North Mountain Region, including Montana, Wyoming, Colorado, Utah, Idaho, and Oregon. Biological field surveys will include surveys for rare plants and threatened, endangered, and sensitive wildlife species. Assist with wetland and biological surveys, permitting, and documentation. Exercise responsible and ethical decision-making by adhering to WSP’s Code of Conduct and related policies and procedures. Perform additional responsibilities as required by business needs.
We should preserve that.
Qualifications: Required Qualifications list: Bachelor’s degree in Wildlife Biology, Environmental Science, Ecology, or other related field. Three to five (3-5) + years prior consulting work, ideally with linear corridor projects, e.g., pipelines and/or electric transmission. Strong analytical and problem-solving skills. Familiarity with the USFWS, BLM, USFS, and state-agency survey requirements. Attention to detail and commitment to quality and professionalism. Excellent written and oral communication skills. Substantial biological field survey knowledge. Must be able to work in remote conditions and independently or as part of a survey team as needed. Valid driver’s license and clean driving record. Must be willing and able to periodically travel throughout the region with potential travel throughout the U.S. Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies.
Preferred Qualifications: Northwest permitting experience – i.e. northern spotted owl, marbles murrelet, anadromous fish, etc. Experience in construction compliance monitoring. Experience in writing and managing the preparation of technical reports or permit applications. Experience organizing and managing complex field survey efforts for transmission line, pipeline, or renewable energy projects.
We could present as two lists under Qualifications: Required and Preferred.
Benefits: WSP provides a comprehensive suite of benefits focused on a providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings.
We could list as bullet list.
Pay: Expected Salary (all locations): $65,300 - $125,300. Expected Salary (Colorado only): $73,500 - $117,600. Also includes the disclaimer language about good faith belief etc. We need to preserve all substantive info, not just the range. The disclaimer is substantive? It's boilerplate but maybe considered part of compensation description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation disclaimer might be considered legal boilerplate? It's about compensation range and reserves right to pay more or less. Might be considered boilerplate but it's part of the compensation description. However, we need to preserve ALL substantive information; do NOT invent or summarize away detail. The disclaimer is not substantive detail about the job; it's a legal statement. Might be considered boilerplate to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal boilerplate about compensation. Likely we should remove it. But we need to keep the salary ranges. The instruction: "Prefer a few substantive sections over many thin ones." So we can include Pay section with just the salary ranges (maybe two lines). We can present as
Expected Salary (all locations): $65,300 - $125,300
and Expected Salary (Colorado only): $73,500 - $117,600
. That preserves substantive info.
We must not include Schedule.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ...
...
Qualifications
Maybe we split into Required and Preferred as subheadings? But we only allowed h3 for section headings. Could we use ? Not allowed. So we could have two separate sections: Required Qualifications and Preferred Qualifications each as h3. But that would be many thin
for prose. Do NOT repeat the job title as a heading. 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 to include based on content. We have content for About the role (first paragraph). Responsibilities (Your Impact...). Qualifications (required and preferred). Skills (maybe part of qualifications). Benefits (explicit). Pay (explicit). Schedule none. We could combine Required and Preferred Qualifications into a Qualifications section with sublists? But we must use
- for any list of duties/requirements/benefits. Could have separate lists for Required and Preferred under Qualifications.
Skills: Could be extracted from required qualifications: Strong analytical and problem-solving skills, Excellent written and oral communication skills, Substantial biological field survey knowledge, Ability to work in remote conditions, Valid driver's license, Travel willingness, Safety track record. Those are more like qualifications/requirements. Might be better to keep them under Qualifications rather than separate Skills section to avoid thin sections.
Thus we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
But the instruction gave examples of possible headings; we can choose subset.
We need to ensure we preserve all substantive info. Let's extract each piece.
About the role: The first paragraph includes location, role description, detail-oriented candidate, ability to work independently/team, history completing botanical and wildlife surveys, supporting wetland inventories, experience to complete and manage biological field surveys including avian, wildlife, vegetation, wetland/waterway, sensitive species and T&E species, effective communication skills important for success especially while completing field work and working as part of larger team.
We should preserve that.
Responsibilities: The "Your Impact" paragraph: Support and help build the environmental project team working on transmission lines, fire hardening, renewable energy, oil and gas pipelines, transportation projects, environmental surveys, NEPA analyses, and permitting services. Support biological field survey efforts throughout the North Mountain Region, including Montana, Wyoming, Colorado, Utah, Idaho, and Oregon. Biological field surveys will include surveys for rare plants and threatened, endangered, and sensitive wildlife species. Assist with wetland and biological surveys, permitting, and documentation. Exercise responsible and ethical decision-making by adhering to WSP’s Code of Conduct and related policies and procedures. Perform additional responsibilities as required by business needs.
We should preserve that.
Qualifications: Required Qualifications list: Bachelor’s degree in Wildlife Biology, Environmental Science, Ecology, or other related field. Three to five (3-5) + years prior consulting work, ideally with linear corridor projects, e.g., pipelines and/or electric transmission. Strong analytical and problem-solving skills. Familiarity with the USFWS, BLM, USFS, and state-agency survey requirements. Attention to detail and commitment to quality and professionalism. Excellent written and oral communication skills. Substantial biological field survey knowledge. Must be able to work in remote conditions and independently or as part of a survey team as needed. Valid driver’s license and clean driving record. Must be willing and able to periodically travel throughout the region with potential travel throughout the U.S. Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies.
Preferred Qualifications: Northwest permitting experience – i.e. northern spotted owl, marbles murrelet, anadromous fish, etc. Experience in construction compliance monitoring. Experience in writing and managing the preparation of technical reports or permit applications. Experience organizing and managing complex field survey efforts for transmission line, pipeline, or renewable energy projects.
We could present as two lists under Qualifications: Required and Preferred.
Benefits: WSP provides a comprehensive suite of benefits focused on a providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings.
We could list as bullet list.
Pay: Expected Salary (all locations): $65,300 - $125,300. Expected Salary (Colorado only): $73,500 - $117,600. Also includes the disclaimer language about good faith belief etc. We need to preserve all substantive info, not just the range. The disclaimer is substantive? It's boilerplate but maybe considered part of compensation description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation disclaimer might be considered legal boilerplate? It's about compensation range and reserves right to pay more or less. Might be considered boilerplate but it's part of the compensation description. However, we need to preserve ALL substantive information; do NOT invent or summarize away detail. The disclaimer is not substantive detail about the job; it's a legal statement. Might be considered boilerplate to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal boilerplate about compensation. Likely we should remove it. But we need to keep the salary ranges. The instruction: "Prefer a few substantive sections over many thin ones." So we can include Pay section with just the salary ranges (maybe two lines). We can present as
Expected Salary (all locations): $65,300 - $125,300
andExpected Salary (Colorado only): $73,500 - $117,600
. That preserves substantive info. We must not include Schedule. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:About the role
...
Responsibilities
- ... ...
Qualifications
Maybe we split into Required and Preferred as subheadings? But we only allowed h3 for section headings. Could we use? Not allowed. So we could have two separate sections: Required Qualifications and Preferred Qualifications each as h3. But that would be many thin