Senior Power System Studies Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "Why Nexus", "What you can expect", "Work Environment & Physical Demands", "About Nexus Engineering Group", "Equal Opportunity Employer & Reasonable Accommodation", "Sponsorship & Work Authorization", "Third‑Party Agency Notice", etc. Also remove "The posted salary range..." etc? That's about pay; we need to include Pay section only if posting actually states them. The posting includes "The posted salary range represents the anticipated base pay for this position..." and then lists benefits. So we have pay info (salary range) and benefits. So we should include a Pay section with that info (maybe summarizing but not inventing). Must not create placeholder text like "commensurate with experience". The posting says "The posted salary range represents the anticipated base pay for this position in accordance with applicable pay-transparency requirements and may vary based on experience, qualifications, skills, certifications, work location, and market conditions." That's somewhat vague but it's actual content. We can include that as Pay section. Also benefits: list of benefits given. So Benefits section. Schedule: not explicitly stated; there is "Flexible work arrangements where business needs allow" under "What you can expect". Also "Flexible work arrangements where business needs allow" appears in Benefits list. There's no explicit schedule like full-time, etc. Might not include Schedule section if no concrete schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Schedule, we have "Flexible work arrangements where business needs allow" which is a schedule flexibility mention. Could be considered schedule content. But it's vague. Might still include Schedule section with that line. However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Flexible work arrangements where business needs allow" is not filler; it's actual statement. So we could include Schedule section with that. But also there is "Work Environment & Physical Demands" which includes occasional travel etc. That could be considered Schedule? Not exactly. Might be better to include a "Work Environment" section? Not in allowed headings list. The allowed headings are limited to those listed. So we should map content to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. About the role: likely the introductory paragraph: "Nexus Engineering Group is employee-owned, full-service, and built by the people who do the work. As a Senior Power System Studies Engineer, you’ll own the analytical studies that keep industrial power systems safe, reliable, and compliant — and help set the standard for how Nexus delivers them." That's about the role. Responsibilities: the bullet list under "What You’ll Do". Also maybe some responsibilities like serving as technical point of contact, reviewing junior engineers, etc. Those are in that list. Requirements: maybe "Required Qualifications" section. That's a list. Qualifications: maybe "Preferred Qualifications". That's another list. Skills: could be combined from required qualifications like proficiency in ETAP, etc. But we already have Requirements and Qualifications. Might not need Skills separate if content overlaps. But we could still include Skills if there is distinct skill info not captured elsewhere. The posting includes "Advanced, hands-on proficiency in ETAP, EasyPower or SKM including building and validating models to complete studies", "Deep command of the core study types...", "Proven ability to own studies independently...", "Working knowledge of applicable standards...", "Strong written communication and reporting skills, plus working proficiency in Excel and the Microsoft Office suite". Those could be Skills. However they are also under Required Qualifications. Might be okay to put them under Requirements. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are prescribed; we can omit sections if no real content. We could have About the role, Responsibilities, Requirements (including both required and preferred), Benefits, Pay, Schedule. That's six sections. We must not repeat job title as heading. Good. We must not include Job ID etc. We must remove boilerplate: EEO, etc. We must preserve all substantive information. So we need to include all details from the posting except removed boilerplate. Let's extract substantive content: Intro: "Nexus Engineering Group is employee-owned, full-service, and built by the people who do the work. As a Senior Power System Studies Engineer, you’ll own the analytical studies that keep industrial power systems safe, reliable, and compliant — and help set the standard for how Nexus delivers them. You’ll lead power system studies for industrial clients — building and validating models in ETAP (and EasyPower or SKM), running the analysis, and producing the detailed reports clients rely on. As a senior member of the team, you’ll own studies end-to-end, serve as a technical point of contact for clients, review and mentor junior engineers, and help shape Nexus’s study methodology and standards. Your work is reviewed by the discipline manager before it reaches the client — and increasingly, you’ll be the one performing that review for others." That's About the role. Then "Why Nexus" and "What you can expect": includes employee ownership (ESOP), ownership of high-impact studies, senior seat, full-service EPCm exposure, clear path toward lead/principal/discipline leadership, flexible work arrangements where business needs allow. This is more about benefits/role expectations. Could go under Benefits or About the role? But we have Benefits section for benefits like ESOP, medical, etc. The "What you can expect" includes non-benefit items like ownership of studies, senior seat, EPCm exposure, career path, flexible work arrangements. Some could be under Responsibilities or About the role. But we already covered responsibilities. The "ownership of high-impact studies" is similar to responsibilities. "Senior seat — shape methodology, mentor engineers, and work directly with clients" is also responsibility. "Full-service EPCm exposure, from concept through startup, across a diverse client base" is maybe about role exposure. "Clear path toward lead, principal, and discipline leadership" is career development, could be under Benefits? Not typical benefit but could be under Benefits? Might be better to include under About the role or Responsibilities. However we need to preserve all substantive info; we can incorporate these into About the role or Responsibilities as appropriate. Then "What You’ll Do" list: Lead and own power system studies end-to-end — scoping, modeling, analysis, quality control, and the final client-ready report; Build and validate models in ETAP, EasyPower, or SKM Power*Tools, as the study requires; Perform the full range of studies: load flow, short-circuit, arc-flash, protective device and relay coordination; Additional studies as required include dynamic and/or static motor-starting, harmonics, ground grid analysis, transient stability, and lightning analysis; Create and analyze relay setting files and coordinate protection schemes; Serve as a technical point of contact for clients — scoping work, gathering data, and presenting findings and recommendations; Review and QC studies produced by junior engineers, and mentor them on modeling, analysis, and standards; Help develop and maintain Nexus’s study templates, methodology, and quality standards; Travel occasionally (2–3 times per year, up to a week) to client facilities to gather field data alongside other Nexus personnel. That's responsibilities. Then "Required Qualifications What We’re Looking For": list: Bachelor of Science in Electrical Engineering; 8+ years of experience performing power system studies for industrial clients; Advanced, hands-on proficiency in ETAP, EasyPower or SKM including building and validating models to complete studies; Deep command of the core study types — load flow, short-circuit, arc-flash, protective device and relay coordination, motor-starting, and harmonics — and the calculation methods behind them; Proven ability to own studies independently, from scoping through client-ready deliverables; Working knowledge of applicable standards, such as IEEE 1584, IEEE 3000 Series (formerly Color Books), and NFPA 70 & 70E; Strong written communication and reporting skills, plus working proficiency in Excel and the Microsoft Office suite. Then "Preferred Qualifications": Professional Engineer (PE) license, or active progress toward licensure; Experience with additional analysis tools such as PSS®E, PSCAD, DIgSILENT PowerFactory, Cyme, Aspen Oneliner or EMTP; Transient stability, dynamic, or utility interconnection study experience; Master’s degree in Power Systems, Electric Power, or Energy Systems; Experience mentoring engineers and supporting proposals and estimating. Then "Work Environment & Physical Demands": This position is available on-site and hybrid at one of our five Nexus office location (Cleveland, OH, Maumee, OH, Columbus, OH, Midland, MI, Oak Brook, IL). This role may require: Occasional travel, typically 2–3 times per year, up to about a week per trip; Visits to client facilities to gather field data alongside other Nexus personnel; The ability to work in industrial or utility environments, wearing appropriate PPE, when require. Then "About Nexus Engineering Group": description of firm. Then "Equal Opportunity Employer & Reasonable Accommodation": boilerplate to remove. Then "Sponsorship & Work Authorization": boilerplate to remove. Then "Third‑Party Agency Notice": boilerplate. Then "We may use AI tools...": boilerplate. Then "The posted salary range represents the anticipated base pay for this position...": Pay info. Then "In addition to base pay, eligible employees may receive:" list of benefits: Employee Stock Ownership Plan (ESOP) — an ownership stake and a share in the long-term success of Nexus; Medical, dental, and vision coverage, plus life and disability insurance; 401(k) with company match and discretionary bonus opportunities; Paid time off, holidays, and paid parental leave; Professional development and career advancement — training, certifications, licensure support, tuition assistance, and mentorship; Wellness benefits and a flexible schedule where business needs allow. Thus we have Benefits and Pay. Schedule: we have "flexible schedule where business needs allow" in Benefits. Also earlier "Flexible work arrangements where business needs allow" in What you can expect. So schedule info is present. We could create a Schedule section with that statement. But we already have flexible schedule in Benefits; maybe we should not duplicate. The instruction: Prefer a few substantive sections over many thin ones. So we could incorporate schedule info into Benefits or About the role. But we need a Schedule section only if posting actually states them. It does state flexible schedule. So we could include Schedule section with that statement. However we already have Benefits section listing "Wellness benefits and a flexible schedule where business needs allow." That's a benefit. So schedule is already covered under Benefits. If we also create a Schedule section, we'd be duplicating content. Better to keep schedule info within Benefits, and not create a separate Schedule section to avoid thin section. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't forbid having both Benefits and Schedule if both have content. But we should avoid thin sections. Since schedule info is already captured under Benefits as a bullet, we could keep Benefits and not have Schedule. That seems reasonable. Thus final sections: About the role, Responsibilities, Requirements (maybe combine required and preferred?), Benefits, Pay. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit Qualifications, Skills, Schedule if no distinct content. However we have both Required and Preferred qualifications; we could put Required under Requirements and