Senior Electrical Engineer- Kiewit Power Engineering
Kiewit · New York, NY · 3 wk ago
On-siteInformation Technology$143k–$149k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Position Overview, District Overview, Location, Responsibilities, Qualifications, Working Conditions (Other Requirements), Base Compensation, Benefits. Also maybe "Overview" etc. We need to use for section headings. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like EEO etc. We need to preserve all substantive info.
We need to decide which sections to include based on content.
We have:
- Position Overview (intro paragraph)
- District Overview (description of Kiewit Engineering Group)
- Location (list of locations)
- Responsibilities (list of duties)
- Qualifications (list of requirements)
- Working Conditions (Other Requirements) (list of statements)
- Base Compensation (salary range)
- Benefits (description)
We should not include sections with placeholder or vague like "commensurate with experience". Not present.
We need to use
for section headings. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like EEO etc. We need to preserve all substantive info.
We need to decide which sections to include based on content.
We have:
- Position Overview (intro paragraph)
- District Overview (description of Kiewit Engineering Group)
- Location (list of locations)
- Responsibilities (list of duties)
- Qualifications (list of requirements)
- Working Conditions (Other Requirements) (list of statements)
- Base Compensation (salary range)
- Benefits (description)
We should not include sections with placeholder or vague like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive info; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, maybe a
About the role? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose appropriate headings based on content. The posting has "Position Overview" and "District Overview". Could combine into "About the role" or keep as separate sections? The instruction: "include a section ONLY when the posting has real, specific content for it". So we can have sections for Position Overview, District Overview, Location, Responsibilities, Qualifications, Working Conditions, Pay, Benefits.
But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list District Overview or Location. However we can still use those headings if they reflect content. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we can also use other headings if appropriate? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. It might be safer to map content to those headings.
Thus we need to map:
- About the role: could combine Position Overview and District Overview? Or maybe Position Overview is about the role, District Overview about company. Could put both under About the role? But they said "About the role" as example; we could put Position Overview there. District Overview maybe could be part of About the role as well (company info). Could also create a separate section like "About Kiewit" but not in list. Safer to follow examples: Use About the role for Position Overview. Use Responsibilities for responsibilities. Use Qualifications for qualifications. Use Benefits for benefits. Use Pay for compensation. Use Schedule? Not present. Could omit Schedule.
Location: Not in examples but we have location info. Could we put Location under About the role? Might be okay to include location details in About the role paragraph. But we need to preserve all substantive info; we could include location as a
within About the role section.
Working Conditions (Other Requirements) could be under Requirements? The examples include Requirements. Could map Working Conditions to Requirements. Or we could create a section "Requirements" for those.
Thus sections:
About the role
(contains Position Overview paragraph + District Overview paragraph + Location paragraph maybe)
Responsibilities
(ul list)
Qualifications
(ul list)
Requirements
(ul list for Working Conditions/Other Requirements)
Benefits
(p description)
Pay
(p with salary range)
We must not include empty sections.
Now we need to extract content.
Position Overview text:
"Does the chance to change a skyline excite you? Do you consider yourself a high performer? Creative? Committed to high-quality work? Is adventure your middle name? If so, you may have a future in design engineering at Kiewit! We’re known for creating innovative, world-class building projects throughout the United States, Canada and Mexico — many are once-in-a-lifetime opportunities you won’t find anywhere else. How do we do it? We hire only the best and we employ them to do career-defining work that changes the landscape in communities around the world. You bring your talent, skills, and drive to succeed. We’ll provide the training, on-the-job experience and responsibility from day one that will shape your professional growth. Let’s go!"
District Overview text:
"Kiewit Engineering Group, Inc is a full-service consulting and engineering firm serving the infrastructure and engineering markets. Our combined staff of more than 1,300 engineers and design professionals have expertise that spans all major engineering disciplines to serve transportation, power, water/wastewater, mining, building, and oil, gas & chemical markets. Backed by 130 years of construction experience, our construction-driven engineering focuses on constructability and safety in the earliest phases of projects to ensure on-time and on-budget project delivery. Our rapidly growing Power district, which includes structural, civil, piping, mechanical, process, process safety, electrical, instrument and control disciplines, is a multi-faceted division of Kiewit with best-in-class technical expertise focused on the EPC delivery model for power facilities. We offer a variety of engineering services, including owner's engineering, project development, detailed engineering and design, construction management and plant services. Our engineering teams bring power projects to life across North America in the following areas: Gas-fired generation Power delivery Environmental retrofits Renewables and new technology Water/wastewater We are a high performing team of engineers and designers that develop projects through the project life-cycle engaging exciting projects throughout North America. Our staff leads the power markets engineering process and collaborates with Kiewit’s construction teams to approach construction-driven engineering with a focus on safe, cost-effective, and innovative designs that achieve client expectations and further Kiewit’s legacy of excellence."
Location text:
"This position can be based in any of the following office locations: Lenexa, KS; Lone Tree, CO; Houston, TX; Raleigh, NC; Phoenix/Tempe, AZ; New York City, NY; or Woodcliff Lake, NJ. For roles in Chattanooga, TN; Detroit, MI; or Richmond, VA, the position will start remotely and transition to a hybrid/in office arrangement once the new office is established."
Responsibilities list: many bullet-like sentences. We need to extract each as - . Let's copy them:
- Performs complex calculations and applies standards correctly without supervision.
- Takes lead when works with peers.
- Reviews the work of engineers and designers developing engineering and design documents as needed for the project.
- Possesses critical analytical skills and is adept at utilizing good decision making tool; high level of data analysis skills.
- Regularly performs reviews of vendor documents to ensure specifications and data sheet requirements are met.
- Leads mid to large-size project or proposals.
- Develops and leads others in ways of improving the design and lowering cost.
- Considers multiple solutions and makes good decisions based on good data analysis.
- Manages several different assignments simultaneously.
- Applies techniques/technologies to improve processes and business results.
- Utilizes industry and company standards to design and engineer effectively.
- Serves as resource to less experienced engineers.
- Reviews application of standards for correct interpretations (including NEC).
- Leads projects in how to interpret and apply codes and standards.
- Leads team to identify changes in the scope of work during mid to large-sized projects.
- Produces design changes as needed to stay within budget and schedule.
- Recognizes the importance of customer needs.
- Performs assigned work efficiently and effectively to maximize person productivity.
- Leads quality checks of the design and engineering of a mid to major-sized project to ensure accuracy.
- Establishes credibility in terms of technical competency and team leading ability.
- Prioritizes time to meet team commitments and individual work requirements.
- Prepare engineering deliverables consisting of one-lines, schematics, wiring diagrams, equipment data sheets, hazardous area classification drawings, electrical power studies (ETAP), etc.
Note: Some sentences have semicolons; we keep as is.
Qualifications list:
- Bachelor’s degree in Electrical Engineering minimum required.
- At least 15 years’ relevant experience in electrical engineering.
- Self directs work with limited supervision.
- Provides guidance, leadership and training to less experienced engineers.
- Leads small team to complete task/design on project.
- Work with project team as representative and coordinates work within discipline department.
- Adjusts to varying demands of work and performs well.
- Develops and presents work in well-constructed written and verbal presentations.
- Clearly conveys messages and ideas, gains understanding.
- Communicates effectively with supervisor and members of immediate department.
- Works collaboratively across departments and involves others in solving problems.
- Initiates meetings within own team, other disciplines or internal customers for clarity on work.
- Supports project teams and departments in a positive and productive manner.
- Works well with other to accomplish common goals and objectives.
- Serves as technical resource and point of contact for external or internal customers.
- Knowledge of industry codes, guidelines and regulatory standards to include NEC, NFPA and API.
- Experience with ETAP Electrical Power System Analysis software desired.
- Knowledgeable in power system studies including load flow, short circuit, arc flash, and relay coordination preferred.
Working Conditions / Other Requirements list (note duplicated lines). We need to deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to remove duplicate lines. The list appears twice with same content. We'll keep one copy.
Items:
- Regular, reliable attendance
- Work productively and meet deadlines timely
- Communicate and interact effectively and professionally with supervisors, employees, and others individually or in a team environment
- Perform work safely and effectively.
- Understand and follow oral and written instructions, including warning signs, equipment use, and other policies.
- Work during normal operating hours to organize and complete work within given deadlines.
- Work overtime and weekends as required.
- May work at various different locations and conditions may vary.
- Openings are to fill both existing vacancies and newly created positions
Note: Some lines have no period; we keep as is.
Benefits description:
"We offer our fulltime staff employees a comprehensive benefits package that’s among the best in our industry, including top-tier medical, dental and vision plans covering eligible employees and dependents, voluntary wellness and employee assistance programs, life insurance, disability, retirement plans with matching, and generous paid time off."
Pay description:
"Base Compensation: $143,000/yr - $149,000/yr (Actual compensation is subject to variation due to such factors as education, experience, skillset, and/or location)"
We need to output HTML fragment.
Structure:
About the role
Position Overview paragraph
District Overview paragraph
Location paragraph
But we might want to separate Position Overview and District Overview as separate under same heading. That's fine.
Then:
Responsibilities
- ...
...
Qualifications
...
Requirements
...
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine.
Check for any boilerplate: EEO etc removed. We removed the equal opportunity line.
Check for any duplicated lines: we removed duplicate Working Conditions lines.
Check for any placeholder like "
. We need to preserve all substantive info; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a
About the role? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose appropriate headings based on content. The posting has "Position Overview" and "District Overview". Could combine into "About the role" or keep as separate sections? The instruction: "include a section ONLY when the posting has real, specific content for it". So we can have sections for Position Overview, District Overview, Location, Responsibilities, Qualifications, Working Conditions, Pay, Benefits.
But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list District Overview or Location. However we can still use those headings if they reflect content. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we can also use other headings if appropriate? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. It might be safer to map content to those headings.
Thus we need to map:
- About the role: could combine Position Overview and District Overview? Or maybe Position Overview is about the role, District Overview about company. Could put both under About the role? But they said "About the role" as example; we could put Position Overview there. District Overview maybe could be part of About the role as well (company info). Could also create a separate section like "About Kiewit" but not in list. Safer to follow examples: Use About the role for Position Overview. Use Responsibilities for responsibilities. Use Qualifications for qualifications. Use Benefits for benefits. Use Pay for compensation. Use Schedule? Not present. Could omit Schedule.
Location: Not in examples but we have location info. Could we put Location under About the role? Might be okay to include location details in About the role paragraph. But we need to preserve all substantive info; we could include location as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we can also use other headings if appropriate? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. It might be safer to map content to those headings.
Thus we need to map:
- About the role: could combine Position Overview and District Overview? Or maybe Position Overview is about the role, District Overview about company. Could put both under About the role? But they said "About the role" as example; we could put Position Overview there. District Overview maybe could be part of About the role as well (company info). Could also create a separate section like "About Kiewit" but not in list. Safer to follow examples: Use About the role for Position Overview. Use Responsibilities for responsibilities. Use Qualifications for qualifications. Use Benefits for benefits. Use Pay for compensation. Use Schedule? Not present. Could omit Schedule.
Location: Not in examples but we have location info. Could we put Location under About the role? Might be okay to include location details in About the role paragraph. But we need to preserve all substantive info; we could include location as a
within About the role section. Working Conditions (Other Requirements) could be under Requirements? The examples include Requirements. Could map Working Conditions to Requirements. Or we could create a section "Requirements" for those. Thus sections:
About the role
(contains Position Overview paragraph + District Overview paragraph + Location paragraph maybe)Responsibilities
(ul list)Qualifications
(ul list)Requirements
(ul list for Working Conditions/Other Requirements)Benefits
(p description)Pay
(p with salary range) We must not include empty sections. Now we need to extract content. Position Overview text: "Does the chance to change a skyline excite you? Do you consider yourself a high performer? Creative? Committed to high-quality work? Is adventure your middle name? If so, you may have a future in design engineering at Kiewit! We’re known for creating innovative, world-class building projects throughout the United States, Canada and Mexico — many are once-in-a-lifetime opportunities you won’t find anywhere else. How do we do it? We hire only the best and we employ them to do career-defining work that changes the landscape in communities around the world. You bring your talent, skills, and drive to succeed. We’ll provide the training, on-the-job experience and responsibility from day one that will shape your professional growth. Let’s go!" District Overview text: "Kiewit Engineering Group, Inc is a full-service consulting and engineering firm serving the infrastructure and engineering markets. Our combined staff of more than 1,300 engineers and design professionals have expertise that spans all major engineering disciplines to serve transportation, power, water/wastewater, mining, building, and oil, gas & chemical markets. Backed by 130 years of construction experience, our construction-driven engineering focuses on constructability and safety in the earliest phases of projects to ensure on-time and on-budget project delivery. Our rapidly growing Power district, which includes structural, civil, piping, mechanical, process, process safety, electrical, instrument and control disciplines, is a multi-faceted division of Kiewit with best-in-class technical expertise focused on the EPC delivery model for power facilities. We offer a variety of engineering services, including owner's engineering, project development, detailed engineering and design, construction management and plant services. Our engineering teams bring power projects to life across North America in the following areas: Gas-fired generation Power delivery Environmental retrofits Renewables and new technology Water/wastewater We are a high performing team of engineers and designers that develop projects through the project life-cycle engaging exciting projects throughout North America. Our staff leads the power markets engineering process and collaborates with Kiewit’s construction teams to approach construction-driven engineering with a focus on safe, cost-effective, and innovative designs that achieve client expectations and further Kiewit’s legacy of excellence." Location text: "This position can be based in any of the following office locations: Lenexa, KS; Lone Tree, CO; Houston, TX; Raleigh, NC; Phoenix/Tempe, AZ; New York City, NY; or Woodcliff Lake, NJ. For roles in Chattanooga, TN; Detroit, MI; or Richmond, VA, the position will start remotely and transition to a hybrid/in office arrangement once the new office is established." Responsibilities list: many bullet-like sentences. We need to extract each asAbout the role
Position Overview paragraph
District Overview paragraph
Location paragraph
But we might want to separate Position Overview and District Overview as separateunder same heading. That's fine. Then:
Responsibilities
- ... ...
Qualifications
- ...
Requirements
- ...
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine. Check for any boilerplate: EEO etc removed. We removed the equal opportunity line. Check for any duplicated lines: we removed duplicate Working Conditions lines. Check for any placeholder like "