Jobs · Business Development · New York

Pop-Up Seasonal Retail Team Member - NYC

Levain Bakery · New York, NY · 4 wk ago
Business Development$17–$19.25/hrTemporary
We need to output HTML fragment with sections: About the role? Actually we have description of company and role. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have: The role description (THE ROLE: SEASONAL RETAIL TEAM MEMBER) and then "What We’re Looking For", "Job Responsibilities", "Requirements", "Compensation & Benefits". Also there is a brief description of company (maybe "About the role"? Actually "About the role" could be the brief description of the role? The posting includes a brief description of the company and the role. We could treat that as "About the role" section. Also we have "Compensation & Benefits" with pay and benefits. There's no explicit schedule but maybe we can infer open availability etc. But schedule is not given explicitly; we have "Open availability: ability to work mornings, nights, weekends, and holidays". That could be schedule info. So we could include a Schedule section with that. However we must not create sections with placeholder text. If we have actual content, we can include. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO etc. At end there is a statement about diversity etc - that's boilerplate? It's EEO/equal-opportunity. Should remove. Also remove application instructions (none). Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Company description / brief description: "Brief Description Competitive triathletes and passionate bakers, Pam Weekes and Connie McDonald left their careers to open a small bread shop in New York City in 1995 — Levain Bakery. One day, they baked a BIG chocolate chip walnut cookie as energy for triathlon training. At Levain, a batch of these 6-ounce cookies flew off the shelves, and an icon was born. The cozy shop on West 74th Street became a neighborhood favorite and a destination for epicurious visitors from around the world, hungry for “the cookie.” From the start, Pam, Connie, and the team baked everything fresh on-site each day, donating the day’s leftovers to charity — and we still do, nearly 30 years later. Today, Levain has bakeries across the country (with more to come!), plus ecommerce gift boxes to treat cookie lovers in every state. Our Vision: To give rise to lifelong memories Our Mission: To bring together people who treat their work and the craft of baking and all who come to visit with great care. Every day, we strive to embody our company’s five core values: Welcome All- We are all in it together Work Hard and Be Kind- We pull our weight, we do our best, and take care of each other Lead with Heart- We operate with empathy and integrity Rise Up- We take initiative to make things better Savor It- We are present and find the fun!" That's substantive. Could be placed under

    About the role

    maybe? Actually "About the role" could be description of the role, but we have company description. Could also be "About the company". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate. We have: - About the role: maybe the brief description of the role? The posting includes "THE ROLE: SEASONAL RETAIL TEAM MEMBER" and then description of what they do. That could be About the role. We'll put that. - Responsibilities: we have "Job Responsibilities" with subpoints: Team Collaboration, Customer Service, Operations. We'll list as
    • each bullet. - Requirements: we have "Requirements" bullet list. - Benefits: we have "Compensation & Benefits" includes pay and benefits: "$17-19.25/hour + tips Commuter Benefits Employee Assistance Program". Also maybe other benefits? Only those. - Pay: we could separate Pay section with the hourly rate. But we already have Benefits section includes pay? The instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they said include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. We have both pay and benefits specifics. Could make a Benefits section that includes both pay and benefits. Or we could make Pay and Benefits separate. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine Pay and Benefits into one section maybe labeled "Benefits" (including pay). But they also list Pay as a possible heading. However we can choose to combine. - Schedule: we have open availability statement. That's schedule info. Could make a Schedule section. - Qualifications: not separate; maybe covered in Requirements. - Skills: not separate; maybe covered in Requirements. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits (including pay), Schedule. We must not repeat job title as heading. So we won't put "Seasonal Retail Team Member" as heading. We need to preserve all substantive information. Let's extract details: About the role: Should include the description of the role from "THE ROLE: SEASONAL RETAIL TEAM MEMBER Seasonal Retail Team Members play a crucial role during our busiest times of the year in delivering warm, helpful, and accurate customer service that reflects the dedication of the Levain brand. Seasonal Retail Team Members create a welcoming environment that encourages customers to return again and again and are responsible for supporting the team in daily operations." Also maybe the "What We’re Looking For" bullet list? That could be part of Requirements or Skills. But we already have Requirements section. The "What We’re Looking For" includes: People-forward attitude with exceptional customer service skills; Be proactive and empathetic in assisting customers and team members Strong communication & interpersonal skills; team-oriented with a positive attitude Maintain a high level of professionalism and care: be adaptable, flexible, and patient Must be reliable, responsible, and punctual Ability to remain calm under pressure in a fast-paced environment when troubleshooting issues: be consistent, patient, and even keeled Strong attention to detail in customer interactions and product knowledge Embody and promote the values and standards of Levain Bakery That's more like qualifications/skills. Could be placed under Requirements or Skills. Since we have Requirements section already with bullet list: "Previous retail or customer service experience is preferred Open availability: ability to work mornings, nights, weekends, and holidays Ability to lift/push up to 25+ pounds, including overhead Stand/walk for an 8-hour shift (excluding a ½ hour break); some locations require walking up and down stairs Read and communicate in English, both verbally and in writing". That's separate. Thus we could treat "What We’re Looking For" as Skills or Qualifications. Let's make a Skills section. Thus sections: About the role, Responsibilities, Skills, Requirements, Benefits (pay+benefits), Schedule. We must not create sections with placeholder text. All have content. Now format:

      About the role

      ... (prose)

      Responsibilities

      • Team Collaboration: Lead with curiosity and compassion by showing care for your co-workers and build meaningful connections that broaden your perspective; Display a strong sense of teamwork: Work collaboratively with team members to ensure smooth store operations; Facilitate open, clear, and timely communication with your team members and management; Stay informed about new products, procedures, and promotions
      • Customer Service: Greet customers with a warm and welcoming demeanor; Ensure every guest receives consistent, accurate, high-quality service that reflects Levain’s brand standards; Foster strong, lasting relationships with customers to enhance their sense of belonging and connection to our community surrounding the bakery; Resolve customer issues promptly and courteously and operate with empathy
      • Operations: Consistently adhere to established protocols and maintain the highest standards of excellence to ensure all baked goods meet Levain Bakery’s quality standards; Adept knowledge of Toast POS system; Ensure all in-store and third-party delivery (3PD) orders are accurate and safely prepared; Maintain cleanliness in all areas of the store, including customer areas, restrooms, and workspaces; Assist in restocking and organizing inventory and adhere to guidelines given from Shift Lead or management
      But we need to preserve the bullet points exactly as given. The original had separate bullet points under each heading. We could keep each bullet as separate
    • . Let's extract: Under Team Collaboration: - Lead with curiosity and compassion by showing care for your co-workers and build meaningful connections that broaden your perspective - Display a strong sense of teamwork: Work collaboratively with team members to ensure smooth store operations - Facilitate open, clear, and timely communication with your team members and management - Stay informed about new products, procedures, and promotions Under Customer Service: - Greet customers with a warm and welcoming demeanor - Ensure every guest receives consistent, accurate, high-quality service that reflects Levain’s brand standards - Foster strong, lasting relationships with customers to enhance their sense of belonging and connection to our community surrounding the bakery - Resolve customer issues promptly and courteously and operate with empathy Under Operations: - Consistently adhere to established protocols and maintain the highest standards of excellence to ensure all baked goods meet Levain Bakery’s quality standards - Adept knowledge of Toast POS system - Ensure all in-store and third-party delivery (3PD) orders are accurate and safely prepared - Maintain cleanliness in all areas of the store, including customer areas, restrooms, and workspaces - Assist in restocking and organizing inventory and adhere to guidelines given from Shift Lead or management Thus we can make each bullet a separate
    • . That's fine. Now Skills section: from "What We’re Looking For". Let's list each bullet: - People-forward attitude with exceptional customer service skills - Be proactive and empathetic in assisting customers and team members - Strong communication & interpersonal skills; team-oriented with a positive attitude - Maintain a high level of professionalism and care: be adaptable, flexible, and patient - Must be reliable, responsible, and punctual - Ability to remain calm under pressure in a fast-paced environment when troubleshooting issues: be consistent, patient, and even keeled - Strong attention to detail in customer interactions and product knowledge - Embody and promote the values and standards of Levain Bakery We could split some combined bullets but keep as is. Now Requirements section: list: - Previous retail or customer service experience is preferred - Open availability: ability to work mornings, nights, weekends, and holidays - Ability to lift/push up to 25+ pounds, including overhead - Stand/walk for an 8-hour shift (excluding a ½ hour break); some locations require walking up and down stairs - Read and communicate in English, both verbally and in writing Now Benefits section: include pay and benefits: - Compensation: $17-19.25/hour + tips - Commuter Benefits - Employee Assistance Program We could also mention that it's seasonal? Not needed. Now Schedule section: from open availability? Actually we already used open availability in Requirements. But schedule could be about shift times: "Open availability: ability to work mornings, nights, weekends, and holidays". That's schedule. Since we already used it in Requirements, maybe we should not duplicate. Better to keep schedule separate and remove from Requirements? But the requirement includes open availability as a requirement. It's both a requirement and schedule info. We could keep it in Requirements and not have a separate Schedule section to avoid duplication. The instruction says preserve ALL substantive information; not duplicate? It

Similar jobs