Full-Time Key Holder

We need to output HTML fragment with sections: About the role? Actually we have company overview, description of duties, qualifications, physical requirements, total rewards package, hourly rate. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have: - Company Overview: could be "About the role"? Actually "Company Overview" is about the company, not role. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have description of duties (Essential Duties And Responsibilities) -> Responsibilities. Qualifications -> Qualifications. Physical Requirements maybe could be under Requirements? Or we could have a separate "Requirements" section for qualifications? But we already have Qualifications. Physical Requirements could be part of Requirements? Might be better to include a "Requirements" section for physical requirements. However we already have Qualifications; we could combine qualifications and physical requirements under Qualifications? But they are separate. The instruction: Use headings as examples; we can choose which to include. We need to avoid filler. We have: - Company Overview: maybe we can put under "About the role"? Not exactly. Could we omit company overview? It's substantive info about company; maybe we can put under a heading like "About the company"? Not in list. But we could still use

for any section heading; the examples are just examples, not exclusive? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate, but we could also use other headings? It says use

for section headings (e.g. ...). Likely they expect us to use those specific headings where applicable. So we need to map content to those headings. We have: - About the role: could include company overview and description of duties? Actually "About the role" could be a brief summary of the position. We have "Description Of Duties" which includes leadership, customer service, general. That's responsibilities. So we could put that under Responsibilities. - Responsibilities: we have the duties broken into Leadership, Customer Service, General. We'll output as

• items. - Requirements: could include qualifications and physical requirements? But we also have Qualifications heading. We could have Qualifications separate. Requirements could be things like "Minimum 1 years experience..." etc. That's qualifications. Physical requirements could be under Requirements as well? But we have separate heading for Qualifications; we can put qualifications there, and physical requirements maybe under Requirements? However we already used Qualifications heading; we could also have Requirements for things like "Ability to work a flexible schedule including holidays and weekends." That's also a qualification. Might be overlapping. Better: Use Qualifications heading for the bullet list of qualifications (experience, skills, tech). Use Requirements heading for physical requirements? But physical requirements are also requirements. However we can decide to have Qualifications and Requirements both, but ensure we don't duplicate. Let's list content: Company Overview: Launched in 2016... mission... etc. This is about the company, not role. Could we put under "About the role"? Not ideal but maybe acceptable as overview of the role's context. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid adding a section like "About the company". But they gave examples; we could still use

  for any heading, but they said use

  for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings only. So we need to map company overview to something like "About the role"? Might be a stretch but okay. Alternatively we could omit company overview entirely? But we must preserve ALL substantive information; cannot omit. So we need to include it somewhere. Could put it in a

  without a heading? The instruction: Use

  for section headings (e.g...). It doesn't say every paragraph must be under a heading; we could have a

  directly after the fragment. But they likely expect sections with headings. However we could include a

  for company overview without a heading, then headings for other sections. That would preserve info. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose." So we can have prose in

    . So we can have a

    for company overview, then headings for Responsibilities, Qualifications, Benefits, Pay. Physical requirements could be under Requirements as a list? But we have no separate Requirements heading; we could include physical requirements under Qualifications as part of list? Might be okay. Let's decide sections: -

    Company Overview (prose) -

    Responsibilities

    with
    • items (leadership, customer service, general) -

      Qualifications

      with
      • items (experience, personality, communication, multitask, schedule flexibility, tech competency) -

        Benefits

        with
        • items (Paid vacation, sick time, holidays; Healthcare, Vision, Dental; 401k plan w/company match; competitive salary with discretionary bonuses) -

          Pay

          with

          Hourly Rate $32 USD (maybe also mention hourly range $32.00/hour) We also have "Hourly Range: $32.00/hour" and "Hourly Rate $32 USD". So we can put Pay: $32.00/hour. We also have "Total Rewards Package" includes those benefits. So we can combine. We must not include sections with filler like "commensurate with experience". We have specific content. We must not include navigation/legal/EEO etc. There's an Equal Opportunity Employer line; we should drop it. We must not include application instructions. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We have classification: Non-Exempt; location; maybe we could include location in a

          under company overview? Could add location as part of overview. But location is substantive; we could add a

          for location. However we could also incorporate location into the company overview paragraph. Let's craft:

          Launched in 2016 and founded by Santa Barbara-born sisters Margaret and Katherine Kleveland, DÔEN is a digitally-led, multi-channel fashion and lifestyle brand committed to creating lasting, beautiful collections while supporting individuals across the organization, supply chain, and community. The brand partners with domestic and international partners who share its values of gender and social equality and giving back through foundations that benefit employees and surrounding communities. The Keyholder position is based at 337 King St., Charleston, SC 29401.

          Then Responsibilities: list items. We need to capture all duties: Leadership: - Supports the Store Manager in all aspects of running the store. - Demonstrate shop ownership in the absence of the Store Manager or Assistant Store Manager. - Interface with the store team in a manner that promotes learning, respect and a positive work environment, and serve as a mentor to the sales team. - Delegate responsibilities to the sales staff, as needed. - Demonstrate basic knowledge in retail, including inventory management, visual merchandising, customer service and daily processes. - Operate business profitably and minimize potential for loss, while protecting store assets and inventory. - Supports new initiatives in line with business strategy and goals. Customer Service: - Deliver a personalized client experience by leading with exceptional service on the sales floor, greeting customers in a timely and engaging manner, and providing styling advice that reflects the brand’s aesthetic using product knowledge. - Drive business growth and meet sales goals as an individual and as part of the store team, by addressing customer needs and preferences. - Build and maintain client relationships. General: - Partner with the Store Manager to oversee basic inventory management. - Assist in monthly inventory counts to execute verification processes, as needed. - Arrive on time and be floor ready with a professional presence in line with the DÔEN brand, and respond promptly to internal and external communication. - Maintain visual standards on a daily basis, while supporting a visually enticing store and backstock that is neat, clean, and organized. - Understanding of receiving and processing merchandise/inventory management. - Perform daily operations and closing procedures. - Be proactive and take initiative. - Understand and follow employee handbook and company guidelines including but not limited to core values, dress code guidelines and customer service guidelines. - Process sales and returns through the POS systems with accuracy and efficiency. - Abide by company policies. We'll output each as
        • . Qualifications: - Minimum 1 years experience in a supervisor role within a fashion retail environment, luxury retail preferred. - Energetic, confident and adaptable personality, with critical thinking and problem solving skills. - Excellent communication and organizational skills, detail-oriented. - Ability to multi-task in a fast-paced environment. - Ability to work a flexible schedule including holidays and weekends. - Technological competency and computer literacy; experience with NetSuite, Shopify and Gladly desired. Physical Requirements could be added under Qualifications as separate bullet? But they are separate. Could we add a

          Requirements? But we already used Qualifications. Maybe we can add a

          Requirements for physical requirements. Let's do that:

          Requirements

          with list of physical requirements. Physical Requirements list: - Must be able to perform essential duties satisfactorily with reasonable accommodation. - Ability to move through a store for most of a shift to help customers and accomplish assigned tasks. - Efficiently and accurately process sales transactions using the POS register system. - Verbal and written communication with others. - Able to walk, sit and stand for long periods of time. - Able to operate equipment such as computers, copy machines, phones. - Must be able to access various areas of a given location and lift/move/push/pull objects up to 25lbs minimum including fixtures and product. We could also include "Must be able to perform essential duties satisfactorily with reasonable accommodation." as first. Now Benefits: - Paid vacation, sick time, and holidays. - Healthcare, Vision, Dental. - 401k plan w/company match. - Competitive salary with additional discretionary bonuses based on store performance. Pay: - Hourly Rate $32.00/hour (or $32 USD). We'll state $32.00/hour. We should not include "Compensation will be determined based on experience and other factors permitted by law." That's vague/filler? It's somewhat specific but maybe considered filler? It says compensation will be determined based on experience and other factors permitted by law. That's generic; maybe we should omit as filler? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. This line is not exactly filler but it's generic; but we already have Pay section with specific hourly rate. The line about compensation determined based on experience is somewhat redundant with the hourly rate; we could omit it to avoid filler. It's not required to preserve all info? The instruction says "Preserve ALL substantive information; do NOT invent