Senior Commissioning Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions (none present). Need to preserve all substantive info. We need to parse the posting: Position Title: SENIOR COMMISSIONING ENGINEER (ignore) Location: FIELD OFFICE (maybe location is metadata; could be included in a short p) FLSA Class: Exempt (metadata) Responsible to: Operations Engineering Manager (metadata) Position Summary: ... (prose) Essential Duties And Responsibilities: list of duties (many bullet-like sentences) Other Qualifications: list (education, experience, knowledge, abilities) Preferred Qualifications: list (more specifics) Then some generic statements about description, EEO etc (remove). We need sections: About the role (could contain Position Summary and maybe location/metadata). Responsibilities (Essential Duties). Requirements (maybe "Other Qualifications" as requirements). Qualifications (maybe "Preferred Qualifications" as qualifications? But we have both Requirements and Qualifications sections; we need to decide mapping. Typically Requirements = mandatory qualifications; Qualifications = preferred? But we have both Other Qualifications (mandatory) and Preferred Qualifications. Could put mandatory under Requirements, preferred under Qualifications. Skills maybe combine some skills from both? Could also have Skills section for specific technical skills. Benefits, Pay, Schedule: we have schedule info: rotational schedule three weeks field, one week remote; also willingness to travel 75%; ability to work extended hours, weekends. That's schedule info. No explicit pay or benefits mentioned. So we should not create Pay or Benefits sections because no specific content. Schedule section we can include. Thus sections: About the role (summary + location maybe), Responsibilities, Requirements, Qualifications, Skills, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all duties, qualifications, etc. We need to be careful not to include boilerplate like EEO, etc. Let's extract content. Position Summary paragraph: "The Senior Commissioning Engineer is responsible for the successful startup, commissioning, troubleshooting, testing, and operational turnover of VoltaGrid power generation systems throughout North America. This role serves as the primary technical representative during equipment installation, startup, and commissioning activities, ensuring systems are installed, tested, and operating safely and reliably before being transitioned to Operations. Working a rotational schedule of approximately three weeks in the field followed by one week working remotely, this position partners closely with field technicians, project managers, engineering teams, operations personnel and vendors to deliver reliable power generation solutions." We could include location metadata maybe in a short p: "Location: FIELD OFFICE". Also FLSA Class etc maybe not needed but could be minor metadata folded into short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location, FLSA, Reports to in a short p maybe under About the role. Thus About the role section:

  About the role

  then a

  containing position summary plus maybe location etc. Could separate into multiple

  but okay. Responsibilities: list of duties from "Essential Duties And Responsibilities". Each sentence starts with a verb. We'll make each as

• . Let's copy them exactly: - Lead commissioning, startup, functional testing, and operational validation of power generation systems at customer sites. - Verify proper installation of electrical, mechanical, instrumentation, controls, and auxiliary systems prior to startup. - Perform system checkout, equipment calibration, loop checks, and pre-commissioning inspections. - Execute commissioning procedures and performance testing to ensure systems meet design specifications and customer requirements. - Troubleshoot electrical, mechanical, controls, PLC, engine, generator, and balance-of-plant issues during startup and commissioning. - Serve as the primary technical liaison between VoltaGrid, contractors, vendors, and customer personnel throughout the commissioning process. - Coordinate daily commissioning activities with project management, construction, operations, and field service teams. - Develop commissioning punch lists, track deficiencies, and verify completion of corrective actions. - Conduct root cause analysis for startup issues and implement effective corrective actions. - Support system energization, synchronization, load testing, and operational acceptance testing. - Ensure all commissioning activities are performed safely and in compliance with company procedures, customer requirements, and regulatory standards. - Prepare commissioning reports, startup documentation, turnover packages, test records, and field engineering reports. - Provide technical training and operational guidance to customers and Operations personnel during project turnover. - Support warranty investigations, post-commissioning troubleshooting, and field modifications as required. - During remote rotation weeks, prepare commissioning documentation, review project drawings, develop commissioning procedures, support engineering teams, analyze field issues, and assist with planning upcoming deployments. - Support emergency field response and travel to customer locations as required. That's all. Requirements: from "Other Qualifications". Items: - Bachelor's degree in Electrical Engineering, Mechanical Engineering, Engineering Technology, or related technical field preferred. - 5+ years of experience in commissioning, startup, field engineering, power generation, industrial construction, or related technical environments. - Strong knowledge of generators, switchgear, medium- and low-voltage electrical systems, PLC controls, instrumentation, engines, and balance-of-plant equipment. - Experience commissioning industrial power generation, distributed energy systems, microgrids, utility-scale equipment, or similar infrastructure. - Demonstrated ability to troubleshoot complex electrical, mechanical, and controls issues under field conditions. - Ability to read and interpret electrical one-line diagrams, P&IDs, control schematics, wiring diagrams, and construction drawings. - Strong understanding of commissioning processes, startup sequencing, lockout/tagout, energized work practices, and industrial safety standards. - Excellent verbal and written communication skills with strong customer-facing abilities. - Ability to prioritize multiple projects in fast-paced field environments. - Willingness to travel approximately 75%, working a rotational schedule of three weeks at project sites followed by one week working remotely from home. - Ability to work extended hours, weekends, and flexible schedules during project startup as needed. Note: Some of these overlap with schedule; but we keep them in Requirements. Qualifications: from "Preferred Qualifications". Items: - Experience commissioning reciprocating engines, gas turbines, generators, switchgear, substations, or microgrid systems. - Experience with PLC platforms such as Allen-Bradley, Siemens, GE, or Schneider. - Experience with protective relays, ideally SELs - Familiarity with SCADA systems, protective relays, generator controls, and synchronization equipment. - Knowledge of NFPA 70, NFPA 70E, NEC, IEEE, and power generation industry standards. - Customer-facing experience supporting industrial, oil & gas, utility, or data center projects. - OSHA 30, NFPA 70E, or other industrial safety certifications. - Experience supporting projects from construction through final commissioning and operational turnover. We could also consider Skills section: maybe extract specific skills like "Strong knowledge of generators, switchgear..." etc. But we already have those in Requirements. Could create Skills section for technical skills like PLC platforms, protective relays, SCADA, NFPA standards, etc. However we must not invent or summarize away detail; we can move some items to Skills if they are skill-like. But we need to preserve all info; we can duplicate? Better to keep them in Requirements and Qualifications; Skills maybe not needed if no distinct skill list. But we could create Skills section for items like "Excellent verbal and written communication skills", "Ability to prioritize multiple projects", etc. However those are already in Requirements. To avoid thin sections, we might omit Skills if no specific skill list beyond those already covered. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. But we have many skill-like items in Requirements and Qualifications; maybe we can combine them into Requirements and Qualifications only. However the instruction says we must use sections only when posting has real specific content for it. It does not require us to use all possible headings. So we can omit Skills if we think it would be thin. But we have communication skills etc. Could still be considered Skills. But we already have them in Requirements; we could move them to Skills to avoid duplication? But we must preserve all info; duplication is okay but not required. Better to keep them in Requirements and Qualifications and not create Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Schedule: we have schedule info in Requirements (willingness to travel..., rotational schedule...). Also in Position Summary we have schedule mention. Could create Schedule section with that info. But we already have schedule info in Requirements; moving it to Schedule would duplicate. Perhaps better to create Schedule section for schedule details and remove from Requirements. However we must preserve all info; we can keep schedule info in Schedule section and also maybe keep a brief note in Requirements? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid duplication? Not explicitly forbidden. However we could keep schedule info only in Schedule section and remove from Requirements to avoid redundancy. But then we lose some other requirements like willingness to travel 75% etc. That is schedule-related. So we can move those to Schedule. Thus Requirements will exclude schedule items. Let's separate. From Other Qualifications list, schedule-related items: - Willingness to travel approximately 75%, working a rotational schedule of three weeks at project sites followed by one week working remotely from home. - Ability to work extended hours, weekends, and flexible schedules during project startup as needed. These go to Schedule. Also Position Summary includes schedule mention; but we can keep that in About the role maybe. Thus Requirements list will be the remaining items: - Bachelor's degree in Electrical Engineering, Mechanical Engineering, Engineering Technology, or related technical field preferred. - 5+ years of experience in commissioning, startup, field engineering, power generation, industrial construction, or related technical environments. - Strong knowledge of generators, switchgear, medium- and low-voltage electrical systems, PLC controls, instrumentation, engines, and balance-of-plant equipment. - Experience commissioning industrial power generation, distributed energy systems, microgrids, utility-scale equipment, or similar infrastructure. - Demonstrated ability to troubleshoot complex electrical, mechanical, and controls issues under field conditions. - Ability to read and interpret electrical one-line diagrams, P&IDs, control schematics, wiring diagrams, and construction drawings. - Strong understanding of commissioning processes, startup sequencing, lockout/tagout, energized work practices, and industrial safety standards. - Excellent verbal and written communication skills with strong customer-facing abilities. - Ability to prioritize multiple projects in fast-paced field environments. Now Qualifications (Preferred) list as above. Schedule section: include: - Willingness to travel approximately 75%, working a rotational schedule of three weeks at project sites followed by one week working remotely from home. - Ability to work extended hours, weekends, and flexible schedules during project startup as needed. Also maybe mention from Position Summary: "Working a rotational schedule of approximately three weeks in the field followed by one week working remotely". That's same. We'll put schedule items as
  • . Now About the role: include Position Summary paragraph plus location metadata maybe. Location: FIELD OFFICE. FLSA Class: Exempt. Responsible to: Operations Engineering Manager. We can combine into a short p: "Location: FIELD OFFICE. FLSA Class: Exempt. Reports to: Operations Engineering Manager." Then another p for Position Summary. Thus About the role section:

    About the role

    Location: FIELD OFFICE. FLSA Class: Exempt. Reports to: Operations