Manager, Foodservice Sourcing
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate.
We need to decide which sections to include.
We have content: "What you will be doing:" description (prose). Could be under "About the role" or "Responsibilities". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (intro), Responsibilities (list), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe list of skills), Benefits, Pay, Schedule (maybe travel). Also maybe Working Conditions (but not in list of allowed headings; but we could incorporate into Schedule? Not exactly. The allowed headings list is examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those.
Thus:
- About the role: prose summarizing what you will be doing (the initial paragraph). Could include the description of managing contracting life cycle etc.
- Responsibilities: list of duties from "Key Responsibilities" sections (Project Management, Process Execution, Strategic/Administrative, Quality Control). Could break into bullet points.
- Requirements: maybe Required Qualifications (Work Experience, Education). Could also include Additional Job Requirements (like stationary position, adaptability, etc.) but those might be more like "Requirements". We'll include them under Requirements.
- Qualifications: Preferred Qualifications (skills, experience, education). Could be separate.
- Skills: maybe list of skills from Preferred Qualifications: Food Service Program Operations, Data Analytics, Account management, Supply Chain Management, Negotiation, Project Management, etc.
- Benefits: list of benefits: Health, dental, vision, life and disability insurance, 401k retirement program, Paid time off, Participation in Premier’s employee incentive plans, Tuition reimbursement and professional development opportunities, Perks and discounts, Access to on-site and online exercise classes.
- Pay: salary range $90,000 - $150,000.
- Schedule: maybe travel requirements (Travel 1-20% within the US) and maybe remote? Also Working Conditions: Remote? Actually says Remote Travel Requirements: Travel 1-20% within the US. Also Working Conditions: maybe not needed. Could include schedule: maybe "Remote" not given; but we have travel. Could put under Schedule: Travel 1-20% within the US.
We must not include boilerplate like EEO, awards, Premier at a glance, etc. Also remove duplicated lines.
We must preserve all substantive information. So we need to include the details from "What you will be doing:" paragraph, the responsibilities bullet points, required qualifications, preferred qualifications, skills, additional job requirements, working conditions? Actually "Additional Job Requirements" includes things like remain stationary, adaptable, attention to detail, operate computer programs, communicate effectively, day-to-day contact, independent decisions, collaborative environment. Those are substantive; we should include them somewhere, maybe under Requirements or Qualifications. Since we have Requirements section for required qualifications, we can include those there.
Also "Working Conditions: Remote Travel Requirements: Travel 1-20% within the US Physical Demands: Sedentary..." This is substantive; we could include under Schedule (travel) and maybe a separate section? But we only have allowed headings; maybe we can include travel under Schedule, and physical demands maybe under Requirements? Not ideal but we need to include all substantive info. Could add a section "Working Conditions" but not in allowed list; but 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 ...)". Likely they expect those headings; but we could still add other headings if needed. However to be safe, we can map physical demands to Requirements or maybe a separate "Working Conditions" but risk being considered extra. I think we can include a "Working Conditions" section as it's substantive; the instruction didn't forbid other headings, just gave examples. So we can include.
But we must not include boilerplate like awards, Premier at a glance, EEO, etc.
Now produce HTML fragment.
Structure:
About the role
... (the "What you will be doing:" paragraph)
Responsibilities
- Project Management – 30%: ... (list of bullet points from that subsection)
- Process Execution – 30%: ...
- Strategic / Administrative – 20%: ...
- Quality Control – 20%: ...
But we need to preserve all details; we could break each responsibility into separate - items. However the instruction: use
- for any list of duties/requirements/benefits. So we can have a list of duties; each duty can be a sentence. Could combine the subheadings as part of each
- . Eg:
- Project Management – 30%: Develops and manages workplans and monitor necessary timelines; Uses contract calendar and project workplans to properly allocate resources to projects and tasks; Prioritizes and systematically organize the team's efforts around project scope and objectives; Ensures scope is clearly defined and validated continuously; Adheres to / adjusts the milestones and cycle times outlined in product category workplan; Coaches team members in prioritizing tasks and handling daily work challenges; Delegates decision-making authority and task responsibilities to appropriate subordinates: utilizing subordinates’ time, skills, and potential effectively; Develops and review project status reports which outline project accomplishments, issues and timelines; Sets up ongoing procedures for collection and review of information necessary for the management of projects or an organization; Reviews and approves deliverables. Reviews work of team members for accuracy; Identifies and resolves project issues; Defines critical issues for risk management with clients and manages clients' expectations related to these areas; Participates in Product Planning and Contract Management sourcing meetings to ensure a seamless integration throughout the Product Planning, Contract Negotiation and Contract Management processes.
Similarly for Process Execution, Strategic/Admin, Quality Control.
Alternatively we could break each bullet into separate - but that may be too granular but still okay. The instruction didn't forbid splitting. I'd keep each major bullet as a
- with sub-detail separated by semicolons.
Requirements
Required Qualifications:
- Work Experience: 5 or more years of applicable experience
- Education: High School Diploma or GED (Required)
Additional Job Requirements:
- Remain in a stationary position for prolonged periods of time
- Be adaptive and change priorities quickly; meet deadlines
- Attention to detail
- Operate computer programs and software
- Ability to communicate effectively with audiences in person and in electronic formats
- Day-to-day contact with others (co-workers and/or the public)
- Making independent decisions
- Ability to work in a collaborative business environment in close quarters with peers and varying interruptions
But we need to preserve all substantive info; we could combine into one list under Requirements.
Qualifications
Preferred Qualifications:
- Skills: Food Service Program Operations, Data Analytics, Account management, Supply Chain Management, Negotiation, Project Management
- Experience: Experience in foodservice operations, administration, marketing, purchasing/category management, and/or sales with strong product knowledge; Contract/account management in with diverse and vast contracts; Demonstrated analytical experience managing and interpreting contract related data (large data sets) and presenting results; Experience leading cross-functional projects
- Education: Bachelor's degree
But we also have a separate Skills section maybe. However we already listed skills under Preferred Qualifications. Could separate Skills section: list of skills.
Better to follow the allowed headings: Skills separate.
Thus:
Skills
- Food Service Program Operations
- Data Analytics
- Account management
- Supply Chain Management
- Negotiation
- Project Management
Then Qualifications could be for education and experience preferences.
But we need to avoid duplication. Let's decide:
- About the role: intro paragraph.
- Responsibilities: list of duties (from Key Responsibilities).
- Requirements: Required Qualifications + Additional Job Requirements (maybe combined).
- Qualifications: Preferred Qualifications (education, experience).
- Skills: list of skills (Food Service Program Operations, Data Analytics, Account management, Supply Chain Management, Negotiation, Project Management).
- Benefits: list of benefits.
- Pay: salary range.
- Schedule: travel requirements (Travel 1-20% within the US) and maybe remote? Not given remote; but we could note "Remote" not specified; but we shouldn't add filler. So just travel.
We also have Physical Demands and Working Conditions (Remote Travel Requirements). Could include under Schedule as well: "Travel 1-20% within the US; Sedentary work: exerting up to 10 pounds of force occasionally...". That is substantive.
Thus Schedule section includes travel and physical demands.
Now we need to ensure we don't include boilerplate like "Premier’s compensation philosophy is to ensure that compensation is reasonable, equitable, and competitive..." We can keep the salary range sentence but maybe we can keep the sentence about compensation philosophy? It's substantive but maybe considered boilerplate? It's about compensation philosophy; could be considered filler but it's actual statement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation philosophy is not boilerplate; it's part of the posting. We could keep it but we already have Pay section with salary range; we could include the philosophy as a under Pay.
But we must not include "Premier utilizes a wide-range salary structure to allow base salary flexibility within our ranges." That's also part of compensation description; could keep.
But we need to avoid duplication.
Let's extract the Pay-related sentences:
"Premier’s compensation philosophy is to ensure that compensation is reasonable, equitable, and competitive in order to attract and retain talented and highly skilled employees. Premier’s internal salary range for this role is $90,000 - $150,000. Final salary is dependent upon several market factors including, but not limited to, departmental budgets, internal equity, education, unique skills/experience, and geographic location. Premier utilizes a wide-range salary structure to allow base salary flexibility within our ranges."
We can keep all
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate. We need to decide which sections to include. We have content: "What you will be doing:" description (prose). Could be under "About the role" or "Responsibilities". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (intro), Responsibilities (list), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe list of skills), Benefits, Pay, Schedule (maybe travel). Also maybe Working Conditions (but not in list of allowed headings; but we could incorporate into Schedule? Not exactly. The allowed headings list is examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those.
Thus:
- About the role: prose summarizing what you will be doing (the initial paragraph). Could include the description of managing contracting life cycle etc.
- Responsibilities: list of duties from "Key Responsibilities" sections (Project Management, Process Execution, Strategic/Administrative, Quality Control). Could break into bullet points.
- Requirements: maybe Required Qualifications (Work Experience, Education). Could also include Additional Job Requirements (like stationary position, adaptability, etc.) but those might be more like "Requirements". We'll include them under Requirements.
- Qualifications: Preferred Qualifications (skills, experience, education). Could be separate.
- Skills: maybe list of skills from Preferred Qualifications: Food Service Program Operations, Data Analytics, Account management, Supply Chain Management, Negotiation, Project Management, etc.
- Benefits: list of benefits: Health, dental, vision, life and disability insurance, 401k retirement program, Paid time off, Participation in Premier’s employee incentive plans, Tuition reimbursement and professional development opportunities, Perks and discounts, Access to on-site and online exercise classes.
- Pay: salary range $90,000 - $150,000.
- Schedule: maybe travel requirements (Travel 1-20% within the US) and maybe remote? Also Working Conditions: Remote? Actually says Remote Travel Requirements: Travel 1-20% within the US. Also Working Conditions: maybe not needed. Could include schedule: maybe "Remote" not given; but we have travel. Could put under Schedule: Travel 1-20% within the US.
We must not include boilerplate like EEO, awards, Premier at a glance, etc. Also remove duplicated lines.
We must preserve all substantive information. So we need to include the details from "What you will be doing:" paragraph, the responsibilities bullet points, required qualifications, preferred qualifications, skills, additional job requirements, working conditions? Actually "Additional Job Requirements" includes things like remain stationary, adaptable, attention to detail, operate computer programs, communicate effectively, day-to-day contact, independent decisions, collaborative environment. Those are substantive; we should include them somewhere, maybe under Requirements or Qualifications. Since we have Requirements section for required qualifications, we can include those there.
Also "Working Conditions: Remote Travel Requirements: Travel 1-20% within the US Physical Demands: Sedentary..." This is substantive; we could include under Schedule (travel) and maybe a separate section? But we only have allowed headings; maybe we can include travel under Schedule, and physical demands maybe under Requirements? Not ideal but we need to include all substantive info. Could add a section "Working Conditions" but not in allowed list; but 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 ...)". Likely they expect those headings; but we could still add other headings if needed. However to be safe, we can map physical demands to Requirements or maybe a separate "Working Conditions" but risk being considered extra. I think we can include a "Working Conditions" section as it's substantive; the instruction didn't forbid other headings, just gave examples. So we can include.
But we must not include boilerplate like awards, Premier at a glance, EEO, etc.
Now produce HTML fragment.
Structure:
About the role
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 ...)". Likely they expect those headings; but we could still add other headings if needed. However to be safe, we can map physical demands to Requirements or maybe a separate "Working Conditions" but risk being considered extra. I think we can include a "Working Conditions" section as it's substantive; the instruction didn't forbid other headings, just gave examples. So we can include.
But we must not include boilerplate like awards, Premier at a glance, EEO, etc.
Now produce HTML fragment.
Structure:
About the role
About the role
... (the "What you will be doing:" paragraph)
Responsibilities
- Project Management – 30%: ... (list of bullet points from that subsection)
- Process Execution – 30%: ...
- Strategic / Administrative – 20%: ...
- Quality Control – 20%: ...
- for any list of duties/requirements/benefits. So we can have a list of duties; each duty can be a sentence. Could combine the subheadings as part of each
- . Eg:
- Project Management – 30%: Develops and manages workplans and monitor necessary timelines; Uses contract calendar and project workplans to properly allocate resources to projects and tasks; Prioritizes and systematically organize the team's efforts around project scope and objectives; Ensures scope is clearly defined and validated continuously; Adheres to / adjusts the milestones and cycle times outlined in product category workplan; Coaches team members in prioritizing tasks and handling daily work challenges; Delegates decision-making authority and task responsibilities to appropriate subordinates: utilizing subordinates’ time, skills, and potential effectively; Develops and review project status reports which outline project accomplishments, issues and timelines; Sets up ongoing procedures for collection and review of information necessary for the management of projects or an organization; Reviews and approves deliverables. Reviews work of team members for accuracy; Identifies and resolves project issues; Defines critical issues for risk management with clients and manages clients' expectations related to these areas; Participates in Product Planning and Contract Management sourcing meetings to ensure a seamless integration throughout the Product Planning, Contract Negotiation and Contract Management processes. Similarly for Process Execution, Strategic/Admin, Quality Control. Alternatively we could break each bullet into separate
- but that may be too granular but still okay. The instruction didn't forbid splitting. I'd keep each major bullet as a
- with sub-detail separated by semicolons.
Requirements
Required Qualifications:
- Work Experience: 5 or more years of applicable experience
- Education: High School Diploma or GED (Required)
Additional Job Requirements:
- Remain in a stationary position for prolonged periods of time
- Be adaptive and change priorities quickly; meet deadlines
- Attention to detail
- Operate computer programs and software
- Ability to communicate effectively with audiences in person and in electronic formats
- Day-to-day contact with others (co-workers and/or the public)
- Making independent decisions
- Ability to work in a collaborative business environment in close quarters with peers and varying interruptions
Qualifications
Preferred Qualifications:
- Skills: Food Service Program Operations, Data Analytics, Account management, Supply Chain Management, Negotiation, Project Management
- Experience: Experience in foodservice operations, administration, marketing, purchasing/category management, and/or sales with strong product knowledge; Contract/account management in with diverse and vast contracts; Demonstrated analytical experience managing and interpreting contract related data (large data sets) and presenting results; Experience leading cross-functional projects
- Education: Bachelor's degree
Skills
- Food Service Program Operations
- Data Analytics
- Account management
- Supply Chain Management
- Negotiation
- Project Management
under Pay. But we must not include "Premier utilizes a wide-range salary structure to allow base salary flexibility within our ranges." That's also part of compensation description; could keep. But we need to avoid duplication. Let's extract the Pay-related sentences: "Premier’s compensation philosophy is to ensure that compensation is reasonable, equitable, and competitive in order to attract and retain talented and highly skilled employees. Premier’s internal salary range for this role is $90,000 - $150,000. Final salary is dependent upon several market factors including, but not limited to, departmental budgets, internal equity, education, unique skills/experience, and geographic location. Premier utilizes a wide-range salary structure to allow base salary flexibility within our ranges." We can keep all