Vice President, Delivery

We need to output HTML fragment with sections: About the role? Actually the posting includes "The Company" description, "The Position", "Key Responsibilities", "The Details", "Must-Have Qualifications", "Preferred Qualifications", "This Might Be Right For You If", "WHY STACK?" plus benefits etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: could be "The Position" description (the paragraph about Vice President, Delivery). That's substantive. - Responsibilities: "Key Responsibilities" list. - Requirements/Qualifications: Must-Have Qualifications and Preferred Qualifications. Could combine into Requirements? But we have separate headings: Requirements, Qualifications, Skills. We need to decide. Probably "Requirements" for must-have qualifications, "Preferred Qualifications" maybe as "Qualifications" or "Skills". But we need to avoid filler. We'll include sections: Responsibilities, Requirements (must-have), Qualifications (preferred), Skills (maybe technical skills?), Benefits (WHY STACK? includes benefits), Pay (not mentioned), Schedule (not mentioned). So we omit Pay and Schedule. Also we have location, onsite/wfh, travel, eligibility, background screening - these could be part of "Details". Could be placed under a section like "Details" but not in prescribed headings. 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? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. For location etc maybe we can put under About the role? Or maybe we can include a short

for metadata (like location) not as heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location etc as a short

after the About the role maybe. Thus structure:

About the role

... description of Vice President, Delivery ... plus maybe location etc as separate

after? Actually location is minor metadata, we can fold into a short

. Then

Responsibilities

• ... each responsibility ...

Then

Requirements

• ... must-have qualifications ...

Then

Qualifications

• ... preferred qualifications ...

Then

Skills

Maybe we can list technical skills from must-have? But we already have them in Requirements. Could also list skills like communication, leadership etc. But to avoid duplication, maybe we can skip Skills if no distinct content. However we need to include a section only when posting has real specific content. The posting does mention skills like "Excellent written and verbal communication and presentation skills", "Ability to prioritize, delegate", etc. Those could be considered Skills. But they are also in Requirements. Might be okay to have Skills section with those items. But we must not invent or summarize away detail. We need to preserve all substantive information. So we need to ensure we don't lose any info. If we split must-have into Requirements and Skills, we need to ensure we cover all must-have items. Could categorize: Requirements: education, experience, eligibility, background, etc. Skills: technical skills, soft skills. But risk of missing some. Better: Keep Requirements for must-have qualifications (including education, experience, etc). Keep Skills for technical and soft skills listed (like mastery of tools, financial acumen, communication, etc). Keep Qualifications for preferred qualifications. Thus we need to parse must-have qualifications list: - Demonstrated experience leading multiple large-scale, fast-moving data center construction projects or programs across a regional or national portfolio - Strong leadership skills, high emotional intelligence, and a proven record of leading, mentoring, and developing highly collaborative, high-performing teams - Proven ability to identify issues early, establish accountability, and drive timely resolution across organizational boundaries - Client-facing and team leadership experience required - Mastery of the tools of the trade (AIA Contracts, Construction Schedules, Budgets & Schedules of Values, Payment Applications, Lien Releases, Subcontracts, Purchase Orders, Invoices, Vendor Agreements, Construction Insurance types, etc.) - Expert-level proficiency with the Microsoft Office Suite, particularly Excel (also Word, PowerPoint, Outlook, SharePoint, OneNote, Project) - Knowledge and competency with Bluebeam and BIM platforms is a plus - Excellent financial acumen (familiarity with NetSuite preferred, but not required) - Exceptional Data Center technical knowledge, including OFCI/CFCI equipment, procurement strategies and lead times, Owner-direct vendors, lender requirements, etc. - Rigorous attention to detail, precision and accuracy, particularly in financial matters, budgets, cost projections, etc. - Excellent written and verbal communication and presentation skills, externally with Clients and across all levels of the organization including the Executive level - Ability to prioritize, delegate and stay focused under high levels of pressure, manage multiple competing priorities and adapt to constantly changing requirements; strong organizational skills are a must - Positive, can-do attitude and team player - Minimum of a bachelor’s degree from an accredited four-year college or university in Construction Management, Engineering, Architecture, Business Management, or a related field. Also eligibility: Must be eligible to work in the United States, Must pass comprehensive background screening. Those could be in Requirements as well. We'll split: Requirements: education, eligibility, background screening, experience leading projects, leadership, client-facing, ability to identify issues, etc. Skills: mastery of tools, MS Office, Bluebeam/BIM, financial acumen, data center technical knowledge, attention to detail, communication, prioritization, attitude. But we need to ensure we don't lose any. Let's list all must-have items and assign. I'll create two lists: Requirements (education, eligibility, background, experience, leadership, client-facing, issue identification, positive attitude maybe?). Skills: tools mastery, MS Office, Bluebeam/BIM, financial acumen, data center technical knowledge, attention to detail, communication, prioritization/delegate, positive attitude? Actually attitude already in must-have; could be in Skills as soft skill. But we need to avoid duplication. Might be simpler: Keep Requirements for all must-have qualifications (including skills). Then we can omit Skills section if no distinct content beyond that. However the instruction says prefer a few substantive sections over many thin ones. So we could have just Requirements covering all must-have. Then Qualifications for preferred. Benefits for WHY STACK? (benefits). Responsibilities for Key Responsibilities. About the role for The Position description plus location etc. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to ensure we don't include Pay or Schedule. Now we need to extract all substantive content and preserve. Let's gather: About the role: The paragraph starting "The Position The Vice President, Delivery is an essential partner..." plus maybe the preceding company description? The company description is also substantive but maybe belongs to About the role? Could be included as part of About the role. The instruction: "About the role" heading for section headings e.g. About the role, Responsibilities... So we can put company overview and role description under About the role. Thus About the role content: - Company description: "The Company STACK INFRASTRUCTURE (STACK) provides digital infrastructure to scale the world’s most innovative companies. We are an award-winning industry leader in building, owning, and operating highly efficient, cost-effective wholesale, colocation, and cloud data centers. Each of our national facilities meets or exceeds the highest industry standards in all operational categories of availability, security, connectivity, and physical resilience. STACK offers the scale and geographic reach that rapidly growing hyperscale and enterprise companies need. The world runs on data. Data runs on STACK." - Role description: "The Position The Vice President, Delivery is an essential partner to the Senior VP of Construction, helping translate STACK’s high-intensity growth strategy and commercial pipeline into coordinated, executable data center delivery plans. In addition to overseeing construction project delivery and execution, the role leads strategic and tactical initiatives spanning business operations, investor and Senior Leadership Team engagement, pre-leasing support, pipeline planning, and delivery readiness. Operating across Construction, Development, Preconstruction, Sales, Finance, Operations, and other enterprise functions, the Vice President, Delivery strengthens organizational alignment, ensures emerging opportunities are effectively evaluated, and prepares delivery teams to execute; driving accelerated, more predictable and consistent portfolio outcomes. The ideal candidate is comfortable operating at both strategic and detailed levels, translating complex data center delivery and construction information into clear recommendations for investors and senior leaders while working directly with teams to identify risks, remove roadblocks, and establish actionable plans. Success requires exceptional and fast-paced communication and problem solving, sound business judgement, strong industry knowledge, organizational discipline, attention to details, and thorough understanding of how STACK operates as an enterprise. The Vice President, Delivery must be a highly effective connector who can influence across organizational boundaries, create clarity in ambiguous situations, and demonstrate the resilience, creativity, persistence, and relentless commitment to follow-through needed to advance STACK’s Data Center Construction portfolio." We can combine into a few paragraphs. Now Responsibilities: list from "Key Responsibilities" bullet points. Need to preserve each bullet as

. The bullet points are sentences starting with verbs. We'll extract each. Let's list them: - Coordinate with the SVP of Construction and internal and external recruitment staff to support the rapid growth and expansion of the Construction Team - Lead and support a culture of safety, quality, collaboration and professionalism - Regional Construction Project and Portfolio Responsibilities include: - Own the Owner Budget(s) Template and secure approvals for regular updates and improvements. - Partner with STACK IT & Preconstruction in the effort to shift from Excel-based budget spreadsheets to a more reliable software platform, such as Procore - Maintain accountability for the Project Owner Budget(s) in the region, ensuring accurate and timely updates through to completion - Provide high-level direction to the GC, Owner vendors and other trade partners, either directly or through regional project teams - Lead and support project teams in leading the GC RFP process, including proposals, bidding, leveling sheets, recommendations and presentations to leadership - Maintain accountability for design, permits and entitlements phase, ensuring the team is empowered to implement an efficient and expedient process - Review and negotiate Construction Schedules from GCs and Owner-direct vendors, as required, and prepare/present schedule overviews - Maintain accountability for GC Contract Negotiations and Administration, including coordination with STACK Legal - Lead high-tempo business operations initiatives that improve delivery governance, organizational scalability, cross-functional coordination, and portfolio performance. - Provide delivery focused input into commercial strategies, proposals, customer commitments, lease requirements, project assumptions, preliminary schedules, budgets, and execution plans - Maintain an integrated view of STACK’s development and delivery pipeline, including anticipated project timing, sequencing, interdependencies, resource demands, and execution constraints. - Develop scenarios and recommendations to support pipeline prioritization, resource allocation, capital planning, procurement strategy, and capacity decisions. - Lead the consistent delivery-readiness process that evaluates scope, budget, schedule, design, permitting, contracting strategy, resource capacity, and operational requirements as projects advances towards execution - Anticipate senior leadership and investor questions and ensure that delivery teams are prepared with the appropriate analysis, context, and recommendations - Collaborate successfully with other STACK teams, including Strategy, Sales