Team Member
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. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting has:
- Position Overview: prose about role.
- Core Responsibilities: list of duties (multiple bullet-like sentences).
- Skills And Qualifications: Required and Preferred.
- Benefits: list.
- Address: location.
- Compensation Range: pay range.
- Physical demands etc: maybe not needed? It's substantive but not a standard section; we could include under a "Details" or "Additional Information". But we must only use headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly create other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we could use other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings when applicable. We can also include a heading like "Location" if needed? Not in list. Might be safer to stick to those headings. We have content for: About the role (Position Overview), Responsibilities (Core Responsibilities), Skills (Skills And Qualifications), Benefits (Benefits), Pay (Compensation Range). Schedule? Not explicitly given, but there is "Ability to work a flexible schedule, including early mornings, evenings, weekends, nights, and holidays". That's schedule info. Could include Schedule section. Requirements? Could be under Skills? The posting has Required and Preferred under Skills And Qualifications. Could split into Requirements and Qualifications? But we have Skills heading; we could put both required and preferred under Skills. Or we could have Requirements and Qualifications separate. The instruction says we can use those headings; we need to decide.
We must not create sections with filler. So we need actual content.
Let's extract:
Position Overview paragraph: "At Caribou Coffee we create day-making experiences that spark a chain reaction of GOOD! This is our purpose. Our team brings this to life by focusing on what’s really important around here – TEAM, GUEST, BUSINESS! It’s that simple. If you’re ready to work somewhere you can be yourself while making an impact on your community, creating life-long relationships, and serving the best coffee around, join our herd! Apply today and be part of the ‘Bou Crew! Position Overview: The Team Member is the core of the Caribou Coffee experience. They are responsible for creating day-making experiences through delivering unparalleled guest service, making exceptional hand-crafted beverages and bringing the Purpose and Values of Caribou to life in every interaction."
We can combine the intro and Position Overview into a prose
under About the role.
Core Responsibilities: list of bullet points:
- No previous experience required.
- Delivers guest service that builds real connections, active listening, personal attention, and the small moments that make someone's day
- Hand-crafts beverages and prepares food to standard recipes, customizing to Guest preferences
- Confidently moves between barista, greeter, and any other role the shift calls for, ready to take on whatever task is needed in the moment
- Takes orders and manages the cash drawer accurately, following cash-handling, safety, and security standards
- Keeps the coffeehouse clean, organized, and well-stocked, meeting Caribou's operating standards for quality and safety
- Anticipates what's needed next for a Guest or a teammate and acts on it before being asked
- Makes recommendations to Guests grounded in real product knowledge, not just a script
- Knows the difference between a problem to solve on the spot and one that calls for a leader, and asks for support accordingly
- Takes direction from leaders and understands the team is balancing multiple priorities at once
- Shows up for every scheduled shift on time and ready to go, maintaining reliable, consistent attendance
- Brings the Core Values to life in all that you do: Support One Another, Make Fun Happen, Be Yourself, Take Ownership, Serve with Love
- Brings exceptional and engaging energy to the shift, making fun happen with teammates, and for Guests
- Approaches the role with a learner's mindset, always looking to sharpen skills and improve
- Shows up as a dependable teammate, staying steady under pressure and asking for help when needed
- Takes ownership of the impact they have on the people around them
We need to output as
- items.
Skills And Qualifications:
Required:
- Must be at least 16 years of age
- Ability to work a flexible schedule, including early mornings, evenings, weekends, nights, and holidays as the coffeehouse needs
- Excellent customer service mindset
- Ability to thrive in a fast-paced environment
- Passion for coffee, hospitality, and being part of a team
Preferred:
- Restaurant, retail, or guest service experience.
Benefits:
- Employee Discount & Free Shift Drink
- Flexible schedule
- Growth Opportunities
- Tips
Address: "3673 Lexington Avenue N , Arden Hills, Minnesota 55126"
Compensation Range: "$11.23 - $18.71 per hour Starting pay is subject to Local and State Minimum Wage regulations. Ranges reflect what employer reasonably and in good faith expects to pay for such position."
Physical demands etc: maybe we can include under a "Details" section but not in allowed headings. Could we include under About the role? Probably not. Could we drop it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep physical demands info. Where to put? Could create a section "Details" but not in list. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g ...)". It implies we should use those headings for sections. But we could also add other headings if needed, but better to stick to those. Physical demands could be placed under "About the role" as additional prose? Might be okay but it's not about role overview. Could be under "Responsibilities"? Not exactly. Could be under "Requirements"? Not exactly. Could be under "Qualifications"? Not exactly. Could be under "Skills"? Not exactly. Could be under "Pay"? Not exactly. Could be under "Schedule"? Not exactly.
Maybe we can create a section "Details" using Details
. The instruction didn't explicitly forbid other headings, just gave examples. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when we have those sections. It doesn't say we cannot use other headings. But to be safe, we could incorporate physical demands into a
under About the role or maybe under Responsibilities as an extra bullet? It's not a responsibility but a requirement. Could be under Requirements (if we make a Requirements section). We could create a Requirements section for age, schedule, etc, and Qualifications for preferred experience. Then physical demands could be under Requirements as well? It's more about physical demands, which could be a qualification. Might be okay to put under Requirements.
Let's plan sections:
- About the role (Position Overview + intro)
- Responsibilities (Core Responsibilities)
- Requirements (Required: age, schedule, customer service mindset, fast-paced, passion, physical demands?)
- Qualifications (Preferred: restaurant/retail/guest service experience)
- Skills (maybe we could combine required skills? But we already have Requirements. Could also have Skills for things like customer service mindset, thriving in fast-paced, passion for coffee, etc. But we already have those in Requirements. Might be redundant. Better to follow the example: Skills And Qualifications heading. Could split into Skills and Qualifications. But we have both Required and Preferred. Could treat Required as Skills, Preferred as Qualifications. Let's do:
- Skills (Required)
- Qualifications (Preferred)
- Benefits
- Pay (Compensation Range)
- Schedule (maybe we already have schedule in Skills; but we could also have Schedule section with flexible schedule info. However we already have schedule in Skills. To avoid duplication, we could put schedule info under Skills (Required) and not create a separate Schedule section unless there is extra schedule info beyond that. The posting only mentions flexible schedule as part of required ability. So we could keep it under Skills.
- Location? Could be a short
after sections.
We must not repeat job title as heading. Good.
We need to output only HTML fragment.
Let's craft:
About the role
At Caribou Coffee we create day-making experiences that spark a chain reaction of GOOD! This is our purpose. Our team brings this to life by focusing on what’s really important around here – TEAM, GUEST, BUSINESS! It’s that simple. If you’re ready to work somewhere you can be yourself while making an impact on your community, creating life-long relationships, and serving the best coffee around, join our herd! Apply today and be part of the ‘Bou Crew! The Team Member is the core of the Caribou Coffee experience. They are responsible for creating day-making experiences through delivering unparalleled guest service, making exceptional hand-crafted beverages and bringing the Purpose and Values of Caribou to life in every interaction.
Responsibilities
- No previous experience required.
- Delivers guest service that builds real connections, active listening, personal attention, and the small moments that make someone's day
- Hand-crafts beverages and prepares food to standard recipes, customizing to Guest preferences
- Confidently moves between barista, greeter, and any other role the shift calls for, ready to take on whatever task is needed in the moment
- Takes orders and manages the cash drawer accurately, following cash-handling, safety, and security standards
- Keeps the coffeehouse clean, organized, and well-stocked, meeting Caribou's operating standards for quality and safety
- Anticipates what's needed next for a Guest or a teammate and acts on it before being asked
- Makes recommendations to Guests grounded in real product knowledge, not just a script
- Knows the difference between a problem to solve on the spot and one that calls for
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting has: - Position Overview: prose about role. - Core Responsibilities: list of duties (multiple bullet-like sentences). - Skills And Qualifications: Required and Preferred. - Benefits: list. - Address: location. - Compensation Range: pay range. - Physical demands etc: maybe not needed? It's substantive but not a standard section; we could include under a "Details" or "Additional Information". But we must only use headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly create other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we could use other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings when applicable. We can also include a heading like "Location" if needed? Not in list. Might be safer to stick to those headings. We have content for: About the role (Position Overview), Responsibilities (Core Responsibilities), Skills (Skills And Qualifications), Benefits (Benefits), Pay (Compensation Range). Schedule? Not explicitly given, but there is "Ability to work a flexible schedule, including early mornings, evenings, weekends, nights, and holidays". That's schedule info. Could include Schedule section. Requirements? Could be under Skills? The posting has Required and Preferred under Skills And Qualifications. Could split into Requirements and Qualifications? But we have Skills heading; we could put both required and preferred under Skills. Or we could have Requirements and Qualifications separate. The instruction says we can use those headings; we need to decide.
We must not create sections with filler. So we need actual content.
Let's extract:
Position Overview paragraph: "At Caribou Coffee we create day-making experiences that spark a chain reaction of GOOD! This is our purpose. Our team brings this to life by focusing on what’s really important around here – TEAM, GUEST, BUSINESS! It’s that simple. If you’re ready to work somewhere you can be yourself while making an impact on your community, creating life-long relationships, and serving the best coffee around, join our herd! Apply today and be part of the ‘Bou Crew! Position Overview: The Team Member is the core of the Caribou Coffee experience. They are responsible for creating day-making experiences through delivering unparalleled guest service, making exceptional hand-crafted beverages and bringing the Purpose and Values of Caribou to life in every interaction."
We can combine the intro and Position Overview into a prose
under About the role. Core Responsibilities: list of bullet points: - No previous experience required. - Delivers guest service that builds real connections, active listening, personal attention, and the small moments that make someone's day - Hand-crafts beverages and prepares food to standard recipes, customizing to Guest preferences - Confidently moves between barista, greeter, and any other role the shift calls for, ready to take on whatever task is needed in the moment - Takes orders and manages the cash drawer accurately, following cash-handling, safety, and security standards - Keeps the coffeehouse clean, organized, and well-stocked, meeting Caribou's operating standards for quality and safety - Anticipates what's needed next for a Guest or a teammate and acts on it before being asked - Makes recommendations to Guests grounded in real product knowledge, not just a script - Knows the difference between a problem to solve on the spot and one that calls for a leader, and asks for support accordingly - Takes direction from leaders and understands the team is balancing multiple priorities at once - Shows up for every scheduled shift on time and ready to go, maintaining reliable, consistent attendance - Brings the Core Values to life in all that you do: Support One Another, Make Fun Happen, Be Yourself, Take Ownership, Serve with Love - Brings exceptional and engaging energy to the shift, making fun happen with teammates, and for Guests - Approaches the role with a learner's mindset, always looking to sharpen skills and improve - Shows up as a dependable teammate, staying steady under pressure and asking for help when needed - Takes ownership of the impact they have on the people around them We need to output as
- items.
Skills And Qualifications:
Required:
- Must be at least 16 years of age
- Ability to work a flexible schedule, including early mornings, evenings, weekends, nights, and holidays as the coffeehouse needs
- Excellent customer service mindset
- Ability to thrive in a fast-paced environment
- Passion for coffee, hospitality, and being part of a team
Preferred:
- Restaurant, retail, or guest service experience.
Benefits:
- Employee Discount & Free Shift Drink
- Flexible schedule
- Growth Opportunities
- Tips
Address: "3673 Lexington Avenue N , Arden Hills, Minnesota 55126"
Compensation Range: "$11.23 - $18.71 per hour Starting pay is subject to Local and State Minimum Wage regulations. Ranges reflect what employer reasonably and in good faith expects to pay for such position."
Physical demands etc: maybe we can include under a "Details" section but not in allowed headings. Could we include under About the role? Probably not. Could we drop it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep physical demands info. Where to put? Could create a section "Details" but not in list. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g ...)". It implies we should use those headings for sections. But we could also add other headings if needed, but better to stick to those. Physical demands could be placed under "About the role" as additional prose? Might be okay but it's not about role overview. Could be under "Responsibilities"? Not exactly. Could be under "Requirements"? Not exactly. Could be under "Qualifications"? Not exactly. Could be under "Skills"? Not exactly. Could be under "Pay"? Not exactly. Could be under "Schedule"? Not exactly. Maybe we can create a section "Details" using
Details
. The instruction didn't explicitly forbid other headings, just gave examples. It says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when we have those sections. It doesn't say we cannot use other headings. But to be safe, we could incorporate physical demands into a
under About the role or maybe under Responsibilities as an extra bullet? It's not a responsibility but a requirement. Could be under Requirements (if we make a Requirements section). We could create a Requirements section for age, schedule, etc, and Qualifications for preferred experience. Then physical demands could be under Requirements as well? It's more about physical demands, which could be a qualification. Might be okay to put under Requirements. Let's plan sections: - About the role (Position Overview + intro) - Responsibilities (Core Responsibilities) - Requirements (Required: age, schedule, customer service mindset, fast-paced, passion, physical demands?) - Qualifications (Preferred: restaurant/retail/guest service experience) - Skills (maybe we could combine required skills? But we already have Requirements. Could also have Skills for things like customer service mindset, thriving in fast-paced, passion for coffee, etc. But we already have those in Requirements. Might be redundant. Better to follow the example: Skills And Qualifications heading. Could split into Skills and Qualifications. But we have both Required and Preferred. Could treat Required as Skills, Preferred as Qualifications. Let's do: - Skills (Required) - Qualifications (Preferred) - Benefits - Pay (Compensation Range) - Schedule (maybe we already have schedule in Skills; but we could also have Schedule section with flexible schedule info. However we already have schedule in Skills. To avoid duplication, we could put schedule info under Skills (Required) and not create a separate Schedule section unless there is extra schedule info beyond that. The posting only mentions flexible schedule as part of required ability. So we could keep it under Skills. - Location? Could be a short
after sections. We must not repeat job title as heading. Good. We need to output only HTML fragment. Let's craft:
About the role
At Caribou Coffee we create day-making experiences that spark a chain reaction of GOOD! This is our purpose. Our team brings this to life by focusing on what’s really important around here – TEAM, GUEST, BUSINESS! It’s that simple. If you’re ready to work somewhere you can be yourself while making an impact on your community, creating life-long relationships, and serving the best coffee around, join our herd! Apply today and be part of the ‘Bou Crew! The Team Member is the core of the Caribou Coffee experience. They are responsible for creating day-making experiences through delivering unparalleled guest service, making exceptional hand-crafted beverages and bringing the Purpose and Values of Caribou to life in every interaction.
Responsibilities
- No previous experience required.
- Delivers guest service that builds real connections, active listening, personal attention, and the small moments that make someone's day
- Hand-crafts beverages and prepares food to standard recipes, customizing to Guest preferences
- Confidently moves between barista, greeter, and any other role the shift calls for, ready to take on whatever task is needed in the moment
- Takes orders and manages the cash drawer accurately, following cash-handling, safety, and security standards
- Keeps the coffeehouse clean, organized, and well-stocked, meeting Caribou's operating standards for quality and safety
- Anticipates what's needed next for a Guest or a teammate and acts on it before being asked
- Makes recommendations to Guests grounded in real product knowledge, not just a script
- Knows the difference between a problem to solve on the spot and one that calls for