Electrical Construction Project Management Director

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Company Description" maybe? The company description is part of posting but not a required heading; we can include as prose maybe under a heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have: - About the role: Could be from Job Description paragraph: "We are seeking an experienced Electrical Project Manager Director to lead and oversee electrical systems installation and commissioning for a major convention center construction project. This role requires a seasoned professional with a strong background in construction management, electrical engineering, and project leadership. The successful candidate will ensure the project is executed efficiently, safely, and in compliance with all relevant codes and standards." - Responsibilities: Key Responsibilities list. - Requirements: Minimum Requirements? Actually "Minimum Requirements" and "Preferred Qualifications". Could treat Minimum Requirements as Requirements, Preferred Qualifications as Qualifications? But we have separate headings: Requirements and Qualifications. Could put Minimum Requirements under Requirements, and Preferred Qualifications under Qualifications. Also there is "Additional Information" about sponsorship, substance test, onsite, compensation range, etc. That could go under Pay (compensation) and maybe Schedule? There's schedule: "This position is not hybrid nor remote." Also "in-person Day 1 onboarding". Not exactly schedule but indicates onsite. Could include under Schedule? The instruction: include Schedule section only if posting actually states them. It states "This position is not hybrid nor remote." That's about work location model, not schedule. Could treat as Schedule? Might be better to omit Schedule if not explicit hours. There's no mention of hours. So we may omit Schedule. - Benefits: There's a paragraph about AECOM benefits: "AECOM is proud to offer comprehensive benefits...". That's benefits content. - Pay: Compensation range: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $154340.53 to $285529.99." Also later "Compensation: USD 154340.53 - USD 285529.99 - yearly". So we include Pay section with that range. - Skills: Could be from Preferred Qualifications: list of skills like experience with medium/high voltage, familiarity with industrial electrical systems, expertise in commissioning, etc. Also "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." Those could go under Skills. - Qualifications: Could be Minimum Requirements (education/experience). Also maybe "Preferred Qualifications" could be Qualifications? But we already used Preferred for Skills. Might need to decide. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid filler. Ensure each heading has substantive content. Let's extract: About the role: as above. Responsibilities: bullet list from "Key Responsibilities :" - Manage the full lifecycle of electrical systems projects, including procurement, installation, testing, and commissioning. - Lead multidisciplinary teams, including electrical engineers, contractors, and construction personnel, to achieve project goals. - Review and approve electrical designs, specifications, and submittals to ensure compliance with project requirements, codes, and standards. - Collaborate with architects, engineers, utility companies, and other stakeholders to ensure seamless integration of electrical systems with the overall project. - Develop and manage project budgets, timelines, and resources to ensure on-time and within-budget delivery. - Prepare and review daily and weekly reports, change orders, pay applications, and commissioning plans. Requirements: Minimum Requirements: "BS Construction Management/Engineering and 12 years of electrical construction experience or AA/AS and 14 years of experience or HSD/GED and 16 years of relevant experience or demonstrated equivalency of experience and/or education, 4 years of leadership". That's substantive. Qualifications: Could be "Preferred Qualifications" list? But we might treat that as Qualifications. However we also have Skills heading. Could split: Qualifications = Preferred Qualifications (experience with medium/high voltage, familiarity with industrial electrical systems, expertise in commissioning, utility coordination, managing large-scale projects, strong knowledge of codes, excellent communication, leadership, problem-solving). Skills = maybe the same? Might be redundant. Better: Qualifications = Minimum Requirements? But we already used Requirements for Minimum Requirements. Actually we could swap: Requirements = Minimum Requirements, Qualifications = Preferred Qualifications. Then Skills could be something else like "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." But those are already in Preferred Qualifications. Could still list them under Skills. Let's decide: - Requirements: Minimum Requirements (education/experience). - Qualifications: Preferred Qualifications (list of experiences/skills). - Skills: maybe we can extract specific skill items: "Experience with medium and high voltage power distribution systems. Familiarity with industrial electrical systems and automation. Expertise in commissioning and testing of electrical systems, including NETA standards. Experience in managing utility coordination and electrical system upgrades. Demonstrated success in the management of large-scale electrical systems projects in large and complicated construction building projects. Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." But that is essentially same as Qualifications. To avoid duplication, maybe we can put Qualifications as the Preferred Qualifications, and Skills as a subset like "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." However that would lose some content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop content. We need to include all specifics somewhere. If we put all Preferred Qualifications under Qualifications, we still need to include Skills section with something; but we could make Skills section contain the same items? That would duplicate content, which is allowed? The instruction says do NOT invent or summarize away detail; duplication is not prohibited but might be considered redundant. Better to avoid duplication by distributing content: maybe Requirements = Minimum Requirements, Qualifications = Preferred Qualifications (including experience items), Skills = maybe we can extract "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." but those are already in Preferred Qualifications. Could we instead put under Skills the items that are skills: "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." and keep Qualifications as the experience/education preferences (like experience with medium/high voltage, familiarity with industrial electrical systems, expertise in commissioning, utility coordination, managing large-scale projects). That splits content without duplication. Let's parse Preferred Qualifications list: - Experience with medium and high voltage power distribution systems. - Familiarity with industrial electrical systems and automation. - Expertise in commissioning and testing of electrical systems, including NETA standards. - Experience in managing utility coordination and electrical system upgrades. - Demonstrated success in the management of large-scale electrical systems projects in large and complicated construction building projects. - Strong knowledge of electrical codes, standards, and best practices. - Excellent communication, leadership, and problem-solving skills. We can assign first five to Qualifications (experience/familiarity/expertise/management). Last two to Skills. Thus: Qualifications (

Qualifications

):

• Experience with medium and high voltage power distribution systems.
• Familiarity with industrial electrical systems and automation.
• Expertise in commissioning and testing of electrical systems, including NETA standards.
• Experience in managing utility coordination and electrical system upgrades.
• Demonstrated success in the management of large-scale electrical systems projects in large and complicated construction building projects.

Skills (

Skills

):

• Strong knowledge of electrical codes, standards, and best practices.
• Excellent communication, leadership, and problem-solving skills.

Now Benefits: paragraph about AECOM benefits. Pay: compensation range. Schedule: we have "This position is not hybrid nor remote." Also "in-person Day 1 onboarding". Could treat as Schedule? Not exactly schedule but maybe work location model. The instruction: include Schedule section only if posting actually states them. It does state work location model (On-Site) and that it's not hybrid nor remote. Could treat as Schedule? Might be better to include a section "Schedule" with content: "On-site work required; not hybrid or remote." However the heading Schedule usually refers to hours/shift. But we can still include as it's about work schedule model. The instruction says "Prefer a few substantive sections over many thin ones." If we add Schedule with minimal content, maybe it's thin. But we have info about work location model; we could incorporate that into About the role or Responsibilities? Not really. Could add a short line under About the role? But we must preserve all substantive info. The work location model is substantive. Could we put it under About the role as a sentence? That would preserve info without creating a thin section. The About the role currently is a paragraph; we can append "This position is on-site (not hybrid or remote)." That would keep info. Thus we may omit Schedule section entirely. Now Benefits: we have paragraph about AECOM benefits. Also there is line "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's part of Pay. Now we need to ensure we didn't include boilerplate: Remove EEO, equal opportunity, scam warning, etc. Also remove "Additional Information" lines about sponsorship, substance test, onboarding, etc. Those are substantive? They are about sponsorship, substance test, onboarding requirement. Are they considered boilerplate? They are specific to the job: "This position does not include sponsorship for United States work authorization now or in the future. Qualified applicants who are offered a position must pass a pre-employment substance abuse test. This position is not hybrid nor remote. At AECOM, we are committed to maintaining a secure and trustworthy recruitment process and take any fraudulent hiring activity seriously. To support this commitment, all newly hired employees are required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment." Some of that is boilerplate-ish but still specific. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sponsorship statement, substance test, onboarding requirement might be considered part of "Additional Information" not boilerplate. Should we keep? It's substantive info about the job. The instruction says preserve ALL substantive information. So we should keep that info somewhere. Where to put? Could be under About the role or a separate section like "Additional Information". But we only have allowed headings list; we could add a paragraph under About the role or under Responsibilities? Probably better to add a short paragraph under About the role after the description. Or we could create a section "Additional Information" but not in allowed headings; we should stick to allowed headings. So we can incorporate into About the role. Thus About the role paragraph will include: "We are seeking an experienced Electrical Project Manager Director to lead and oversee electrical systems installation and commissioning for a major convention center construction project. This role requires a seasoned professional with a strong background in construction management, electrical engineering, and project leadership. The successful candidate will ensure the project is executed efficiently, safely, and in compliance with all relevant codes and standards. This position does not include sponsorship for United States work authorization now or in the future. Qualified applicants who are