Project Executive (Civil)

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 as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the URL maybe? It's part of posting but maybe considered navigation? It's a link to careers page; might be considered boilerplate? Probably remove. We need to parse the posting. First paragraph: "As Project Executive, you will be the driving force..." That's about the role. So we can put under

About the role

with

containing that paragraph. Then "Responsibilities" heading: list of responsibilities after "Responsibilities". The posting shows a block: "Responsibilities Drive strategic initiatives..." It's a long list of sentences separated by periods. We need to turn into

• items. Each sentence likely a responsibility. Let's extract: - Drive strategic initiatives and capture strategies to expand Clark Civil’s substation business line and market share. - Oversee total project portfolio performance, ensuring enterprise level risk mitigation, contractual compliance, and profitability. - In coordination with the Substation business unit leader, direct pursuit strategies, lead high stakes proposal presentations, and cultivate executive relationships with Owners, key trade partners, and engineering firms. - Identify strategic market trends, capital project pipelines, and prospective business growth opportunities. - Assemble, mentor, and deploy project management teams to execute project delivery. - Champion a strong culture of safety, quality, and operational excellence across all project operations. - Oversee major prime contract negotiations, master service agreements, high-level change orders, and macro-level schedule/financial reporting. - Establish operational governance, high-level milestone monitoring, and risk response strategies across all active project sites. - Build, train, and develop executive level project management leaders and foster succession planning. - Serve as the primary executive contact for client, owner, engineering, and partner executives. - Lead executive level job status reviews, financial forecasting, long range resource planning, and high level project closeout strategies. That seems correct. Next "Basic Qualifications" heading: list of qualifications. We'll put under

  Requirements

  maybe? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Basic Qualifications" maps to Requirements. Also there is "Preferred Qualifications" maybe map to Qualifications? Or Skills? Let's decide: Basic Qualifications -> Requirements. Preferred Qualifications -> Qualifications (maybe includes certifications, software, etc). Also there may be Skills section: we can extract soft skills etc from Basic Qualifications? Actually Basic Qualifications includes many items: Education, Experience, Technical Substation Expertise, Industry Profile, Leadership, Project Management, Business Acumen, Decision-Making, Relationship Building, Soft Skills, Core Values Alignment. Those could be split into Requirements and Skills. But we have separate headings for Requirements, Qualifications, Skills. We need to decide mapping. We could put Education, Experience, Technical Substation Expertise, Industry Profile under Requirements. Leadership, Project Management, Business Acumen, Decision-Making, Relationship Building under Skills? Soft Skills also under Skills. Core Values Alignment maybe under Qualifications? Hmm. Better: Use Requirements for mandatory qualifications (education, experience, technical expertise, industry profile). Use Qualifications for preferred qualifications (delivery methods, software, certifications). Use Skills for soft skills and core values alignment? But the instruction says we can have few substantive sections over many thin ones. We need to include sections only when posting has real specific content. We have content for each. Let's extract: Basic Qualifications bullet list: - Education: Undergraduate or graduate degree in engineering, architecture, construction management, a related discipline, or equivalent relevant work experience. - Experience: Minimum of 15+ years of project management experience, directly overseeing, directing, and executing $100M+ complex, self-perform, civil or substation construction projects. - Technical Substation Expertise: Specific, hands-on experience with high voltage Gas-Insulated Switchgear (GIS) projects rated >= 34.5 kV. Work must have been physically constructed (built environment experience required). - Industry Profile: Background as a Prime Contractor is preferred, followed by Subcontractor, Design/Engineering, Manufacturer, or Owner/Utility experience. - Leadership: 7+ years leading, developing, and motivating teams on substation projects. - Project Management: Track record of managing project departments successfully from start to finish. - Business Acumen: Deep understanding of the strategic, operational, and financial components of a construction project. - Decision-Making: Demonstrated ability to make timely and effective decisions. - Relationship Building: Skilled at developing and negotiating relationships with owners and trade contractors. - Soft Skills: Strong work ethic, leadership ability, and comfort working in a fast-paced environment. - Core Values Alignment: Alignment to Clark Standards of Excellence (self-motivated, results-oriented, adaptable, team player, accountable, ethical, innovative, resilient, relationship builder, team developer, sets direction, and executes). Preferred Qualifications: - Delivery Methods: Direct experience with Design/Build or EPC (Engineering, Procurement, and Construction) project delivery models. - Software/Systems: Proficiency with Primavera P6, SAP (or similar financial systems), Procore, and Microsoft Excel. - Certifications: DBIA and LEED Accreditation. Also there is compensation info: "For this role the base salary range is $83,200-260,000. Compensation may vary outside of this range depending on a number of factors, including a candidate’s education, experience, skills, and geographic location." That's Pay section. Benefits: "Clark offers a total compensation package that includes base salary, bonus potential, and a comprehensive benefits package including health/dental/vision benefits, paid time off, retirement/401k, and Company Contribution plan. Additional benefits include life insurance, commuter benefit, short & long term disability, fitness reimbursement, FSA, tuition reimbursement, back-up daycare, tutoring & family support benefits, EAP/Work-Life assistance, and a holiday contribution program." We can put that under Benefits. Schedule: Not explicitly mentioned. There's mention of "flexibility to work extended hours, especially during critical project phases or client deadlines." Also "Beyond regular working hours, there will be occasions where business needs require your attention..." That's about schedule/hours. Could be considered Schedule. But the instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention extended hours, flexibility, etc. So we can include Schedule with that info. Also there is "Physical Side of the Role", "Your Work Environment", "Our High-Performing Culture", "A Drug Free Workplace". Those could be considered part of About the role or maybe separate sections like Working Conditions, but not in allowed headings. We could incorporate into About the role as additional paragraphs. But we must not invent sections not allowed. We can add extra paragraphs under About the role covering those details. We must remove boilerplate: The URL, maybe the "Clark Civil Clark Civil performs heavy/civil work..." That's description of company; could be considered About the role? It's not about the role but about company. Might be considered boilerplate? It's substantive info about the company; but not about the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info somewhere. Where? Could be under About the role as a paragraph describing the company. Or we could create a separate section like "About the Company" but not allowed headings. So we incorporate into About the role. Also "Clark Civil is a division of Clark Construction Group, LLC" etc. Also "The Physical Side of the Role:" etc. That's about role demands; we can include under About the role. Also "Your Work Environment:" etc. Also "Our High-Performing Culture:" etc. Also "A Drug Free Workplace:" etc. Also "Clark promotes a drug free workplace..." etc. Also "Clark offers a total compensation package..." we already captured benefits. Also "For this role the base salary range..." we captured pay. Also "https://www.clarkconstruction.com/careers/clark-experience" - maybe remove as navigation/link. Also duplicate lines? Not seeing duplicates. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

  About the role

  ... (combine paragraphs)

  Responsibilities

  • ...
  ...

  Requirements

  • Education: Undergraduate or graduate degree in engineering, architecture, construction management, a related discipline, or equivalent relevant work experience.
  • Experience: Minimum of 15+ years of project management experience, directly overseeing, directing, and executing $100M+ complex, self-perform, civil or substation construction projects.
  • Technical Substation Expertise: Specific, hands-on experience with high voltage Gas-Insulated Switchgear (GIS) projects rated >= 34.5 kV. Work must have been physically constructed (built environment experience required).
  • Industry Profile: Background as a Prime Contractor is preferred, followed by Subcontractor, Design/Engineering, Manufacturer, or Owner/Utility experience.
  • Leadership: 7+ years leading, developing, and motivating teams on substation projects.
  • Project Management: Track record of managing project departments successfully from start to finish.
  • Business Acumen: Deep understanding of the strategic, operational, and financial components of a construction project.
  • Decision-Making: Demonstrated ability to make timely and effective decisions.
  • Relationship Building: Skilled at developing and negotiating relationships with owners and trade contractors.
  • Soft Skills: Strong work ethic, leadership ability, and comfort working in a fast-paced environment.
  • Core Values Alignment: Alignment to Clark Standards of Excellence (self-motivated, results-oriented, adaptable, team player, accountable, ethical, innovative, resilient, relationship builder, team developer, sets direction, and executes).

  Qualifications

  • Delivery Methods: Direct experience with Design/Build or EPC (Engineering, Procurement, and Construction) project delivery models.
  • Software/Systems: Proficiency with Primavera P6, SAP (or similar financial systems), Procore, and Microsoft Excel.
  • Certifications: DBIA and LEED Accreditation.

  Skills

  Maybe we can combine soft skills already in Requirements; but we could keep Skills empty? Better to not create empty section. Since we already have soft skills in Requirements, we could omit Skills section. But we might want to highlight skills like "Proficiency with Primavera P6..." but that's in Qualifications. So maybe we don't need Skills. But we have to decide: The instruction says prefer a few substantive sections over many thin ones. We could merge Requirements and Qualifications into one section called Requirements? But they said use headings like Requirements, Qualifications, Skills. We can still use them if we have content. We have content for Requirements and Qualifications. Skills we could omit if we don't have distinct skills beyond those already covered. However we have "Soft Skills" and "Core Values Alignment" which could be considered skills. But they are already in Requirements. Could move them to Skills section. Let's think: Requirements usually are mandatory qualifications (education, experience, technical expertise). Skills could be abilities like leadership, decision-making, relationship building, soft skills, core values. Qualifications could be preferred qualifications (delivery methods, software, certifications). That seems logical.