Catering Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job posting. Key sections: - About the role: The Role at a glance paragraph: "Constellation Culinary Group is seeking a motivated, organized, and detail-oriented Catering Coordinator to support our Sales and Event Management teams across the Philadelphia and New Jersey region. This is a highly administrative role focused on keeping sales, marketing, and event processes organized, accurate, and moving forward. The Catering Coordinator will provide behind-the-scenes administrative support to the Directors of Catering, Event Managers, and Regional Director of Sales, including managing inquiry data, preparing proposals and reports, preparing materials for site tours and client meetings, supporting sales outreach and marketing initiatives, and assisting with event administration. The ideal candidate is highly organized, detail-oriented, comfortable managing multiple priorities, and eager to learn catering systems and processes." - Responsibilities: "What you'll be doing:" list of duties. - Qualifications & Skills: "What we're looking for:" list. - Where you'll be working: location. - Benefits: "Our Benefits:" list. - Possibly Pay and Schedule: not mentioned. So we should not include Pay or Schedule sections. - About Constellation and About Elior North America: these are company description; could be considered "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could possibly put company description under About the role? But it's separate. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should use those headings when appropriate. Probably we should include About the role, Responsibilities, Qualifications & Skills (maybe combine Qualifications and Skills), Benefits, Location (maybe not a standard heading but we could put under About the role? But location is substantive; we could create a section "Location" but not in list. However instruction says use those headings for section headings; we could still use other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should map content to those headings. Thus: - About the role: include the role description paragraph. - Responsibilities: list of duties from "What you'll be doing:". - Qualifications: maybe combine Qualifications & Skills: we could have a heading "Qualifications" and list qualifications, then another heading "Skills" for skills list. Or we could combine into one section "Qualifications & Skills". But the instruction says we can use those headings; we could have both Qualifications and Skills separate. - Benefits: list. - Location: Not in list; maybe we could put location under About the role as a paragraph? But it's separate. Could we omit location? The instruction says preserve ALL substantive information. So we need to include location. We could add a

after About the role that includes location. Or we could create a custom heading like "Location" but that deviates from examples. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list; we can use other headings if needed, but they gave examples. Safer to include a heading "Location" as

. It's not prohibited. The instruction didn't say we cannot use other headings; just that we should use

for section headings (e.g., those). So we can use other headings as needed. Thus we will output:

About the role

... role description ...

Responsibilities

• ...
...

Qualifications

• Prior administrative, catering, hospitality, event experience preferred.
• Strong written and verbal communication skills.
• Excellent organizational skills and attention to detail.
• Ability to manage multiple priorities and meet deadlines.
• Strong computer skills, including Microsoft Office Suite and spreadsheets.
• Ability and willingness to learn CaterXpert and other catering/event systems.
• Ability to work independently while collaborating effectively with Sales, Operations, Culinary, and Event Management.
• Professional, positive, and service-oriented approach.
• Comfortable working in a fast-paced environment with competing priorities.
• Strong communication skills with coworkers, supervisors, vendors, clients, and other stakeholders.

Skills

• Experience with Canva and online marketing platforms preferred.

But note that some qualifications overlap with skills; we could keep as above. Alternatively combine Qualifications & Skills into one section. But we have both. Now Benefits:

Benefits

• Medical (FT Employees)
• Dental
• Vision
• Voluntary UNUM offering for Accident, Critical Illness and Hospital Indemnity
• Discount Program
• Commuter Benefits (Parking and Transit)
• EAP
• 401k
• Sick Pay
• Holiday Pay (9 paid holidays)
• Tuition Reimbursement (FT Employees)
• Paid Time Off

Location:

Location

667 N Broad St, Philadelphia, PA 19123

Also maybe include "About Constellation" and "About Elior North America" as company description; but not required headings. Could we include under About the role? Might be okay to add a paragraph after role description about company. But we must preserve all substantive info. The "About Constellation:" and "About Elior North America:" paragraphs are substantive. We could add a section "About the Company" with

About the Company

and include those two paragraphs. That seems reasonable. Thus final HTML fragment includes sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Location, About the Company. We must not include any boilerplate like EEO, disclaimer, etc. Remove those. Now ensure we don't repeat job title as heading. Not included. Check for any list items that are not substantive: ensure we keep all. Now produce HTML. Let's craft the About the role paragraph: combine the two sentences from "The Role at a glance:" plus maybe the first sentence about seeking. Actually the paragraph: "Constellation Culinary Group is seeking a motivated, organized, and detail-oriented Catering Coordinator to support our Sales and Event Management teams across the Philadelphia and New Jersey region. This is a highly administrative role focused on keeping sales, marketing, and event processes organized, accurate, and moving forward. The Catering Coordinator will provide behind-the-scenes administrative support to the Directors of Catering, Event Managers, and Regional Director of Sales, including managing inquiry data, preparing proposals and reports, preparing materials for site tours and client meetings, supporting sales outreach and marketing initiatives, and assisting with event administration. The ideal candidate is highly organized, detail-oriented, comfortable managing multiple priorities, and eager to learn catering systems and processes." That's good. Now Responsibilities list: need to capture each bullet from "What you'll be doing:" The text includes many items separated by periods. Let's break into list items: - Learn and utilize CaterXpert to support daily sales and administrative needs. - Assist in lead inquiry process by entering, maintaining, and auditing inquiries and opportunities for accuracy and completeness. - Assist with proposal revisions, updates, re-issuing, and quality control. - Maintain organized SharePoint files and sales resources. - Prepare and organize BEOs, menus, and other sales/event materials as needed. - Prepare site tour materials, including collateral packets, menus, venue information, floor plans, and client gifts. - Assist with client tastings, sales meetings, networking events, trade shows, and sales blitzes. - Support sales and business development projects as needed. - Assist Sales with maintaining venue profiles and listings on industry platforms, including uploading images, albums, menus, and updated venue information. - Provide administrative support to Event Managers, including PRL updates, BEOs, event paperwork, and internal follow-up. - Assist with third-party vendor communication and administrative needs. - Support menu signs, menu cards, lookbooks, and other event production materials. - Attend weekly BEO and event recap meetings and take notes when needed. - Assist with internal follow-up related to logistics, rentals, and event production. - Assist Events Managers in planning, coordinating, and executing events on a need basis during peak season - Support special projects and other administrative needs across Sales and Operations. Make sure each is a

. Now Qualifications list: from "What we're looking for:" The bullet list includes: - Prior administrative, catering, hospitality, event experience preferred. - Strong written and verbal communication skills. - Excellent organizational skills and attention to detail. - Ability to manage multiple priorities and meet deadlines. - Strong computer skills, including Microsoft Office Suite and spreadsheets. - Experience with Canva and online marketing platforms preferred. (Actually this is under skills but we can treat as qualification) - Ability and willingness to learn CaterXpert and other catering/event systems. - Ability to work independently while collaborating effectively with Sales, Operations, Culinary, and Event Management. - Professional, positive, and service-oriented approach. - Comfortable working in a fast-paced environment with competing priorities. - Strong communication skills with coworkers, supervisors, vendors, clients, and other stakeholders. We could split Qualifications and Skills: Qualifications: prior experience, communication skills, organizational skills, ability to manage priorities, computer skills, ability to learn systems, ability to work independently, professional approach, fast-paced comfort, communication skills (maybe duplicate). Skills: Experience with Canva and online marketing platforms preferred. But we already have communication skills listed twice; we can keep as is. Better to have Qualifications: all except Canva. Skills: Experience with Canva and online marketing platforms preferred. Now Benefits list: as above. Location: paragraph. About the Company: include two paragraphs: "From retail spaces to office buildings, Constellation provides high-quality business dining and catering experiences all over the United States. Constellation takes pride in building every meal around its goal of fostering connections through food and hospitality." "Elior North America is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status. We are committed to diversity and encourage applications from people of all backgrounds and abilities. We take pride in supporting the development of our employees and their skills at all levels and in fostering an environment of growth. At Elior North America, we are committed to offering growth and advancement opportunities for all of our employees. The valuable skills and experience you’ve gained with Elior will propel you further in your career, whether with our corporate office or one of our brand segments." We must remove EEO boilerplate? Actually the "About Elior North America:" includes EEO statement; but it's part of the company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That suggests we should remove the EEO statement. However the "About Elior North America:" paragraph includes EEO statement;