Interim Support Lead Part Time Elmwood Park NJ

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about company purpose. That could be "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. We have: - Intro paragraph: "At Five Below our growth is a result of the people who embrace our purpose: ..." This is about company culture, could be "About the role" or maybe "About the company". We'll treat as "About the role". Provide

. - Responsibilities: list of duties. Use

• . - Qualifications: list: High School Graduate or equivalent, College experience preferred, Minimum 1 years of management experience, Excellent verbal and written communication skills, Ability to multi-task, Creative thinking, Ability to maintain composure under pressure. Use
  . - Essential Job Functions: maybe could be "Requirements" or "Skills"? The instruction says we can use Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Essential Job Functions could be considered "Requirements" or "Skills". We'll treat as "Requirements". Provide
  . - Benefits: mention "Explore our benefits site to discover all the perks and support we offer! From health coverage to financial and personal wellness, we've got you covered—check it out today! benefits.fivebelow.com/public/welcome". That's a benefits mention but not specific list. The instruction: never create Benefits section unless posting actually states them. It does state benefits exist and gives a URL. It's not a list but we could still include a Benefits section with a

  describing. However they said prefer a few substantive sections over many thin ones. Benefits is somewhat vague but we have a statement. Could include Benefits section with a

  . But we need to avoid filler like "commensurate with experience". This is not filler. It's a statement about benefits. So we can include Benefits. - Pay: "Position Type Hourly Position Starting At $16.42". That's pay info. So we can include Pay section with

  . - Schedule: "Ability to work a flexible schedule to meet the needs of the business, which will require day, evening, weekends and may include overnight shifts and travel (as required)". That's schedule info. So we can include Schedule section with

  . We must not include Job ID, requisition numbers, boilerplate like EEO, fraud warnings, application instructions, navigation, cookie, legal. Remove those. We must preserve all substantive information. So we need to keep the responsibilities list exactly as given. Also qualifications list. Essential job functions list. Benefits statement. Pay statement. Schedule statement. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  At Five Below our growth is a result of the people who embrace our purpose: We know life is way better when you are free to Let Go & Have Fun in an amazing experience, filled with unlimited possibilities, priced so low, you can always say yes to the newest, coolest stuff! Just ask any of our over 20,000 associates who work at Five Below and they’ll tell you there’s no other place like it. It all starts with our purpose and then, The Five Below Way, which is our values and behaviors that each and every associate believes in. It’s all about culture at Five Below, making this a place that can inspire you as much as you inspire us with big ideas, super energy, passion, and the ability to make the workplace a WOWplace!

  Responsibilities

  • Ensures all crew members are Wowing the Customer through personal contact with customers.
  • Trains the crew on the B.E.S.T. customer service experience; ensuring that each guest has a fast, friendly check out experience.
  • Helps oversee the daily activities of all store associates, ensuring they are performing their duties effectively and providing excellent customer service.
  • Assists with the receiving, unpacking, and organizing of new stock to ensure items are quickly and efficiently placed on the sales floor
  • Acts as Manager on Duty when needed, taking full responsibility for store operations, staff management, customer service, and addressing any urgent issues.
  • Occasionally manages the entire process of opening or closing the store, which includes securing cash, locking doors, setting alarms, and ensuring everything is in place for a smooth daily operation.
  • Supports the onboarding and ongoing training of associates, helping them learn store policies, product knowledge, and operational procedures to improve their performance.
  • Drives store sales and controls expenses: Actively seeks ways to boost sales by optimizing merchandising, staff performance, and customer service.
  • Partners with the entire store leadership team in merchandising procedures and World Recovery.
  • Performs store maintenance including but not limited to taking out garbage, sweeping, cleaning bathrooms, maintaining stock room

  Qualifications

  • High School Graduate or equivalent
  • College experience preferred
  • Minimum 1 years of management experience
  • Excellent verbal and written communication skills
  • Ability to multi-task
  • Creative thinking
  • Ability to maintain composure under pressure

  Requirements

  • Frequently operates cash register, computer, hand-held, phone, walkie, and mobile devices
  • Frequently move merchandise weighing up to 25 lbs and places/removes merchandise up to a height of 5-10 feet
  • Frequently ascend/descend ladders in order to retrieve and put away stock
  • Frequently position self to kneel, bend, twist, and stoop, including in the stock room and on the sales floor
  • Frequently communicate and exchange information with customers on the telephone and face-to-face in the store, as well as with managers and coworkers. Must be able to exchange accurate information in these situations
  • Frequently move across the sales floor assisting customers, as well as to and from the stock room retrieving and putting away merchandise
  • Ability to work a flexible schedule to meet the needs of the business, which will require day, evening, weekends and may include overnight shifts and travel (as required)
  • Must be able to identify and discern email and print instructions regarding merchandise layouts, associate schedules, and standard operating procedures
  • Must be able to remain in a stationary, upright position for 80% of the time
  But note: The schedule item appears also in Requirements list; we might want to separate schedule section. However we already included schedule ability in Requirements. But we could also create a Schedule section separate. The instruction: prefer a few substantive sections over many thin ones. Having schedule as separate may be thin. But we have schedule info also in Requirements; we could keep schedule inside Requirements and not create separate Schedule section. However the instruction says include Schedule section only if posting actually states them. It does state schedule info. But we could incorporate schedule info into Requirements or have a separate Schedule section. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. If we put schedule info inside Requirements, we avoid an extra section. However the schedule info is a distinct bullet; but we can keep it there. The schedule section would be thin (just one sentence). So better to not create Schedule section. Similarly Benefits: we have a statement about benefits; could be a Benefits section with a paragraph. That's not too thin. Could be okay. Pay: we have a statement about starting pay $16.42. That's also thin but could be a Pay section. However we could combine Pay and Benefits into a "Compensation & Benefits" section? But headings are prescribed; we could still create Pay and Benefits sections; they'd be thin but maybe acceptable. The instruction: "Prefer a few substantive sections over many thin ones." So we should aim for fewer sections. Perhaps we can combine Pay and Benefits into one section? But headings are fixed examples; we could still use

  Pay

  and

  Benefits

  but that adds two sections. Could we instead put Pay info inside Benefits section? Not ideal. Maybe we can create a "Compensation and Benefits" section using

  Compensation and Benefits

  but not in the list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we could still use other headings? Safer to stick to those. So we may need to include Pay and Benefits sections if we have content. They are thin but we have actual content. The instruction says "Prefer a few substantive sections over many thin ones." So we should evaluate if we can avoid creating Pay and Benefits sections by merging into other sections. Could we put Pay info into Responsibilities? No. Could we put Benefits into About the role? Possibly but that would dilute. However we could include a short sentence about benefits in About the role? The About the role paragraph already is long; we could add benefits there but that would be adding info not originally there? Actually benefits statement is separate; we could incorporate it into About the role but that would be moving content; still preserving all info. It's okay to reorder? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid reordering. So we could merge benefits and pay into About the role or Qualifications? But that might be weird. Better to keep them separate but we risk many thin sections. However we have About the role, Responsibilities, Qualifications, Requirements, Benefits, Pay. That's 6 sections. Could we combine Benefits and Pay into one section called "Compensation & Benefits"? Not in examples but maybe acceptable. However the instruction says use those headings; but not strictly limited. Safer to follow examples: we can include Benefits and Pay sections. It's still a few sections (6). Not many thin ones? Each has substantive content: Benefits paragraph, Pay paragraph. That's okay. We should not include Schedule section because we already placed schedule info in Requirements. But we have schedule info also as a bullet; we could keep it there. That avoids an extra section. Thus final sections: About the role, Responsibilities, Qualifications, Requirements, Benefits, Pay. Check that we haven't missed any substantive info: The "Job description is not all-inclusive..." sentence: "This job description is not all-inclusive. Additional responsibilities will be determined by the Store Manager, as dictated by store needs." That's substantive; we should preserve it. Where to put? Could be after Responsibilities as a note. Could be a

  after the responsibilities list. We'll add a

  after the responsibilities list. Also "Explore our benefits site to discover all the perks and support we offer! From health coverage to financial and personal wellness, we've got you covered—check it out today! benefits.fivebelow.com/public/welcome". That's benefits statement. Also "Position Type Hourly Position Starting At $16.42". That's pay. Also "Five Below is an Equal Opportunity Employer..." etc is boilerplate to remove. Also fraud warning etc to remove. Also "crewservices.zendesk.com/hc/en-us/requests/new" etc remove. Thus final HTML. Let's craft. Be careful to not include any extra text outside HTML. We