Construction Project Manager - Transmission Line - Michels Power, Inc.
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. No Pay or Schedule unless stated. The posting does not mention pay or schedule specifics, so we should not include those sections. Benefits are mentioned: "Comprehensive Benefits Package" with list. So include Benefits heading. Also maybe "Work Environment & Physical Demands" could be considered but not in allowed headings; we can either omit or map to something else? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings; we can also have other headings? It says use for section headings (e.g. ...). Likely we should stick to those headings only. So we need sections: About the role (position overview), Responsibilities, Requirements (maybe includes education/experience), Qualifications (maybe core competencies?), Skills (maybe software proficiency), Benefits. We must not repeat job title as heading. Also we must not include Job ID etc.
We need to preserve all substantive information. Let's parse.
Posting content:
- Location: Various Employment Type: Full-Time Travel: Required (metadata, can be short p)
- Build the Lines That Power the Grid (intro)
- At Michels Power... (description)
- Position Overview (paragraph)
- As a Project Manager – Transmission Line Construction, you will lead...
- Key Responsibilities (list bullet points)
- What it takes? (list of requirements)
- Core Development Competencies (list)
- Work Environment & Physical Demands (description)
- Why Michels Power, Inc.? (list)
- Why you? (list)
- Join a company... (closing)
- AA/EOE... (boilerplate to remove)
- Link to privacy policy (boilerplate)
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove AA/EOE line and link.
We need to preserve all substantive info. So we need to include the intro paragraphs, position overview, responsibilities, requirements (education/experience), core competencies maybe as Qualifications or Skills, benefits, why Michels (maybe as Benefits? but we already have Benefits heading for benefits package; why Michels could be part of About the role? Might be better to include as a separate section like "About the company" but not allowed headings. Could incorporate into About the role or maybe omit? But we must preserve all substantive information; we cannot omit "Why Michels Power, Inc.?" and "Why you?" sections. We need to place them somewhere. Since only allowed headings are those listed, we could put them under About the role (as prose) or under Responsibilities? Better to create a section "About the role" that includes position overview and maybe why Michels and why you? But that may mix.
Alternatively, we could create additional headings not in the list? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. We can put "Why Michels Power, Inc.?" and "Why you?" under About the role as prose paragraphs.
We also have "Work Environment & Physical Demands" - could be part of About the role or Requirements? Might be considered as part of Requirements? Not exactly. Could be included under About the role as well.
We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we include Benefits.
We need to not repeat job title as heading.
We need to output only HTML fragment.
Let's craft:
About the role
for section headings (e.g. ...). Likely we should stick to those headings only. So we need sections: About the role (position overview), Responsibilities, Requirements (maybe includes education/experience), Qualifications (maybe core competencies?), Skills (maybe software proficiency), Benefits. We must not repeat job title as heading. Also we must not include Job ID etc.
We need to preserve all substantive information. Let's parse.
Posting content:
- Location: Various Employment Type: Full-Time Travel: Required (metadata, can be short p)
- Build the Lines That Power the Grid (intro)
- At Michels Power... (description)
- Position Overview (paragraph)
- As a Project Manager – Transmission Line Construction, you will lead...
- Key Responsibilities (list bullet points)
- What it takes? (list of requirements)
- Core Development Competencies (list)
- Work Environment & Physical Demands (description)
- Why Michels Power, Inc.? (list)
- Why you? (list)
- Join a company... (closing)
- AA/EOE... (boilerplate to remove)
- Link to privacy policy (boilerplate)
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove AA/EOE line and link.
We need to preserve all substantive info. So we need to include the intro paragraphs, position overview, responsibilities, requirements (education/experience), core competencies maybe as Qualifications or Skills, benefits, why Michels (maybe as Benefits? but we already have Benefits heading for benefits package; why Michels could be part of About the role? Might be better to include as a separate section like "About the company" but not allowed headings. Could incorporate into About the role or maybe omit? But we must preserve all substantive information; we cannot omit "Why Michels Power, Inc.?" and "Why you?" sections. We need to place them somewhere. Since only allowed headings are those listed, we could put them under About the role (as prose) or under Responsibilities? Better to create a section "About the role" that includes position overview and maybe why Michels and why you? But that may mix.
Alternatively, we could create additional headings not in the list? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. We can put "Why Michels Power, Inc.?" and "Why you?" under About the role as prose paragraphs.
We also have "Work Environment & Physical Demands" - could be part of About the role or Requirements? Might be considered as part of Requirements? Not exactly. Could be included under About the role as well.
We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we include Benefits.
We need to not repeat job title as heading.
We need to output only HTML fragment.
Let's craft:
About the role
About the role
Location: Various. Employment Type: Full-Time. Travel: Required.
[Intro paragraph about building lines...]
[Position Overview paragraph]
[Why Michels Power, Inc.? list as prose? Could convert list to
- but that would be a list; but we already have Responsibilities list; we could still have another list under About the role. That's okay. Actually we can have multiple
- ...
What it takes? list: education/experience etc. We'll put under
Requirements
maybe. Core Development Competencies list: could be underQualifications
orSkills
. The heading Qualifications is for qualifications; Skills for skills. Core competencies are like behaviors; could be Qualifications. We'll put underQualifications
. Skills: maybe we can list software proficiency etc. But we already have experience with project management software etc under Requirements. Could also put under Skills. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications? But we need to follow headings. We could have Requirements (education/experience) and Qualifications (core competencies). Skills maybe not needed if not much left. However we have "Proficiency with Microsoft Office Suite" and "Experience with project management software (Primavera, HCSS, or similar preferred)" which are skills. Could put under Skills heading. But we already have those in Requirements list; we could move them to Skills. Let's decide: Requirements: education, years experience, ability to manage multiple projects, strong understanding of contracts, scheduling, cost control, valid driver's license, willingness to travel. Skills: experience with project management software, proficiency with Microsoft Office Suite, excellent communication, leadership, organizational skills (these are also skills). However communication/leadership/organizational are also in Core Development Competencies. Might duplicate. Better: Use Requirements for education/experience, Qualifications for core competencies, Skills for software/office proficiency. That seems reasonable. Benefits: list underBenefits
. We also have Work Environment & Physical Demands; we could incorporate into About the role as a paragraph. We also have "Why Michels Power, Inc.?" and "Why you?" lists; we can incorporate into About the role as- sections.
Now we need to ensure we don't create empty sections.
Let's draft HTML.
We'll start with
About the role
Inside:Location: Various. Employment Type: Full-Time. Travel: Required.
ThenStrengthening the power grid requires more than generation—it depends on the safe, reliable transmission of electricity across vast distances. At Michels Power, Inc., we build and maintain the transmission infrastructure that connects energy sources to communities, industries, and businesses across the country. From new line construction to rebuilds and system upgrades, our teams deliver critical projects that keep the grid strong and resilient. As one of the nation’s leading power delivery contractors, Michels Power performs work across transmission, substations, distribution, renewable energy, and emergency restoration—supporting utilities and energy providers nationwide.
ThenAs a Project Manager – Transmission Line Construction, you will lead the execution of transmission line projects or key phases of large, complex programs. You will be accountable for all aspects of project success—from bid development and planning through execution and closeout—ensuring strong safety performance, client satisfaction, and financial results. This role requires a proactive, organized leader who can effectively manage multiple priorities, collaborate across teams, and make informed decisions in a fast-paced construction environment.
Then maybeWhy Michels Power, Inc.?
but not allowed heading. We'll instead put under About the role as a- with heading? Could add a
Why Michels Power, Inc.?
then list. That's okay. Similarly for Why you?. Now Responsibilities section. Then Requirements. Then Qualifications. Then Skills. Then Benefits. We must not include Pay or Schedule. Now let's extract exact bullet points. Key Responsibilities list: - Lead projects from proposal and bidding through execution and closeout - Promote and maintain a strong safety culture across all project activities - Review project plans and contracts to define scope, schedule, staffing, and resource requirements - Manage project performance, including schedule adherence, cost control, and risk management - Build and maintain strong relationships with clients, subcontractors, and project partners - Serve as the primary point of contact for contractual matters, including changes and issue resolution - Collaborate with field leadership to coordinate construction activities and ensure efficient execution - Develop and manage project work plans, assigning responsibilities and driving accountability - Review project status reports and adjust schedules or plans as needed - Prepare and present reports to leadership, clients, and stakeholders - Coordinate compliance with regulatory requirements and customer specifications - Lead or support bid development, RFP responses, and estimating efforts as needed - Resolve project challenges proactively and escalate issues when appropriate - Perform other duties as assigned What it takes? list: - Bachelor’s degree in Project Management, Construction Management, Engineering, or related field (or equivalent experience) - 5–7+ years of project management experience, preferably in transmission line, utility,
- inside a section.
Better: After position overview, we can add a
- for Why Michels Power, Inc.? and another for Why you?.
But we need to keep the content.
Let's extract exact sentences.
Intro: "Build the Lines That Power the GridStrengthening the power grid requires more than generation—it depends on the safe, reliable transmission of electricity across vast distances."
Actually there is no space between "GridStrengthening". We'll keep as is but maybe add space for readability? We must preserve ALL substantive information; we can keep the text exactly as given, but we can also format with proper spacing? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid minor formatting changes like adding spaces? Safer to keep the exact text but we can correct obvious typo? Might be considered inventing? Probably better to keep as is but we can add a space after "Grid" to make readable; but that changes content. I'd keep as given but maybe it's okay to add a space because it's clearly a missing space due to PDF extraction. However, to be safe, I'll keep the exact string but maybe add a space? I'd rather keep as is but it's ugly. I think it's acceptable to add a space because it's not adding information, just fixing formatting. However, the instruction says do NOT invent or summarize away detail. Adding a space is not inventing detail; it's just formatting. I'll add a space.
Let's copy paragraphs:
"Strengthening the power grid requires more than generation—it depends on the safe, reliable transmission of electricity across vast distances.
At Michels Power, Inc., we build and maintain the transmission infrastructure that connects energy sources to communities, industries, and businesses across the country. From new line construction to rebuilds and system upgrades, our teams deliver critical projects that keep the grid strong and resilient.
As one of the nation’s leading power delivery contractors, Michels Power performs work across transmission, substations, distribution, renewable energy, and emergency restoration—supporting utilities and energy providers nationwide."
Position Overview: "As a Project Manager – Transmission Line Construction, you will lead the execution of transmission line projects or key phases of large, complex programs.
You will be accountable for all aspects of project success—from bid development and planning through execution and closeout—ensuring strong safety performance, client satisfaction, and financial results.
This role requires a proactive, organized leader who can effectively manage multiple priorities, collaborate across teams, and make informed decisions in a fast-paced construction environment."
Key Responsibilities list (each bullet). We'll put under