Field Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Hensel Phelps" then "Job Description". 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/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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections: About Hensel Phelps (maybe "About the role"? Actually "About Hensel Phelps" is company description; we could treat as "About the role"? The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for company overview? Or we could use "About Hensel Phelps" but they said use headings e.g. About the role, Responsibilities... It doesn't forbid other headings, but they gave examples. Safer to use those exact headings when appropriate. For company description we could use "About the role". For responsibilities we have "Key Responsibilities". For qualifications we have "Qualifications" and "Preferred Qualifications". For education we have "Education". For benefits we have "Benefits". For physical requirements we could maybe put under "Requirements"? Or "Skills"? Physical requirements maybe under "Requirements". The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills? Not explicit but we could include skills under Qualifications. We'll include sections only if content present. We must remove boilerplate: Equal Opportunity Employer Statement, etc. Also remove duplicated lines. We need to preserve all substantive information: company description, job description paragraph, responsibilities list, qualifications list, education (maybe duplicate of qualifications), benefits list, physical requirements (maybe under Requirements). Also maybe include "Preferred Qualifications" as part of Qualifications. We need to format lists with

  • . For prose use

    . We need to avoid repeating job title (Field Engineer) as heading. We need to not include Pay/Schedule sections because not stated. We need to output only HTML fragment. Let's extract content: About Hensel Phelps paragraph: "At Hensel Phelps, we don’t just build projects—we build careers, communities, and a culture of excellence. As an employee-owned company, every person here plays a vital role in shaping our success and future. Guided by our core values of Ownership, Integrity, Builder mindset, Diversity, and Community, we combine cutting-edge technology with hands-on expertise to deliver landmark projects across the nation. When you join Hensel Phelps, you join a team that values your growth, empowers your ideas, and invests in your journey. Together, we create an environment where innovation thrives, safety is paramount, and every individual has the opportunity to make a lasting impact." Job Description paragraph: "The Field Engineer (FE) works directly for the Superintendent and is expected to exercise judgment and discretion in making recommendations, implementing policies and procedures and handling a wide variety of matters in the field. The position is normally, but not necessarily preparatory to becoming an Office Engineer or Project Engineer. The primary purpose of the position is to proactively aid the Superintendent in front-line field management. In addition, the position requires a considerable amount of work, responsibility, persistence, problem solving ability and good attitude, because the FE is responsible for the majority of the layout on a project, supervision of trade workers and subcontractor employees, as well as lift drawings, safety, and quality control responsibilities. Although the majority of a Field Engineer's time will be spent in the field, there are some duties which will require work in the field office. This is a safety sensitive position." Key Responsibilities list (multiple bullet points). Let's extract each: - Project layout (surveying) in conformance with design and contract documents - Check concrete forms for accuracy and adequacy of construction, including all embedded items, before placement of concrete - Perform production trend analysis for quantities of work in place and report for the weekly and monthly schedule and cost control reports - Assist with quality control, site safety initiatives and coordination of trade partners as delegated by the project superintendent - May include directing a small work force to gain supervisory experience - Coordinate material deliveries by checking material requirements in advance and comparing with the delivery status - Additionally, inspect materials delivered to the job for quantity, quality and condition, and report on missing and/or damaged items - Assist foremen and trade partners with interpretation of plans and specifications - Oversight of trade partners, as assigned, and direction of workforces (e.g., a labor crew) of employees or trade partner employees to gain supervisory experience - Participate in jobsite safety meetings, weekly safety audits, etc - Collaborate with the VDC team on VDC scope of work, execution plan and deliverables related to field operations - Review and navigate within the current 3D model viewing and scheduling software. Qualifications list: - A 4 -year degree in Civil, Structural, Architecture, Construction Management or related field - 1 year of experience and/or a combination of education and experience - Valid Driver’s License - Strong communication skills - Computer software - Microsoft Office Suite, specifically Excel-based templates, ProjectSight, Primavera and AutoDesk Suite Preferred Qualifications: Past internships in the construction industry are preferred, but not required. Physical Requirements: a paragraph describing moderate work etc. We'll treat as Requirements. Education: repeats qualifications: "A 4 -year degree in Civil, Structural, Architecture, Construction Management or related field. 1 year of experience and/or a combination of education and experience." This is duplicate; we can omit duplicate to avoid redundancy but must preserve all substantive information; we can keep it once. Benefits paragraph: "Hensel Phelps provides generous benefits for our salaried employees. This position is eligible for company paid medical insurance, life insurance, accidental death & dismemberment, long-term disability, 401(K) retirement plan, health savings account (HSA) (HSA not available in Hawaii), and our employee assistance program (EAP). It also is eligible for employee paid enrollment in vision and dental insurance. Hensel Phelps also believes in the importance of taking time to recharge. As a result, salaried employees are eligible for paid time off beginning upon hire. Salaried positions (project engineers and above) participate in an annual bonus plan, subject to company and employee performance. Salaried employees (this is all salaried employees) are also eligible for a company cell phone or cell phone allowance in accordance with company policy. Further, salaried employees (project engineers and above) also receive either a vehicle or vehicle allowance in accordance with Hensel Phelps’ policies. Based on position location, a cost of living adjustment (COLA) may also be included (subject to periodic review and adjustment)." We need to format benefits as list? The instruction: Use

    • for any list of duties/requirements/benefits. So we should turn benefits into list items. However the benefits paragraph includes sentences; we can split into list items: company paid medical insurance, life insurance, accidental death & dismemberment, long-term disability, 401(K) retirement plan, health savings account (HSA) (HSA not available in Hawaii), employee assistance program (EAP), employee paid enrollment in vision and dental insurance, paid time off beginning upon hire, annual bonus plan (for project engineers and above), company cell phone or cell phone allowance, vehicle or vehicle allowance (for project engineers and above), cost of living adjustment (COLA) based on location. We'll keep the explanatory sentences maybe as

      then list? But instruction says use

      • for any list of benefits. So we can make a
        with each benefit as
        • . Might lose some nuance but okay. Physical Requirements: we can put under Requirements section as list? It's a paragraph describing moderate work etc. Could be list of items: Moderate Work. Exerting up to 50 pounds of force occasionally, and/or up to 25 pounds of force frequently, and/or 10 pounds of force constantly to move objects. The individual in this position will periodically walk, kneel, sit, crouch, reach, stoop, read/see, speak, push, pull, lift, stand, and finger/type. The frequency of each action varies by workflow and office activity. Then subpoints: Walking - ... Constantly operates a computer... etc. That's lengthy. We could keep as

          under Requirements. We need to avoid duplication: Qualifications and Education overlapping. We'll combine into Qualifications section maybe include education bullet. We must not include EEO boilerplate. Now produce HTML:

          About the role

          At Hensel Phelps, we don’t just build projects—we build careers, communities, and a culture of excellence. As an employee-owned company, every person here plays a vital role in shaping our success and future. Guided by our core values of Ownership, Integrity, Builder mindset, Diversity, and Community, we combine cutting-edge technology with hands-on expertise to deliver landmark projects across the nation. When you join Hensel Phelps, you join a team that values your growth, empowers your ideas, and invests in your journey. Together, we create an environment where innovation thrives, safety is paramount, and every individual has the opportunity to make a lasting impact.

          Job Description

          The Field Engineer (FE) works directly for the Superintendent and is expected to exercise judgment and discretion in making recommendations, implementing policies and procedures and handling a wide variety of matters in the field. The position is normally, but not necessarily preparatory to becoming an Office Engineer or Project Engineer. The primary purpose of the position is to proactively aid the Superintendent in front-line field management. In addition, the position requires a considerable amount of work, responsibility, persistence, problem solving ability and good attitude, because the FE is responsible for the majority of the layout on a project, supervision of trade workers and subcontractor employees, as well as lift drawings, safety, and quality control responsibilities. Although the majority of a Field Engineer's time will be spent in the field, there are some duties which will require work in the field office. This is a safety sensitive position.

          But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Job Description as a heading example, but we could use Responsibilities for duties. However we have a separate Responsibilities section for key responsibilities. The job description paragraph could be considered part of Responsibilities or About the role? The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. To be safe, we could map: About the role (company overview), Responsibilities (job description + key responsibilities), Requirements (qualifications + education + physical requirements), Benefits. But we need to keep lists separate. Maybe better: