Operations - Vice President

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Legence" (company description) then "Vice President, Operations Legence | Reports to: Chief Operating Officer | Segments: Installation & Maintenance and Engineering & Consulting" then "Job Summary". Then "Key Responsibilities". Then "Required Qualifications". Then "Preferred Experience". Then "Travel & Compensation". Then "Benefits Overview". Then other sections like "Reasonable Accommodations", "Employment Eligibility", "Third-Party Recruiting Disclaimer", "Pay Disclosure & Considerations", "Equal Employment Opportunity Employer". According to rules, we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Reasonable Accommodations"? That's maybe considered application instructions? It's about accommodations during application; likely considered application instructions, so remove. "Employment Eligibility" maybe also boilerplate? It's about work authorization; could be considered required info but maybe it's boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Employment Eligibility" is legal requirement; might be considered boilerplate? Not sure. Usually they'd keep it? The instruction says remove EEO/equal-opportunity boilerplate. "Employment Eligibility" is not EEO but work authorization; could be considered legal. Might be removed. Safer to remove it. Also "Third-Party Recruiting Disclaimer" is legal; remove. "Pay Disclosure & Considerations" maybe keep? It's about pay disclosure; but we already have Pay section with salary range etc. The "Pay Disclosure & Considerations" is more boilerplate; maybe remove. "Equal Employment Opportunity Employer" definitely remove. We need to include sections only when posting has real specific content. So we need sections: About the role? Actually we have "Job Summary" which is prose. Could be 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 these headings. We have: - About Legence (company description) maybe "About the role"? Actually "About the role" is not present; we have company overview. Could treat as "About the role"? But instruction says use those headings as examples; we can use others if appropriate? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. So we can have sections: About the role (maybe company description), Responsibilities (Key Responsibilities), Qualifications (Required Qualifications), Skills (maybe not explicit), Benefits, Pay, Schedule (Travel). Also maybe "Preferred Experience" could be under Qualifications or Skills. We'll decide. We need to preserve all substantive information. So we need to include company description, job summary, responsibilities, required qualifications, preferred experience, travel, compensation (base salary, bonus, long-term incentive), benefits overview. We must not repeat job title as heading. The page already shows it, so we don't add heading for Vice President, Operations. We must not put Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. There's "Reports to: Chief Operating Officer | Segments: Installation & Maintenance and Engineering & Consulting". That's minor metadata; we can include in a short

after job summary maybe. We must not include filler like "commensurate with experience" etc. Actually we can include that if it's real content? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay section with actual numbers; we have base salary range, bonus, long-term incentive. That's specific. So we include Pay section. Schedule: we have Travel: Yes, 40–50%. That's schedule/travel. So we can include Schedule section with travel percentage. Benefits: we have Benefits Overview with details; include Benefits section. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Legence (Nasdaq: LGN) is a leading provider of engineering, consulting, installation, and maintenance services for mission-critical systems in buildings. The company specializes in designing, fabricating, and installing complex HVAC, process piping, and other mechanical, electrical, and plumbing (MEP) systems—enhancing energy efficiency, reliability, and sustainability in new and existing facilities. Legence also delivers long-term performance through strategic upgrades and holistic solutions. Serving some of the world’s most technically demanding sectors, Legence counts over 60% of the Nasdaq-100 Index among its clients.

Then maybe a short p for Reports to and Segments.

Job Summary

but Job Summary is not in the list of headings examples; but we could treat as About the role? Actually we already used About the role for company description. Job Summary could be a paragraph under About the role? Or we could have a separate section "Job Summary" as

Job Summary

. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to use Job Summary as heading. However to be safe, we could incorporate Job Summary into About the role or Responsibilities? Better to have a separate heading "Job Summary". The examples are not exhaustive; they say e.g. So we can use Job Summary. Thus:

Job Summary

The Vice President of Operations will serve as a key operating partner to the Chief Operating Officer, providing enterprise-wide operational leadership across Legence's Installation & Maintenance (I&M) and Engineering & Consulting (E&C) segments. This role owns the operating cadence, performance standards, and execution discipline that connect segment Presidents and their teams to the COO's strategic agenda — driving consistency, accountability, and growth across a decentralized, multi-company platform. This is a high-visibility, enterprise-facing leadership role for someone who can operate at both altitudes: setting strategy and standards with the COO and segment Presidents, while personally driving hands-on resolution of complex operational challenges across installation, maintenance, engineering, and consulting functions — including within newly acquired businesses joining the Legence platform.

Then we can include the Reports to and Segments as a short p after that. Then Responsibilities:

Responsibilities

• Partner with the COO, segment Presidents, and senior leadership to set and advance operational priorities across both the I&M and E&C segments.
• Own the enterprise operating rhythm — business reviews, KPI dashboards, and accountability systems — that give the COO and executive team visibility into performance across all business units.
• Identify and drive cross-segment synergies between I&M and E&C, including shared best practices, resource sharing, and commercial hand-offs between installation/maintenance and engineering/consulting teams.
• Lead efforts to solve complex, cross-functional operational challenges across installation, maintenance, engineering, and consulting functions.
• Assess current workflows across business units, identify inefficiencies, and implement process improvements that drive consistency, scalability, and performance.
• Support the operational integration of newly acquired businesses joining the Legence platform, standardizing practices while preserving business-unit-specific strengths.
• Support leaders and teams across both union and non-union environments with a practical, business-minded approach.
• Analyze business performance across segments, identify trends, and recommend solutions to improve service, productivity, margin, and execution.
• Provide input to the COO and segment Presidents on operational resourcing, tooling, and capital investment priorities.
• Own enterprise-level visibility into safety performance and drive consistent safety standards across field operations in both segments.
• Collaborate with finance, HR, and other corporate functions to align operational decisions with enterprise business goals and reporting requirements, including board- and investor-level reporting.
• Sponsor and drive change management efforts, and lead adoption of new processes, tools, and expectations across a multi-company platform.

Then Required Qualifications:

Qualifications

• Bachelor's degree required; MBA strongly preferred.
• 15+ years of progressive people management experience, including experience managing other operating leaders/managers (not solely individual contributors).
• 10+ years of consulting, management, or senior operational leadership experience.
• Demonstrated experience owning P&L or operating performance across multiple business units, locations, or entities in a complex, decentralized environment — ideally with exposure to managed revenue in the hundreds of millions of dollars.
• Strong track record of solving operational problems and improving business performance at scale.
• Ability to work effectively in both union and non-union environments.
• Strong communication, analytical, and cross-functional leadership skills, with experience presenting to executive leadership and/or a board.
• Proven ability to influence and partner with senior leaders, including C-suite executives.
• Military/Trade leadership experience is a plus.

Preferred Experience could be under Skills or Qualifications; we could add a section "Preferred Experience" as

Preferred Experience

with list.

Preferred Experience

• Experience in installation, maintenance, field operations, engineering, or similar service-based environments.
• Experience integrating acquired businesses or leading through organizational growth and transformation.
• Strong executive presence and ability to operate independently in a remote, enterprise-wide setting.

Then Pay:

Pay

• Base salary: $240,000–$300,000 per year, commensurate with experience and scope.
• Bonus: Eligible for an annual incentive target of approximately 25% of base salary, based on company and individual performance.
• Long-term incentive: Eligible for participation in Legence's applicable long-term incentive / equity program, subject to plan terms.

But note: we must not include filler like "commensurate with experience". That's considered filler? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says we should not emit a heading followed by filler/placeholder text. That means if we have a Pay section, we should not include just "commensurate with experience" as the only content? Actually the example filler includes "commensurate with experience". So we should avoid that phrase? But it's part of the actual posting; it's not filler? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests we should not include those phrases as the only content under a heading. But we can include them as part of content? It's ambiguous. Safer to rephrase to avoid that exact phrase? But we must preserve ALL substantive information; we cannot invent or summarize away detail. So we must keep the phrase "commensurate with experience and scope." That's part