Electrical Engineer - Power Generation - REMOTE

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role (the paragraph after "Join a dynamic..."). Responsibilities (Key Responsibilities list). Technical & Professional Qualifications (Qualifications). Highly Desirable (maybe Skills). Key Attributes (maybe Skills). Pay & Benefits: they mention "Competitive pay, full benefits package" but no specifics. They later detail Kelly benefits: medical, dental, vision, etc. That is benefits info. Pay specifics: only "Competitive pay" no amount, so we should not create Pay section because it's not specific (just "competitive pay" is vague). Schedule: they mention remote with quarterly travel, travel up to 30% but not schedule like full-time etc. Could include Schedule? The posting says "REMOTE, Contract-to-Hire" and "Travel up to 30%". That's schedule info? Might be considered schedule but not explicit hours. Probably we can include a Schedule section with remote and travel info. However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They state "Competitive pay, full benefits package" which is vague but still states benefits exist. They then detail benefits later. So Benefits section is justified. Pay: they only say competitive pay, no specifics; that is vague but still states pay is competitive. The rule says never create Pay section unless posting actually states them. It does state "Competitive pay". That is a statement, albeit vague. Should we include? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay". So we could include Pay section with that sentence. However they also say "Prefer a few substantive sections over many thin ones." Might be better to omit Pay because it's not substantive. But the rule says we can include if stated. I'd lean to include Pay with that line. Schedule: they mention remote, quarterly travel, travel up to 30%. That's schedule info. So we can include Schedule section. We need headings:

for each section. We need to not repeat job title as heading. Not include Job ID. We need to use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include sections only when posting has real specific content. Let's extract content: About the role: "Join a dynamic and innovative engineering team as a Senior Electrical Engineer, shaping the future of gas-powered generation, CHP, and renewable energy projects across the full project lifecycle. This is a REMOTE opportunity with quarterly travel to Wisconsin for site visits, meetings, and project collaboration." That's prose. Responsibilities: list bullet points under "Key Responsibilities:" each sentence. We need to capture each responsibility as

• . List: - Lead the translation of concepts and project requirements into robust electrical designs for power generation, Combined Heat & Power (CHP), and Renewable Natural Gas (RNG) facilities. - Develop and detail specifications, perform calculations, select components, and ensure all deliverables meet functional and contractual standards. - Support early-stage project sales by preparing conceptual designs and tender documentation with high quality and timely turnaround. - Collaborate closely with Mechanical Engineers, CAD Designers, and Project Managers, coordinating and leading design activities through to installation and commissioning. - Oversee the preparation of full electrical design packages, including one-line and three-line diagrams, layouts, schematics, equipment specifications, bills of materials, and cable schedules. - Conduct and lead HAZOP and risk assessment studies as required. - Provide technical support during project installation, commissioning, and testing phases, ensuring documentation compliance and project success. - Interface confidently with internal teams, suppliers, stakeholders, and customers. - Ensure strict adherence to health, safety, environmental, and quality management policies and standards. - Travel up to 30% for customer site meetings, surveys, and project support. That's all. Requirements: maybe "Technical & Professional Qualifications:" list. We need to decide sections: Could have Requirements (mandatory) and Qualifications (maybe same). The instruction list includes Requirements and Qualifications separate. We can put mandatory qualifications under Requirements, and highly desirable under Skills or Qualifications. But we need to avoid duplication. Let's parse: Technical & Professional Qualifications: - Bachelor’s Degree in Electrical Engineering (required) - Minimum 5 years of electrical engineering experience in power generation (1–25MW) or renewable natural gas sectors - In-depth knowledge of LV/MV power trains, controls, switchgear, motor control, transformers, cables, protective relaying, grounding and lightning protection, and utility interconnection - Proficiency with AutoCAD and solid IT skills (MS Office) - Experience with project management, scope development, proposals, and risk mitigation - Familiarity with the latest engineering design software (ETAP, SKM, or equivalent) - Technical leadership ability—mentoring, coaching, and peer review Highly Desirable: - Professional Engineering (PE) registration - Experience in CHP, Microgrid, Battery Storage, or Solar PV systems - Experience using SKM, ETAP, Homar Key Attributes: - Analytical thinker with strong planning and prioritization skills - Effective under pressure, adaptable to shifting priorities, shows resilience and tenacity - Excellent attention to detail, decision-making, and communication skills - Trusted team player, collaborator, and technical leader - Commitment to continuous quality and improvement We could map: Requirements: the mandatory qualifications (Bachelor's, 5 years experience, in-depth knowledge, proficiency with AutoCAD, experience with project management, familiarity with ETAP/SKM, technical leadership ability). Could also include "Bachelor’s Degree in Electrical Engineering (required)" etc. Qualifications: maybe the highly desirable? But the instruction list includes Qualifications as a section; we could put the highly desirable there. Skills: Key Attributes. Alternatively, we could combine Requirements and Qualifications into one but better to follow instruction. Let's decide: Section Requirements: list of mandatory qualifications (the bullet points under Technical & Professional Qualifications). Section Qualifications: list of highly desirable items. Section Skills: list of Key Attributes. Benefits: details from Kelly benefits paragraph. Pay: "Competitive pay, full benefits package" maybe we can put that as a short paragraph. Schedule: remote, quarterly travel to Wisconsin, travel up to 30% for customer site meetings, surveys, and project support. We need to ensure we don't repeat info. Let's craft HTML. We'll start with

  About the role

  ...

  Then

  Responsibilities

  ...
  Then

  Requirements

  ...
  Then

  Qualifications

  ...
  Then

  Skills

  ...
  Then

  Benefits

  ...
  Then

  Pay

  Competitive pay.

  (maybe include full benefits package? but that's benefits.) Then

  Schedule

  Remote position with quarterly travel to Wisconsin required; travel up to 30% for customer site meetings, surveys, and project support.

  Check for duplication: Responsibilities includes travel up to 30% already. We should not duplicate that in Schedule. But schedule section can mention remote and quarterly travel; travel % already in responsibilities. Might be okay but could be considered duplication. However schedule section is about remote and quarterly travel; responsibilities includes travel up to 30% for customer site meetings etc. It's okay to mention both but we should avoid repeating same sentence. We can keep schedule focusing on remote and quarterly travel, not mention % again. Responsibilities already includes travel up to 30% for customer site meetings, surveys, and project support. So schedule can mention remote and quarterly travel to Wisconsin. Now benefits: we need to extract from Kelly benefits paragraph: "Kelly offers eligible employees voluntary benefit plans including medical, dental, vision, telemedicine, term life, whole life, accident insurance, critical illness, a legal plan, and short-term disability. As a Kelly employee, you will have access to a retirement savings plan, service bonus and holiday pay plans (earn up to eight paid holidays per benefit year), and a transit spending account. In addition, employees are entitled to earn paid sick leave under the applicable state or local plan." We should list each as
• . Also note earlier: "As part of our promise to talent, Kelly supports those who work with us through a variety of benefits, perks, and work-related resources." That's generic; we can ignore. We'll produce benefits list. Now ensure we don't include boilerplate like EEO etc. Now produce final HTML fragment. Check for any missing substantive info: The job title line is not needed. Location: Remote (Quarterly travel to Wisconsin required) - we covered in schedule and responsibilities. Contract: 6–12 months, with potential for permanent hire - we haven't included that. That's substantive. Should we include in About the role or a separate section? Could add to About the role paragraph. The About the role currently only has the join sentence. We can add contract length info there. Let's incorporate: "This is a 6–12 month contract-to-hire REMOTE opportunity with quarterly travel to Wisconsin for site visits, meetings, and project collaboration." That preserves info. Also industry: Power Generation / Renewable Energy / Engineering - maybe not needed. We should preserve all substantive info. Let's add contract length to About the role. Also "Industry: Power Generation / Renewable Energy / Engineering" maybe not needed but could be included in About the role? Might be considered substantive but not required. The instruction: preserve ALL substantive information. So we should include industry. Could add a sentence: "The role is within the power generation, renewable energy, and engineering industry." But that's somewhat generic. Might be okay. Better to incorporate: "Join a dynamic and innovative engineering team as a Senior Electrical Engineer, shaping the future of gas-powered generation, CHP, and renewable energy projects across the full project lifecycle within the power generation / renewable energy / engineering industry." That's a bit awkward but okay. Alternatively we could add a separate section "About the company" but not required. We'll add industry phrase to About the role. Now ensure we didn't miss any other substantive info: "Key Responsibilities:" we captured. "Technical & Professional Qualifications:" we captured as Requirements. "Highly Desirable:" as Qualifications. "Key Attributes:" as Skills. "Pay & Benefits: Competitive pay, full benefits package" we captured Pay and Benefits. "As part of our promise to Kelly..." we captured benefits details. The rest about Kelly Engineering etc is boilerplate about the staffing agency; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Kelly Engineering promotional paragraphs are likely boilerplate; we should remove them. The "About Kelly Work changes everything..." etc is boilerplate. So we strip that. Thus final HTML includes only the sections we defined. Now craft. Be careful to not include any markdown fences. Let's write:

  About the role

  Join a dynamic and innovative engineering team as a Senior Electrical Engineer, shaping the future of gas-powered generation, CHP, and renewable energy projects across the full project lifecycle within the power generation, renewable energy, and engineering industry. This is a 6–12 month contract-to-hire REMOTE opportunity with quarterly travel to Wisconsin for site visits, meetings, and project collaboration.

  Responsibilities

  • Lead the translation of concepts and project requirements into robust electrical designs for power generation, Combined Heat & Power (CHP), and Renewable Natural Gas (R