Sr. Planning Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- About the role: maybe the paragraph after "We are seeking an experienced Senior Planning Engineer..." That's description of role. Could be considered About the role.
- Responsibilities: the list under "Key Responsibilities". Should be - .
- Requirements: maybe the "Required Qualifications" list.
- Qualifications: maybe the "Preferred Qualifications" list? But they said Qualifications as a heading; we could put both required and preferred under Qualifications? But they have separate headings Requirements and Qualifications. Usually Requirements = required qualifications, Qualifications = preferred or additional qualifications. We'll follow that.
- Skills: maybe we can extract skills like Python programming, power-system modeling tools, communication, collaboration. Could be a separate section if there is specific content. The posting mentions skills within qualifications; but we could still create a Skills section summarizing those. However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine skills into Qualifications or Requirements. But we have both headings; we could still include Skills if there is explicit skill list. The posting mentions "Proficiency in Python programming for engineering analysis and automation." Also "Ability to independently analyze complex engineering problems", "Excellent written, verbal, and interpersonal communication skills." Those are skills. Could be a Skills section.
- Benefits: posting does not mention benefits. So omit.
- Pay: posting includes "Hourly Pay Range: $65.50-$80". So we need a Pay section with that info.
- Schedule: posting mentions "Location: Off-Site | Contract". No explicit schedule like full-time, part-time, shift. Could infer contract but not schedule. So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe), Pay.
We need to preserve all substantive information; do not invent or summarize away detail. So we must include all details from posting.
Let's extract content:
Header: Sr. Planning Engineer | Location: Off-Site | Contract | Hourly Pay Range: $65.50-$80
Then paragraph: "We are seeking an experienced Senior Planning Engineer to support electric transmission and distribution planning initiatives. This role involves providing technical expertise in system assessments, planning studies, and project development within the utility or energy sector, focusing on long-term strategic infrastructure growth."
Then "Key Responsibilities" followed by a list of responsibilities (each line starts with a verb). We need to keep each as list item.
Then "Required Qualifications" list.
Then "Preferred Qualifications" list.
Then "About Delphi-US - Peacemakers In The Talent War" paragraph(s). This is about the company; maybe we could treat as About the role? But it's about the company. The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid adding other headings, but we should stick to those. The About Delphi-US content is not about the role; but we could include it under About the role? Might be considered filler but it's substantive about employer. However they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." They didn't forbid adding other headings, but they gave examples. Probably we should include About the role as the introductory paragraph(s) about the role and maybe also include the company description? But the company description is not about the role; but we could still include it as part of About the role? Might be okay.
Better: Use About the role for the description of the role (the first two paragraphs). Then we could add another section like "About the Company" but not in allowed headings. Since they only gave examples, but didn't say we cannot add other headings. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they also said "Prefer a few substantive sections over many thin ones." So we should avoid many sections. Adding About the Company would be another section; maybe we can incorporate that info into About the role as a short paragraph.
Thus About the role will contain: "We are seeking an experienced Senior Planning Engineer to support electric transmission and distribution planning initiatives. This role involves providing technical expertise in system assessments, planning studies, and project development within the utility or energy sector, focusing on long-term strategic infrastructure growth." plus maybe the Delphi-US description? But that is about the company, not role. Could be considered minor metadata? It's not minor; it's a paragraph about the employer. Might be okay to include as part of About the role? Might be stretching.
Alternatively, we could omit the Delphi-US description entirely? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info. So we need to include it somewhere. Could add a section "About the Company" but not in the list; but we can still use for that heading. The instruction didn't forbid other headings; just gave examples. So we can add About the Company.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, About the Company.
But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the pattern. I'd include About the Company as a heading.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
We are seeking an experienced Senior Planning Engineer to support electric transmission and distribution planning initiatives. This role involves providing technical expertise in system assessments, planning studies, and project development within the utility or energy sector, focusing on long-term strategic infrastructure growth.
Responsibilities
- PERFORM electric distribution and transmission planning studies to evaluate system reliability, capacity, and future requirements.
- CONDUCT capacity assessments for feeders, substations, and transmission facilities to identify constraints and opportunities.
- ANALYZE existing and forecasted system conditions to develop practical system improvement recommendations.
- DEVELOP feeder and substation recommendations based on load growth, reliability, and long-range planning needs.
- SUPPORT annual and long-term electric system planning activities, preparing detailed technical reports and documentation.
- EVALUATE alternatives for system upgrades, expansions, and capital projects to optimize system performance.
- BUILD, maintain, and analyze electrical system models using planning and power-system analysis software.
- PERFORM contingency, load flow, voltage, thermal, and reliability analyses to inform planning decisions.
- SUPPORT project development by translating study results into actionable engineering recommendations.
- COORDINATE with engineering, operations, project management, and stakeholder teams to ensure alignment.
- COMMUNICATE technical findings and recommendations effectively to both technical and non-technical audiences.
- DOCUMENT assumptions, methodologies, and results to support compliance and continuous improvement.
- UTILIZE Python programming for data analysis, automation, and reporting to enhance planning processes.
Requirements
- 10+ years of professional engineering experience within the electric utility, consulting, or energy industry.
- EXPERIENCE with power-system modeling and planning tools such as PSS/E, TARA, PowerWorld, ASPEN, or similar.
- Demonstrated expertise in electric transmission and/or distribution planning.
- Strong understanding of electric power systems, planning methodologies, and load growth analysis.
- Ability to independently analyze complex engineering problems and develop practical solutions.
- Proficiency in Python programming for engineering analysis and automation.
- Excellent written, verbal, and interpersonal communication skills.
- Ability to collaborate effectively within multidisciplinary teams.
Qualifications
- Experience with cloud-based or mixed Windows/Linux database environments.
- Familiarity with industry standards and utility planning regulations.
- Prior experience supporting long-term infrastructure projects.
- Knowledge of stakeholder engagement and technical presentation skills.
Skills
- Proficiency in Python programming for data analysis, automation, and reporting.
- Expertise in power-system modeling tools (PSS/E, TARA, PowerWorld, ASPEN, etc.).
- Electric transmission and distribution planning.
- Load growth analysis and system assessment.
- Technical reporting and documentation.
- Stakeholder communication and presentation.
- Collaboration in multidisciplinary teams.
Pay
Hourly Pay Range: $65.50-$80
About the Company
Delphi-US is a national IT Services firm based in Newport, Rhode Island. Delphi attracts our nation's best and brightest Technical & Professional Talent and positions our nation's finest employers to further their competitive advantages. Delphi's core technical focus includes Data Intelligence Engineering & Analytics, AI/ML Operational Excellence, DevOps & Cloud Computing, Health IT & Life Sciences, and Energy Management/Power Systems; serving domains from sensitive national energy sectors to critical financial services, biomed, life sciences & pharma, major government & municipal institutions, and much of the USA's Fortune 500 corporations. Delphi Associates are deployed on critical IT Projects where their consultative business acumen, comprehensive technical expertise, and committed service mission drives our client's success. Our proprietary skill-based and cultural matching process results in higher qualified project teams, custom curated for our client's specific technical & functional goals. We are supremely experienced, friendly, professional, and ready to advocate on your behalf. Delphi has an indelible understanding of employer expectations, a track record of project success and we deliver lasting results.
We need to ensure we didn't repeat job title as heading. We didn't. We didn't include Job ID/requisition numbers. We omitted navigation etc.
Check that we preserved all substantive information: The responsibilities list includes all lines. The required qualifications list includes all bullet points. The preferred qualifications list includes all bullet points. The Delphi-US description is fully included. The pay range is included. The location and contract info: we omitted location and contract? The posting had "Location: Off-Site | Contract". That's substantive metadata. Should we include it? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." Location and contract could be considered minor metadata; we could fold into a short
maybe under About the role or Pay. Better to include a short paragraph after About the role: maybe include location and contract. Let's add a
under About the role: "Location: Off-Site. Contract position." Or combine.
We need to preserve all substantive information, so we should include location and contract. We'll add a short paragraph after the About the role description.
Thus About the role section will have two paragraphs: role description, and location/contract.
Let's adjust
or drop it." They didn't forbid adding other headings, but they gave examples. Probably we should include About the role as the introductory paragraph(s) about the role and maybe also include the company description? But the company description is not about the role; but we could still include it as part of About the role? Might be okay. Better: Use About the role for the description of the role (the first two paragraphs). Then we could add another section like "About the Company" but not in allowed headings. Since they only gave examples, but didn't say we cannot add other headings. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they also said "Prefer a few substantive sections over many thin ones." So we should avoid many sections. Adding About the Company would be another section; maybe we can incorporate that info into About the role as a short paragraph.
Thus About the role will contain: "We are seeking an experienced Senior Planning Engineer to support electric transmission and distribution planning initiatives. This role involves providing technical expertise in system assessments, planning studies, and project development within the utility or energy sector, focusing on long-term strategic infrastructure growth." plus maybe the Delphi-US description? But that is about the company, not role. Could be considered minor metadata? It's not minor; it's a paragraph about the employer. Might be okay to include as part of About the role? Might be stretching.
Alternatively, we could omit the Delphi-US description entirely? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info. So we need to include it somewhere. Could add a section "About the Company" but not in the list; but we can still use for that heading. The instruction didn't forbid other headings; just gave examples. So we can add About the Company.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, About the Company.
But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the pattern. I'd include About the Company as a heading.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the pattern. I'd include About the Company as a heading.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
We are seeking an experienced Senior Planning Engineer to support electric transmission and distribution planning initiatives. This role involves providing technical expertise in system assessments, planning studies, and project development within the utility or energy sector, focusing on long-term strategic infrastructure growth.
Responsibilities
- PERFORM electric distribution and transmission planning studies to evaluate system reliability, capacity, and future requirements.
- CONDUCT capacity assessments for feeders, substations, and transmission facilities to identify constraints and opportunities.
- ANALYZE existing and forecasted system conditions to develop practical system improvement recommendations.
- DEVELOP feeder and substation recommendations based on load growth, reliability, and long-range planning needs.
- SUPPORT annual and long-term electric system planning activities, preparing detailed technical reports and documentation.
- EVALUATE alternatives for system upgrades, expansions, and capital projects to optimize system performance.
- BUILD, maintain, and analyze electrical system models using planning and power-system analysis software.
- PERFORM contingency, load flow, voltage, thermal, and reliability analyses to inform planning decisions.
- SUPPORT project development by translating study results into actionable engineering recommendations.
- COORDINATE with engineering, operations, project management, and stakeholder teams to ensure alignment.
- COMMUNICATE technical findings and recommendations effectively to both technical and non-technical audiences.
- DOCUMENT assumptions, methodologies, and results to support compliance and continuous improvement.
- UTILIZE Python programming for data analysis, automation, and reporting to enhance planning processes.
Requirements
- 10+ years of professional engineering experience within the electric utility, consulting, or energy industry.
- EXPERIENCE with power-system modeling and planning tools such as PSS/E, TARA, PowerWorld, ASPEN, or similar.
- Demonstrated expertise in electric transmission and/or distribution planning.
- Strong understanding of electric power systems, planning methodologies, and load growth analysis.
- Ability to independently analyze complex engineering problems and develop practical solutions.
- Proficiency in Python programming for engineering analysis and automation.
- Excellent written, verbal, and interpersonal communication skills.
- Ability to collaborate effectively within multidisciplinary teams.
Qualifications
- Experience with cloud-based or mixed Windows/Linux database environments.
- Familiarity with industry standards and utility planning regulations.
- Prior experience supporting long-term infrastructure projects.
- Knowledge of stakeholder engagement and technical presentation skills.
Skills
- Proficiency in Python programming for data analysis, automation, and reporting.
- Expertise in power-system modeling tools (PSS/E, TARA, PowerWorld, ASPEN, etc.).
- Electric transmission and distribution planning.
- Load growth analysis and system assessment.
- Technical reporting and documentation.
- Stakeholder communication and presentation.
- Collaboration in multidisciplinary teams.
Pay
Hourly Pay Range: $65.50-$80
About the Company
Delphi-US is a national IT Services firm based in Newport, Rhode Island. Delphi attracts our nation's best and brightest Technical & Professional Talent and positions our nation's finest employers to further their competitive advantages. Delphi's core technical focus includes Data Intelligence Engineering & Analytics, AI/ML Operational Excellence, DevOps & Cloud Computing, Health IT & Life Sciences, and Energy Management/Power Systems; serving domains from sensitive national energy sectors to critical financial services, biomed, life sciences & pharma, major government & municipal institutions, and much of the USA's Fortune 500 corporations. Delphi Associates are deployed on critical IT Projects where their consultative business acumen, comprehensive technical expertise, and committed service mission drives our client's success. Our proprietary skill-based and cultural matching process results in higher qualified project teams, custom curated for our client's specific technical & functional goals. We are supremely experienced, friendly, professional, and ready to advocate on your behalf. Delphi has an indelible understanding of employer expectations, a track record of project success and we deliver lasting results.
We need to ensure we didn't repeat job title as heading. We didn't. We didn't include Job ID/requisition numbers. We omitted navigation etc. Check that we preserved all substantive information: The responsibilities list includes all lines. The required qualifications list includes all bullet points. The preferred qualifications list includes all bullet points. The Delphi-US description is fully included. The pay range is included. The location and contract info: we omitted location and contract? The posting had "Location: Off-Site | Contract". That's substantive metadata. Should we include it? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." Location and contract could be considered minor metadata; we could fold into a short
maybe under About the role or Pay. Better to include a short paragraph after About the role: maybe include location and contract. Let's add a
under About the role: "Location: Off-Site. Contract position." Or combine. We need to preserve all substantive information, so we should include location and contract. We'll add a short paragraph after the About the role description. Thus About the role section will have two paragraphs: role description, and location/contract. Let's adjust