Vice President of Procurement

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "The Opportunity", "Responsibilities", "Required Qualifications", "Additional Information" (salary, exempt, location, travel, openings, start date), "Interview Process", "Equal Opportunity Employer", "Reasonable Accommodation", etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove Equal Opportunity Employer, Reasonable Accommodation, maybe also "We love building our team directly! ..." as application instructions. Also remove "Interview Process" maybe? It's not a required heading but we could keep if it has substantive content. It lists steps: Recruiter Screen, First Interview - Director Procurement, Hiring Manager Interview - Chief People & Procurement Officer, Finance and/or Operations Interview, Conditional offer upon successful background check. That's substantive. Should we keep? The instruction: "Prefer a few substantive sections over many thin ones." Could keep Interview Process as a section if it's substantive. But we might combine into Responsibilities? Probably better to keep as separate section if it's substantive. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Interview Process has specific steps, so we can include. We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings? Probably we should stick to those headings where applicable. But we have sections like "Who We Are" maybe map to "About the role"? Actually "About the role" is typical. But we have "Who We Are" describing company. Could be "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can 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 where appropriate. For company description maybe "About the role" is not correct; maybe we can omit that section. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: Who We Are (company overview) maybe could be part of About the role? But About the role usually describes the role, not company. However we could treat "Who We Are" as "About the role"? Might be okay. But better to follow examples: we could have sections: About the role (maybe combine Who We Are and The Opportunity?), Responsibilities, Requirements (maybe Required Qualifications), Skills (maybe Technical Skills/Core Competencies), Benefits (maybe Additional Information includes salary, bonus, exempt status, travel, remote, openings, start date), Pay (salary range), Schedule (maybe travel requirements? Not exactly schedule). But we have travel requirements 5-10% and remote work location model. Could be Schedule? Not exactly. Could treat Schedule as work location/remote/travel. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range, bonus, exempt status, travel, remote, start date. So we can have Pay, Benefits, Schedule sections. We need to preserve all substantive information. Let's extract: Company description: Glass Roots Construction (GRC) is a first-class fiber optic utility construction firm founded by career telecom and construction professionals. We leverage the latest technologies and up-to-date construction practices to design and build high-performance networks that deliver fast, reliable connectivity for businesses, schools, and healthcare. At GRC, we believe that great infrastructure is built on two foundational commitments: Safety First: This is our #1 priority and a mutual commitment. We protect our team members, the public, and our customers' assets by prioritizing safety over production and ensuring every project is executed without shortcuts so everyone goes home safe. Quality & Excellence: We commit to excellence in every detail. By investing in our people, best-in-industry equipment, and processes, we deliver reliable, lasting work and exceptional, professional service for our customers. We are looking for people who take pride in their trade and want to help us lay the foundation for a safer, more connected future. The Opportunity: Glass Roots Construction (GRC) is seeking a strategic and results-driven VP of Procurement to own and scale our national supply chain and procurement operations. As we rapidly expand our fiber optic utility construction footprint, this role is critical to optimizing our cost structure and driving our bottom line. This role is for a seasoned executive who has built procurement functions from the ground up and is ready to lead the next phase: transforming spend consolidation, executing high-stakes negotiations, and ensuring a resilient supply chain. Working directly with executive leadership, you will set the operating standards, design the systems, and build the team that executes our procurement strategy accurately, efficiently, and at scale. This position reports to the CP&PO and offers an opportunity to join a strong, collaborative team at an early stage of growth, gain valuable experience, and contribute to the continued expansion of GRC. Responsibilities (list): - Strategic Sourcing & Cost Optimization * Architect and execute GRC's national procurement strategy end-to-end by building a centralized purchasing model that consolidates material and labor spend across all regions. * Drive bottom-line impact by proactively analyzing market trends, leveraging our collective scale, and utilizing internal usage data to deliver significant cost savings, improved pricing, and favorable terms. * Mitigate supply chain risks by anticipating market disruptions and ensuring contingency planning for critical materials to guarantee zero operational downtime. - Vendor Management & Operational Integration * Lead enterprise-level negotiations as the primary relationship manager for all key vendors and subcontractors, building high-value partnerships that prioritize reliability and competitive cost structures. * Act as a strategic partner to Finance and Operations leadership to seamlessly integrate and optimize procurement processes into day-to-day project workflows, balancing consistent execution with regional flexibility. - Compliance & Team Leadership * Hire, coach, and develop the Procurement team by building team capacity, setting clear goals, and holding a high bar for data-driven analysis, speed, and collaborative problem-solving. * Establish and enforce procurement compliance, internal financial controls, and enforce both contractual and risk management protocols (including contract language, insurance/COI compliance) to ensure audit-ready operations across all states. Required Qualifications (Education & Experience): - 10-15+ years of progressive procurement or supply chain leadership experience, with a track record of managing multi-million dollar spend portfolios. - Demonstrated experience building or significantly scaling a procurement function in a high-growth construction, utility, or infrastructure environment. - 5+ years directly managing, developing, and scaling procurement teams. - 1 year of construction experience. - Understanding of utility construction processes terminology, vendor and subcontractor dynamics is a plus Technical Skills: - Deep, hands-on expertise in enterprise ERP systems, procurement software, and data analytics tools to drive operational insights and reporting in order to drive process efficiency partnering with Financing, and Operations teams. Core Competencies: - Executive-level negotiation and contract management skills, with a proven ability to secure favorable, long-term terms. - Strong leadership judgment and financial acumen; able to influence C-suite stakeholders and build consensus. - Extreme attention to detail paired with the ability to move fast and keep operations flowing. Additional Information: - Salary Range: $180,000 - $210,000 per year, based on experience + 25% bonus - Exempt/Non-Exempt Status: This position is Exempt under the Fair Labor Standards Act (FLSA) and is not eligible for overtime pay. - Work Location Model: Remote - Travel Requirements: 5-10% - Role Openings: 1 - Target Start Date: 2-3 weeks from offer Interview Process: - Recruiter Screen - First Interview - Director Procurement - Hiring Manager Interview - Chief People & Procurement Officer - Finance and/or Operations Interview - Conditional offer upon successful background check We must remove boilerplate: Equal Opportunity Employer, Reasonable Accommodation, "We love building our team directly! At this time, we are only considering direct applications from candidates. We respectfully ask recruiting agencies not to reach out." Also duplicate salary line at end: "The Pay Range For This Role Is 180,000 - 210,000 USD per year(Remote)" - we already have salary range. We must not include Job ID/requisition numbers. Now decide sections to output. Use

for each section heading. We need to decide which headings to use from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (maybe combine Who We Are and The Opportunity). Responsibilities (list). Requirements (maybe Education & Experience). Qualifications (maybe Technical Skills + Core Competencies? Actually Qualifications could be Education & Experience; Skills could be Technical Skills; Core Competencies could be Skills? But we have both Technical Skills and Core Competencies. Could combine into Skills section. Or we could have Qualifications (Education & Experience) and Skills (Technical Skills + Core Competencies). Benefits: maybe we have none explicit besides salary? Actually benefits not listed besides salary and bonus. Could treat salary as Pay, benefits maybe none. But we have exempt status, work location, travel, openings, start date. Those could be Schedule? Not exactly. Schedule could be work location model and travel requirements? Might be okay. Pay: salary range + bonus. Schedule: Work Location Model: Remote; Travel Requirements: 5-10%; Target Start Date: 2-3 weeks from offer; Role Openings: 1 maybe not schedule. But we could also include a section "Details" but not in examples. However 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 suggests using those. Safer to stick to those. Thus we need to map content to these headings. About the role: combine Who We Are and The Opportunity. Responsibilities: as given. Requirements: Education & Experience (10-15+ years etc.) Qualifications: maybe Technical Skills? Actually Qualifications often includes education/experience; but we already used Requirements for that. Could swap: Requirements = Education & Experience; Qualifications = Technical Skills + Core Competencies. Or we could treat Requirements as both education/experience and technical skills, and Qualifications as core competencies. But we need to avoid thin sections. Let's think: we have enough content for each. Option: - About the role (company + opportunity) - Responsibilities - Requirements (Education & Experience) - Qualifications (Technical Skills + Core Competencies) - Benefits (maybe none, but we have salary? Actually salary is Pay) - Pay (Salary range + bonus) - Schedule (Work Location Model, Travel Requirements, Target Start Date, Role Openings) We must not create Benefits section unless posting actually states benefits. There's no explicit benefits like health insurance etc. So we should omit Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Check if any content left: Interview Process. Should we include? It's substantive. Could we add a section "Interview Process"? Not in examples but maybe allowed. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list