Project Engineer/Assistant Project Manager: Transmission & Distribution
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- Intro paragraph about Jacobs and impact: could be "About the role" or maybe "About Jacobs". The instruction says we can use "About the role" as a heading. We'll put that.
- "Your impact" paragraph: maybe part of About the role.
- "Key Responsibilities": that's a section with bullet list. We'll make
Responsibilities
with - items.
- "What Success Looks Like": could be part of Responsibilities or maybe separate "Expectations". But we can include as part of Responsibilities or maybe a separate section "Performance Expectations". However instruction says prefer few substantive sections over many thin ones. Could combine "What Success Looks Like" into Responsibilities as prose. But we have bullet list of responsibilities; we could add a
after list for success criteria. That's okay.
- "Here's what you'll need": that's qualifications/requirements. We'll make
Requirements
with bullet list.
- "Preferred Qualifications": could be part of Requirements or separate "Preferred Qualifications". Might be okay to have a separate section "Preferred Qualifications". But we need to avoid many thin sections. Could combine into Requirements with subheadings? But we only allowed headings; we could have two sections: Requirements and Preferred Qualifications. That's okay.
- "Desired Characteristics": could be Skills. We'll make Skills
with bullet list.
- "Our health and welfare benefits...": Benefits section. We'll make Benefits
with bullet list (medical, dental, vision, basic life insurance, 401(k), ability to purchase company stock at a discount, deferred compensation plan, Executive Deferral Plan, unlimited U.S. Personalized Paid Time Off (PPTO) policy for full-time salaried/exempt employees, seven paid holidays, caregiver leave, merit increases, performance discretionary bonus, stock). Also mention hybrid working policy? That's more about work arrangement; could be part of Benefits or maybe separate "Work Arrangement". But we can include in Benefits as bullet.
- Pay: The posting includes base salary range: $106,000.00 to $139,050.00. So we need a Pay section. We'll make Pay
with
stating the range and note about location etc.
- Schedule: Not explicitly mentioned besides hybrid working policy. No explicit schedule like full-time, etc. Could infer full-time but not stated. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we should not create a Schedule section.
- Also there is some boilerplate about EEO etc which we must remove.
- Also there is some text about "Job posted on August 12, 2026. This position will be open for at least 3 days." That's minor metadata; we can fold into a short
maybe under About the role or at end. But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
with that info.
- Also there is some text about "At Jacobs, we’re partnering across the globe..." etc. That's more about company culture; could be part of About the role.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep all details from the posting, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can reformat. However we can combine similar items but must not lose detail. For bullet lists we need to keep each item.
Let's extract details.
Intro: "At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good."
Impact: "Your impact As a Project Engineer / Assistant Project Manager, you will be an integral part of Jacobs' Energy & Power team supporting electric utility capital projects across transmission, distribution, substation and related infrastructure programs. This role provides project delivery support throughout the project lifecycle, including project planning, governance, execution support, stakeholder coordination, permitting assistance, materials tracking and project controls activities. Working closely with Project Managers, engineers, clients, contractors and internal stakeholders, you will help drive projects through gated execution processes while maintaining alignment with project scope, schedule, budget, quality and compliance requirements. This position is ideal for a detail-oriented professional with utility or infrastructure experience who enjoys balancing technical, operational and project management responsibilities while developing toward increasing project ownership and independent project management responsibilities."
We can combine into a paragraph.
Key Responsibilities bullet list:
- Project Planning & Execution Support
- Support Project Managers in planning and executing utility capital projects from initiation through closeout.
- Assist with project setup, governance documentation, project scheduling and execution planning.
- Support project progression through gated execution processes.
- Coordinate project meetings, track action items and support timely resolution of project deliverables.
- Collaborate with engineering, construction, permitting and client teams to support successful project delivery.
- Project Controls & Reporting
- Maintain project documentation, logs, action item trackers, risk registers and governance records.
- Prepare weekly and monthly project reports.
- Support dashboard development and performance reporting utilizing Excel, Power BI and project management systems.
- Assist with cost, schedule and performance tracking activities.
- Risk, Change & Stakeholder Management
- Support change management activities through collection and evaluation of technical, cost and schedule information.
- Maintain risk, issue, action item and change logs.
- Assist with stakeholder communications and project updates.
- Build productive working relationships with utility personnel, contractors, consultants and project team members.
- Project Administration & Coordination
- Support permitting, land, environmental and right-of-way activities as required.
- Assist with procurement tracking, materials coordination and contractor interfaces.
- Maintain project records, approvals and governance documentation.
- Ensure adherence to project procedures, quality requirements and utility standards.
What Success Looks Like bullet list (actually it's prose with bullet-like sentences):
- During the first year, the successful candidate will
- Develop a strong understanding of client governance and project execution processes.
- Build effective working relationships with project teams and client stakeholders.
- Support active utility capital projects through planning, execution and reporting activities.
- Progress from supporting project workstreams to taking ownership of select project responsibilities.
- Develop toward independent Project Manager responsibilities as workload and project opportunities expand.
We could incorporate as a
or
. Since it's a list of expectations, we can make - .
Here's what you'll need (requirements):
- 4-7 years of experience supporting utility, infrastructure, engineering, construction, or capital projects.
- Experience working within a regulated utility, consulting, engineering, or infrastructure environment.
- Strong understanding of project management fundamentals and project lifecycle delivery.
- Excellent written and verbal communication skills.
- Proficiency with Microsoft Excel and Microsoft Office applications.
- Strong organizational skills and attention to detail.
- Ability to manage multiple priorities and support several active projects simultaneously.
- Demonstrated ability to work effectively with technical and non-technical stakeholders.
Preferred Qualifications:
- Experience supporting transmission, distribution, substation, or other utility capital projects.
- Familiarity with project governance and gated execution processes.
- Experience with Primavera P6, Power BI, Oracle, SAP, Microsoft Project, or similar project management tools.
- Ability to read and interpret engineering drawings and technical documentation.
- Experience supporting permitting, right-of-way, environmental, procurement, or materials management activities.
- Exposure to EPC, utility consulting, or owner's engineer environments.
Desired Characteristics:
- Strong communication and stakeholder management skills.
- Self-motivated with a willingness to learn and grow into increasing project responsibilities.
- Analytical mindset with strong problem-solving capabilities.
- Highly organized with an attention to quality and detail.
- Ability to balance technical details with project execution priorities.
- Collaborative team player who can build trust across client and project teams.
Benefits:
- Employees have access to medical, dental, vision, and basic life insurance, a 401(k) plan, and the ability to purchase company stock at a discount.
- Eligible employees may also enroll in a deferred compensation plan or the Executive Deferral Plan.
- Jacobs has an unlimited U.S. Personalized Paid Time Off (PPTO) policy for full-time salaried/exempt employees, seven paid holidays, and caregiver leave.
- And certain roles may be eligible for additional rewards, including merit increases, performance discretionary bonus, and stock.
- We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work.
Pay:
- The base salary range for this position is $106,000.00 to $139,050.00.
- Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training.
Metadata:
- Job posted on August 12, 2026.
- This position will be open for at least 3 days.
- Also there is a line: "At Jacobs, we’re partnering across the globe to create the best project outcomes by maximizing the design, digital technology, and support capabilities of our Global Integrated Delivery (GID) teammates. By joining Jacobs, you’ll commit to supporting and engaging with these teams, as we work to build a company like no other." This is substantive about company culture; we can include in About the role.
- Also: "Qualified applicants with criminal histories will be considered for employment". That's EEO? Actually it's a statement about criminal histories; might be considered EEO/boilerplate? It's not exactly EEO but could be considered a hiring practice statement. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This statement about criminal histories might be considered EEO-related? It's about considering applicants with criminal histories; could be considered a fair chance hiring statement. Might be considered boilerplate; but it's substantive? It's a policy. Might be okay to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but could be considered a hiring policy. I'd lean to keep it as it's substantive about consideration. However it's similar to EEO statements. Safer to
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Intro paragraph about Jacobs and impact: could be "About the role" or maybe "About Jacobs". The instruction says we can use "About the role" as a heading. We'll put that. - "Your impact" paragraph: maybe part of About the role. - "Key Responsibilities": that's a section with bullet list. We'll make
Responsibilities
with- items.
- "What Success Looks Like": could be part of Responsibilities or maybe separate "Expectations". But we can include as part of Responsibilities or maybe a separate section "Performance Expectations". However instruction says prefer few substantive sections over many thin ones. Could combine "What Success Looks Like" into Responsibilities as prose. But we have bullet list of responsibilities; we could add a
after list for success criteria. That's okay. - "Here's what you'll need": that's qualifications/requirements. We'll make
Requirements
with bullet list. - "Preferred Qualifications": could be part of Requirements or separate "Preferred Qualifications". Might be okay to have a separate section "Preferred Qualifications". But we need to avoid many thin sections. Could combine into Requirements with subheadings? But we only allowedheadings; we could have two sections: Requirements and Preferred Qualifications. That's okay. - "Desired Characteristics": could be Skills. We'll make
Skills
with bullet list. - "Our health and welfare benefits...": Benefits section. We'll makeBenefits
with bullet list (medical, dental, vision, basic life insurance, 401(k), ability to purchase company stock at a discount, deferred compensation plan, Executive Deferral Plan, unlimited U.S. Personalized Paid Time Off (PPTO) policy for full-time salaried/exempt employees, seven paid holidays, caregiver leave, merit increases, performance discretionary bonus, stock). Also mention hybrid working policy? That's more about work arrangement; could be part of Benefits or maybe separate "Work Arrangement". But we can include in Benefits as bullet. - Pay: The posting includes base salary range: $106,000.00 to $139,050.00. So we need a Pay section. We'll makePay
withstating the range and note about location etc. - Schedule: Not explicitly mentioned besides hybrid working policy. No explicit schedule like full-time, etc. Could infer full-time but not stated. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we should not create a Schedule section. - Also there is some boilerplate about EEO etc which we must remove. - Also there is some text about "Job posted on August 12, 2026. This position will be open for at least 3 days." That's minor metadata; we can fold into a short
maybe under About the role or at end. But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
with that info. - Also there is some text about "At Jacobs, we’re partnering across the globe..." etc. That's more about company culture; could be part of About the role. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep all details from the posting, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can reformat. However we can combine similar items but must not lose detail. For bullet lists we need to keep each item. Let's extract details. Intro: "At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good." Impact: "Your impact As a Project Engineer / Assistant Project Manager, you will be an integral part of Jacobs' Energy & Power team supporting electric utility capital projects across transmission, distribution, substation and related infrastructure programs. This role provides project delivery support throughout the project lifecycle, including project planning, governance, execution support, stakeholder coordination, permitting assistance, materials tracking and project controls activities. Working closely with Project Managers, engineers, clients, contractors and internal stakeholders, you will help drive projects through gated execution processes while maintaining alignment with project scope, schedule, budget, quality and compliance requirements. This position is ideal for a detail-oriented professional with utility or infrastructure experience who enjoys balancing technical, operational and project management responsibilities while developing toward increasing project ownership and independent project management responsibilities." We can combine into a paragraph. Key Responsibilities bullet list: - Project Planning & Execution Support - Support Project Managers in planning and executing utility capital projects from initiation through closeout. - Assist with project setup, governance documentation, project scheduling and execution planning. - Support project progression through gated execution processes. - Coordinate project meetings, track action items and support timely resolution of project deliverables. - Collaborate with engineering, construction, permitting and client teams to support successful project delivery. - Project Controls & Reporting - Maintain project documentation, logs, action item trackers, risk registers and governance records. - Prepare weekly and monthly project reports. - Support dashboard development and performance reporting utilizing Excel, Power BI and project management systems. - Assist with cost, schedule and performance tracking activities. - Risk, Change & Stakeholder Management - Support change management activities through collection and evaluation of technical, cost and schedule information. - Maintain risk, issue, action item and change logs. - Assist with stakeholder communications and project updates. - Build productive working relationships with utility personnel, contractors, consultants and project team members. - Project Administration & Coordination - Support permitting, land, environmental and right-of-way activities as required. - Assist with procurement tracking, materials coordination and contractor interfaces. - Maintain project records, approvals and governance documentation. - Ensure adherence to project procedures, quality requirements and utility standards. What Success Looks Like bullet list (actually it's prose with bullet-like sentences): - During the first year, the successful candidate will - Develop a strong understanding of client governance and project execution processes. - Build effective working relationships with project teams and client stakeholders. - Support active utility capital projects through planning, execution and reporting activities. - Progress from supporting project workstreams to taking ownership of select project responsibilities. - Develop toward independent Project Manager responsibilities as workload and project opportunities expand. We could incorporate as a
or
- . Since it's a list of expectations, we can make
- . Here's what you'll need (requirements): - 4-7 years of experience supporting utility, infrastructure, engineering, construction, or capital projects. - Experience working within a regulated utility, consulting, engineering, or infrastructure environment. - Strong understanding of project management fundamentals and project lifecycle delivery. - Excellent written and verbal communication skills. - Proficiency with Microsoft Excel and Microsoft Office applications. - Strong organizational skills and attention to detail. - Ability to manage multiple priorities and support several active projects simultaneously. - Demonstrated ability to work effectively with technical and non-technical stakeholders. Preferred Qualifications: - Experience supporting transmission, distribution, substation, or other utility capital projects. - Familiarity with project governance and gated execution processes. - Experience with Primavera P6, Power BI, Oracle, SAP, Microsoft Project, or similar project management tools. - Ability to read and interpret engineering drawings and technical documentation. - Experience supporting permitting, right-of-way, environmental, procurement, or materials management activities. - Exposure to EPC, utility consulting, or owner's engineer environments. Desired Characteristics: - Strong communication and stakeholder management skills. - Self-motivated with a willingness to learn and grow into increasing project responsibilities. - Analytical mindset with strong problem-solving capabilities. - Highly organized with an attention to quality and detail. - Ability to balance technical details with project execution priorities. - Collaborative team player who can build trust across client and project teams. Benefits: - Employees have access to medical, dental, vision, and basic life insurance, a 401(k) plan, and the ability to purchase company stock at a discount. - Eligible employees may also enroll in a deferred compensation plan or the Executive Deferral Plan. - Jacobs has an unlimited U.S. Personalized Paid Time Off (PPTO) policy for full-time salaried/exempt employees, seven paid holidays, and caregiver leave. - And certain roles may be eligible for additional rewards, including merit increases, performance discretionary bonus, and stock. - We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work. Pay: - The base salary range for this position is $106,000.00 to $139,050.00. - Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Metadata: - Job posted on August 12, 2026. - This position will be open for at least 3 days. - Also there is a line: "At Jacobs, we’re partnering across the globe to create the best project outcomes by maximizing the design, digital technology, and support capabilities of our Global Integrated Delivery (GID) teammates. By joining Jacobs, you’ll commit to supporting and engaging with these teams, as we work to build a company like no other." This is substantive about company culture; we can include in About the role. - Also: "Qualified applicants with criminal histories will be considered for employment". That's EEO? Actually it's a statement about criminal histories; might be considered EEO/boilerplate? It's not exactly EEO but could be considered a hiring practice statement. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This statement about criminal histories might be considered EEO-related? It's about considering applicants with criminal histories; could be considered a fair chance hiring statement. Might be considered boilerplate; but it's substantive? It's a policy. Might be okay to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but could be considered a hiring policy. I'd lean to keep it as it's substantive about consideration. However it's similar to EEO statements. Safer to