Seasonal Holiday Retail Assistant Manager - Uptown Christiansburg
Cherry Hill Programs · Christiansburg, VA · 1 mo ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the job description.
Sections present:
- About Us (but we need "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes "About Us" describing company, but not specifically about the role. However we can treat "About the role" as description of role: The paragraph after "About Us" describing Assistant Local Manager responsibilities? Actually there is a paragraph: "As our Assistant Local Manager, you’ll work alongside the Local Manager to help lead the team responsible for creating magical holiday memories for children and families. You’ll support daily photo operations, help motivate and develop the seasonal team, drive sales and service excellence, and ensure every family enjoys a memorable Santa visit, exceptional photo experience, and outstanding guest service from start to finish." That's role description. So we can put that under About the role.
- Responsibilities: The "What You’ll Do" bullet list.
- Requirements: The "What We’re Looking For" includes Must Haves and Nice to Haves. Could split into Requirements (must haves) and Qualifications (nice to haves) or Skills. But we need to follow headings: Requirements, Qualifications, Skills. We need to decide mapping.
We have Must Haves: list of requirements. Nice to Haves: list of preferred qualifications/experience.
We could put Must Haves under Requirements, Nice to Haves under Qualifications. Skills maybe not separate; but we could also put some skills under Skills if present. However we have communication, organization, time management, problem-solving skills listed under Must Haves. Those are skills. But we can keep them under Requirements.
We also have Benefits: "Why You’ll Love Working With Us" includes bullet points: Build valuable leadership experience..., Flexible scheduling..., Same day pay options..., Employee Referral Program..., fun fast-paced..., Opportunities beyond the season..., Exclusive Holiday Perks for You & Your Family: list.
Also Pay: Not explicitly mentioned except "Same day pay options". No specific pay rate. So we should NOT create Pay section because no specific pay stated. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list). So we include Benefits. Schedule: The posting mentions flexible scheduling, availability to work evenings, weekends, holidays, peak retail periods, minimum 20 hours a week. That's schedule info. So we can include Schedule section.
Pay: Not specific, so omit.
Now we need to output HTML fragment with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes "About Us" describing company, but not specifically about the role. However we can treat "About the role" as description of role: The paragraph after "About Us" describing Assistant Local Manager responsibilities? Actually there is a paragraph: "As our Assistant Local Manager, you’ll work alongside the Local Manager to help lead the team responsible for creating magical holiday memories for children and families. You’ll support daily photo operations, help motivate and develop the seasonal team, drive sales and service excellence, and ensure every family enjoys a memorable Santa visit, exceptional photo experience, and outstanding guest service from start to finish." That's role description. So we can put that under About the role.
- Responsibilities: The "What You’ll Do" bullet list.
- Requirements: The "What We’re Looking For" includes Must Haves and Nice to Haves. Could split into Requirements (must haves) and Qualifications (nice to haves) or Skills. But we need to follow headings: Requirements, Qualifications, Skills. We need to decide mapping.
We have Must Haves: list of requirements. Nice to Haves: list of preferred qualifications/experience.
We could put Must Haves under Requirements, Nice to Haves under Qualifications. Skills maybe not separate; but we could also put some skills under Skills if present. However we have communication, organization, time management, problem-solving skills listed under Must Haves. Those are skills. But we can keep them under Requirements.
We also have Benefits: "Why You’ll Love Working With Us" includes bullet points: Build valuable leadership experience..., Flexible scheduling..., Same day pay options..., Employee Referral Program..., fun fast-paced..., Opportunities beyond the season..., Exclusive Holiday Perks for You & Your Family: list.
Also Pay: Not explicitly mentioned except "Same day pay options". No specific pay rate. So we should NOT create Pay section because no specific pay stated. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list). So we include Benefits. Schedule: The posting mentions flexible scheduling, availability to work evenings, weekends, holidays, peak retail periods, minimum 20 hours a week. That's schedule info. So we can include Schedule section.
Pay: Not specific, so omit.
Now we need to output HTML fragment with headings and appropriate
or
- .
We must not include any markdown fences.
We need to preserve all substantive info; not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. The text includes "We Work Together to Win Together" mission statement etc. That's substantive? It's about company values; could be considered part of About the role? But we already have About the role description. The mission statement could be placed under About the role or maybe a separate section like About Us but not required. Since we only have allowed headings, we could include it under About the role as additional paragraph.
We must not repeat job title as heading. So no heading for Assistant Local Manager.
We must not put Job ID/requisition numbers as headings; none present.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The text includes "Santas’s season is short and spots fill fast- apply now to lock in your schedule!" That's application instruction; should be removed. Also "apply now" etc. Also "We Work Together to Win Together" is not boilerplate; it's mission statement; keep.
Also "Our mission is simple: to bring magic to every experience by capturing moments that last a lifetime." That's also mission; keep.
Now let's extract content.
About Us paragraph: "Cherry Hill Programs brings the magic to every experience by capturing moments that last a lifetime. In partnership with retail locations, tourist attractions, and destinations across North America, Cherry Hill Programs contributes millions of holiday and souvenir experiences for children and families, year after year." That's about company; could be included under About the role or maybe we could add a separate About the role that includes both company and role. Since we only have About the role heading, we can combine.
Then role description paragraph: "As our Assistant Local Manager, you’ll work alongside the Local Manager to help lead the team responsible for creating magical holiday memories for children and families. You’ll support daily photo operations, help motivate and develop the seasonal team, drive sales and service excellence, and ensure every family enjoys a memorable Santa visit, exceptional photo experience, and outstanding guest service from start to finish."
Combine these into About the role.
Now Responsibilities: "What You’ll Do" list:
- Promote a positive, collaborative environment while upholding company values and policies
- Support opening-day preparations, including hiring completion, inventory, equipment setup/testing, scheduling, training, and opening/closing procedures
- Capture photos and help guests choose memorable souvenirs to take home
- Photography experience not required
- Resolve customer concerns and service issues to support a positive guest experience
- Lead by example and reinforce procedures set by senior management
- Troubleshoot technical issues and escalate to IT or Local Management as needed
- Assist the Local Manager with inventory, scheduling, training, recruiting, and other administrative tasks
- Perform other duties as assigned
Note: "Photography experience not required" is a statement; we keep as list item.
Now Requirements (Must Haves):
- Must be at least 18 years of age
- Strong communication, organization, time management, and problem-solving skills
- Must be comfortable in a cash handling/ sales transaction position
- Ability to lead a team, work independently, and make sound decisions
- Availability to attend required pre-season training
- Ability to work a flexible schedule, including evenings, weekends, holidays, and peak retail periods
- Available to work a minimum of 20 hours a week or as needed
- Ability to lift and carry equipment up to 10-25 pounds and stand for prolonged periods of time
Now Qualifications (Nice to Haves):
- Previous leadership or management experience in retail, hospitality, customer service, or a similar environment
- High school diploma or equivalent
- Experience managing teams or operations across multiple locations
- Demonstrated success driving sales, guest experience, and operational results
- Experience with scheduling, training, coaching, and developing team members
Now Skills: Could we separate communication etc? But we already included them under Requirements. If we want a Skills section, we could pull out the skills: Strong communication, organization, time management, problem-solving skills; Ability to lead a team, work independently, make sound decisions; Ability to lift and carry equipment etc. But that duplicates. Better to not create a Skills section if not needed; we can omit Skills heading if no specific content beyond what's already covered. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills.
Now Benefits: "Why You’ll Love Working With Us" list:
- Build valuable leadership experience developing skills in team leadership, staffing and scheduling, coaching, sales performance, problem-solving, and delivering exceptional guest experiences
- Flexible scheduling to fit your lifestyle
- Same day pay options for early access to your paycheck
- Employee Referral Program
- A fun, fast-paced environment where you’ll lead a team that helps create memorable experiences for families
- Opportunities beyond the season — return for future holiday seasons and explore growth opportunities within our souvenir photography division, where available
- Exclusive Holiday Perks for You & Your Family:
- One free visit with Santa for friends and family including:
* 10 photo prints
* 10 free holiday cards from Shutterfly
* A personalized digital message from Santa, powered by Portable North Pole
* 3 free months of access to Pixie Post, our digital greeting card platform
We need to format as nested lists? The instruction: Use
- for any list of duties/requirements/benefits. So we can have top-level ul for benefits, and nested ul for sub-items.
Now Schedule: The posting mentions flexible scheduling, availability to work evenings, weekends, holidays, peak retail periods, minimum 20 hours a week. That's already covered in Requirements (flexible schedule) and Benefits (flexible scheduling). But we can still create a Schedule section with that info. However we must not repeat content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have overlapping info? Might be duplication but we could still include. However we should avoid duplication if possible. But we could put schedule details under Schedule section, and maybe remove from Requirements? But Requirements includes "Ability to work a flexible schedule, including evenings, weekends, holidays, and peak retail periods" and "Available to work a minimum of 20 hours a week or as needed". That's definitely schedule info. If we create a Schedule section, we could move those items there and keep Requirements focused on other must-haves (age, communication, cash handling, leadership ability, training attendance, lifting). But the instruction says preserve all substantive info; moving is fine as long as we keep it.
We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly also Skills? We'll omit Skills.
Now we need to ensure we don't include any boilerplate like "We Work Together to Win Together" mission statement etc. That's not boilerplate; it's substantive about company values. Could be placed under About the role.
Let's craft HTML.
We'll start with
About the role
thencontaining combined paragraphs. Paragraph 1: Company description. Paragraph 2: Role description. Paragraph 3: Mission statement maybe. We need to ensure we don't include any application instruction like "apply now". Remove that line. Now Responsibilities:
Responsibilities
- with each item.
Now Requirements:
Requirements
- with must-haves.
Now Qualifications:
Qualifications
- with nice-to-haves.
Now Benefits:
Benefits
- with items; for the exclusive holiday perks we need nested list.
Now Schedule:
Schedule
- with items: Flexible scheduling to fit your lifestyle (maybe duplicate), Ability to work a flexible schedule including evenings, weekends, holidays, peak retail periods, Available to work a minimum of 20 hours a week or as needed. But we already have flexible scheduling in Benefits; we could keep only schedule-specific items not already in Benefits. However Benefits includes "Flexible scheduling to fit your lifestyle". That's similar. To avoid duplication, we could keep schedule section with the specifics: Ability to work a flexible schedule including evenings, weekends, holidays, peak retail periods; Available to work a minimum of 20 hours a week or as needed. We'll keep that.
Now check for any other substantive info: "Same day pay options for early access to your paycheck" is benefit; we have that.
"Employee Referral Program" benefit.
"Opportunities beyond the season — return for future holiday seasons and explore growth opportunities within our souvenir photography division, where available" benefit.
Now ensure we didn't miss any: "Build valuable leadership experience developing skills in team leadership, staffing and scheduling, coaching, sales performance, problem-solving, and delivering exceptional guest experiences" benefit.
Now "A fun, fast-paced environment where you’ll lead a team that helps create memorable experiences for families" benefit.
Now "Exclusive Holiday Perks for You & Your Family:" with subitems.
Now also "We Work Together
- for any list of duties/requirements/benefits. So we can have top-level ul for benefits, and nested ul for sub-items.
Now Schedule: The posting mentions flexible scheduling, availability to work evenings, weekends, holidays, peak retail periods, minimum 20 hours a week. That's already covered in Requirements (flexible schedule) and Benefits (flexible scheduling). But we can still create a Schedule section with that info. However we must not repeat content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have overlapping info? Might be duplication but we could still include. However we should avoid duplication if possible. But we could put schedule details under Schedule section, and maybe remove from Requirements? But Requirements includes "Ability to work a flexible schedule, including evenings, weekends, holidays, and peak retail periods" and "Available to work a minimum of 20 hours a week or as needed". That's definitely schedule info. If we create a Schedule section, we could move those items there and keep Requirements focused on other must-haves (age, communication, cash handling, leadership ability, training attendance, lifting). But the instruction says preserve all substantive info; moving is fine as long as we keep it.
We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly also Skills? We'll omit Skills.
Now we need to ensure we don't include any boilerplate like "We Work Together to Win Together" mission statement etc. That's not boilerplate; it's substantive about company values. Could be placed under About the role.
Let's craft HTML.
We'll start with