Project Engineering Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the job description. Let's extract sections: - About the role / summary: The first paragraph(s) about need for clean energy, GE Vernova Hitachi, etc. Also description of role: "The Project Engineering Manager will provide leadership..." etc. So we can put that under About the role. - Responsibilities: The list under "Essential Responsibilities: As The Project Engineering Manager, You Will" then many bullet-like sentences. We'll turn each into

. - Requirements: There's "Required Qualifications" and "Eligibility Requirements". Also "Desired Qualifications". Could combine into Requirements and Qualifications sections. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: Required Qualifications: - Bachelor of Science in Engineering, Physics, Mathematics or related Science or technical discipline. - At least 12 years of progressive experience in engineering design and/or project leadership experience. - At least 8 years of experience in the nuclear industry or equivalent large scale new build experience in the power industry. Eligibility Requirements: - The required work location is Wilmington, NC (relocation assistance provided if not already local) Desired Qualifications: - Proven ability to be a liaison between organizations that are operating in separate geographic locations. - High performing individual with demonstrated ability to deliver results while exhibiting behaviors that promote strong team performance. - Proven interpersonal and leadership skills with the ability to think strategically, be creative and move quickly. - Demonstrated ability to lead a team of highly experienced engineers and balance multiple demands and priorities. - High performing energetic leader with demonstrated ability to deliver results while exhibiting behaviors that promote strong team performance. - Experience with project management skillset (communication, risk, planning/scheduling, change mgmt). - EPC experience and knowledge; specifically, power plant. - Understanding of nuclear industry and technology. - Excellent written and verbal communication skills. - Demonstrated ability to document, plan, market and manage programs that further the knowledge, understanding and capability of the business. - This role requires access to U.S. export-controlled information. If applicable, final offers will be contingent on ability to obtain authorization for access to U.S. export-controlled information from the U.S. Government. Also Additional Information includes pay range, benefits, etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's map: - About the role: we have summary paragraphs. Yes. - Responsibilities: we have essential responsibilities list. Yes. - Requirements: we have Required Qualifications and Eligibility Requirements (location). That's specific. So include Requirements. - Qualifications: we have Desired Qualifications. Could be separate Qualifications section. Or we could combine Required and Desired under Qualifications? But we have both headings possible. We'll include Qualifications for desired qualifications. - Skills: we could extract skills from desired qualifications (e.g., interpersonal, leadership, project management, communication, etc.) but we might just put them under Skills if we have content. However we already have many skill-like items in Desired Qualifications. Could create Skills section listing those. But we must not invent or summarize away detail; we can list them as items. It's okay to create Skills section if we have specific skill statements. The desired qualifications include many skill statements. We'll put them under Skills. - Benefits: we have "Available benefits include medical, dental, vision, and prescription drug coverage; access to Health Coach from GE Vernova, a 24/7 nurse-based resource; and access to the Employee Assistance Program, providing 24/7 confidential assessment, counseling and referral services. Retirement benefits include the GE Vernova Retirement Savings Plan, a tax-advantaged 401(k) savings opportunity with company matching contributions and company retirement contributions, as well as access to Fidelity resources and financial planning consultants. Other benefits include tuition assistance, adoption assistance, paid parental leave, disability benefits, life insurance, 12 paid holidays, and permissive time off." That's specific. So include Benefits. - Pay: we have "For candidates applying to a U.S. based position, the pay range for this position is between $134,400.00 and $257,600.00. The Company pays a geographic differential of 110%, 120% or 130% of salary in certain areas. The specific pay offered may be influenced by a variety of factors, including the candidate’s experience, education, and skill set. Bonus eligibility: discretionary annual bonus." That's specific. So include Pay. - Schedule: no mention of schedule (e.g., full-time, hours). Not present, so omit Schedule. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "This posting is expected to remain open for at least seven days after it was posted on September 17, 2026." That's not substantive? It's metadata about posting duration; could be considered minor metadata; we can drop it. Also "Relocation Assistance Provided: Yes" we already captured location with relocation assistance. Could include in Requirements or maybe a short paragraph. We'll incorporate location and relocation assistance in Requirements. We must preserve all substantive information; not invent or summarize away detail. So we need to keep all specifics: pay range numbers, differential percentages, bonus eligibility, benefits list, etc. Now produce HTML fragment. Structure:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

• Bachelor of Science in Engineering, Physics, Mathematics or related Science or technical discipline.
• At least 12 years of progressive experience in engineering design and/or project leadership experience.
• At least 8 years of experience in the nuclear industry or equivalent large scale new build experience in the power industry.
• Required work location is Wilmington, NC (relocation assistance provided if not already local).

Qualifications

• Proven ability to be a liaison between organizations that are operating in separate geographic locations.
• High performing individual with demonstrated ability to deliver results while exhibiting behaviors that promote strong team performance.
• Proven interpersonal and leadership skills with the ability to think strategically, be creative and move quickly.
• Demonstrated ability to lead a team of highly experienced engineers and balance multiple demands and priorities.
• High performing energetic leader with demonstrated ability to deliver results while exhibiting behaviors that promote strong team performance.
• Experience with project management skillset (communication, risk, planning/scheduling, change mgmt).
• EPC experience and knowledge; specifically, power plant.
• Understanding of nuclear industry and technology.
• Excellent written and verbal communication skills.
• Demonstrated ability to document, plan, market and manage programs that further the knowledge, understanding and capability of the business.
• This role requires access to U.S. export-controlled information; final offers are contingent on obtaining authorization for access to U.S. export-controlled information from the U.S. Government.

Skills

We could list skills but many are overlapping with Qualifications. Might be redundant. Perhaps better to not create Skills if content duplicates Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills? But we have headings for both; we could decide to omit Skills if it's thin. However we have skill statements that could be considered skills. But we already have Qualifications (desired). Could we treat Qualifications as both required and desired? Actually we have Required Qualifications separate; we could put Required under Requirements and Desired under Qualifications. Then Skills could be omitted. Let's see if we have any distinct skill statements not already in Qualifications: The desired qualifications include many skill-like items; they could be considered skills. But we could still create Skills section listing e.g., interpersonal, leadership, strategic thinking, creativity, project management, communication, etc. However that would duplicate content. To avoid thin sections, better to omit Skills and keep Qualifications as desired qualifications. The instruction says use headings for Skills if posting has real specific content for it. We have skill statements; but they are already captured under Qualifications. Could we still create Skills with those same items? That would be duplication but not invented. However "Prefer a few substantive sections over many thin ones." Having both Qualifications and Skills might be thin if they overlap. I'd choose to omit Skills and keep Qualifications as desired qualifications. But we already used Qualifications for desired; we have Required under Requirements. That seems fine. Now Benefits:

Benefits

• Medical, dental, vision, and prescription drug coverage.
• Access to Health Coach from GE Vernova, a 24/7 nurse-based resource.
• Access to the Employee Assistance Program, providing 24/7 confidential assessment, counseling and referral services.
• GE Vernova Retirement Savings Plan, a tax-advantaged 401(k) savings opportunity with company matching contributions and company retirement contributions.
• Access to Fidelity resources and financial planning consultants.
• Tuition assistance.
• Adoption assistance.
• Paid parental leave.
• Disability benefits.
• Life insurance.
• 12 paid holidays.
• Permissive time off.

Pay:

Pay

• Pay range for U.S.-based position: $134,400.00 to $257,600.00.
• Geographic differential of 110%, 120%, or 130% of salary in certain areas.
• Specific pay influenced by candidate’s experience, education, and skill set.
• Bonus eligibility: discretionary annual bonus.

We should also include maybe a short paragraph about relocation assistance already in Requirements. Now ensure we didn't include any boilerplate: removed EEO, legal, etc. Also removed "GE Vernova is an Equal Opportunity Employer..." etc. Also removed "GE Vernova will only employ those who are legally authorized to work in the United States for this opening." etc. Also removed "Any offer of employment is conditioned upon the successful completion of a drug screen (as applicable)." Also removed "This posting is expected to remain open for at least seven days after it was posted on September 17, 2026." Also removed "GE Vernova Inc. or its affiliates (collectively or individually, “GE Vernova”) sponsor certain employee benefit plans or programs ..." etc. Also removed "GE Vernova reserves the right to terminate, amend, suspend, replace, or modify its benefit plans and programs at any time and for any reason, in its sole discretion." etc. Also removed "No individual has a vested right to any benefit under a GE Vernova welfare benefit plan or program." Also removed "This document does not create a contract of employment with any individual." Now produce final HTML fragment. Check that we didn't miss any substantive info: The initial summary about need for clean energy, GE Vernova Hitachi, world leader, etc. Also the description of role: "The Project Engineering Manager will provide leadership to a diverse technical team..." etc. We need to include that in About the role. Let's craft