Substation Engineer – Protection & Controls

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 that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, etc). Must not include placeholder sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits: Employee ownership (ESOP), medical/dental/vision, life/disability, 401(k) with match, PTO, holidays, parental leave, professional development, wellness benefits, flexible schedule. Also mentions salary range but not specific numbers: "The posted salary range represents the anticipated base pay..." but no actual numbers. Since they didn't give actual numbers, we should not create Pay section because it's not specific. However they mention salary range but not numbers; it's vague. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we can include Benefits. Schedule: they mention flexible work arrangements where business needs allow, also flexible schedule where business needs allow. That's somewhat specific? It says "Flexible work arrangements where business needs allow" and later "Wellness benefits and a flexible schedule where business needs allow". That's a statement about schedule flexibility. Could include Schedule section? The rule: only include if posting actually states them. It does state flexible schedule. So we could include Schedule with that content. However we must avoid placeholder like "varies". It's not placeholder; it's a statement. So we can include Schedule. We need sections: About the role (maybe "About the role" corresponds to introductory paragraph). Responsibilities (What You'll Do). Requirements (Required Qualifications). Qualifications (Preferred Qualifications). Skills maybe not separate; could combine. Benefits. Schedule. We must not include sections like "About Nexus Engineering Group" maybe that is about company; could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. We have: - Intro: "Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Engineer – Protection & Controls, you’ll develop the protection, control, and wiring design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the single-line and three-line diagrams, schematics, and wiring documentation — including protective relaying and SCADA/automation scope — that keep substations running safely and reliably. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation protection and control packages." That's about the role. Could be "About the role". - "Why Nexus" bullet list: Employee ownership (ESOP) — build equity..., Real ownership that grows..., Mentorship..., Full-service EPCm exposure..., Career paths..., Flexible work arrangements where business needs allow. That could be part of Benefits or maybe separate but we have Benefits section for tangible benefits; "Why Nexus" includes culture/ownership etc. Could be part of About the role or separate but we don't have a heading for culture. We could incorporate into About the role or Benefits. Since Benefits section is for tangible benefits, we could put ESOP etc there. But the "Why Nexus" also includes mentorship, exposure, career paths, flexible work arrangements. Those could be Benefits or maybe we could have a "Benefits" section covering those. - "What You’ll Do" list: responsibilities. - "Required Qualifications" list. - "Preferred Qualifications" list. - "Work Environment & Physical Demands": could be part of Requirements or maybe a separate section but not in allowed headings. Could be folded into Requirements or maybe we can omit? But we must preserve all substantive information. We could include it under Requirements as additional details. Or we could create a separate section but not allowed headings; we could incorporate into Requirements. - "About Nexus Engineering Group": company description; could be part of About the role or maybe we could omit as boilerplate? It's substantive about company but not required heading. Could be included in About the role. - Then EEO etc: remove. - Sponsorship & Work Authorization: remove (legal). - Third‑Party Agency Notice: remove. - AI tools notice: remove. - Salary range paragraph: we should not create Pay section because no specific numbers. Could we include a short paragraph about salary range under Benefits? Probably not; it's about pay. Since we cannot create Pay section without specific numbers, we might omit that paragraph entirely? But we must preserve ALL substantive information; removing salary range would be losing substantive info. However the rule says: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range exists but not numbers. It's still stating that there is a posted salary range. Could we include a Pay section with the statement that "The posted salary range represents the anticipated base pay for this position..."? That is substantive but not a specific number. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state that there is a posted salary range (though not numbers). Is that considered filler? It's not exactly "commensurate with experience". It's a statement about existence of range. Might be okay to include Pay section with that statement. However the rule also says "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that statement. But we also have Schedule: they mention flexible work arrangements where business needs allow, and flexible schedule where business needs allow. That's substantive. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, Pay. But we need to avoid duplication. Let's extract content. About the role: combine introductory paragraph + "Why Nexus" + "About Nexus Engineering Group" maybe. Responsibilities: "What You’ll Do" bullet list. Requirements: "Required Qualifications" list + Work Environment & Physical Demands (maybe as part of Requirements). Qualifications: "Preferred Qualifications" list. Benefits: list from "Why Nexus" (Employee ownership, Real ownership, Mentorship, Full-service EPCm exposure, Career paths, Flexible work arrangements) plus benefits listed later: Employee Stock Ownership Plan (ESOP) — ownership stake and share in long-term success, Medical, dental, vision coverage, plus life and disability insurance, 401(k) with company match and discretionary bonus opportunities, Paid time off, holidays, paid parental leave, Professional development and career advancement — training, certifications, licensure support, tuition assistance, mentorship, Wellness benefits and a flexible schedule where business needs allow. Note some overlap with Why Nexus; we should combine and deduplicate. Schedule: maybe we already covered flexible schedule in Benefits; but we could still have Schedule section with statement about flexible work arrangements where business needs allow. However to avoid duplication, we could put flexible schedule under Benefits and not have separate Schedule. But rule: we should include section only when posting has real specific content for it. It does have flexible schedule content; we could put it under Benefits. Having both Benefits and Schedule might duplicate. Better to have Benefits include flexible schedule and not have separate Schedule. However the instruction list includes Schedule as possible heading; we can omit if we feel it's covered elsewhere. The rule: "Prefer a few substantive sections over many thin ones." So we can omit Schedule if its content is already in Benefits. Pay: we have salary range statement; we could include Pay section with that statement. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to format with

headings,

• for lists,

  for prose. We must not include any markdown code fences. Let's craft. About the role: combine paragraphs. Paragraph 1: Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Engineer – Protection & Controls, you’ll develop the protection, control, and wiring design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the single-line and three-line diagrams, schematics, and wiring documentation — including protective relaying and SCADA/automation scope — that keep substations running safely and reliably. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation protection and control packages. Paragraph 2: Why Nexus: You’ll own a piece of what you build. Nexus is employee-owned through our ESOP, so the value you help create comes back to you — not just outside shareholders. We invest in our engineers and give them room to grow into greater ownership of the work. What you can expect: Employee ownership (ESOP) — build equity in the firm as it grows; Real ownership that grows with you — from production support toward independent design; Mentorship from senior engineers and designers on a collaborative team; Full-service EPCm exposure, from concept through startup, across a diverse client base; Career paths that grow with you — toward technical leadership, project management, or discipline leadership; Flexible work arrangements where business needs allow. Paragraph 3: About Nexus Engineering Group: Nexus Engineering Group, a distinguished independent full-service engineering, procurement, and construction management (EPCm) firm, provides comprehensive support to clients from concept through startup. With over a decade of demonstrated engineering and design success, Nexus stands out as the firm of choice for those valuing integrity and expertise. At Nexus, you will be part of a talented and passionate team dedicated to excellence and innovation. We foster a collaborative and engaging work environment, making it a place where you’ll enjoy contributing to impactful projects. Joining Nexus means aligning with a firm renowned for its creativity, dedication, and relentless focus on achieving client goals. We could combine into one

  but it's long; maybe split into multiple

  under same heading? The instruction: use

  for prose. Could have multiple

  under heading. Now Responsibilities: list from What You’ll Do. - Develop and revise single-line diagrams, three-line diagrams, schematics, and wiring documentation in CAD, with growing independence as you develop - Build and maintain cable/conduit lists, nameplates, and client-specific documentation - Assist the project lead in developing protection and control documentation, applying technical design standards - Support protective relaying, SCADA/RTU, and automation design and interfaces within your scope - Apply internal and external processes, procedures, and design standards (IEEE, ANSI, NEC, NESC) - Coordinate with drafters, designers, other disciplines, clients, and vendors to deliver complete, constructible packages Now Requirements: Required Qualifications + Work Environment & Physical Demands. Required Qualifications list: - Bachelor of Science in Electrical Engineering, Electrical Engineering Technology, or a related discipline - 2+ years of experience in substation, power delivery, or electrical design - Proficiency with CAD (AutoCAD and/or AutoCAD Electrical) - Familiarity with the wiring scope — AC/DC schematics, control wiring, protective relaying, and SCADA/RTU/automation interfaces - Working knowledge of IEEE, ANSI, NEC, and NESC standards - Proficiency with Bluebeam (or equivalent) for redlines and markups - Ability to travel to project and substation sites, some of which are not accessible by public transportation Work Environment & Physical Demands (we can incorporate as bullet points maybe under same heading or as prose). Let's make a

  summarizing: This role combines office-based design work with periodic visits to substation and construction sites. It may require prolonged periods of sitting and working at a computer workstation, with or without reasonable accommodation; periodic travel to substation and construction sites, some not accessible by