Associate Electrical Engineer - Power System Studies (Distribution)
Black & Veatch · Overland Park, KS · 1 mo ago
Hybrid$91k–$152k/yrFull-time
We need to produce HTML fragment with sections: About the role? The posting includes company description, why Black & Veatch, The Opportunity, Key Responsibilities, Preferred Qualifications, Minimum Qualifications, Work Environment/Physical Demands (maybe not detailed), Compensation Transparency (salary ranges), Benefits (described), etc.
We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content. So we need to map content.
We have:
- About the role: maybe from "The Opportunity" paragraph describing role. Could be "About the role". We'll put that.
- Responsibilities: from "Key Responsibilities" bullet list (though it's paragraph with sentences). We'll extract each sentence as list items.
- Requirements: maybe "Minimum Qualifications" and "Preferred Qualifications". Could combine into Requirements? But we have separate headings: Requirements, Qualifications, Skills. We need to decide.
We have "Preferred Qualifications" and "Minimum Qualifications". Could put under "Qualifications" heading (maybe includes both). Or separate "Requirements" for minimum, "Qualifications" for preferred, "Skills" for specific skills.
We have "Skills": maybe list of software, analytics, scripting, leadership, etc.
We have "Benefits": described in benefits paragraph.
We have "Pay": compensation transparency with salary ranges per state.
We have "Schedule": not explicitly mentioned; maybe flexible ways of working mentioned under "Why Black & Veatch?" but not explicit schedule. The posting mentions "flexible ways of working". That could be schedule info. But we should only include Schedule if posting actually states them. It says "With flexible ways of working and meaningful development opportunities". That's somewhat schedule. Could include Schedule section with that note. However we must avoid placeholder like "not specified". It's specific enough: flexible ways of working. So we can include Schedule.
We must not include boilerplate like EEO, legal, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like salary ranges per state, benefits list, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content. So we need to map content.
We have:
- About the role: maybe from "The Opportunity" paragraph describing role. Could be "About the role". We'll put that.
- Responsibilities: from "Key Responsibilities" bullet list (though it's paragraph with sentences). We'll extract each sentence as list items.
- Requirements: maybe "Minimum Qualifications" and "Preferred Qualifications". Could combine into Requirements? But we have separate headings: Requirements, Qualifications, Skills. We need to decide.
We have "Preferred Qualifications" and "Minimum Qualifications". Could put under "Qualifications" heading (maybe includes both). Or separate "Requirements" for minimum, "Qualifications" for preferred, "Skills" for specific skills.
We have "Skills": maybe list of software, analytics, scripting, leadership, etc.
We have "Benefits": described in benefits paragraph.
We have "Pay": compensation transparency with salary ranges per state.
We have "Schedule": not explicitly mentioned; maybe flexible ways of working mentioned under "Why Black & Veatch?" but not explicit schedule. The posting mentions "flexible ways of working". That could be schedule info. But we should only include Schedule if posting actually states them. It says "With flexible ways of working and meaningful development opportunities". That's somewhat schedule. Could include Schedule section with that note. However we must avoid placeholder like "not specified". It's specific enough: flexible ways of working. So we can include Schedule.
We must not include boilerplate like EEO, legal, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like salary ranges per state, benefits list, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
Black & Veatch is seeking a Power System Studies Engineer with 5-10 years’ experience to join our Power System Studies team. The ideal candidate has significant working experience and knowledge of Distribution System design concepts & analyses such as Short Circuit (Fault) Analysis, Load Flow, DER Impact Analysis, Protection Coordination Studies, Distribution Interconnection Studies, System Impact Studies and system modeling software for the same.
Responsibilities
- Continues to learn and remains current on departmental design guides, standards, systems, applicable engineering codes and B&V policies and procedures.
- Applies to assigned tasks as appropriate.
- Continues developing and can independently apply knowledge.
- Complies with B&V quality program relative to assigned tasks.
- Supports continuous improvement and change management efforts.
- Prepares a variety of increasingly complex engineering deliverables.
- Performs research and develops recommendations for equipment and/or materials selection.
- Collects, assimilates, and manages data for engineering work.
- Prepares increasingly complex engineering calculations following standard methods and principles.
- Understands and adheres to budget, schedule, and quality requirements.
- May recognize, define and resolve problems within assigned area.
- May provide direction and guidance to others.
- Assigns tasks to develop entry level professionals and interns.
- Coordinates with project leadership and other internal/external team members on less complex projects.
- Interacts as needed with other disciplines on details of design work.
- Works to understand external client's interest and drivers through regular interaction and communication.
- Also focuses on needs of internal clients and project leadership.
- May provide support to business development or pursuit activities.
- Shares current knowledge of latest technology and processes.
- As skills develop, may assist with performance management process, recognition, and any corrective actions required.
- Actively mentors entry level professionals and interns.
Qualifications
Minimum Qualifications
- Requires a bachelor's degree in engineering from either a recognized accredited program in their home country or the country in which the professional is practicing.
- Minimum of 1 year related work experience.
- All applicants must be able to complete pre-employment onboarding requirements (if selected) which may include any/all of the following: criminal/civil background check, drug screen, and motor vehicle records search, in compliance with any applicable laws and regulations.
Preferred Qualifications
- 5-10 years of experience in performing Distribution System planning studies.
- Previous working experience with Distribution System design concepts, analyses, calculations, et cetera.
- 5 years of experience performing studies such as Short Circuit (Fault) Analysis, Load Flow, DER Impact Analysis, Protection Coordination Studies, Distribution Interconnection Studies, System Impact Studies, et cetera.
- 5 years of significant experience utilizing one of the below system modeling software programs and knowledge with others that are listed: CYME, Synergi Electric, et cetera.
- Working experience performing various power system studies which are performed in support of Distribution System design (Short Circuit, Power Flow, Voltage Analysis, et cetera).
- Knowledge and working experience with analytics and scripting (Python, et cetera).
- Proven ability to independently develop written communication and to facilitate coordination with team members and clients.
- Proven ability to work cooperatively in a team environment.
- Proven ability to lead small projects including management of project schedules, budgets, and staffing.
- Significant experience supporting proposal development including scope of work, level of work, engineering estimates, schedule.
- Strong leadership skills, with desire to train and develop early career and/or inexperienced professionals.
- Significant experience functioning in a QA/QC capacity.
- PE License (preferred, not required)
Skills
- Distribution System design concepts & analyses: Short Circuit (Fault) Analysis, Load Flow, DER Impact Analysis, Protection Coordination Studies, Distribution Interconnection Studies, System Impact Studies.
- System modeling software: CYME, Synergi Electric (and others).
- Analytics and scripting (Python).
- Written communication and coordination.
- Teamwork and collaboration.
- Project leadership: managing schedules, budgets, staffing.
- Proposal development and engineering estimates.
- Leadership and mentoring early career professionals.
- QA/QC experience.
Benefits
- Medical, dental and vision insurances.
- Disability coverage.
- Robust wellness program.
- Flexible work schedules.
- Paid vacation and holiday time.
- Sick time and dependent sick time.
- Company-matched 401k plan.
- Adoption reimbursement.
- Tuition reimbursement.
- Vendor discounts.
- Employment referral program.
- AD&D insurance.
- Pre-taxed accounts.
- Voluntary legal plan.
- B&V Credit Union.
- Performance-based bonus program eligibility.
- 100 percent ESOP ownership (employee‑owned).
Pay
- State of Colorado: $91,047 – $152,053
- State of Minnesota: $86,909 – $145,142
- Salary Plan ENG: Engineering Job Grade 015
Schedule
Flexible ways of working are offered.
We need to ensure we didn't include any boilerplate like EEO, legal, etc. We omitted those. Check that we didn't repeat job title as heading. We didn't. We didn't include Job ID/Req Id. We preserved all substantive info: company description? We omitted the initial company description paragraph about employee-owned etc. That is substantive. Should we include it? The instructions: "Preserve ALL substantive information". The company description at start is substantive. We should include it maybe under About the role or a separate section like "About the company". But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role (makes sense). So we need to incorporate that paragraph into About the role. Thus About the role should include both the company description and the opportunity description. Let's craft About the role paragraph(s) combining: "Together, we own our company, our future, and our shared success. As an employee-owned company, our people are Black & Veatch. We put them at the center of everything we do and empower them to grow, explore new possibilities and use their diverse talents and perspectives to solve humanity's biggest challenges in an ever-evolving world. With over 100 years of innovation in sustainable infrastructure and our expertise in engineering, procurement, consulting and construction, together we are building a world of difference." Then "Why Black & Veatch?" paragraph: "At Black & Veatch, you’ll be part of work that matters—designing, creating, and building the infrastructure communities rely on every day, from concept through execution. We care about how the work gets done as much as what we build. Safety is built into every decision, and people look out for each other—speaking up, collaborating, and doing the right thing because it affects real lives. You’ll work alongside teams solving complex challenges and turning ideas into solutions that perform in the real world—gaining hands-on experience across projects, technologies, and disciplines. Ownership shows up in how we work. We take responsibility for outcomes, follow through on commitments, and take pride in what we deliver. As a 100% employee-owned company, employees share in the long-term success we build together. With flexible ways of working and meaningful development opportunities, you’ll build a career you can be proud to stand behind." Then "The Opportunity Black & Veatch is seeking a Power System Studies Engineer with 5-10 years’ experience to join our Power System Studies team. The ideal candidate has significant working experience and knowledge of Distribution System design concepts & analyses such as Short Circuit (Fault) Analysis, Load Flow, DER Impact Analysis, Protection Coordination Studies, Distribution Interconnection Studies, System Impact Studies and system modeling software for the same." We can combine into About the role. Thus About the role will have multiple paragraphs. Now ensure we didn't include any fluff like "commensurate with experience". Not present. Check Benefits: we included flexible work schedules (already in Benefits). Also we have Schedule section separate; maybe redundant. But we can keep Schedule as separate with "Flexible ways of working are offered." However Benefits already includes flexible work schedules. To avoid duplication, maybe we should not duplicate. But instructions: preserve ALL substantive information; duplication is okay if it's in posting? The posting mentions flexible ways of working in Why Black & Veatch? and also in Benefits. It's okay to have both but we might be duplicating. However we should not invent or summarize away detail; duplication is not summarizing