Electrical Construction Project Management Director

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. We need to parse the job posting. First, remove boilerplate: "Work with Us. Change the World..." intro, "At AECOM, we're delivering a better world..." etc. Also remove "About Construction Management – AECOM Hunt" maybe considered about the company but not a required heading? Could be "About the role"? Actually "About Construction Management – AECOM Hunt" is about the division; maybe we can treat as "About the role"? But we should not invent headings. 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 if present. We have: - Job Description: "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." That's about the role. Could be "About the role". We'll put that under

About the role

with a

. - Key Responsibilities: list bullet points. We'll put under

Responsibilities

with

• . - Qualifications: includes Minimum Requirements and Preferred Qualifications. That's qualifications. So

  Qualifications

  with maybe subpoints? Could list as
  for each bullet. - Skills: Not explicitly listed as separate, but qualifications include skills like communication, leadership, problem-solving. Could we create a Skills section? The instruction says include a section ONLY when posting has real, specific content for it. There's no explicit "Skills" heading, but we could infer skills from qualifications. However better to not create a Skills section unless there is explicit list of skills. The posting includes "Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills." That's skills. Could be placed under Qualifications or Skills. Since we have Qualifications already, we could keep them there. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Qualifications. - Benefits: The posting mentions "About AECOM AECOM is proud to offer comprehensive benefits..." includes list of benefits. That's specific content. So we should include a Benefits section. - Pay: Not mentioned. No salary info. So we should NOT include Pay section. - Schedule: Not mentioned (no mention of full-time/part-time, remote/hybrid). There is statement: "This position is not hybrid nor remote." That's about work arrangement, not schedule. Could be considered schedule? But schedule usually refers to hours, shift. Not present. So we omit Schedule. - About the company: Could be "About the role"? Already used. There's also "About AECOM" paragraph describing company. Could be considered "About the role"? Not exactly. But we could include an "About the company" but not in allowed headings list. The allowed headings are those examples; we could still use other headings? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also use other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. The "About AECOM" could be considered "About the role"? Not really. But we could omit it as it's boilerplate? It's describing the company, maybe not needed. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we don't have a heading for it, we could put it under a generic

  without heading? The instruction says use

  for section headings (e.g...). It doesn't forbid having paragraphs without headings. So we can include a

  about AECOM after the sections. Similarly, "About Construction Management – AECOM Hunt" could be a paragraph. We also need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc. Remove that. Also remove "Additional Information" about sponsorship, substance abuse test, in-person onboarding. That's substantive? It's about work authorization, test, onboarding. Should we keep? It's substantive info about the job. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. Where to place? Could be under a heading like "Additional Information" but not in allowed headings. Could be a

  after Qualifications. We also need to remove duplicated lines. Let's extract substantive content: Intro paragraph about AECOM delivering better world etc. Might be considered boilerplate? It's generic marketing but maybe substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not those categories; it's about the company. Might be considered substantive? It's describing AECOM's mission. Could keep as a paragraph. But we also have later "About AECOM" repeating similar content. That's duplicated. We should keep only one instance. Let's identify duplicates: - Early paragraph: "Work with Us. Change the World. At AECOM, we're delivering a better world...." That's a marketing intro. - Later: "About AECOM AECOM is proud to offer comprehensive benefits..." Actually that's about benefits. - Later: "AECOM is the global infrastructure leader, committed to delivering a better world...." That's similar to earlier. - Later: "What Makes AECOM a Great Place To Work ..." that's also marketing. We need to decide what to keep. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep all distinct pieces of information, not just unique. But duplicates we should remove duplicated lines. So if same sentences appear multiple times, we keep one. Let's list distinct substantive pieces: 1. Intro marketing about AECOM delivering better world, global team, etc. (first paragraph) 2. Job Description paragraph about seeking Electrical Project Manager Director. 3. Key Responsibilities list (6 items). 4. About Construction Management – AECOM Hunt paragraph (history). 5. Qualifications: Minimum Requirements (list of education/experience combos) and Preferred Qualifications (list). 6. Additional Information: no sponsorship, must pass substance abuse test, not hybrid nor remote, in-person Day 1 onboarding. 7. About AECOM benefits paragraph (list of benefits). 8. AECOM global infrastructure leader paragraph (revenue $16.1B FY2025). 9. What Makes AECOM a Great Place To Work paragraph (growth, projects, training, etc.) 10. EEO statement etc (to remove). Also there is "About Construction Management – AECOM Hunt" maybe considered part of "About the role"? We'll keep as separate paragraph. Now we need to map to headings. We have About the role: could combine intro marketing + Job Description? But maybe better to have About the role = Job Description paragraph. The intro marketing about AECOM could be a separate paragraph without heading or under a generic heading like "About AECOM". But not in allowed list. However we could still use

  About AECOM

  though not in examples but maybe acceptable. 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. So we can use other headings as needed. Safer to use those examples only? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could stick to those. However we have info that doesn't fit those categories: company overview, benefits, etc. Benefits fits. Company overview maybe could be placed under "About the role"? Not accurate. Could be under "About the role" as a description of the company and role? Might be stretching. Alternatively we could create a section "About the company" using

  About the company

  . Since not prohibited, I think it's okay. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed. I'll include headings for: About the role, Responsibilities, Qualifications, Benefits, About AECOM (company overview), Additional Information (maybe as a paragraph without heading). However Additional Information could be under "Requirements"? Not exactly. Could be under "Qualifications"? No. Better to keep Additional Information as a

  after Qualifications. Let's craft HTML:

  About the role

  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

  • 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.

  Qualifications

  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.

  Preferred 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. Strong knowledge of electrical codes, standards, and best practices. Excellent communication, leadership, and problem-solving skills.

  Benefits

  AECOM is proud to offer comprehensive benefits to meet the diverse needs of our employees. Depending on your employment status, AECOM benefits may include medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absences, voluntary benefits, perks, flexible work options, well-being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, and employee stock purchase plan.