Substation Physical Designer or Engineer
Nexus Engineering Group · Oak Brook, IL · 1 mo ago
HybridEngineeringFull-time
We need to output HTML fragment with headings for sections: 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, no invention. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, cookie/navigation, etc.
We need to parse the posting.
Key sections:
- Intro: "Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Physical Designer, you’ll develop the physical design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the general arrangement layouts, elevation and section views, grounding, conduit routing, and equipment placement that bring substations to life — from new builds to upgrades and expansions. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation physical packages."
That's about the role. Could be "About the role" section.
- "Why Nexus" bullet list: 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.
That could be "Benefits" or maybe "What you can expect". Could be Benefits section.
- "What You’ll Do": bullet list: Develop and revise physical layouts, elevation and section views, below-grade drawings, and supporting documentation in CAD, with growing independence as you develop; Lay out grounding systems (IEEE Std 80), conduit and cable routing, bus arrangements, and equipment placement; Build and maintain cable/conduit lists, nameplates, and client-specific documentation; Assist the project lead in developing physical documentation, applying technical design standards; 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.
That's Responsibilities.
- "Required Qualifications" heading: "What We’re Looking For": Associate Degree in a technical discipline or equivalent technical experience; 2+ years of experience in substation, power delivery, or electrical design; Proficiency with CAD (AutoCAD and/or MicroStation); Familiarity with substation physical design — layouts, grounding (IEEE Std 80), conduit and cable routing, and equipment placement; Working knowledge of IEEE, ANSI, NEC, and NESC standards; Ability to travel to project and substation sites, some of which are not accessible by public transportation.
That's Requirements/Qualifications.
- "Preferred Qualifications": Inventor or Substation Design Suite (SDS) experience; Grounding or photometric analysis software (WinIGS, CDEGS, AGi32, Visual Lighting, or equivalent); Engineer-in-Training (EIT) certification, with progress toward Professional Engineer (PE) licensure.
That could be Skills or Qualifications.
- "Work Environment & Physical Demands": This role combines office-based design work with periodic visits to substation and construction sites. This role may require: Periodic travel to substation and construction sites; Appropriate PPE on site, including arc-rated clothing; The ability to access outdoor substation yards and walk uneven terrain, with or without reasonable accommodation.
That could be maybe "Work Environment" but not in allowed headings. Could be part of Responsibilities? Not exactly. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map Work Environment & Physical Demands to maybe "Responsibilities"? Not appropriate. Could be omitted if not matching allowed headings. But we might include it under "Requirements"? Not ideal. However we could treat as "Skills"? Not. Perhaps we can omit it because not in allowed headings, but we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that info, we lose substantive info. So we need to include it somewhere. Perhaps we can put it under "Responsibilities" as part of duties? But it's not a duty; it's work environment. Could we create a section not in allowed list? The instruction says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those. Probably we should stick to those headings and place content accordingly. Work Environment & Physical Demands could be considered part of "Responsibilities" or "Requirements"? Might be considered "Requirements" (physical demands). Could be under "Requirements". We'll include it under Requirements as a bullet.
- "About Nexus Engineering Group": description of firm. Could be part of "About the role"? Might be separate but we could incorporate into About the role? The About the role heading is for role description; but we could also include company overview there. However we have "Why Nexus" which is benefits. The "About Nexus Engineering Group" is more about company. Could be part of "About the role"? Might be okay to include under About the role as extra context. But we must not repeat job title as heading. It's fine.
- "Equal Opportunity Employer & Reasonable Accommodation", "Sponsorship & Work Authorization", "Third‑Party Agency Notice", etc. Those are boilerplate to remove.
- "The posted salary range represents the anticipated base pay..." This is Pay info. It says salary range may vary based on experience etc. It also mentions benefits list: 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 Pay and Benefits content. The earlier "Why Nexus" also listed benefits (ESOP, ownership, mentorship, EPCm exposure, career paths, flexible work arrangements). There's overlap. We should combine benefits info, not duplicate. We must preserve all substantive info, but we can combine similar points without losing detail. We should not repeat identical lines. We'll create a Benefits section that includes all distinct benefits: 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; 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. Note flexible work arrangements appears twice; we can keep one.
Pay: 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." No actual numbers given. So we have only that statement. It's not a specific number or range, just a statement. According to instruction: 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 something about pay: "The posted salary range represents the anticipated base pay..." This is somewhat vague but it's still stating that there is a posted salary range (though not given). It's not a filler like "varies". It says may vary based on... It's not a specific number but it's stating that there is a posted salary range. I think we can include Pay section with that sentence. It's not exactly filler; it's a statement about pay transparency. We'll include.
Schedule: No explicit schedule info besides flexible work arrangements where business needs allow (mentioned in benefits). No specific schedule like full-time, part-time, shift. So we should not create a Schedule section because no specific content.
Now we need to output HTML fragment with
for sections: 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, no invention. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, cookie/navigation, etc.
We need to parse the posting.
Key sections:
- Intro: "Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Physical Designer, you’ll develop the physical design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the general arrangement layouts, elevation and section views, grounding, conduit routing, and equipment placement that bring substations to life — from new builds to upgrades and expansions. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation physical packages."
That's about the role. Could be "About the role" section.
- "Why Nexus" bullet list: 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.
That could be "Benefits" or maybe "What you can expect". Could be Benefits section.
- "What You’ll Do": bullet list: Develop and revise physical layouts, elevation and section views, below-grade drawings, and supporting documentation in CAD, with growing independence as you develop; Lay out grounding systems (IEEE Std 80), conduit and cable routing, bus arrangements, and equipment placement; Build and maintain cable/conduit lists, nameplates, and client-specific documentation; Assist the project lead in developing physical documentation, applying technical design standards; 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.
That's Responsibilities.
- "Required Qualifications" heading: "What We’re Looking For": Associate Degree in a technical discipline or equivalent technical experience; 2+ years of experience in substation, power delivery, or electrical design; Proficiency with CAD (AutoCAD and/or MicroStation); Familiarity with substation physical design — layouts, grounding (IEEE Std 80), conduit and cable routing, and equipment placement; Working knowledge of IEEE, ANSI, NEC, and NESC standards; Ability to travel to project and substation sites, some of which are not accessible by public transportation.
That's Requirements/Qualifications.
- "Preferred Qualifications": Inventor or Substation Design Suite (SDS) experience; Grounding or photometric analysis software (WinIGS, CDEGS, AGi32, Visual Lighting, or equivalent); Engineer-in-Training (EIT) certification, with progress toward Professional Engineer (PE) licensure.
That could be Skills or Qualifications.
- "Work Environment & Physical Demands": This role combines office-based design work with periodic visits to substation and construction sites. This role may require: Periodic travel to substation and construction sites; Appropriate PPE on site, including arc-rated clothing; The ability to access outdoor substation yards and walk uneven terrain, with or without reasonable accommodation.
That could be maybe "Work Environment" but not in allowed headings. Could be part of Responsibilities? Not exactly. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map Work Environment & Physical Demands to maybe "Responsibilities"? Not appropriate. Could be omitted if not matching allowed headings. But we might include it under "Requirements"? Not ideal. However we could treat as "Skills"? Not. Perhaps we can omit it because not in allowed headings, but we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that info, we lose substantive info. So we need to include it somewhere. Perhaps we can put it under "Responsibilities" as part of duties? But it's not a duty; it's work environment. Could we create a section not in allowed list? The instruction says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It also says: IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should only use those headings if we have content. If we have content that doesn't fit those headings, maybe we should not create a heading; we could just put the content in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those. Probably we should stick to those headings and place content accordingly. Work Environment & Physical Demands could be considered part of "Responsibilities" or "Requirements"? Might be considered "Requirements" (physical demands). Could be under "Requirements". We'll include it under Requirements as a bullet.
- "About Nexus Engineering Group": description of firm. Could be part of "About the role"? Might be separate but we could incorporate into About the role? The About the role heading is for role description; but we could also include company overview there. However we have "Why Nexus" which is benefits. The "About Nexus Engineering Group" is more about company. Could be part of "About the role"? Might be okay to include under About the role as extra context. But we must not repeat job title as heading. It's fine.
- "Equal Opportunity Employer & Reasonable Accommodation", "Sponsorship & Work Authorization", "Third‑Party Agency Notice", etc. Those are boilerplate to remove.
- "The posted salary range represents the anticipated base pay..." This is Pay info. It says salary range may vary based on experience etc. It also mentions benefits list: 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 Pay and Benefits content. The earlier "Why Nexus" also listed benefits (ESOP, ownership, mentorship, EPCm exposure, career paths, flexible work arrangements). There's overlap. We should combine benefits info, not duplicate. We must preserve all substantive info, but we can combine similar points without losing detail. We should not repeat identical lines. We'll create a Benefits section that includes all distinct benefits: 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; 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. Note flexible work arrangements appears twice; we can keep one.
Pay: 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." No actual numbers given. So we have only that statement. It's not a specific number or range, just a statement. According to instruction: 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 something about pay: "The posted salary range represents the anticipated base pay..." This is somewhat vague but it's still stating that there is a posted salary range (though not given). It's not a filler like "varies". It says may vary based on... It's not a specific number but it's stating that there is a posted salary range. I think we can include Pay section with that sentence. It's not exactly filler; it's a statement about pay transparency. We'll include.
Schedule: No explicit schedule info besides flexible work arrangements where business needs allow (mentioned in benefits). No specific schedule like full-time, part-time, shift. So we should not create a Schedule section because no specific content.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include markdown fences.
Let's structure:
About the role
... (intro + maybe company overview)
Responsibilities
- ... each duty
Requirements
- ... required qualifications + work environment physical demands
Skills
- ... preferred qualifications
Benefits
- ... benefits list
Pay
... pay statement
We must ensure we don't repeat content. Let's extract precise sentences.
About the role: Combine intro and company overview.
Intro: "Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Physical Designer, you’ll develop the physical design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the general arrangement layouts, elevation and section views, grounding, conduit routing, and equipment placement that bring substations to life — from new builds to upgrades and expansions. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation physical packages."
Company overview: "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 can combine into a paragraph.
Responsibilities list:
- Develop and revise physical layouts, elevation and section views, below-grade drawings, and supporting documentation in CAD, with growing independence as you develop
- Lay out grounding systems (IEEE Std 80), conduit and cable routing, bus arrangements, and equipment placement
- Build and maintain cable/conduit lists, nameplates, and client-specific documentation
- Assist the project lead in developing
- for lists,
for prose. We must not include markdown fences. Let's structure:
About the role
... (intro + maybe company overview)
Responsibilities
- ... each duty
Requirements
- ... required qualifications + work environment physical demands
Skills
- ... preferred qualifications
Benefits
- ... benefits list
Pay
... pay statement
We must ensure we don't repeat content. Let's extract precise sentences. About the role: Combine intro and company overview. Intro: "Nexus Engineering Group is employee-owned, full-service, and growing our Substation Department. As a Substation Physical Designer, you’ll develop the physical design of high-voltage substation projects — and grow from production support toward independent design. You’ll produce the general arrangement layouts, elevation and section views, grounding, conduit routing, and equipment placement that bring substations to life — from new builds to upgrades and expansions. Working alongside a collaborative team of engineers and designers, you’ll take on more ownership as you develop, building toward independent design of substation physical packages." Company overview: "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 can combine into a paragraph. Responsibilities list: - Develop and revise physical layouts, elevation and section views, below-grade drawings, and supporting documentation in CAD, with growing independence as you develop - Lay out grounding systems (IEEE Std 80), conduit and cable routing, bus arrangements, and equipment placement - Build and maintain cable/conduit lists, nameplates, and client-specific documentation - Assist the project lead in developing