Substation Communication Engineer (Entry, Staff, Senior, or Principal)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. 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, etc. We need to parse the posting. Key content: - Intro about Xcel Energy: description of company, mission, hybrid work model, many roles expected onsite three days per week (Tuesday–Thursday); however, work location expectations vary based on role, team, and business needs. - Position Summary: description of entry engineer level role, etc. - Essential Responsibilities: list of duties. - Entry Engineer Level (Salary Range: $70,000-$86,667) Minimum Requirements etc. - Staff Engineer Level (Salary Range: $81,800-$106,267) Minimum Requirements etc. - Senior Engineer Level (Salary Range: $97,000-$129,267) Minimum Requirements etc. - Principal Engineer (Salary Range: $112,000-$156,600) Minimum Requirements etc. - Culture values etc. - Benefits list: Annual Incentive Program, Medical/Pharmacy Plan, Dental, Vision, Life Insurance, Dependent Care Reimbursement Account, Health Care Reimbursement Account, Health Savings Account (HSA) (if enrolled in eligible health plan), Limited-Purpose FSA (if enrolled in eligible health plan and HSA), Transportation Reimbursement Account, Short-term disability (STD), Long-term disability (LTD), Employee Assistance Program (EAP), Fitness Center Reimbursement (if enrolled in eligible health plan), Tuition reimbursement, Transit programs, Employee recognition program, Pension, 401(k) plan, Paid time off (PTO), Holidays, Volunteer Paid Time Off (VPTO), Parental Leave. - Pay: "The anticipated starting base pay for this position is: $70,000.00 to $156,600.00 per year". Also there are salary ranges per level. - Schedule: hybrid work model, many roles expected onsite three days per week (Tuesday–Thursday); however, work location expectations vary based on role, team, and business needs. We need to decide sections. We have About the role: could include company description and role summary. Responsibilities: essential responsibilities list. Requirements: maybe combine minimum requirements across levels? Could separate by level? But we need to avoid thin sections. Could have a Requirements section that lists the minimum requirements for entry engineer level? However posting includes multiple levels with different requirements. We could include a Requirements section that summarizes the general requirement: bachelor's degree in engineering from ABET accredited, etc. But we must preserve all substantive info; we cannot invent or summarize away detail. We need to preserve all details, not summarize away. So we need to include each level's requirements as separate subsections? The instruction: "Prefer a few substantive sections over many thin ones." So we could have a Requirements section that contains sub-lists for each level. That's okay. Qualifications: maybe preferred qualifications (EIT/FE, PE, etc). Could combine. Skills: maybe technical skills? Not explicitly listed besides "technical standards, principles, theories, concepts, and techniques". Could be covered in responsibilities. Benefits: we have list. Pay: we have salary ranges and anticipated starting base pay. Schedule: hybrid work model. We must not include sections with filler like "commensurate with experience". The posting includes "The successfully chosen candidate will be placed at a level that is commensurate with their skills and experience". That's filler? It's somewhat generic but it's actual content. However instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should avoid a section that only contains that phrase. But we can include it within a paragraph if combined with other substantive content. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out: - Intro about Xcel Energy (maybe keep as About the role? It's about company, not role specifically. Could be About the role? Might be better as About the role: includes company overview and role context. - The line "The below job summary and responsibilities reflect the entry engineer level role. The successfully chosen candidate will be placed at a level that is commensurate with their skills and experience as different skills and/or experience will be required at the staff, senior and principal engineer levels." This is somewhat generic but includes info about levels. Could be part of About the role. - Position Summary paragraph. - Essential Responsibilities list. - Then the levels with salary ranges and requirements. - Culture values etc maybe not needed? Could be part of About the role? But values are not directly about role. Might be considered boilerplate? It's about culture, could be kept as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Culture values not explicitly listed as boilerplate, but could be considered generic. However it's substantive info about company culture. Might be okay to keep in About the role. - Benefits list. - Pay: anticipated starting base pay. - Schedule: hybrid work model. - Deadline to Apply: 10/15/26 (application instruction) -> remove. - EEO statements etc -> remove. - Accessibility statement etc -> remove. - Recruiting assistance etc -> remove. Now craft HTML. We'll have sections:

About the role

Xcel Energy is a leading energy provider and Fortune 500 company serving millions of electricity and natural gas customers across eight states: Minnesota, Colorado, Wisconsin, Michigan, North Dakota, South Dakota, New Mexico and Texas. The company focuses on delivering reliable, resilient, and sustainable energy while supporting employee growth and the clean energy transition. Xcel Energy supports a hybrid work model; many roles are expected to work onsite three days per week (Tuesday–Thursday), though expectations vary by role, team, and business needs. This position is an entry‑level engineer role designed to develop technical expertise in a specialty area, with placement at a level commensurate with skills and experience (entry, staff, senior, or principal engineer).

That seems to capture company description, hybrid work, role summary. Next Responsibilities:

Responsibilities

• Uses and applies technical standards, principles, theories, concepts, and techniques to perform activities/assignments of limited scope.
• Supports the development of technical documentation (including but not limited to designs, testing, calculations, reports, standards, etc.).
• Utilizes and may assist with the development of procedures.
• Provides ongoing technical support for project activities within areas such as Operations, Maintenance, Testing/diagnostics, Regulatory, etc.
• May provide field engineering oversight for activities such as commissioning, testing, inspections, etc. under direct supervision.
• Coordinates/leads projects or portions of projects (including phases such as research, design, equipment selection, procurement support, installation and commissioning), under the direction of a higher level engineer or supervisor.
• Under the direction of a higher level engineer/supervisor, supports bid/evaluation processes by performing basic analysis and calculations on existing documentation and materials that support the preparation of bid documents.
• In completing segments of technical evaluations for proposals may need to effectively communicate with other business areas of the company following appropriate processes.
• Effectively exchanges information in all formats, on matters having a wide range of importance and complexity both inter‑organizationally and with outside customers/vendors.
• May coordinate the work of interns, drafters, technicians, and/or others and provides guidance and mentoring to less experienced engineers.
• Responsible for continuous self‑development of technical skills and competencies.
• May perform activities such as budgeting, estimating, forecasting, accounting, work order management, in support of engineering projects.

Next Requirements: we need to capture minimum requirements for each level. We could structure as:

Requirements

Entry Engineer Level

• Bachelor's degree in engineering from ABET‑accredited curriculum.
• 0+ years relevant engineering experience.
• Ability to demonstrate the unique technical skills and core competencies for this engineering level established & documented by the organization.
• Preferred: EIT/FE (Engineer in Training/Fundamentals of Engineering).

Staff Engineer Level

• Bachelor’s degree in engineering from ABET accredited.
• 2+ years relevant engineering experience.
• Demonstrated broad knowledge & proficiency in specialty area, knowledge of related specialties, & general knowledge of other related disciplines.
• Ability to demonstrate the unique technical skills & core competencies for this engineering level established & documented by the organization.
• Preferred: EIT/FE strongly preferred.

Senior Engineer Level

• Required bachelor’s degree in engineering from ABET accredited curriculum.
• 5+ years relevant engineering experience with EIT/FE required; 7+ years relevant engineering experience without EIT/FE.
• Ability to demonstrate the unique technical skills and core competencies for this engineering level established & documented by the organization.
• Preferred: PE (Professional Engineer) registration may be required depending on business need.

Principal Engineer Level

• Required bachelor’s degree in engineering from ABET accredited curriculum.
• 9+ years relevant engineering experience with PE registration required; 15+ years relevant engineering experience without PE.
• Ability to demonstrate the unique technical skills and core competencies for this engineering level established & documented by the organization.
• Preferred: Electrical Engineering degree preferred; Certified Information Systems Security Professional (CISSP).

But we must not create thin sections; having subheadings h4 inside a section is okay? The instruction only mentions using

for section headings. It didn't forbid other headings, but we should follow the rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other headings, but to be safe we could avoid extra headings and just list within

with maybe bold text? But we need to preserve info. Could we just have a single Requirements section with nested lists? Might be okay to use

but risk violating instruction. Safer to avoid any headings besides

. So we can have a Requirements section with paragraphs for each level, maybe using to denote level. Thus:

Requirements

Entry Engineer Level

• Bachelor's degree in engineering from ABET‑accredited curriculum.
• 0+ years relevant engineering experience.
• Ability to demonstrate the unique technical skills and core competencies for this engineering level established & documented by the organization.
• Preferred: EIT/FE (Engineer in Training/Fundamentals of Engineering).

Staff Engineer Level

• Bachelor’s degree in engineering from ABET accredited.
• 2+ years relevant engineering experience.
• Demonstrated broad knowledge & proficiency in specialty area, knowledge of related specialties