Archaeological Specialist (On-Call)

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. Need to extract content from posting. Let's parse: - About the role: The first paragraph describes ESA and the position: "Environmental Science Associates (ESA) is a 100% employee-owned environmental consulting firm... actively seeking On-Call Archaeological Field Technicians in the Northwest Region, including Seattle, WA, Portland, and Bend, OR." That's about the role. Also "Who You Are" is more like requirements. But we can treat "About the role" as description of job and location. - Responsibilities: "What You Will Do For ESA" includes duties: monitor construction activities, communicate, write logs, etc. Also earlier "You will participate in compliance monitoring and reporting activities for on-going construction projects; you will work near heavy equipment." That's responsibilities. - Requirements/Qualifications/Skills: The "Who You Are" section lists many requirements: 5+ years experience, associate's degree or equivalent, able to work with staff, valid driver's license, pass background check, operate field equipment, may direct small crews, familiar with active construction sites, knowledge of archaeological materials, minimum six months field experience in NW region, enjoy fieldwork, can walk long distances carrying backpack, lift at least 40 pounds, confident working outside remote/rural/urban, physical outdoor work may include various conditions, some night/weekend work may be required. Also "You are familiar with working on active construction sites..." etc. We need to decide which headings to use. Could combine Requirements and Qualifications into one section? The instruction says use headings for those categories if content exists. We can have separate sections if distinct content. But we can also combine to avoid thin sections. Prefer few substantive sections. We have Pay: there is CA Pay Transparency Clause "$24.93—$40.16 USD". That's pay range. So we can include Pay section with that. Benefits: mentions sick leave program, employee stock ownership program, tax deferred 401(k) plan if eligible. Also "You are eligible to participate in ESA’s sick leave program. You may be eligible to participate in our employee stock ownership program and tax deferred 401(k) plan if you meet the eligibility requirements for these plans." That's benefits. Also maybe other benefits not mentioned. So we can include Benefits. Schedule: mentions "Some night and/or weekend work may be required." That's schedule info. Could include Schedule section. We should not include headings with filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. We must preserve all substantive information. So we need to include all details from the posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the details, not omit them. We can keep them as is, maybe in

or

. We cannot summarize away detail, but we can keep them as is. However we need to format into HTML with headings and lists. We must not repeat the job title as a heading. The job title is "On-Call Archaeological Field Technicians". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Environmental Science Associates (ESA) is a 100% employee-owned environmental consulting firm with 50 years of experience across 21 offices in California, the Pacific Northwest, and the Southeastern United States. ESA is seeking On‑Call Archaeological Field Technicians for the Northwest Region, including Seattle, WA; Portland, OR; and Bend, OR.

Responsibilities

• Participate in compliance monitoring and reporting activities for ongoing construction projects.
• Work near heavy equipment on active construction sites.
• Monitor construction activities and identify archaeological resources.
• Effectively communicate with construction crews and project personnel.
• Write and maintain written daily surveys, monitoring, recordation, and cataloging logs, utilizing electronic data collection tools and GIS mapping applications.

Requirements

• 5+ years of experience in relevant academic and/or professional scientific or environmental consulting environment focused on archaeological contexts.
• Associate’s degree or equivalent combination of relevant college‑level coursework in archaeology, anthropology, history or related field, plus applied experience.
• Able to work with all staff levels and handle multiple tasks in a fast‑paced environment.
• Valid driver's license.
• Ability to pass a federal and state background check for project‑based assignments.
• Skills to safely operate field equipment, including sampling equipment, GPS units, tablets/smart phones, and job‑specific equipment.
• May be asked to direct small crews of archaeological technicians.
• Familiarity working on active construction sites and knowledge of archaeological materials common to the region.
• Minimum of six months of field experience or relative academic field experience in the Northwest Region.
• Enjoy fieldwork, able to walk long distances carrying a backpack, and lift at least 40 pounds.
• Confident working outside in remote, rural, and urban settings.
• Prepared for physical outdoor work in all types of weather, traversing uneven ground, steep terrain, forested environments, fields, arid lands, stream banks, and coastal/intertidal areas.
• Some night and/or weekend work may be required.

Benefits

• Eligible to participate in ESA’s sick leave program.
• May be eligible to participate in the employee stock ownership program.
• May be eligible to participate in the tax‑deferred 401(k) plan, subject to eligibility requirements.

Pay

CA Pay Transparency Clause: $24.93—$40.16 USD (actual compensation based on experience, education, skills, and location).

Schedule

Some night and/or weekend work may be required.

Check if any content duplicated: We included night/weekend work both in Requirements and Schedule. That's duplication but we need to preserve all substantive information; we could keep it only once. However the instruction says preserve ALL substantive information; does that mean we cannot omit any piece? If we put it only in Schedule, we still preserve the info (it's present). It's okay to not duplicate. But we have it also in Requirements list; we could remove from Requirements to avoid duplication. However the requirement list includes "Some night and/or weekend work may be required." That is a requirement. If we remove it, we might be losing that requirement detail. But we still have it in Schedule section; the info is still present. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary duplication? Not explicitly forbidden. However "Prefer a few substantive sections over many thin ones." Duplication may be considered thin? Not sure. Safer to keep it only once, maybe under Requirements as it's a requirement. Then Schedule could be omitted if no other schedule info. But we have schedule info only that line. If we move it to Requirements, we could drop Schedule section entirely because no other schedule specifics. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we drop Schedule, we avoid a thin section. So we can keep the night/weekend work under Requirements. Thus we will not have a Schedule section. Now Benefits: we have sick leave, ESOP, 401k. That's substantive. Pay: we have the range. Now ensure we didn't include any boilerplate: We omitted EEO, legal, vaccination statement, application instructions, etc. Also omitted "We are a 100% employee-owned environmental consulting firm who values diversity..." that's boilerplate? It's about culture but maybe considered boilerplate? It's not a legal EEO but still generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The diversity statement may be considered boilerplate but it's not EEO. It's about culture and values. Might be considered part of "Who We Are" section. The posting includes a "Who We Are" paragraph about being 100% employee-owned, valuing diversity, etc. That's somewhat substantive about company culture. Should we keep? It's not about the role directly but could be considered "About the role" or "About ESA". The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that info. However we already have an About the role paragraph that includes the first paragraph about ESA being 100% employee-owned etc. The later "Who We Are" repeats similar content. We can combine or keep one. To avoid duplication, we can incorporate the culture details into About the role. Let's extract the "Who We Are" paragraph: "We are a 100% employee-owned environmental consulting firm who values diversity and inclusion and celebrate the differences that make each of us unique. Our culture is built on mutual respect, recognizing that our variety of backgrounds, experiences, and perspectives leads to better solutions, which fosters our continued success for our employee-owners and clients. In accordance with ESA’s duty and responsibility to provide and maintain a safe workplace that is free of known hazards and to minimize the exposure to potential hazards, any employee who works from an ESA office or conducts any other in-person ESA work-related activity is required to submit their proof of vaccination status or have received an approved exemption and accommodation in states which this applies." That includes vaccination requirement. That might be considered legal/health requirement; maybe we should keep as it's a requirement for employment. However the instruction says remove legal boilerplate? Vaccination requirement could be considered legal/health requirement. It's not EEO but it's a condition. Might be considered substantive. However the instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. Vaccination requirement could be considered legal/health requirement, but it's not exactly boilerplate? It's a specific policy. Might be okay to keep. However we already have a requirement about background check; we could add vaccination requirement as a requirement. But we need to check if we should keep it. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The vaccination requirement is a legal requirement (state law). Might be considered legal boilerplate. Safer to remove it. However we need to preserve ALL substantive information; if we remove it, we might be removing a substantive requirement. But the instruction explicitly says to remove legal boilerplate. So we should remove that vaccination paragraph. Also the earlier "We are a 100% employee-owned environmental consulting firm who values diversity and inclusion..." is also somewhat boilerplate but maybe part of company culture. Not explicitly listed to remove. Could keep. But we already have a similar statement in the first paragraph about ESA being 100% employee-owned. We can keep that and maybe add the diversity/inclusion line. Let's craft About the role to include: ESA is 100% employee-owned, 50 years strong, 21 offices across CA, PNW, SE US. Actively seeking On-Call Archaeological Field Technicians in Northwest Region (Seattle, Portland, Bend). Also mention values: diversity and inclusion, culture of mutual respect, etc. That would capture the Who We Are content