Vice President, Design & Construction - SL
Sodexo · Greenville, SC · 4 wk ago
Management$181k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Must remove boilerplate, navigation, legal, EEO, etc. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay Range: $181220 per year - $281380 per year, Incentive Eligibility: eligible to participate in Sodexo's incentive plan. So we have Pay info. Benefits: "What We Offer" includes benefits list: Medical, Dental, Vision Care and Wellness Programs, 401(k) Plan with Matching Contributions, Paid Time Off and Company Holidays, Career Growth Opportunities and Tuition Reimbursement. So Benefits section exists. Schedule: Not mentioned. So we should not include Schedule heading. Also "About the role" maybe we have "About The Job" and description. We'll create About the role section with prose. Responsibilities: many bullet points under "What’s In It For You" (actually that's responsibilities). Also bullet points under "What You’ll Bring" are requirements/skills. We need to separate: Responsibilities (duties), Requirements (education, experience), Qualifications (maybe overlapping), Skills (specific abilities). The posting includes "What You’ll Bring" which lists leadership & business acumen etc. That's skills and qualifications. Also "Education Requirement: Bachelor’s degree or equivalent experience Management Experience: 10 years Related Experience: 10 years". That's requirements. Also "Leadership & Business Acumen – Proven ability to develop and execute large-scale projects" etc. That's skills/qualifications.
We need to decide sections: About the role (intro), Responsibilities (list of duties), Requirements (education, experience), Qualifications (maybe combine with Requirements? But we can separate: Qualifications could be education/experience; Skills could be leadership etc). However we must not create thin sections. Perhaps combine Requirements and Qualifications into one? But rules: Use headings for those specific names if we have content. We can include both if we have distinct content. Let's extract:
About the role: The first paragraph(s) describing role: "At Sodexo Live!, we take pride...". Also "A client-facing executive responsible for leading design, construction, purchasing & capital development initiatives across Sodexo Live! The role manages multiple projects from concept and design through construction and opening". Also "The Vice President, design & construction Sodexo Live! Sports & Leisure North America is the leading role providing strategic and operational leadership...". That's about role.
Responsibilities: bullet list from "What’s In It For You": Act as a solution designer..., Assess the needs..., Build capital projects..., Actively lead the construction..., Lead the Facility Designer..., Oversee the installations..., Ensure consistency..., Provide expertise..., Ensure consistent robust management..., Ensure that the design..., Manage team’s performance..., Lead safety and quality..., Monitor and ensure...
Also maybe other responsibilities like "Provides strategic vision and direction, leading organization or its business function." etc from earlier paragraph. Those are also responsibilities.
Requirements: Education Requirement: Bachelor’s degree or equivalent experience; Management Experience: 10 years; Related Experience: 10 years.
Qualifications: maybe same as requirements? Could treat as "Qualifications" heading for education/experience. But we already have Requirements. Could combine? The instruction: Use headings for those specific names if we have content. It didn't forbid having both Requirements and Qualifications if content distinct. We could put education/experience under Requirements, and under Qualifications put "Proven ability to develop and execute large-scale projects", etc. But those are more skills. Actually "What You’ll Bring" includes leadership & business acumen etc. That's skills. So we can put Skills section for those bullet points. Qualifications could be education/experience. But we already have Requirements for education/experience. Might be redundant. Perhaps better: Requirements = education/experience; Qualifications = leadership & business acumen etc; Skills = specific abilities like project management systems, analytic skills, financial management, etc. However the posting lumps many together.
We need to avoid thin sections. Let's see if we can make three substantive sections: About the role, Responsibilities, Requirements & Qualifications (combined), Benefits, Pay. But we must use specific headings; we cannot create custom headings. So we need to map content to allowed headings. If we combine, we could put all under Requirements (or Qualifications) but then we lose some headings. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit headings if content is thin. But we must include a section only when posting has real specific content for it. So we can decide to include About the role, Responsibilities, Requirements (education/experience), Skills (leadership etc), Benefits, Pay. That's six sections. Are any thin? Let's evaluate each.
About the role: we have several paragraphs -> substantive.
Responsibilities: we have many bullet points -> substantive.
Requirements: education/experience -> substantive (three lines).
Skills: we have leadership & business acumen, client & stakeholder management, organizational, presentation, public speaking, written and interpersonal skills, proficiency with project management systems, strong analytic skills, management/ownership of department financials, ability to motivate and influence, ability to promote team environment, excellent people leadership skills, creative mindset. That's substantive.
Benefits: list of benefits -> substantive.
Pay: pay range and incentive eligibility -> substantive.
We should not include Schedule (no content). Also Qualifications maybe we skip because we used Skills and Requirements. But we could also include Qualifications if we want to separate education/experience from skills. However we already have Requirements for education/experience; Qualifications could be something else like "Proven ability to develop and execute large-scale projects" but that's also skill. To avoid duplication, we can omit Qualifications heading.
Thus output HTML with sections:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Must remove boilerplate, navigation, legal, EEO, etc. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay Range: $181220 per year - $281380 per year, Incentive Eligibility: eligible to participate in Sodexo's incentive plan. So we have Pay info. Benefits: "What We Offer" includes benefits list: Medical, Dental, Vision Care and Wellness Programs, 401(k) Plan with Matching Contributions, Paid Time Off and Company Holidays, Career Growth Opportunities and Tuition Reimbursement. So Benefits section exists. Schedule: Not mentioned. So we should not include Schedule heading. Also "About the role" maybe we have "About The Job" and description. We'll create About the role section with prose. Responsibilities: many bullet points under "What’s In It For You" (actually that's responsibilities). Also bullet points under "What You’ll Bring" are requirements/skills. We need to separate: Responsibilities (duties), Requirements (education, experience), Qualifications (maybe overlapping), Skills (specific abilities). The posting includes "What You’ll Bring" which lists leadership & business acumen etc. That's skills and qualifications. Also "Education Requirement: Bachelor’s degree or equivalent experience Management Experience: 10 years Related Experience: 10 years". That's requirements. Also "Leadership & Business Acumen – Proven ability to develop and execute large-scale projects" etc. That's skills/qualifications.
We need to decide sections: About the role (intro), Responsibilities (list of duties), Requirements (education, experience), Qualifications (maybe combine with Requirements? But we can separate: Qualifications could be education/experience; Skills could be leadership etc). However we must not create thin sections. Perhaps combine Requirements and Qualifications into one? But rules: Use headings for those specific names if we have content. We can include both if we have distinct content. Let's extract:
About the role: The first paragraph(s) describing role: "At Sodexo Live!, we take pride...". Also "A client-facing executive responsible for leading design, construction, purchasing & capital development initiatives across Sodexo Live! The role manages multiple projects from concept and design through construction and opening". Also "The Vice President, design & construction Sodexo Live! Sports & Leisure North America is the leading role providing strategic and operational leadership...". That's about role.
Responsibilities: bullet list from "What’s In It For You": Act as a solution designer..., Assess the needs..., Build capital projects..., Actively lead the construction..., Lead the Facility Designer..., Oversee the installations..., Ensure consistency..., Provide expertise..., Ensure consistent robust management..., Ensure that the design..., Manage team’s performance..., Lead safety and quality..., Monitor and ensure...
Also maybe other responsibilities like "Provides strategic vision and direction, leading organization or its business function." etc from earlier paragraph. Those are also responsibilities.
Requirements: Education Requirement: Bachelor’s degree or equivalent experience; Management Experience: 10 years; Related Experience: 10 years.
Qualifications: maybe same as requirements? Could treat as "Qualifications" heading for education/experience. But we already have Requirements. Could combine? The instruction: Use headings for those specific names if we have content. It didn't forbid having both Requirements and Qualifications if content distinct. We could put education/experience under Requirements, and under Qualifications put "Proven ability to develop and execute large-scale projects", etc. But those are more skills. Actually "What You’ll Bring" includes leadership & business acumen etc. That's skills. So we can put Skills section for those bullet points. Qualifications could be education/experience. But we already have Requirements for education/experience. Might be redundant. Perhaps better: Requirements = education/experience; Qualifications = leadership & business acumen etc; Skills = specific abilities like project management systems, analytic skills, financial management, etc. However the posting lumps many together.
We need to avoid thin sections. Let's see if we can make three substantive sections: About the role, Responsibilities, Requirements & Qualifications (combined), Benefits, Pay. But we must use specific headings; we cannot create custom headings. So we need to map content to allowed headings. If we combine, we could put all under Requirements (or Qualifications) but then we lose some headings. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit headings if content is thin. But we must include a section only when posting has real specific content for it. So we can decide to include About the role, Responsibilities, Requirements (education/experience), Skills (leadership etc), Benefits, Pay. That's six sections. Are any thin? Let's evaluate each.
About the role: we have several paragraphs -> substantive.
Responsibilities: we have many bullet points -> substantive.
Requirements: education/experience -> substantive (three lines).
Skills: we have leadership & business acumen, client & stakeholder management, organizational, presentation, public speaking, written and interpersonal skills, proficiency with project management systems, strong analytic skills, management/ownership of department financials, ability to motivate and influence, ability to promote team environment, excellent people leadership skills, creative mindset. That's substantive.
Benefits: list of benefits -> substantive.
Pay: pay range and incentive eligibility -> substantive.
We should not include Schedule (no content). Also Qualifications maybe we skip because we used Skills and Requirements. But we could also include Qualifications if we want to separate education/experience from skills. However we already have Requirements for education/experience; Qualifications could be something else like "Proven ability to develop and execute large-scale projects" but that's also skill. To avoid duplication, we can omit Qualifications heading.
Thus output HTML with sections: About the role
...
thenResponsibilities
- ...