Host/Cashier
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include section ONLY when posting has real, specific content for it
- Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content:
"Why JDK" section has:
- Competitive pay - Based on experience, with a clear path as your impact grows.
- Work-life balance - Flexible scheduling options that work for you.
- Benefits package - Medical, dental, vision, paid time off, and 401(k) with company match. Subject to terms and conditions.
- Values-driven culture - We're Hungry, Humble, and Smart — and we hire people who work the same way.
This is essentially Benefits and Pay and Schedule info. The posting does state pay (competitive, based on experience), schedule (flexible scheduling), and benefits (medical, dental, vision, PTO, 401k match). So we can create sections for Pay, Schedule, Benefits, and maybe Culture/Values.
But the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, the headings should be standard: Pay, Schedule, Benefits. The "Why JDK" heading is not standard; we should use standard headings.
"Who we are" - company background. Could be "About the company" but the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who we are" is not in that list. But we can include it as a section? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But better to stick to those. However, "Who we are" is substantive company info. Could be folded into "About the role" or separate? The rules say "include a section ONLY when the posting has real, specific content for it". The posting has "Who we are" with specific content. But the allowed headings list doesn't include "About the company". The example list includes "About the role". Maybe we can use "About the role" for the role description, and "Who we are" could be a separate heading? But 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 suggests those. I think we can use "About the company" or "Company overview". However, to be safe, I'll include it as a section with heading "About the company" or maybe "Who we are". But the rules say "use for section headings (e.g. ...)". It's not exhaustive. I'll use "About the company" as a heading.
But the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Host/Cashier". The posting starts with "Why JDK" then "Who we are" then "The role". So we should not have a heading "Host/Cashier". Good.
Now, "The role" section: "We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift." This is "About the role".
"What You'll Do" is Responsibilities.
"How you'll thrive" - this seems like Qualifications or Skills. It says: "Take initiative and look for ways to improve in your daily work. Put the team first, stay open to feedback, and lead with respect. Communicate thoughtfully and navigate situations with good judgment." These are behavioral competencies. Could be "Qualifications" or "Skills". The allowed headings include Qualifications and Skills. I'll use "Qualifications" for "What you'll need" and maybe "Skills" for "How you'll thrive"? But "What you'll need" is clearly Requirements. "How you'll thrive" is more about how to succeed, maybe "Qualifications" or "Success factors". I'll combine "How you'll thrive" into "Qualifications" or make a separate "Skills" section. The rules say prefer few substantive sections over many thin ones. So maybe combine "How you'll thrive" and "What you'll need" into "Requirements" or "Qualifications". But "What you'll need" has specific requirements: no experience required, prior experience a plus, ability to work fast-paced, lift 50 lbs, stand/walk/reach/bend. "How you'll thrive" is more soft skills. Could be "Qualifications" for the soft skills and "Requirements" for the physical/experience requirements. However, the allowed headings include both Requirements and Qualifications. I'll create two sections: "Requirements" for "What you'll need" and "Qualifications" for "How you'll thrive". But "Qualifications" often includes both. Let's see typical usage: Requirements = must-haves, Qualifications = nice-to-haves or broader. The posting says "What you'll need" and "How you'll thrive". I'll map "What you'll need" to "Requirements" and "How you'll thrive" to "Qualifications". That seems reasonable.
Now, "Why JDK" contains Pay, Schedule, Benefits, and Culture. I'll create separate sections for Pay, Schedule, Benefits, and maybe "Culture" or "Values". But the allowed headings don't include Culture. However, the posting has "Values-driven culture". Could be part of "About the company" or a separate "Values" section. Since the rules say "use for section headings (e.g. ...)" and not limited to only those, I can add a "Culture" heading. But to keep it standard, maybe include culture in "About the company". The "Who we are" already includes values. So I'll combine "Who we are" and "Values-driven culture" into "About the company". Then "Why JDK" has Pay, Schedule, Benefits. I'll create three sections: Pay, Schedule, Benefits.
But note: The Pay description: "Competitive pay - Based on experience, with a clear path as your impact grows." That's specific enough. Schedule: "Work-life balance - Flexible scheduling options that work for you." Benefits: "Benefits package - Medical, dental, vision, paid time off, and 401(k) with company match. Subject to terms and conditions." So we have content for each.
Now, the disclaimer, E-Verify, EEO, franchise info are boilerplate to remove.
Now, structure:
1. About the company (combining Who we are and Values-driven culture)
2. About the role (The role)
3. Responsibilities (What You'll Do)
4. Qualifications (How you'll thrive)
5. Requirements (What you'll need)
6. Pay
7. Schedule
8. Benefits
But the rules say "Prefer a few substantive sections over many thin ones." Having 8 sections might be many. But each has content. Could combine Pay, Schedule, Benefits into a "Benefits" section? But they are distinct. The allowed headings include Pay, Schedule, Benefits separately. So it's okay.
Alternatively, combine Pay and Schedule into "Compensation & Schedule"? But the example headings are separate. I'll keep separate.
Now, write HTML.
For each section, use for heading, then content. For lists, use - . For prose, use
.
Let's draft:
About the company
Founded in 1958 as a single pancake house in Ohio, Perkins has grown into a leading family dining restaurant known for friendly service, classic comfort food, and great value. Since 1982, JDK has continued to build on Perkins' legacy by serving as the largest franchiser of the brand. Our success is driven by people who live out our guiding principles every day: Stay Hungry, Be Humble, and Work Smart. It's how we collaborate, grow, and support one another – creating an environment where team members can thrive while delivering exceptional experiences to our guests. We're Hungry, Humble, and Smart — and we hire people who work the same way.
About the role
We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift.
Responsibilities
- Greet guests with a friendly and welcoming attitude and provide excellent customer service.
- Manage seating arrangements and wait lists to ensure smooth restaurant flow and guest satisfaction.
- Accurately process guest payments and handle cash, credit card, and other transactions responsibly.
- Answer phones, assist guests with questions, and support carryout or to-go orders as needed.
- Maintain cleanliness and organization of the host stand, front entrance, and dining areas.
- Communicate effectively with servers, kitchen staff, and managers to support efficient operations.
- Perform additional duties as assigned.
Qualifications
- Take initiative and look for ways to improve in your daily work.
- Put the team first, stay open to feedback, and lead with respect.
- Communicate thoughtfully and navigate situations with good judgment.
Requirements
- No experience is required; prior host/cashier experience is a plus.
- Ability to work in a fast-paced, team-oriented environment.
- Ability to lift and carry up to 50 lbs.
- Ability to stand, walk, reach, and bend for extended periods.
Pay
Competitive pay based on experience, with a clear path as your impact grows.
Schedule
Flexible scheduling options that work for you.
Benefits
Medical, dental, vision, paid time off, and 401(k) with company match (subject to terms and conditions).
Check: The "Why JDK" also had "Values-driven
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content: "Why JDK" section has: - Competitive pay - Based on experience, with a clear path as your impact grows. - Work-life balance - Flexible scheduling options that work for you. - Benefits package - Medical, dental, vision, paid time off, and 401(k) with company match. Subject to terms and conditions. - Values-driven culture - We're Hungry, Humble, and Smart — and we hire people who work the same way. This is essentially Benefits and Pay and Schedule info. The posting does state pay (competitive, based on experience), schedule (flexible scheduling), and benefits (medical, dental, vision, PTO, 401k match). So we can create sections for Pay, Schedule, Benefits, and maybe Culture/Values. But the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, the headings should be standard: Pay, Schedule, Benefits. The "Why JDK" heading is not standard; we should use standard headings. "Who we are" - company background. Could be "About the company" but the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who we are" is not in that list. But we can include it as a section? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But better to stick to those. However, "Who we are" is substantive company info. Could be folded into "About the role" or separate? The rules say "include a section ONLY when the posting has real, specific content for it". The posting has "Who we are" with specific content. But the allowed headings list doesn't include "About the company". The example list includes "About the role". Maybe we can use "About the role" for the role description, and "Who we are" could be a separate heading? But 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 suggests those. I think we can use "About the company" or "Company overview". However, to be safe, I'll include it as a section with heading "About the company" or maybe "Who we are". But the rules say "use for section headings (e.g. ...)". It's not exhaustive. I'll use "About the company" as a heading.
But the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Host/Cashier". The posting starts with "Why JDK" then "Who we are" then "The role". So we should not have a heading "Host/Cashier". Good.
Now, "The role" section: "We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift." This is "About the role".
"What You'll Do" is Responsibilities.
"How you'll thrive" - this seems like Qualifications or Skills. It says: "Take initiative and look for ways to improve in your daily work. Put the team first, stay open to feedback, and lead with respect. Communicate thoughtfully and navigate situations with good judgment." These are behavioral competencies. Could be "Qualifications" or "Skills". The allowed headings include Qualifications and Skills. I'll use "Qualifications" for "What you'll need" and maybe "Skills" for "How you'll thrive"? But "What you'll need" is clearly Requirements. "How you'll thrive" is more about how to succeed, maybe "Qualifications" or "Success factors". I'll combine "How you'll thrive" into "Qualifications" or make a separate "Skills" section. The rules say prefer few substantive sections over many thin ones. So maybe combine "How you'll thrive" and "What you'll need" into "Requirements" or "Qualifications". But "What you'll need" has specific requirements: no experience required, prior experience a plus, ability to work fast-paced, lift 50 lbs, stand/walk/reach/bend. "How you'll thrive" is more soft skills. Could be "Qualifications" for the soft skills and "Requirements" for the physical/experience requirements. However, the allowed headings include both Requirements and Qualifications. I'll create two sections: "Requirements" for "What you'll need" and "Qualifications" for "How you'll thrive". But "Qualifications" often includes both. Let's see typical usage: Requirements = must-haves, Qualifications = nice-to-haves or broader. The posting says "What you'll need" and "How you'll thrive". I'll map "What you'll need" to "Requirements" and "How you'll thrive" to "Qualifications". That seems reasonable.
Now, "Why JDK" contains Pay, Schedule, Benefits, and Culture. I'll create separate sections for Pay, Schedule, Benefits, and maybe "Culture" or "Values". But the allowed headings don't include Culture. However, the posting has "Values-driven culture". Could be part of "About the company" or a separate "Values" section. Since the rules say "use for section headings (e.g. ...)" and not limited to only those, I can add a "Culture" heading. But to keep it standard, maybe include culture in "About the company". The "Who we are" already includes values. So I'll combine "Who we are" and "Values-driven culture" into "About the company". Then "Why JDK" has Pay, Schedule, Benefits. I'll create three sections: Pay, Schedule, Benefits.
But note: The Pay description: "Competitive pay - Based on experience, with a clear path as your impact grows." That's specific enough. Schedule: "Work-life balance - Flexible scheduling options that work for you." Benefits: "Benefits package - Medical, dental, vision, paid time off, and 401(k) with company match. Subject to terms and conditions." So we have content for each.
Now, the disclaimer, E-Verify, EEO, franchise info are boilerplate to remove.
Now, structure:
1. About the company (combining Who we are and Values-driven culture)
2. About the role (The role)
3. Responsibilities (What You'll Do)
4. Qualifications (How you'll thrive)
5. Requirements (What you'll need)
6. Pay
7. Schedule
8. Benefits
But the rules say "Prefer a few substantive sections over many thin ones." Having 8 sections might be many. But each has content. Could combine Pay, Schedule, Benefits into a "Benefits" section? But they are distinct. The allowed headings include Pay, Schedule, Benefits separately. So it's okay.
Alternatively, combine Pay and Schedule into "Compensation & Schedule"? But the example headings are separate. I'll keep separate.
Now, write HTML.
For each section, use for heading, then content. For lists, use - . For prose, use
.
Let's draft:
About the company
Founded in 1958 as a single pancake house in Ohio, Perkins has grown into a leading family dining restaurant known for friendly service, classic comfort food, and great value. Since 1982, JDK has continued to build on Perkins' legacy by serving as the largest franchiser of the brand. Our success is driven by people who live out our guiding principles every day: Stay Hungry, Be Humble, and Work Smart. It's how we collaborate, grow, and support one another – creating an environment where team members can thrive while delivering exceptional experiences to our guests. We're Hungry, Humble, and Smart — and we hire people who work the same way.
About the role
We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift.
Responsibilities
- Greet guests with a friendly and welcoming attitude and provide excellent customer service.
- Manage seating arrangements and wait lists to ensure smooth restaurant flow and guest satisfaction.
- Accurately process guest payments and handle cash, credit card, and other transactions responsibly.
- Answer phones, assist guests with questions, and support carryout or to-go orders as needed.
- Maintain cleanliness and organization of the host stand, front entrance, and dining areas.
- Communicate effectively with servers, kitchen staff, and managers to support efficient operations.
- Perform additional duties as assigned.
Qualifications
- Take initiative and look for ways to improve in your daily work.
- Put the team first, stay open to feedback, and lead with respect.
- Communicate thoughtfully and navigate situations with good judgment.
Requirements
- No experience is required; prior host/cashier experience is a plus.
- Ability to work in a fast-paced, team-oriented environment.
- Ability to lift and carry up to 50 lbs.
- Ability to stand, walk, reach, and bend for extended periods.
Pay
Competitive pay based on experience, with a clear path as your impact grows.
Schedule
Flexible scheduling options that work for you.
Benefits
Medical, dental, vision, paid time off, and 401(k) with company match (subject to terms and conditions).
Check: The "Why JDK" also had "Values-driven
for section headings (e.g. ...)". It's not exhaustive. I'll use "About the company" as a heading.
But the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Host/Cashier". The posting starts with "Why JDK" then "Who we are" then "The role". So we should not have a heading "Host/Cashier". Good.
Now, "The role" section: "We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift." This is "About the role".
"What You'll Do" is Responsibilities.
"How you'll thrive" - this seems like Qualifications or Skills. It says: "Take initiative and look for ways to improve in your daily work. Put the team first, stay open to feedback, and lead with respect. Communicate thoughtfully and navigate situations with good judgment." These are behavioral competencies. Could be "Qualifications" or "Skills". The allowed headings include Qualifications and Skills. I'll use "Qualifications" for "What you'll need" and maybe "Skills" for "How you'll thrive"? But "What you'll need" is clearly Requirements. "How you'll thrive" is more about how to succeed, maybe "Qualifications" or "Success factors". I'll combine "How you'll thrive" into "Qualifications" or make a separate "Skills" section. The rules say prefer few substantive sections over many thin ones. So maybe combine "How you'll thrive" and "What you'll need" into "Requirements" or "Qualifications". But "What you'll need" has specific requirements: no experience required, prior experience a plus, ability to work fast-paced, lift 50 lbs, stand/walk/reach/bend. "How you'll thrive" is more soft skills. Could be "Qualifications" for the soft skills and "Requirements" for the physical/experience requirements. However, the allowed headings include both Requirements and Qualifications. I'll create two sections: "Requirements" for "What you'll need" and "Qualifications" for "How you'll thrive". But "Qualifications" often includes both. Let's see typical usage: Requirements = must-haves, Qualifications = nice-to-haves or broader. The posting says "What you'll need" and "How you'll thrive". I'll map "What you'll need" to "Requirements" and "How you'll thrive" to "Qualifications". That seems reasonable.
Now, "Why JDK" contains Pay, Schedule, Benefits, and Culture. I'll create separate sections for Pay, Schedule, Benefits, and maybe "Culture" or "Values". But the allowed headings don't include Culture. However, the posting has "Values-driven culture". Could be part of "About the company" or a separate "Values" section. Since the rules say "use for section headings (e.g. ...)" and not limited to only those, I can add a "Culture" heading. But to keep it standard, maybe include culture in "About the company". The "Who we are" already includes values. So I'll combine "Who we are" and "Values-driven culture" into "About the company". Then "Why JDK" has Pay, Schedule, Benefits. I'll create three sections: Pay, Schedule, Benefits.
But note: The Pay description: "Competitive pay - Based on experience, with a clear path as your impact grows." That's specific enough. Schedule: "Work-life balance - Flexible scheduling options that work for you." Benefits: "Benefits package - Medical, dental, vision, paid time off, and 401(k) with company match. Subject to terms and conditions." So we have content for each.
Now, the disclaimer, E-Verify, EEO, franchise info are boilerplate to remove.
Now, structure:
1. About the company (combining Who we are and Values-driven culture)
2. About the role (The role)
3. Responsibilities (What You'll Do)
4. Qualifications (How you'll thrive)
5. Requirements (What you'll need)
6. Pay
7. Schedule
8. Benefits
But the rules say "Prefer a few substantive sections over many thin ones." Having 8 sections might be many. But each has content. Could combine Pay, Schedule, Benefits into a "Benefits" section? But they are distinct. The allowed headings include Pay, Schedule, Benefits separately. So it's okay.
Alternatively, combine Pay and Schedule into "Compensation & Schedule"? But the example headings are separate. I'll keep separate.
Now, write HTML.
For each section, use for heading, then content. For lists, use - . For prose, use
.
Let's draft:
About the company
Founded in 1958 as a single pancake house in Ohio, Perkins has grown into a leading family dining restaurant known for friendly service, classic comfort food, and great value. Since 1982, JDK has continued to build on Perkins' legacy by serving as the largest franchiser of the brand. Our success is driven by people who live out our guiding principles every day: Stay Hungry, Be Humble, and Work Smart. It's how we collaborate, grow, and support one another – creating an environment where team members can thrive while delivering exceptional experiences to our guests. We're Hungry, Humble, and Smart — and we hire people who work the same way.
About the role
We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift.
Responsibilities
- Greet guests with a friendly and welcoming attitude and provide excellent customer service.
- Manage seating arrangements and wait lists to ensure smooth restaurant flow and guest satisfaction.
- Accurately process guest payments and handle cash, credit card, and other transactions responsibly.
- Answer phones, assist guests with questions, and support carryout or to-go orders as needed.
- Maintain cleanliness and organization of the host stand, front entrance, and dining areas.
- Communicate effectively with servers, kitchen staff, and managers to support efficient operations.
- Perform additional duties as assigned.
Qualifications
- Take initiative and look for ways to improve in your daily work.
- Put the team first, stay open to feedback, and lead with respect.
- Communicate thoughtfully and navigate situations with good judgment.
Requirements
- No experience is required; prior host/cashier experience is a plus.
- Ability to work in a fast-paced, team-oriented environment.
- Ability to lift and carry up to 50 lbs.
- Ability to stand, walk, reach, and bend for extended periods.
Pay
Competitive pay based on experience, with a clear path as your impact grows.
Schedule
Flexible scheduling options that work for you.
Benefits
Medical, dental, vision, paid time off, and 401(k) with company match (subject to terms and conditions).
Check: The "Why JDK" also had "Values-driven
for heading, then content. For lists, use - . For prose, use
.
Let's draft:
About the company
Founded in 1958 as a single pancake house in Ohio, Perkins has grown into a leading family dining restaurant known for friendly service, classic comfort food, and great value. Since 1982, JDK has continued to build on Perkins' legacy by serving as the largest franchiser of the brand. Our success is driven by people who live out our guiding principles every day: Stay Hungry, Be Humble, and Work Smart. It's how we collaborate, grow, and support one another – creating an environment where team members can thrive while delivering exceptional experiences to our guests. We're Hungry, Humble, and Smart — and we hire people who work the same way.
About the role
We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift.
Responsibilities
- Greet guests with a friendly and welcoming attitude and provide excellent customer service.
- Manage seating arrangements and wait lists to ensure smooth restaurant flow and guest satisfaction.
- Accurately process guest payments and handle cash, credit card, and other transactions responsibly.
- Answer phones, assist guests with questions, and support carryout or to-go orders as needed.
- Maintain cleanliness and organization of the host stand, front entrance, and dining areas.
- Communicate effectively with servers, kitchen staff, and managers to support efficient operations.
- Perform additional duties as assigned.
Qualifications
- Take initiative and look for ways to improve in your daily work.
- Put the team first, stay open to feedback, and lead with respect.
- Communicate thoughtfully and navigate situations with good judgment.
Requirements
- No experience is required; prior host/cashier experience is a plus.
- Ability to work in a fast-paced, team-oriented environment.
- Ability to lift and carry up to 50 lbs.
- Ability to stand, walk, reach, and bend for extended periods.
Pay
Competitive pay based on experience, with a clear path as your impact grows.
Schedule
Flexible scheduling options that work for you.
Benefits
Medical, dental, vision, paid time off, and 401(k) with company match (subject to terms and conditions).
Check: The "Why JDK" also had "Values-driven
. Let's draft:
About the company
Founded in 1958 as a single pancake house in Ohio, Perkins has grown into a leading family dining restaurant known for friendly service, classic comfort food, and great value. Since 1982, JDK has continued to build on Perkins' legacy by serving as the largest franchiser of the brand. Our success is driven by people who live out our guiding principles every day: Stay Hungry, Be Humble, and Work Smart. It's how we collaborate, grow, and support one another – creating an environment where team members can thrive while delivering exceptional experiences to our guests. We're Hungry, Humble, and Smart — and we hire people who work the same way.
About the role
We are looking for a Host/Cashier who is responsible for welcoming guests, handling transactions accurately, and creating a warm and friendly first impression. A successful Host/Cashier brings positive energy, strong communication skills, and a team-first mindset to every shift.
Responsibilities
- Greet guests with a friendly and welcoming attitude and provide excellent customer service.
- Manage seating arrangements and wait lists to ensure smooth restaurant flow and guest satisfaction.
- Accurately process guest payments and handle cash, credit card, and other transactions responsibly.
- Answer phones, assist guests with questions, and support carryout or to-go orders as needed.
- Maintain cleanliness and organization of the host stand, front entrance, and dining areas.
- Communicate effectively with servers, kitchen staff, and managers to support efficient operations.
- Perform additional duties as assigned.
Qualifications
- Take initiative and look for ways to improve in your daily work.
- Put the team first, stay open to feedback, and lead with respect.
- Communicate thoughtfully and navigate situations with good judgment.
Requirements
- No experience is required; prior host/cashier experience is a plus.
- Ability to work in a fast-paced, team-oriented environment.
- Ability to lift and carry up to 50 lbs.
- Ability to stand, walk, reach, and bend for extended periods.
Pay
Competitive pay based on experience, with a clear path as your impact grows.
Schedule
Flexible scheduling options that work for you.
Benefits
Medical, dental, vision, paid time off, and 401(k) with company match (subject to terms and conditions).
Check: The "Why JDK" also had "Values-driven