Field Engineer

We need to output HTML fragment with sections: About the role? Actually we have content: "About E-J" description, then Title/Role etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to extract content. We have: - About E-J: description of company. Could be "About the role"? Actually "About the role" is a heading for description of role? The posting includes "Position Summary" etc. We could treat "About the role" as the position summary and company description? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections accordingly. We need to decide what goes where. We have: - Position Summary: description of role: "E-J is seeking motivated and detail-oriented Assistant Project Managers/Field Engineers to support the execution of large-scale data center electrical construction projects..." That's about the role. So we can put that under

About the role

with

. - Responsibilities: list of duties under "What You’ll Do". That's a bullet list. So

Responsibilities

• ... each bullet. - Qualifications & Skills: includes qualifications and skills. Could split into Requirements and Qualifications and Skills? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide based on content. We have bullet list under "Qualifications & Skills": includes: - 1–5 years of field engineering or electrical construction experience, preferably on large commercial or mission-critical projects - Bachelor’s degree in engineering, construction management, or a related technical field; equivalent field experience considered - Proficiency in reading and interpreting electrical construction drawings, specifications, and equipment submittals - Working knowledge of the National Electrical Code (NEC) and electrical construction best practices - Proficiency in Microsoft Office Suite; experience with Procore, Bluebeam, or similar construction management platforms a plus - Strong organizational skills and attention to detail, with the ability to manage multiple open items simultaneously - Effective written and verbal communication skills; comfortable coordinating with field crews, subcontractors, and engineering staff - Ability to work full-time on a construction site and meet the physical demands of a field-based role Then "Nice To Haves": list of additional desirable experience. We could treat the main qualifications as "Requirements" and "Qualifications" maybe overlapping. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have to use headings only if we have content. We could make: -

  Requirements

  for the mandatory qualifications (first 8 bullets) -

  Preferred Qualifications

  not in list; but we have "Nice To Haves". Could be under "Skills"? Actually Skills section could contain both required and nice-to-have skills. But we have also "Advantages Of Working At E-J": list of benefits. That's benefits. Also "Salary Range: $75k-$105k/year" => Pay. Schedule? Not mentioned. So we should not create Schedule section. We also have "About E-J" description of company. Could be placed under "About the role"? Or maybe we could have a separate "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit company description maybe under About the role (makes sense). Or we could omit it? But we must preserve ALL substantive information. So we need to include company description somewhere. Could put it in About the role section as a preamble. Thus About the role section will contain both company overview and position summary. Now Responsibilities: list of duties. Requirements: maybe the mandatory qualifications (first 8 bullets). Qualifications: maybe the education/experience? But we already used Requirements. Could combine Requirements and Qualifications into one? But we need to follow instruction: use headings for those categories if we have content. We could have both Requirements and Qualifications sections, but ensure they are not thin. Let's split: - Requirements: mandatory experience, degree, proficiency in reading drawings, NEC knowledge, MS Office proficiency, organizational skills, communication skills, ability to work full-time. - Qualifications: maybe the "Nice To Haves" list? Actually those are nice-to-haves, not qualifications. But we could treat them as "Preferred Qualifications". However heading "Qualifications" could contain both required and preferred? Might be ambiguous. Better: Use Requirements for mandatory, Qualifications for preferred/nice-to-haves, Skills for technical skills like Procore, Bluebeam, BIM, etc. But we already have some skills in requirements. Let's examine content: Mandatory bullets: 1. 1–5 years of field engineering or electrical construction experience, preferably on large commercial or mission-critical projects 2. Bachelor’s degree in engineering, construction management, or a related technical field; equivalent field experience considered 3. Proficiency in reading and interpreting electrical construction drawings, specifications, and equipment submittals 4. Working knowledge of the National Electrical Code (NEC) and electrical construction best practices 5. Proficiency in Microsoft Office Suite; experience with Procore, Bluebeam, or similar construction management platforms a plus 6. Strong organizational skills and attention to detail, with the ability to manage multiple open items simultaneously 7. Effective written and verbal communication skills; comfortable coordinating with field crews, subcontractors, and engineering staff 8. Ability to work full-time on a construction site and meet the physical demands of a field-based role Nice-to-haves: - Experience on Tier III or Tier IV hyperscale or co-location data center projects - Familiarity with critical power systems, including 2N redundancy architectures, static transfer switches, and PDU configurations - Exposure to integrated systems testing (IST) or commissioning processes for mission-critical facilities - Knowledge of BICSI, Uptime Institute, or TIA-942 standards - Experience with BIM coordination or 3D clash detection in a multi-trade environment - OSHA 30 certification Thus we could map: - Requirements: first 8 bullets (mandatory) - Qualifications: nice-to-haves (preferred qualifications) - Skills: maybe technical skills like proficiency in MS Office, Procore, Bluebeam, NEC, BIM, etc. But we already have some overlapping. Alternatively, we could combine Requirements and Qualifications into one section "Requirements" and put nice-to-haves as a sub-list within that. But instruction says prefer few substantive sections over many thin ones. So maybe we should have: - About the role - Responsibilities - Requirements (including both mandatory and preferred) - Benefits - Pay We could omit Qualifications and Skills sections to avoid thin sections. But we need to use headings only when we have real specific content. If we omit Qualifications and Skills, that's fine. But we still have Skills content (like proficiency in MS Office, Procore, Bluebeam, etc.) which could be part of Requirements. So we can include them there. Thus final sections:

  About the role

  company description + position summary

  Responsibilities

  list of duties

  Requirements

  list of mandatory qualifications + nice-to-haves? Could separate with subheadings? But we cannot add extra headings beyond allowed. Could just list all bullets, maybe separate with a note? But we need to preserve all info. We could separate into two
  within the same section: one for mandatory, one for preferred. That's okay.

  Benefits

  list of advantages

  Pay

  Salary Range: $75k-$105k/year

  We should not include Schedule. Now ensure we remove boilerplate: EEO statement, etc. Also remove "Title/Role: Field Engineer Division: Major Projects Location: Fairless Hills, PA Reporting To". That's metadata; we should fold minor metadata into a short

  or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include location etc in a short

  maybe under About the role? But we already have a lot. Could add a short paragraph after company description: "Location: Fairless Hills, PA. Reports to Project Manager." But we might drop it as minor metadata. However we need to preserve ALL substantive information. Location is substantive? Probably yes. So we should include it somewhere. We can add a short

  after the company description: "Location: Fairless Hills, PA. Reports to Project Manager." That's minor metadata but we can include as a short paragraph. Now let's extract responsibilities list exactly as given: - Support the Project Manager in day-to-day field coordination and execution of data center electrical scopes - Interpret and work from electrical construction drawings, single-line diagrams, specifications, and equipment submittals - Monitor field installations for compliance with contract documents, NEC code, and applicable project specifications - Coordinate with the general contractor, other trades, and MEP engineers to resolve conflicts and maintain the schedule in a concurrent-trade environment - Track and manage RFIs, submittals, and field change notices; maintain organized and up-to-date documentation - Assist with procurement follow-up and delivery tracking for critical equipment, including switchgear, transformers, UPS systems, generators, PDUs, and bus duct - Support phased energization planning and coordination with commissioning agents and the owner’s technical teams - Conduct regular field walks to document progress, identify issues, and verify the quality of installation - Maintain accurate daily field reports, quantity tracking logs, and schedule look-aheads - Assist in quantity takeoffs, cost tracking, and subcontractor coordination as directed by the Project Manager - Participate in project meetings, including coordination meetings, OAC meetings, and safety briefings - Enforce E-J’s safety standards and site-specific safety plans; ensure compliance with NFPA 70E requirements for work on or near energized systems - Support closeout activities, including punch list management, as-built documentation, and final commissioning walkthroughs Now requirements list (mandatory): - 1–5 years of field engineering or electrical construction experience, preferably on large commercial or mission-critical projects - Bachelor’s degree in engineering, construction management, or a related technical field; equivalent field experience considered - Proficiency in reading and interpreting electrical construction drawings, specifications, and equipment submittals - Working knowledge of the National Electrical Code (NEC) and electrical construction best practices - Proficiency in Microsoft Office Suite; experience with Procore, Bluebeam, or similar construction management platforms a plus - Strong organizational skills and attention to detail, with the ability to manage multiple open items simultaneously - Effective written and verbal communication skills; comfortable coordinating with field crews, subcontractors, and engineering staff - Ability to work full-time on a construction site and meet the physical demands of a field-based role Nice-to-haves (preferred qualifications): - Experience on Tier III or Tier IV hyperscale or co-location data center projects - Familiarity with critical power systems, including 2N redundancy architectures, static transfer switches, and PDU configurations - Exposure to integrated systems testing (IST) or commissioning processes for mission-critical facilities - Knowledge of BICSI, Uptime Institute, or TIA-942 standards - Experience with BIM coordination or 3D clash detection in a multi-trade environment - OSHA 30 certification Benefits list: - Leading Electrical Contracting Organization Nationwide - Oldest Family-Owned and Operated Electric Contractor since 1899 - Job training and mentorship - Competitive