Customer Sales Advisor
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect possible Schedule section. Since we have schedule info, we could create a Schedule section with that bullet. But we also have General Requirements which includes schedule. Might duplicate. Better to keep schedule separate and remove from General Requirements? But we must preserve ALL substantive information; we can't remove it. Could keep schedule in both places? That would duplicate. Better to move schedule bullet to Schedule section and keep other general requirements elsewhere. Let's do that.
Thus sections:
- About the Company (maybe "Who are we?" heading? They said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not strictly limited to those; they gave examples. Could use "About the Company" or "Who are we?" Might be okay. But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those examples. For company description maybe "About the role"? But that's about role not company. Could use "About the role" for description of role (What do we want?). Could use "About the role" heading for the paragraph about what we want. Then "Requirements" for General Requirements + Physical Requirements? Could split into Requirements and maybe Qualifications? But we have General Requirements and Physical Requirements; both are requirements. Could combine under Requirements with sublists? But they want - for any list. Could have two separate lists under Requirements heading? Might be okay to have two
under same heading. Or we could have separate headings: "General Requirements" and "Physical Requirements". But they didn't list those as examples; but they said use those examples as possible headings, not exclusive. Safer to use headings that match content: "General Requirements", "Physical Requirements", "Responsibilities", "Benefits", "Pay", "Schedule". Also maybe "About the Company". But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. Let's map:
- About the role: could be "What do we want?" (description of desired candidate). Or could be "Who are we?" but that's about company. I'd use "About the role" for the description of role and desired candidate.
- Responsibilities: list.
- Requirements: could combine General Requirements and Physical Requirements? Might be too thin if split. Could have two subheadings? But they said prefer a few substantive sections over many thin ones. So maybe one Requirements section with two lists: one for General Requirements, one for Physical Requirements. Could precede each list with a
describing? But we must not invent filler. Could just have two
under same heading; that's fine.
- Benefits: list.
- Pay: paragraph with hourly rate.
- Schedule: paragraph with 40 hour work week including evenings and weekends.
- About the Company: maybe not needed but we have info about who we are. Could put under "About the role"? Might be weird. Could add a section "About the Company" though not in examples but still a heading. The instruction: "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. ...). Likely they expect those headings. Safer to stick to those. Where to put company description? Could be under "About the role"? Not ideal. Could be under "Requirements"? No. Could be under "Benefits"? No.
Maybe we can treat "Who are we?" as "About the role"? Actually the role is at Summit Wash Holdings, so describing the company could be part of role context. I'd put it under "About the role" heading, with two paragraphs: first about company, second about desired candidate.
Thus:
About the role
Summit Wash Holdings is a premier group of car wash brands growing throughout the Northeast, Midwest, and Southeast regions. At Summit Wash Holdings, all teammates produce speedy service in a fun and mutually respectful manner with gold-standard integrity, quality, and hospitality, all while maintaining a work-life balance. Our Mission is to provide a fast, quality car wash with friendly-spirited engagement and integrity.
We seek high-energy personalities that thrive in a fast-paced environment to provide a welcoming atmosphere for our Unlimited Wash Pass Members and a memorable first impression on our new car wash guests. A successful candidate would love working outdoors in all conditions and will be excited to roll up their sleeves to get the job done! You must be highly motivated and have an outgoing, friendly personality. All we ask is for you to share our passion for washing cars, creating memorable moments, and our obsession with exceptional guest service!
Then Responsibilities.
Then Requirements: two lists.
We need to include location somewhere. Could be a short after About the role before Responsibilities: "Location: Speeders Car Wash 68 U.S. 46, Mountain Lakes, NJ, USA". That's substantive.
Then Requirements heading.
Under Requirements, we can have two
maybe with a preceding each? Not required but could add a short
like "General Requirements:" but that might be considered filler? It's not invented; it's describing the list. Could be okay. But to avoid filler, we could just have two
sequentially; but then it's ambiguous which list is which. Better to add a like "General Requirements:" then
. That's not invented; it's a label from the original text. The original had "General Requirements" heading. So we can keep that as a or maybe as a
? But we only use for section headings; we can use
for subheading labels. That's fine.
Thus:
Requirements
General Requirements:
- Authorized to work in the U.S.
- 40 Hour Work Week (Including Evenings and Weekends)
- Basic Computer Skills
- Highly developed communication skills – bilingual a plus!
- Carwash experience to understand industry-specific challenges and opportunities preferred
- 8th Grade Proficiency or Above
Physical Requirements:
- Able to lift at least 50lbs.
- Ability to be on your feet for at least 8 hours at a time.
- Mobility to work in areas that require kneeling, crouching, or crawling.
- Capable of working in both extreme weather elements – hot and cold
But note we moved the 40 hour work week to Requirements; we will also need Schedule section? Actually we used that bullet as part of General Requirements. If we keep it there, we may not need separate Schedule section. The instruction says include a section ONLY when posting has real, specific content for it. Since we already have that info under Requirements, we could omit Schedule section. That's fine.
Now Benefits:
Benefits
- Commissions are paid every pay period
- Medical, Dental, and Vision Insurance
- Flexible scheduling
- Paid Time Off (PTO)
- Career Growth based on Performance and not Seniority – 75% of employees were promoted within Summit Wash Holdings
- Referral Bonus up to $800.00 per qualified hire, dependent on position
- Free Car Wash Membership
Pay:
- for any list. Could have two separate lists under Requirements heading? Might be okay to have two
- under same heading. Or we could have separate headings: "General Requirements" and "Physical Requirements". But they didn't list those as examples; but they said use those examples as possible headings, not exclusive. Safer to use headings that match content: "General Requirements", "Physical Requirements", "Responsibilities", "Benefits", "Pay", "Schedule". Also maybe "About the Company". But they said use
- Authorized to work in the U.S.
- 40 Hour Work Week (Including Evenings and Weekends)
- Basic Computer Skills
- Highly developed communication skills – bilingual a plus!
- Carwash experience to understand industry-specific challenges and opportunities preferred
- 8th Grade Proficiency or Above
- Able to lift at least 50lbs.
- Ability to be on your feet for at least 8 hours at a time.
- Mobility to work in areas that require kneeling, crouching, or crawling.
- Capable of working in both extreme weather elements – hot and cold
- Commissions are paid every pay period
- Medical, Dental, and Vision Insurance
- Flexible scheduling
- Paid Time Off (PTO)
- Career Growth based on Performance and not Seniority – 75% of employees were promoted within Summit Wash Holdings
- Referral Bonus up to $800.00 per qualified hire, dependent on position
- Free Car Wash Membership
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. Let's map: - About the role: could be "What do we want?" (description of desired candidate). Or could be "Who are we?" but that's about company. I'd use "About the role" for the description of role and desired candidate. - Responsibilities: list. - Requirements: could combine General Requirements and Physical Requirements? Might be too thin if split. Could have two subheadings? But they said prefer a few substantive sections over many thin ones. So maybe one Requirements section with two lists: one for General Requirements, one for Physical Requirements. Could precede each list with a
describing? But we must not invent filler. Could just have two
- under same heading; that's fine.
- Benefits: list.
- Pay: paragraph with hourly rate.
- Schedule: paragraph with 40 hour work week including evenings and weekends.
- About the Company: maybe not needed but we have info about who we are. Could put under "About the role"? Might be weird. Could add a section "About the Company" though not in examples but still a heading. The instruction: "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. ...). Likely they expect those headings. Safer to stick to those. Where to put company description? Could be under "About the role"? Not ideal. Could be under "Requirements"? No. Could be under "Benefits"? No. Maybe we can treat "Who are we?" as "About the role"? Actually the role is at Summit Wash Holdings, so describing the company could be part of role context. I'd put it under "About the role" heading, with two paragraphs: first about company, second about desired candidate. Thus:
About the role
Summit Wash Holdings is a premier group of car wash brands growing throughout the Northeast, Midwest, and Southeast regions. At Summit Wash Holdings, all teammates produce speedy service in a fun and mutually respectful manner with gold-standard integrity, quality, and hospitality, all while maintaining a work-life balance. Our Mission is to provide a fast, quality car wash with friendly-spirited engagement and integrity.
We seek high-energy personalities that thrive in a fast-paced environment to provide a welcoming atmosphere for our Unlimited Wash Pass Members and a memorable first impression on our new car wash guests. A successful candidate would love working outdoors in all conditions and will be excited to roll up their sleeves to get the job done! You must be highly motivated and have an outgoing, friendly personality. All we ask is for you to share our passion for washing cars, creating memorable moments, and our obsession with exceptional guest service!
Then Responsibilities. Then Requirements: two lists. We need to include location somewhere. Could be a shortafter About the role before Responsibilities: "Location: Speeders Car Wash 68 U.S. 46, Mountain Lakes, NJ, USA". That's substantive. Then Requirements heading. Under Requirements, we can have two
- maybe with a
preceding each? Not required but could add a short
like "General Requirements:" but that might be considered filler? It's not invented; it's describing the list. Could be okay. But to avoid filler, we could just have two
- sequentially; but then it's ambiguous which list is which. Better to add a
like "General Requirements:" then
- . That's not invented; it's a label from the original text. The original had "General Requirements" heading. So we can keep that as a
or maybe as a
? But we only use
for section headings; we can use
for subheading labels. That's fine. Thus:
Requirements
General Requirements:
Physical Requirements:
Benefits