store manager, Hollywood, FL
. But we need to decide if we include Responsibilities section only if there is real specific content. There is some content about leading team, etc. Could be considered responsibilities. Requirements: The list: 3 years retail/customer service management experience OR 4+ years US Military service; Strong organizational, interpersonal and problem solving skills; Entrepreneurial mentality with experience in a sales focused environment; Strong leadership skills and ability to coach and mentor team partners with professional maturity; Minimum High School or GED; Legal documentation establishing identity and eligibility; Ability to work full time (regularly demands >40 hrs/week) including variable hours early mornings, evenings, weekends and/or holidays. Qualifications: Might overlap with requirements; but we could treat requirements as qualifications. However we need to decide sections: maybe combine Requirements and Qualifications? But spec says use headings for those sections if content exists. We have content for both; but we can split: Requirements = experience/skills; Qualifications = education/legal docs? Might be artificial. Better to have one section "Requirements" containing all those bullet points. And maybe "Qualifications" could be omitted if no distinct content. Skills: Could be extracted from requirements: organizational, interpersonal, problem solving, entrepreneurial mentality, sales experience, leadership, coaching, mentoring. Could be separate but might be thin. Benefits: we have detailed benefits. Pay: we have content about base pay based on factors, not typical to hire at high end. Schedule: we have ability to work full time >40 hrs, variable hours early mornings, evenings, weekends, holidays. That's schedule info. Thus we can create sections: About the role (intro), Responsibilities (maybe leading team, creating moments, etc.), Requirements (bullet list), Benefits (bullet list), Pay (paragraph), Schedule (paragraph). Possibly Skills not needed if covered in Requirements. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: e.g., "medical, dental, vision, basic and supplemental life insurance", etc. Must keep all bullet points.
Let's extract bullet points for requirements:
- 3 years retail / customer service management experience OR 4+ years of US Military service
- Strong organizational, interpersonal and problem solving skills
- Entrepreneurial mentality with experience in a sales focused environment
- Strong leadership skills and the ability to coach and mentor team partners with professional maturity
- Minimum High School or GED
- Legal documentation establishing your identity and eligibility to be legally employed in the country in which you apply
- Ability to work full time (the work regularly demands in excess of 40 hours per week) including variable hours including early mornings, evenings, weekends and/or holidays
Note: The last one is schedule but also a requirement. We'll maybe keep it under Requirements but also schedule section. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it in both sections, that's duplication but not invented. Might be okay but could be considered redundant. Better to place schedule info only under Schedule section, and not duplicate in Requirements. But the requirement includes ability to work full time etc. That's also schedule. We could keep it under Requirements as a requirement, and also under Schedule as schedule details. But that duplicates. The instruction didn't forbid duplication, but says preserve all substantive information; duplication preserves it. However they might prefer not to duplicate. I'd rather keep it under Requirements as a requirement, and Schedule section could be omitted if no distinct schedule beyond that. But we have schedule info: variable hours etc. That's same as requirement. Could still have Schedule section with same info; but that would be duplication. Might be okay but they said prefer a few substantive sections over many thin ones. Duplication would create thin schedule section maybe same as requirement. Better to put schedule info under Requirements and not create separate Schedule section unless there is additional schedule info beyond that. There is no extra schedule info besides that. So we can omit Schedule section.
Pay section: we have paragraph about base pay based on factors, not typical to hire at high end. That's specific.
Benefits: we have many details; we need to list them as bullet points.
Let's extract benefits bullet list:
- medical, dental, vision, basic and supplemental life insurance, and other voluntary insurance benefits
- short-term and long-term disability
- paid parental leave
- family expansion reimbursement
- paid vacation from date of hire*
- sick time (accrued at 1 hour for every 25 hours worked)
- eight paid holidays
- two personal days per year
- participation in a 401(k) retirement plan with employer match
- discounted company stock program (S.I.P.)
- Starbucks equity program (Bean Stock)
- incentivized emergency savings
- financial well-being tools
- 100% upfront tuition coverage for a first-time bachelor’s degree through Arizona State University’s online program via the Starbucks College Achievement Plan
- student loan management resources
- access to other educational opportunities
- backup care
- DACA reimbursement
- compliance with applicable state and local laws regarding employee leave benefits, including, but not limited to providing time off pursuant to the Colorado Healthy Families and Workplaces Act, and in accordance with its plans and policies
- list subject to change depending on collective bargaining in locations where partners have a certified bargaining representative
- For additional information regarding partner perks and more detailed information about benefits, go to starbucksbenefits.com (maybe we keep as link? but we should not invent; we can keep as plain text)
- If you are working in CA, CO, IL, LA, ME, MA, NE, ND or RI, you will accrue vacation up to a maximum of 120 hours (190 in CA) for roles below director and 200 hours (316 in CA) for roles at director or above.
- For roles in other states, you will be granted vacation time starting at 120 hours annually for roles below director and 200 hours annually for roles director and above.
We need to keep all that.
Now About the role: The introductory paragraph(s) before "We'd Love To Hear From People With". Let's capture:
"Crafting the world’s finest coffee, one meaningful moment at a time We believe in creating a warm and welcoming space where every cup of coffee sparks connection. As a coffeehouse leader, you don’t just run a business—you lead a team that creates moments of connection and joy. Every day provides an opportunity to lead with craft and heart, making your coffeehouse a place where your community feels welcome. We are invested in your growth journey, empowered through developmental experiences as well as our industry leading benefits."
That's about the role.
Responsibilities: maybe after that: "We'd Love To Hear From People With ..."? Actually that's start of requirements. Responsibilities could be: leading team, creating moments of connection and joy, leading with craft and heart, making coffeehouse welcoming, growth journey, etc. But we already used that in About the role. Might be better to treat About the role as overview, Responsibilities as specific duties: leading a team, creating moments of connection and joy, leading with craft and heart, making coffeehouse welcoming, investing in growth journey, etc. However that overlaps.
Given the instruction to prefer few substantive sections, we could combine About the role and Responsibilities into one section? But spec says use headings
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: e.g., "medical, dental, vision, basic and supplemental life insurance", etc. Must keep all bullet points. Let's extract bullet points for requirements: - 3 years retail / customer service management experience OR 4+ years of US Military service - Strong organizational, interpersonal and problem solving skills - Entrepreneurial mentality with experience in a sales focused environment - Strong leadership skills and the ability to coach and mentor team partners with professional maturity - Minimum High School or GED - Legal documentation establishing your identity and eligibility to be legally employed in the country in which you apply - Ability to work full time (the work regularly demands in excess of 40 hours per week) including variable hours including early mornings, evenings, weekends and/or holidays Note: The last one is schedule but also a requirement. We'll maybe keep it under Requirements but also schedule section. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it in both sections, that's duplication but not invented. Might be okay but could be considered redundant. Better to place schedule info only under Schedule section, and not duplicate in Requirements. But the requirement includes ability to work full time etc. That's also schedule. We could keep it under Requirements as a requirement, and also under Schedule as schedule details. But that duplicates. The instruction didn't forbid duplication, but says preserve all substantive information; duplication preserves it. However they might prefer not to duplicate. I'd rather keep it under Requirements as a requirement, and Schedule section could be omitted if no distinct schedule beyond that. But we have schedule info: variable hours etc. That's same as requirement. Could still have Schedule section with same info; but that would be duplication. Might be okay but they said prefer a few substantive sections over many thin ones. Duplication would create thin schedule section maybe same as requirement. Better to put schedule info under Requirements and not create separate Schedule section unless there is additional schedule info beyond that. There is no extra schedule info besides that. So we can omit Schedule section. Pay section: we have paragraph about base pay based on factors, not typical to hire at high end. That's specific. Benefits: we have many details; we need to list them as bullet points. Let's extract benefits bullet list: - medical, dental, vision, basic and supplemental life insurance, and other voluntary insurance benefits - short-term and long-term disability - paid parental leave - family expansion reimbursement - paid vacation from date of hire* - sick time (accrued at 1 hour for every 25 hours worked) - eight paid holidays - two personal days per year - participation in a 401(k) retirement plan with employer match - discounted company stock program (S.I.P.) - Starbucks equity program (Bean Stock) - incentivized emergency savings - financial well-being tools - 100% upfront tuition coverage for a first-time bachelor’s degree through Arizona State University’s online program via the Starbucks College Achievement Plan - student loan management resources - access to other educational opportunities - backup care - DACA reimbursement - compliance with applicable state and local laws regarding employee leave benefits, including, but not limited to providing time off pursuant to the Colorado Healthy Families and Workplaces Act, and in accordance with its plans and policies - list subject to change depending on collective bargaining in locations where partners have a certified bargaining representative - For additional information regarding partner perks and more detailed information about benefits, go to starbucksbenefits.com (maybe we keep as link? but we should not invent; we can keep as plain text) - If you are working in CA, CO, IL, LA, ME, MA, NE, ND or RI, you will accrue vacation up to a maximum of 120 hours (190 in CA) for roles below director and 200 hours (316 in CA) for roles at director or above. - For roles in other states, you will be granted vacation time starting at 120 hours annually for roles below director and 200 hours annually for roles director and above. We need to keep all that. Now About the role: The introductory paragraph(s) before "We'd Love To Hear From People With". Let's capture: "Crafting the world’s finest coffee, one meaningful moment at a time We believe in creating a warm and welcoming space where every cup of coffee sparks connection. As a coffeehouse leader, you don’t just run a business—you lead a team that creates moments of connection and joy. Every day provides an opportunity to lead with craft and heart, making your coffeehouse a place where your community feels welcome. We are invested in your growth journey, empowered through developmental experiences as well as our industry leading benefits." That's about the role. Responsibilities: maybe after that: "We'd Love To Hear From People With ..."? Actually that's start of requirements. Responsibilities could be: leading team, creating moments of connection and joy, leading with craft and heart, making coffeehouse welcoming, growth journey, etc. But we already used that in About the role. Might be better to treat About the role as overview, Responsibilities as specific duties: leading a team, creating moments of connection and joy, leading with craft and heart, making coffeehouse welcoming, investing in growth journey, etc. However that overlaps. Given the instruction to prefer few substantive sections, we could combine About the role and Responsibilities into one section? But spec says use headings