Banquet Server - Anchorage Convention Centers

Responsibilities

...

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings; we shouldn't create other headings like Working Conditions. So we need to fit the working conditions info into existing headings: maybe Schedule covers schedule info; physical demands maybe could go under Responsibilities? But better to include under Schedule? Not ideal. Could we create a "Requirements" heading for physical demands? The list includes Requirements as an example heading. So we could use Requirements for physical demands and qualifications? Actually we already have Qualifications and Skills. Requirements could be used for physical demands and maybe other mandatory requirements (like TAPS card, ability to lift, etc.). But we already placed TAPS card under Qualifications. Might be better to move TAPS card to Requirements. Let's think. We need to preserve all substantive info. We can allocate: - About the role: brief description. - Responsibilities: duties list. - Qualifications: education/experience (six months service-oriented experience). - Skills: knowledge of catering services, guest service, teamwork, instruction following. - Requirements: physical demands, ability to lift 30 lbs, flexible schedule, TAPS card, etc. - Pay: Competitive Union wage. - Benefits: benefits available through Union membership. - Schedule: maybe we already covered schedule under Requirements; but we could also have Schedule section for schedule specifics. However we might avoid duplication. We need to decide which headings to use. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Perhaps combine related info. We could have: - About the role - Responsibilities - Qualifications and Requirements (maybe combine qualifications and requirements into one section? But we have separate headings for Qualifications and Requirements; we could use Qualifications for education/experience and skills, and Requirements for physical demands and schedule. But that's two sections. - Pay - Benefits - Schedule That's many sections (About, Responsibilities, Qualifications, Requirements, Pay, Benefits, Schedule) = 7 sections. Might be okay if each has substantive content. But we need to ensure we don't create sections with filler like "not specified". All sections have content. Let's extract content for each. About the role: "This is a hands-on position, providing the highest degree of professional catering service to guests with the goal of achieving customer satisfaction and retention." Responsibilities: list as above. Qualifications: Education and/or Experience: Minimum of six (6) months’ work experience in service-oriented environment. Also maybe "Must have or be willing to get a current TAPS card with the Anchorage Municipality." Could be considered qualification. Skills: Knowledge of catering services and terminology; Strong guest service skills; Ability to get along well with others; Ability to receive and carry out instructions in a timely manner. Requirements: Physical demands: Must be able to frequently lift at least 30 lbs.; can carry a service oval tray with up to (8) eight loaded entrée plates/covers throughout the course of an entire event; Must be able to work in a crowded, high-activity, high-demand environment; Must be able to work a flexible schedule, including weekends and holidays; Work hours may range from very early morning to late night; Work is primarily indoors; Some outdoor work may be required; Work will be performed in many different areas of the Anchorage Convention Centers, as well as off-premises, including the Alaska Railroad; Work will involve a considerable amount of walking, lifting, and other high-exertion activities; Must be able to work under deadlines or pressure, dealing with difficult people or situations involving complex issues, and establishing and maintaining cooperative and productive work relationships; Duties require the use of considerable initiative, creativity, judgment, problem-solving, and working under minimal direction; Requires working under deadlines or pressure, dealing with difficult people or situations involving complex issues, and establishing and maintaining cooperative and productive work relationships. (some duplication). Also "Must be able to work in a crowded, high-activity, high-demand environment." etc. We also have "Must be able to work a flexible schedule, including weekends and holidays. Work hours may range from very early morning to late night." That's schedule info; we could put under Schedule section instead of Requirements. But we already have Schedule heading; we could put schedule info there. Thus Requirements could focus on physical demands and maybe other mandatory requirements (like TAPS card if not placed elsewhere). But we need to avoid duplication. Let's allocate: - Qualifications: Education/experience (six months service-oriented) and TAPS card requirement. - Skills: list of skills/abilities. - Requirements: Physical demands (lifting, walking, etc.) and ability to work in high-demand environment, initiative, etc. - Pay: Competitive Union wage. - Benefits: benefits available through Union membership. - Schedule: flexible schedule, weekends/holidays, early morning to late night. We also have location: "Location: On Site at the Anchorage Convention Centers". Could be part of Requirements or maybe we could add a short paragraph under Requirements about location. But location is not in headings list; we could incorporate into Requirements as a sentence. We also have "Work will be performed in many different areas of the Anchorage Convention Centers, as well as off-premises, including the Alaska Railroad." That's location details. We'll include that in Requirements. Now we need to ensure we don't repeat boilerplate: Remove EEO, legal, etc. Also remove duplicated lines like "NOTE: The essential responsibilities..." and "Also, this document..." etc. Also remove "FLSA STATUS: Part-time hourly, Non-Exempt" maybe we could include as metadata? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So FLSA STATUS is minor metadata; we could fold into a short

maybe under About the role? Or we could drop it. Probably drop it as not essential? But it's substantive? It's about employment type; maybe we could include in a short paragraph under About the role or under Schedule? But it's not required to keep; we can drop minor metadata. The instruction: "fold minor metadata into a short

or drop it." So we could either drop or include in a short p. I'd drop it to keep concise. Similarly DEPARTMENT and