Construction Engineer I

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. No job title heading. No Job ID etc. Remove boilerplate, EEO, legal, application instructions, etc. Keep substantive info. We need to parse the job posting. Key sections: - About the role: likely the Job Description Summary paragraph: "SOLV Energy is a leading provider... Job Description Summary: The Construction Engineer I supports four core Construction Engineering functions..." That is about the role. - Responsibilities: list of duties: Warranty Forensics, Emerging Technologies Implementation, Construction Engineering Support During Operations, Pile Load Testing Support During Initial Design, General Engineering Responsibilities. Each has bullet points. - Requirements: maybe Minimum Skills or Experience Requirements? That includes education, experience, EIT, etc. Could be Requirements. - Qualifications: maybe overlapping with Requirements. But we need to decide: The posting has "Minimum Skills or Experience Requirements". Could treat as Requirements. Qualifications maybe not separate. Could combine. - Skills: maybe list of specific skills: reading drawings, understanding construction processes, attention to detail, problem solving, communication, proficiency with MS Office, exposure to CAD/GIS/drone/GPS, willingness to learn emerging tech, ability to conduct field work, sense of urgency, team-oriented, legally authorized to work in US. - Benefits: listed: medical, dental, vision, basic life and disability insurance, 401(k), vacation, sick and holiday pay. - Pay: Compensation Range: $61,942.00 - $77,428.00 Pay Rate Type: Salary - Schedule: Not explicitly mentioned. The role is remote and will require travel. Specific location details and expectations will be discussed during interview. No schedule like full-time, part-time, shift. Could we infer? Not given. So we should not create Schedule section unless posting actually states it. It does not state schedule. So omit. - Also we need to include maybe a short paragraph for metadata like remote, travel? Could be part of About the role or Responsibilities? The posting says: "This role is remote and will require travel. Specific location details and expectations will be discussed during the interview process." That's substantive info about role. Could be placed under About the role or maybe a separate section like "Work Arrangement". But we only allowed headings from list. Could incorporate into About the role paragraph. We must not repeat job title as heading. Must not put Job ID as heading. Must drop boilerplate: EEO, legal, unsolicited recruiter stuff, etc. We must preserve all substantive information: so we need to keep the remote/travel note, the four core functions description, the responsibilities bullet points, the minimum skills/experience, benefits, pay. We must not invent or summarize away detail. Must not use placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

SOLV Energy is a leading provider of infrastructure services to the power industry, designing, building and maintaining utility scale solar, battery storage and high voltage substation projects nationwide. The Construction Engineer I supports four core Construction Engineering functions across SOLV’s EPC operations by providing engineering coordination, technical communication, and documentation rigor. This role contributes to (1) Warranty Analysis, by gathering data and supporting engineering review of potential design or installation issues; (2) Emerging Technologies Implementation, by assisting with GPS-enabled pile driving, drone-based survey workflows, and new construction tools; (3) Construction Engineering Support During Operations, by coordinating RFIs, design updates, and field engineering clarifications; and (4) Pile Load Testing Support During Initial Design, by assisting with planning, scheduling, documentation, and engineering communication for pre-construction pile testing programs. This role is remote and will require travel; specific location details and expectations will be discussed during the interview process.

Then Responsibilities: we can have a heading

Responsibilities

then

with each duty as
• containing the bullet points. However each duty has sub-bullets. We could nest
  • ...
    ... but spec says use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll keep simple: each main duty as
    • and inside we can have
      for subpoints. That still uses
      • . Acceptable. Let's extract subpoints: Warranty Forensics: - Gather field data, photos, as-built information, and installation details to support warranty claim evaluations. - Document potential design, manufacturing, or installation concerns and organize findings for review by senior engineering staff. - Compare field conditions against design documents, specifications, and installation standards to help identify root causes of warranty-related issues. - Maintain accurate, traceable warranty documentation logs to support issue tracking, escalation, and resolution. - Assist in coordinating engineering input for remediation plans and communicating required actions to project teams and clients. Emerging Technologies Implementation: - Support the deployment of advanced construction technologies, including GPS enabled pile driving, drone-based topo capture, and machine control datasets. - Prepare and maintain engineering datasets used for GPS machine control, real time grading/terrain workflows, and other technology-enabled processes. - Assist with field execution of drone flights, data collection, and upload processes as required by construction and engineering teams. - Capture and organize field feedback on technology performance and communicate improvement opportunities to engineering leadership. - Participate in development, rollout, and continuous improvement of new construction technology SOPs. Construction Engineering Support During Operations: - Coordinate daily engineering information flow to field teams, ensuring timely distribution of drawing updates, clarifications, and consultant responses. - Manage RFIs by drafting clear, concise questions, gathering supporting documentation, routing to the correct engineering discipline, and tracking closure to avoid schedule delays. - Interpret and communicate project-specific design requirements such as SOLV standards, contract requirements, and permit conditions. - Maintain engineering document control systems, including drawing sets, data room folders, engineering exhibits, submittals, and version tracking. - Participate in constructability reviews by identifying missing details, design conflicts, or potential field execution risks. - Support owner/IE comment cycles by preparing comment logs, collecting consultant responses, and presenting organized summaries to project managers and field teams. - Monitor engineering deliverable timelines, identify at-risk items, and support mitigation efforts with internal and external engineering partners. Pile Load Testing Support During Initial Design: - Assist with coordinating pre-construction pile load testing activities, including drill-rig scheduling, field logistics, and test setup. - Document load test procedures, test sequences, and field results accurately and consistently. - Track, organize, and communicate pile test data to project engineers, geotechnical consultants, and design partners. - Ensure pile test documentation aligns with contract requirements, industry standards, and engineering expectations. - Support identification of soil behavior or foundation performance concerns based on load test observations and results. General Engineering Responsibilities: - Conduct drawing comparisons, quantity checks, and review of plan sets to identify potential discrepancies or missing information. - Participate in project site visits to gather field data, observe installation methods, validate design assumptions, and enhance constructability awareness. - Identify and escalate engineering risks such as conflicting details, missing information, or unforeseen field conditions. - Contribute to SOP, workflow, and internal database development, including lessons learned, testing procedures, and advanced technology processes. - Build strong working relationships with project managers, superintendents, field engineers, consultants, and internal engineering teams to support fast issue resolution. Now Requirements: maybe we treat "Minimum Skills or Experience Requirements" as Requirements. Could also split into Requirements and Qualifications and Skills. But we have limited headings; we can use Requirements for education/experience, Qualifications for certifications, Skills for abilities. However the posting lumps many items together. We need to decide how to split while preserving all info and not creating thin sections. We could make one section "Requirements" containing all the bullet points from Minimum Skills or Experience Requirements. That would be substantive. Then we could omit Qualifications and Skills sections to avoid thin ones. But the instruction says: "Prefer a few substantive sections over many thin ones." So we can combine. Thus we could have:

        Requirements

        • Bachelor’s degree in Engineering, Construction Management, Environmental Studies, or a closely related technical field (preferred).
        • 0–3 years of relevant experience, with the ability to perform tasks with guidance and grow toward independent execution (aligned with Engineer I expectations).
        • Engineer‑in‑Training (EIT) certification preferred or willingness to pursue certification.
        • Strong ability to read and interpret engineering drawings, including civil, structural, electrical, and geotechnical plans.
        • Foundational understanding of construction processes, testing practices (such as pile load testing), and engineering documentation.
        • High attention to detail with strong organizational skills and the ability to maintain accurate, disciplined documentation across multiple engineering workflows.
        • Problem‑solving mindset with the ability to identify inconsistencies, collect supporting information, and escalate engineering concerns appropriately.
        • Strong communication skills, capable of explaining design updates, gathering field information, and collaborating with project managers, engineers, and field teams.
        • Proficiency with Microsoft Office, especially Excel and Word; exposure to CAD, GIS, drone‑capture platforms, GPS machine‑control datasets, or similar tools preferred.
        • Willingness to learn and support emerging construction technologies, including drone‑based surveys, GPS‑enabled equipment, and digital field data systems.
        • Ability to conduct field work, including walking construction sites, collecting data, observing installation methods, and participating in testing activities.
        • Sense of urgency and ownership, able to support fast‑paced construction environments and respond quickly to engineering information needs.
        • Team‑oriented, with the ability to work collaboratively across engineering, operations, warranty, and technology‑focused groups.
        • Applicants must be legally authorized to work in the U.S. without requiring employer sponsorship now or in the future.
        That covers all. Now Benefits: we have bullet list.

        Benefits

        • Medical, dental, vision, basic life and disability insurance.
        • 401(k) plan.
        • Vacation, sick and holiday pay.
        Pay: we have compensation range and pay rate type.

        Pay

        Compensation Range: $61,942.00 - $77,428.00 (Salary)

        We could also separate but it's fine. We must not include Schedule. Now ensure we didn't include any boilerplate: we removed EEO, legal, recruiter instructions, Job Number, etc. Check that we kept all substantive info: The summary about role, remote/travel, four core functions, responsibilities (all subpoints), requirements (education, experience, EIT, abilities), benefits, pay. We omitted the line "Job Description: This job description reflects management's assignment of essential functions; it does not prescribe or restrict the tasks that may be assigned" - that's boilerplate, can drop. We omitted "Position Responsibilities and Duties:" heading as we used our own. We omitted "Minimum Skills or Experience Requirements:" heading as we incorporated. We omitted "SOLV Energy Is an Equal Opportunity Employer" etc. We omitted "SOLV Energy does not accept unsolicited candidate introductions..." etc. We omitted "Job Number: J13235". We omitted closing paragraph about join the team? That's maybe substantive? It's a call to action, could be considered boilerplate? It's not required to preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The closing line "If you’re interested in a meaningful career with a brighter future, join the SOLV Energy