EVP of Pipeline of Construction

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Job Summary (which could be About the role). It includes Key Responsibilities (Responsibilities). It includes Education & Experience (Qualifications/Requirements). It includes Licenses & Certifications (maybe part of Requirements). It includes Technical & Physical Skills (Skills). It includes Work Environment & Physical Demands (maybe part of Skills or separate? Not a required heading; we could include under Skills or maybe not create a new heading). There's no explicit Benefits, Pay, Schedule. So we should not create those sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. There's no cookie/navigation etc. We need to decide which headings to include: About the role (from Job Summary), Responsibilities (Key Responsibilities), Requirements (maybe Education & Experience + Licenses & Certifications), Qualifications (maybe same as Requirements? Could combine). But we need to avoid duplicate sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Education & Experience and Licenses & Certifications into a single "Requirements" section. Or we could have "Qualifications" for education/experience and "Skills" for technical/physical skills. Let's map: - About the role: Job Summary paragraph(s). - Responsibilities: Key Responsibilities (multiple bullet points). We'll need to turn each responsibility into

• . - Requirements: Education & Experience (bullets) plus Licenses & Certifications (maybe bullet). Could combine. - Skills: Technical & Physical Skills (list) plus maybe the Skills section (Strategic & Systems Thinking etc.) Actually there is a "Skills" section after Work Environment & Physical Demands that lists many skill categories. That seems like a skills section. So we have two skill-related sections: Technical & Physical Skills (specific abilities) and then a "Skills" list (Strategic & Systems Thinking etc.). We could combine them under Skills heading. Thus we have sections: About the role, Responsibilities, Requirements, Skills. We must not include Benefits, Pay, Schedule. Now we need to extract content. Job Summary paragraph: "The EVP Pipeline and Construction is responsible for building and leading an integrated, high-performing operating platform that connects acquisitions, development, asset management and construction functions. This role owns the performance of the enterprise's "pipeline", the end-to-end integrity of approximately 15 deals per year, from acquisition through development, construction, lease-up, and stabilized operations. As the senior executive accountable for cross-functional execution, the EVP allocates resources and resolves conflict across business units, bringing an owner's mindset to risk and reward. Success is defined by predictable growth, operational excellence in construction, clean project stabilization, operating teams prepared to scale, and business unit objectives coordinated in service of long-term portfolio performance while exemplifying Evergreen’s core values. The EVP Pipeline and Construction is successful when the enterprise grows predictably, projects stabilize cleanly, and business unit objectives are coordinated in service of long-term performance." We can keep as

  . Key Responsibilities: It's a long list with headings like Executive Leadership, Pipeline Leadership & Execution, EOS Leadership & Organization Alignment, Cross-Functional Integration, Operational Excellence & Process Standardization, Leadership & Team Development. Each has multiple bullet-like sentences. We need to turn each duty into

• . We should preserve all substantive information; we can break each sentence into separate
• . However we must not lose any detail. Could group under subheadings? But we only allowed

  for section headings; we could still include

  ?? Not specified; only said use

  for section headings. It didn't forbid other headings, but to be safe we can just use

  for each responsibility sentence, maybe grouping under

  Responsibilities and then

  with
  • items. We'll need to parse the responsibilities text. Let's extract responsibilities: Executive Leadership - Partner with the CEO’s direct reports as the executive leadership team translating vision into execution and provide candid feedback on feasibility, capacity, and trade-offs. - Build the infrastructure required to scale consistently and reliably in to the 10-year vision, handling increasing deal volume without loss of execution quality. - Represent the Pipeline business to the board and other external stakeholders as requested by the CEO. Pipeline Leadership & Execution - Ensure the heads of Development, Acquisitions, Construction, and Asset Management, are clear on expectations and have the tools to succeed. - Drive the team to achieve the EOS V/TO goals, scaling construction and development operations to meet annual delivery targets of 15-20 projects. - Own the full lifecycle of projects from deal identification through stabilized operations - Translate CEO-level growth objectives into executable plans - Ensure that pipeline decisions reflect full lifecycle economics, not deal-level optimization. - Ensure each project is delivered on time, on budget, to quality standards, and achieve timely stabilization. - Ensure development supports long-term operational efficiency and asset performance - Ensure assets meet or exceed underwriting projections - Design and enforce a standardized stage-gate process: contract, due diligence, entitlement/construction, stabilization, and handoff applied uniformly across all four development teams, with clear "definition of done" criteria required to advance at each gate - Standardize LPA agreement terms, reporting formats, and information-sharing protocols across acquisitions, development, senior housing, and West Serve as a second set of eyes on active deals, reviewing progress and flagging risk early to prevent costly gaps - Own handoff execution between development, construction, and asset management, eliminating communication breakdowns at stage transitions - Lead recurring cross-functional pipeline reviews to surface stalled deals and drive resolution - Build and maintain a shared system of record / dashboard providing real-time deal status visibility to the CEO, developers, construction, and asset management - Oversee the transition of stabilized properties to property management, ensuring clean data and knowledge transfer - Direct resource allocation and conflict resolution to keep progress on track EOS Leadership & Organization Alignment - Ensure EOS implementation and ongoing execution through the 6 Key Components - Facilitate Level 10 (L10) leadership meetings - Drive accountability through scorecards, Rocks, and measurable outcomes - Lead quarterly and annual planning processes Cross-Functional Integration - Align acquisitions, development, and construction teams on underwriting assumptions, scope, and execution plans - Ensure structured transition protocols exist from construction completion through stabilization. - Eliminate silos and drive collaboration across departments Operational Excellence & Process Standardization - Ensure SOPs exist where needed and are consistently enforced. - Ensure the organization has real-time visibility into budgets, timelines, and performance. - Drive continuous improvement Leadership & Team Development - Lead by living out our Core Values and expect the same from others - Establish clear roles, responsibilities, and performance expectations - Build a culture of accountability, execution, and collaboration - Address and solve organizational challenges quickly and decisively Now Education & Experience: - Bachelor’s degree in Real Estate, Business Administration, Construction Management, or related field required - Master’s degree (MBA or related) preferred - 10–15+ years of experience in real estate operations, with significant exposure to: - Real Estate Development - Multifamily construction - Property and asset management - Proven track record of scaling operations and managing high project volume - Experience implementing and leading EOS or similar operating systems preferred - Deep understanding of the full real estate lifecycle - Strong leadership and organizational design experience - Experience implementing systems, processes, and performance management frameworks - Proven track record of assembling and leading successful teams - Work experience with EOS a plus Licenses & Certifications: - Valid driver’s license required Technical & Physical Skills: - Advanced proficiency in project management, financial analysis, and performance tracking systems - Ability to interpret financial statements, budgets, and operational KPIs - Excellent communication and cross-functional collaboration skills - Ability to operate effectively in a fast-paced, high-growth environment Skills (the later list): - Strategic & Systems Thinking – Designs and implements scalable operating systems that support portfolio growth and long-term performance - Operational Execution & Accountability – Drives disciplined execution, ensuring projects are delivered on time, on budget, and to standard - Cross-Functional Leadership – Aligns teams across acquisitions, development, construction, asset management, and property management to operate as one cohesive platform - EOS Leadership & Organizational Discipline – Leads with clarity and accountability using EOS tools, including Rocks, scorecards, and structured planning - Financial & Performance Acumen – Uses data, KPIs, and financial insights to drive asset performance, improve NOI, and inform strategic decisions - Leadership & Talent Development – Builds and develops high-performing teams; sets clear expectations, coaches effectively, and holds leaders accountable - Change Management & Continuous Improvement – Leads organizational change; identifies inefficiencies, removes bottlenecks, and continuously improves systems, processes, and performance Work Environment & Physical Demands: - This position is primarily based in a professional office environment with a mix of on-site and remote work, as business needs require - Ability to sit, stand, and work at a computer for extended periods of time - May require occasional lifting of up to 15–20 pounds (e.g., files, materials, or equipment) - Occasional travel to property sites, development projects, and construction locations - Ability to walk properties and construction sites, with stairs and uneven terrain We could include Work Environment & Physical Demands under Skills or as its own section? Not a standard heading; we could incorporate into Skills or maybe omit as not required heading. But we need to preserve all substantive information. Could add a section "Work Environment" but not in allowed headings list. 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

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings. So we should not create other headings like Work Environment. We could incorporate those details into Skills section as additional bullet points. Thus Skills section will include both Technical & Physical Skills and the Skills list and Work Environment & Physical Demands. Now we need to output HTML fragment only. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...
    We must not repeat job title as heading. Already not. We need to ensure we preserve all substantive information. Let's craft each
  • exactly as sentences. For Responsibilities, we need to break each bullet into separate
  • . Ensure we keep the exact wording. Let's list them: Executive Leadership: 1. Partner with the CEO’s direct reports as the executive leadership team translating vision into execution and provide candid feedback on feasibility, capacity, and trade-offs. 2. Build the infrastructure required to scale consistently and reliably in to the 10-year vision, handling increasing deal volume without loss of execution quality. 3. Represent the Pipeline business to the board and other external stakeholders as requested by the CEO. Pipeline Leadership & Execution: 4. Ensure the heads of Development, Acquisitions, Construction, and Asset Management, are clear on expectations and have the tools to succeed. 5. Drive the team to achieve the EOS V/TO goals, scaling construction and development operations to meet annual delivery targets of 15-20 projects. 6. Own the full lifecycle of projects from deal identification through stabilized operations 7. Translate CEO-level growth objectives into executable plans