Lead VDC Engineer

We need to output HTML fragment with headings

for sections present: About the role? Actually the posting includes "About Hensel Phelps" (company description) then "Job Description", "Key Responsibilities", "Qualifications", "Physical Requirements", "Education", "Benefits". Also maybe "About the role" not present. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. We must not repeat job title as heading if no real content. We need to preserve all substantive info, remove boilerplate (EEO, legal, etc). Also remove duplicated lines. We need to include sections only when posting has real specific content. We have: - About Hensel Phelps (company overview) -> could be "About the role"? Actually "About the role" is not present; but we have company description. Could we treat as "About Hensel Phelps"? 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? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect those standard headings. But we can still use

for any section heading we include, but they gave examples. Probably they want us to use those exact headings when applicable. For company overview maybe not needed; but we could include "About the role" with content from Hensel Phelps description? However "About the role" would be about the job, not company. The posting includes a job description paragraph after "Job Description". That could be considered "About the role". So we can put that under

About the role

. Then we have "Key Responsibilities" ->

Responsibilities

. Qualifications ->

Qualifications

. Physical Requirements maybe could be under "Requirements"? But they said Requirements heading. Could combine qualifications and physical requirements? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements as a generic heading for things like physical requirements, maybe also education? But Education is separate? Could be under Qualifications. However they have separate Education section in posting. We could treat Education as part of Qualifications, but they said preserve all substantive info; we could keep Education under Qualifications or separate heading? The instruction says use those headings; but we can also add other headings if needed? It 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 using those. Safer to stick to those headings and map content accordingly. Thus we need sections: - About the role: includes the Hensel Phelps overview? Actually the "About Hensel Phelps" is company overview, not role. The role description is under "Job Description". So we can combine both? Maybe About the role includes the job description paragraph: "The Lead VDC Engineer manages the information that utilizes the building model..." etc. That is substantive. - Responsibilities: list of key responsibilities (bullet points). Use

• . - Requirements: could include qualifications (education, experience, skills) and physical requirements? But they also have Qualifications heading separate. Might be better to have Qualifications section for education/experience/skills, and Requirements for physical requirements? But they gave both headings; we can use both. - Qualifications: maybe include education and experience? Actually they have Education separate; but we can put education under Qualifications. - Benefits: list benefits. - Pay and Schedule: not present, so omit. - Skills: not explicitly listed; but qualifications include technical knowledge etc. Could be under Qualifications. Thus we will output:

  About the role

  ... (the job description paragraph)

  Responsibilities

  • ... each responsibility

  Qualifications

  • ... education requirement, experience, skills etc.

  Requirements

  ... physical requirements description

  Benefits

  • ... benefits list
  We must not include boilerplate like Equal Opportunity Employer Statement. We need to preserve all substantive info: ensure we don't lose any details. 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 Lead VDC Engineer manages the information that utilizes the building model. This position supports the regional VDC leadership and the VDC implementation efforts of single large projects or multiple smaller projects. The lead VDC engineer works with on-site VDC engineers, BIM engineers and operations to implement and manage the project’s VDC execution plan." We could combine both into About the role? Or we could keep About Hensel Phelps as separate? But instruction says use headings like About the role, Responsibilities... So maybe we should put the company overview under About the role? Actually About the role would be about the job, not company. But we have no separate "About the role" heading in source. However we could treat the first paragraph as "About Hensel Phelps" but not a required heading. Could we omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that company overview somewhere. If we don't have a heading for it, we could just put it as a

  before any headings. That's allowed: we can have prose outside headings. The instruction says use

  for section headings (e.g...). It doesn't forbid having

  outside headings. So we can output a

  with the company overview, then

  About the role

  with the job description paragraph, then other sections. Thus:

  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.

  About the role

  The Lead VDC Engineer manages the information that utilizes the building model. This position supports the regional VDC leadership and the VDC implementation efforts of single large projects or multiple smaller projects. The lead VDC engineer works with on-site VDC engineers, BIM engineers and operations to implement and manage the project’s VDC execution plan.

  Now Responsibilities: list each bullet from "Key Responsibilities". Let's extract: - Support regional VDC training - Development, implementation and maintenance of project VDC execution plans and strategies in conjunction with the project manager and VDC manager - Management of information dissemination and issues resolution in the model - Quality assurance oversight on model reliability, structure and content - Assist in archiving of models from preconstruction through post construction - Assist VDC manager in project implementation of new software, processes and technology - Assist in creation of VDC coordination schedule and drive implementation with project superintendent support - Assist in providing real world project alignment and validation between survey and 3D models and integration with primary control - Support the Estimating department’s use of provided models for quantity survey, visualization and other communication needs - Support procurement efforts through model development, proposal and interview representation - Participate in the Book of 14 reporting and all point review reporting - Participate with the QC managers in review of the project QC audits. We need to preserve exactly as given. Ensure punctuation. Now Qualifications: extract from "Qualifications" section: - A 4-year degree in civil or structural engineering, architecture, or construction management - Minimum of 3-5 years’ experience on large commercial construction project - Self-motivated with the ability to work independently or within a team - Strong understanding of construction documents - Possess technical knowledge of commercial building design and documentation - Strong organizational skills and graphic communication skills - Computer software - Microsoft Office Suite, specifically Excel-based templates, and Autodesk Suite with the primary focus on 3D authoring tools and Manage Navisworks - A basic understanding of collaboration, 4D, 5D and 6D tools. Note: The bullet "Computer software - Microsoft Office Suite, specifically Excel-based templates, and Autodesk Suite with the primary focus on 3D authoring tools and Manage Navisworks" maybe we keep as is. Now Education section: "Education A 4-year degree in civil or structural engineering, architecture, or construction management." This duplicates the qualification about degree. We should not duplicate. Since we already have that in Qualifications, we can omit the separate Education heading to avoid duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should not repeat the same line. So we can keep the degree only once under Qualifications. Now Physical Requirements: extract the paragraph under "Physical Requirements". It's a long description. We'll keep as a

  under

  Requirements

  . Ensure we keep all details. Now Benefits: extract from "Benefits" section: - 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 preserve all that. Could be list items. Now we must exclude EEO statement etc. Now output HTML fragment only. Let's craft. Check for any duplicated lines: we removed duplicate degree line. Check for any boilerplate: removed "Equal Opportunity Employer Statement" and following legal text. Now ensure we didn't miss any substantive info: The "About Hensel Phelps" paragraph we kept as

  before headings. The "Job Description" paragraph we put under About the role. The "Key Responsibilities" list we put