Electrical Construction Project 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 if posting has real specific content. We need to parse the posting. Content: - Title: NOW HIRING - DATA CENTER CONSTRUCTION | ARIZONA (but we don't repeat job title as heading; we can ignore). - Body: "I'm working with a repeat client that is looking to hire experienced electrical construction professionals for major data center projects in Arizona." - Open Positions: "Electrical Project Manager - Compensation up to $225K" Then bullet list of items: - Strong electrical construction background - Data center construction experience required - Experience managing large-scale projects - Strong leadership and team management experience - Ability to manage schedules, budgets, subcontractors, and project execution - Proven track record delivering complex electrical projects Then "What They're Looking For Location: Arizona" Then "You do not have to currently live in Arizona. My client is open to relocating the right individuals for these opportunities." Then "These are high-level opportunities with a repeat client that has a strong pipeline of major data center work." Then "Interested in one of these positions, or exploring opportunities in general? Send me a message and I'll reach out with additional details." Then "Apply Today If you're an experienced electrical construction professional looking to take the next step in your career, we'd love to discuss this opportunity." Then contact info: Contact: Dan Reuer 605-335-8095 dan.reuer@gogpac.com Then confidentiality statement, EEO, etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove the EEO paragraph and the GPAC description? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO paragraph and the GPAC description (since that's boilerplate about the firm). Also remove "Apply Today" maybe considered application instructions? It says "Apply Today If you're an experienced electrical construction professional looking to take the next step in your career, we'd love to discuss this opportunity." That's kind of a call to action; might be considered application instructions. Probably remove that line as well. Also "Interested in one of these positions, or exploring opportunities in general? Send me a message and I'll reach out with additional details." That's also application instruction; remove. We need to preserve all substantive information: job description, responsibilities, requirements, location, compensation, contact info? Contact info maybe considered not boilerplate; it's substantive. Should we keep contact? Likely yes, as it's part of the posting. However "Contact: Dan Reuer 605-335-8095 dan.reuer@gogpac.com" is contact info; we can keep as a paragraph. We need to structure into sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: maybe a brief description: "I'm working with a repeat client that is looking to hire experienced electrical construction professionals for major data center projects in Arizona." Could be About the role. - Responsibilities: maybe the bullet list items about managing schedules, budgets, subcontractors, project execution, delivering complex electrical projects, managing large-scale projects, leadership, team management. Those could be responsibilities. - Requirements/Qualifications: Strong electrical construction background, data center construction experience required, experience managing large-scale projects, proven track record delivering complex electrical projects. Could be qualifications. - Skills: maybe leadership and team management, ability to manage schedules, budgets, subcontractors, project execution. - Pay: "Compensation up to $225K" (from Electrical Project Manager - Compensation up to $225K). So we have pay. - Schedule: Not mentioned. - Benefits: Not mentioned. - Location: Arizona (maybe part of About the role or a separate section? Not in list but we could include under About the role or maybe a separate "Location" but not in allowed headings. The allowed headings are only those; we could put location in About the role paragraph. We must not create sections with filler text. So we include only sections where we have real content. Thus we can have:

About the role

I'm working with a repeat client that is looking to hire experienced electrical construction professionals for major data center projects in Arizona. The position is for an Electrical Project Manager with compensation up to $225K.

But we might separate Pay into its own section. Better:

About the role

I'm working with a repeat client that is looking to hire experienced electrical construction professionals for major data center projects in Arizona.

Responsibilities

• Manage schedules, budgets, subcontractors, and project execution
• Deliver complex electrical projects
• Manage large-scale projects
• Provide strong leadership and team management

Requirements

• Strong electrical construction background
• Data center construction experience required
• Experience managing large-scale projects
• Proven track record delivering complex electrical projects

Skills

• Leadership and team management
• Ability to manage schedules, budgets, subcontractors, and project execution

Pay

Compensation up to $225K

We could also include Location in About the role. We must not include duplicate content. Ensure we don't repeat same bullet in multiple sections if it's same. For example "Ability to manage schedules, budgets, subcontractors, and project execution" appears both in Responsibilities and Skills; but it's okay if it's substantive. However we might avoid duplication by placing it only once. But the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but we should avoid unnecessary duplication? It didn't forbid duplication. However we might want to keep it once under Responsibilities and maybe not repeat under Skills. But Skills could be something else like "Strong leadership and team management experience". That's already in Responsibilities as leadership. Could combine. Better to have: Responsibilities: manage schedules, budgets, subcontractors, project execution; deliver complex electrical projects; manage large-scale projects; provide leadership and team management. Requirements: strong electrical construction background; data center construction experience; experience managing large-scale projects; proven track record delivering complex electrical projects. Skills: leadership and team management; ability to manage schedules, budgets, subcontractors, project execution (maybe redundant). Could just have skills: leadership and team management; schedule/budget management. But we need to preserve all detail; if we omit some detail, we violate. So we need to keep each piece somewhere. Let's list all distinct pieces: - Strong electrical construction background - Data center construction experience required - Experience managing large-scale projects - Strong leadership and team management experience - Ability to manage schedules, budgets, subcontractors, and project execution - Proven track record delivering complex electrical projects - Compensation up to $225K - Location: Arizona (and openness to relocation) - The client is a repeat client with strong pipeline of major data center work. - Contact: Dan Reuer 605-335-8095 dan.reuer@gogpac.com - Confidentiality statement (we remove) - EEO (remove) - GPAC description (remove) - "Apply Today" etc (remove) - "Interested... send me a message" (remove) - "You do not have to currently live in Arizona. My client is open to relocating the right individuals for these opportunities." (keep as part of location/open to relocation) - "These are high-level opportunities with a repeat client that has a strong pipeline of major data center work." (keep maybe as About the role) We need to incorporate all substantive info. Let's craft sections: About the role: includes description of role, location, client repeat, pipeline, openness to relocation. Responsibilities: managing schedules, budgets, subcontractors, project execution; delivering complex electrical projects; managing large-scale projects; providing leadership and team management. Requirements: strong electrical construction background; data center construction experience; experience managing large-scale projects; proven track record delivering complex electrical projects. Skills: leadership and team management; ability to manage schedules, budgets, subcontractors, project execution (maybe already covered). Could also include "strong leadership and team management experience" as skill. Pay: compensation up to $225K. Contact: maybe a separate section? Not in allowed headings but we could put under About the role as a paragraph. But we must not create headings not listed. So we can embed contact in a paragraph under About the role or maybe under a generic

after sections. We must not include any headings not listed. So we can just have

for contact. Thus final HTML:

About the role

I'm working with a repeat client that is looking to hire experienced electrical construction professionals for major data center projects in Arizona. The client has a strong pipeline of major data center work and is open to relocating the right individuals. Contact: Dan Reuer, 605-335-8095, dan.reuer@gogpac.com.

Responsibilities

• Manage schedules, budgets, subcontractors, and project execution
• Deliver complex electrical projects
• Manage large-scale projects
• Provide strong leadership and team management

Requirements

• Strong electrical construction background
• Data center construction experience required
• Experience managing large-scale projects
• Proven track record delivering complex electrical projects

Skills

• Leadership and team management
• Ability to manage schedules, budgets, subcontractors, and project execution

Pay

Compensation up to $225K

We have not included Schedule or Benefits sections because not present. Check duplication: "Ability to manage schedules, budgets, subcontractors, and project execution" appears in Responsibilities and Skills. That's duplication but it's okay as preserving detail. Could we remove from Skills to avoid duplication? But then we lose the skill detail. However the skill is essentially same as responsibility; but we could argue it's covered under Responsibilities. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit that line from Skills, we still have it in Responsibilities, so the information is preserved. So we can keep Skills maybe just "Leadership and team management". But we already have leadership in Responsibilities. Could we drop Skills entirely? Then we would lose the skill heading but we still have the content under Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine Skills into Responsibilities or Requirements. But we need to decide if we keep Skills section. Since we already have leadership and team management covered, we could omit Skills section to avoid thin section. However we must not omit any substantive info; but if the info is already present elsewhere, it's not omitted. So we can drop Skills. Thus sections: About the role, Responsibilities, Requirements, Pay. Let's craft About the role to include location, client repeat, pipeline, openness to relocation, contact. Responsibilities: as above. Requirements: as above. Pay: compensation. Check that we haven't missed any detail: "Strong leadership and team management experience" is in Responsibilities as