AUTOMOTIVE PARTS DEPARTMENT
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
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate, duplicated lines, application instructions
- Include section ONLY when posting has real, specific content for it
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment
Let me structure:
1. About the role / Company overview: There's a paragraph about Amato Hyundai of Glendale looking for dependable, motivated individuals. Also "Why Work at Amato?" with bullet points. That could be "About the role" or "About the company". I'll use "About the role" for the introductory paragraph and maybe "Why work here" for the bullet points? But the rules say use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". "Why Work at Amato?" is essentially benefits and company culture. Could be "Benefits" but there's also a separate benefits list at top. The top list is labeled "Benefits:" explicitly. So I should have a Benefits section with that list. The "Why Work at Amato?" includes some benefits but also company description. I'll combine: maybe "About the role" for the intro paragraph, "Benefits" for the explicit benefits list, and "Requirements" for "What We're Looking For:". Also "Positions may include..." could be part of About the role.
Let's parse the content:
- "Benefits: 401(k)401(k) matchingBonus based on performanceCompany partiesCompetitive salaryDental insuranceEmployee discountsFree uniformsHealth insurancePaid time offSigning bonusTraining & developmentVision insurance" - this is a list of benefits. Note "401(k)401(k) matching" seems like a typo: "401(k) matching". I'll treat as separate items: "401(k)", "401(k) matching", "Bonus based on performance", "Company parties", "Competitive salary", "Dental insurance", "Employee discounts", "Free uniforms", "Health insurance", "Paid time off", "Signing bonus", "Training & development", "Vision insurance". But "Competitive salary" is more pay than benefit. However it's listed under Benefits. I'll include as benefit.
- Then contact info (remove).
- "AUTOMOTIVE PARTS DEPARTMENT - JOIN OUR TEAM" - job title, skip.
- "Amato Hyundai of Glendale | Glendale, WI" - company and location. Could be a short
metadata.
- "Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you." - prose about role.
- "Why Work at Amato?" with bullet points:
- Established, family-owned automotive group
- Busy, steady service department
- No outside wholesale accounts
- Competitive pay based on experience
- Health insurance, paid time off, and employee benefits
- Long-term stability and opportunities for growth
- "What We're Looking For:" with bullet points:
- Automotive parts or dealership experience preferred
- Strong work ethic and dependable attendance
- Ability to work well with technicians, service advisors, and customers
- Organized, detail-oriented, and comfortable in a fast-paced environment
- Positive attitude and willingness to be part of a team
- "Positions may include experienced parts counter and parts support/shipping & receiving opportunities." - prose about positions.
- Contact info again (remove).
Now, I need to decide sections:
- About the role: include the intro paragraph and maybe the positions sentence.
- Benefits: the explicit benefits list at top. Also the "Why Work at Amato?" includes some benefits but also company culture. Could merge into Benefits? But "Why Work at Amato?" includes "Established, family-owned..." which is not a benefit per se. Could be "About the company" but not a standard heading. The rules allow "About the role" as heading. I'll put the company description and why work here under "About the role" or maybe "Why work here"? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "About the role" for the introductory paragraph and the "Why Work at Amato?" list. But "Why Work at Amato?" is a list of reasons, which are benefits and company attributes. I could create a "Benefits" section for the explicit benefits list, and include the "Why Work at Amato?" list under "About the role" as a list? Or maybe "Benefits" includes both? The explicit benefits list is labeled "Benefits:" so that's clear. The "Why Work at Amato?" includes "Competitive pay based on experience", "Health insurance, paid time off, and employee benefits" which are already in benefits list. I'll keep the explicit benefits list as Benefits section. The "Why Work at Amato?" can be part of "About the role" as a list of company highlights.
- Requirements: "What We're Looking For:" is clearly requirements/qualifications.
- Pay: The posting mentions "Competitive salary" in benefits list, and "Competitive pay based on experience" in Why Work. But no specific pay range. The rules say never create Pay section unless posting actually states them. It states "Competitive salary" and "Competitive pay based on experience". That's not specific. I'd avoid Pay section.
- Schedule: Not mentioned.
- Responsibilities: Not explicitly listed. The role is parts counterperson, but no duties listed. So no Responsibilities section.
- Skills: Not separate.
Thus sections: About the role, Benefits, Requirements.
Also include company/location as a short
at top? The rules say fold minor metadata into a short
or drop it. I'll include a
with company and location.
Now, write HTML.
Structure:
Amato Hyundai of Glendale | Glendale, WI
About the role
Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you.
Why work here
? But not a standard heading. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "Why work here" is not in the example list, but it's a custom heading. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings allowed? But they prefer those. I could incorporate the "Why Work at Amato?" list into "About the role" as a list. But "About the role" already has a paragraph. Could add a sublist? But we need to use - for lists. I could have:
About the role
Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you.
- Established, family-owned automotive group
- Busy, steady service department
- No outside wholesale accounts
- Competitive pay based on experience
- Health insurance, paid time off, and employee benefits
- Long-term stability and opportunities for growth
Positions may include experienced parts counter and parts support/shipping & receiving opportunities.
But the "Why Work at Amato?" is a separate section in the posting. Could make a separate heading "Why work at Amato" but not in the example list. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they prefer those. I think it's okay to have a heading "Why work here" but to be safe, I'll incorporate into "About the role" as a list. However, the list is not duties but reasons to work there. Could be considered "Benefits" but we already have a Benefits section. The Benefits section will have the explicit benefits list. The "Why Work at Amato?" includes some benefits but also company culture. I'll keep them separate: Benefits section for the explicit list, and About the role for the intro and the Why Work list.
But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "Why Work at Amato?" with specific bullet points. That's real content. Could be a section "Why work here". I'll use Why work here
as a heading. It's not in the example but it's a section heading. The rules didn't restrict to only those examples. They said "e.g." So I'll include it.
Alternatively, I could label it "Benefits" but there are two benefits lists. The explicit "Benefits:" list is more comprehensive. The "Why Work at Amato?" includes some overlapping benefits. I'll keep both: Benefits section for the explicit list, and a "Why work here" section for the company highlights.
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Benefits:" explicitly, so Benefits section is warranted. The posting also states "Why Work at Amato?" which is a section. So I'll create a section for that.
Let's decide on headings:
- About the role (for the intro paragraph)
- Why work here (for the Why Work at Amato list)
- Benefits (for the explicit benefits list)
- Requirements (for What We're Looking For)
But "About the role" and "Why work here"
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Let me structure: 1. About the role / Company overview: There's a paragraph about Amato Hyundai of Glendale looking for dependable, motivated individuals. Also "Why Work at Amato?" with bullet points. That could be "About the role" or "About the company". I'll use "About the role" for the introductory paragraph and maybe "Why work here" for the bullet points? But the rules say use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". "Why Work at Amato?" is essentially benefits and company culture. Could be "Benefits" but there's also a separate benefits list at top. The top list is labeled "Benefits:" explicitly. So I should have a Benefits section with that list. The "Why Work at Amato?" includes some benefits but also company description. I'll combine: maybe "About the role" for the intro paragraph, "Benefits" for the explicit benefits list, and "Requirements" for "What We're Looking For:". Also "Positions may include..." could be part of About the role. Let's parse the content: - "Benefits: 401(k)401(k) matchingBonus based on performanceCompany partiesCompetitive salaryDental insuranceEmployee discountsFree uniformsHealth insurancePaid time offSigning bonusTraining & developmentVision insurance" - this is a list of benefits. Note "401(k)401(k) matching" seems like a typo: "401(k) matching". I'll treat as separate items: "401(k)", "401(k) matching", "Bonus based on performance", "Company parties", "Competitive salary", "Dental insurance", "Employee discounts", "Free uniforms", "Health insurance", "Paid time off", "Signing bonus", "Training & development", "Vision insurance". But "Competitive salary" is more pay than benefit. However it's listed under Benefits. I'll include as benefit. - Then contact info (remove). - "AUTOMOTIVE PARTS DEPARTMENT - JOIN OUR TEAM" - job title, skip. - "Amato Hyundai of Glendale | Glendale, WI" - company and location. Could be a short
metadata. - "Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you." - prose about role. - "Why Work at Amato?" with bullet points: - Established, family-owned automotive group - Busy, steady service department - No outside wholesale accounts - Competitive pay based on experience - Health insurance, paid time off, and employee benefits - Long-term stability and opportunities for growth - "What We're Looking For:" with bullet points: - Automotive parts or dealership experience preferred - Strong work ethic and dependable attendance - Ability to work well with technicians, service advisors, and customers - Organized, detail-oriented, and comfortable in a fast-paced environment - Positive attitude and willingness to be part of a team - "Positions may include experienced parts counter and parts support/shipping & receiving opportunities." - prose about positions. - Contact info again (remove). Now, I need to decide sections: - About the role: include the intro paragraph and maybe the positions sentence. - Benefits: the explicit benefits list at top. Also the "Why Work at Amato?" includes some benefits but also company culture. Could merge into Benefits? But "Why Work at Amato?" includes "Established, family-owned..." which is not a benefit per se. Could be "About the company" but not a standard heading. The rules allow "About the role" as heading. I'll put the company description and why work here under "About the role" or maybe "Why work here"? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "About the role" for the introductory paragraph and the "Why Work at Amato?" list. But "Why Work at Amato?" is a list of reasons, which are benefits and company attributes. I could create a "Benefits" section for the explicit benefits list, and include the "Why Work at Amato?" list under "About the role" as a list? Or maybe "Benefits" includes both? The explicit benefits list is labeled "Benefits:" so that's clear. The "Why Work at Amato?" includes "Competitive pay based on experience", "Health insurance, paid time off, and employee benefits" which are already in benefits list. I'll keep the explicit benefits list as Benefits section. The "Why Work at Amato?" can be part of "About the role" as a list of company highlights. - Requirements: "What We're Looking For:" is clearly requirements/qualifications. - Pay: The posting mentions "Competitive salary" in benefits list, and "Competitive pay based on experience" in Why Work. But no specific pay range. The rules say never create Pay section unless posting actually states them. It states "Competitive salary" and "Competitive pay based on experience". That's not specific. I'd avoid Pay section. - Schedule: Not mentioned. - Responsibilities: Not explicitly listed. The role is parts counterperson, but no duties listed. So no Responsibilities section. - Skills: Not separate. Thus sections: About the role, Benefits, Requirements. Also include company/location as a short
at top? The rules say fold minor metadata into a short
or drop it. I'll include a
with company and location. Now, write HTML. Structure:
Amato Hyundai of Glendale | Glendale, WI
About the role
Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you.
Why work here
? But not a standard heading. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "Why work here" is not in the example list, but it's a custom heading. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings allowed? But they prefer those. I could incorporate the "Why Work at Amato?" list into "About the role" as a list. But "About the role" already has a paragraph. Could add a sublist? But we need to use - for lists. I could have:
About the role
Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you.
- Established, family-owned automotive group
- Busy, steady service department
- No outside wholesale accounts
- Competitive pay based on experience
- Health insurance, paid time off, and employee benefits
- Long-term stability and opportunities for growth
Positions may include experienced parts counter and parts support/shipping & receiving opportunities.
But the "Why Work at Amato?" is a separate section in the posting. Could make a separate heading "Why work at Amato" but not in the example list. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they prefer those. I think it's okay to have a heading "Why work here" but to be safe, I'll incorporate into "About the role" as a list. However, the list is not duties but reasons to work there. Could be considered "Benefits" but we already have a Benefits section. The Benefits section will have the explicit benefits list. The "Why Work at Amato?" includes some benefits but also company culture. I'll keep them separate: Benefits section for the explicit list, and About the role for the intro and the Why Work list.
But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "Why Work at Amato?" with specific bullet points. That's real content. Could be a section "Why work here". I'll use Why work here
as a heading. It's not in the example but it's a section heading. The rules didn't restrict to only those examples. They said "e.g." So I'll include it.
Alternatively, I could label it "Benefits" but there are two benefits lists. The explicit "Benefits:" list is more comprehensive. The "Why Work at Amato?" includes some overlapping benefits. I'll keep both: Benefits section for the explicit list, and a "Why work here" section for the company highlights.
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Benefits:" explicitly, so Benefits section is warranted. The posting also states "Why Work at Amato?" which is a section. So I'll create a section for that.
Let's decide on headings:
- About the role (for the intro paragraph)
- Why work here (for the Why Work at Amato list)
- Benefits (for the explicit benefits list)
- Requirements (for What We're Looking For)
But "About the role" and "Why work here"
- for lists. I could have:
About the role
Amato Hyundai of Glendale is looking for dependable, motivated individuals to join our parts department! Whether you're an experienced dealership parts counterperson or someone with automotive experience looking for an opportunity to grow, we'd like to hear from you.
- Established, family-owned automotive group
- Busy, steady service department
- No outside wholesale accounts
- Competitive pay based on experience
- Health insurance, paid time off, and employee benefits
- Long-term stability and opportunities for growth
Positions may include experienced parts counter and parts support/shipping & receiving opportunities.
But the "Why Work at Amato?" is a separate section in the posting. Could make a separate heading "Why work at Amato" but not in the example list. The rules say "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they prefer those. I think it's okay to have a heading "Why work here" but to be safe, I'll incorporate into "About the role" as a list. However, the list is not duties but reasons to work there. Could be considered "Benefits" but we already have a Benefits section. The Benefits section will have the explicit benefits list. The "Why Work at Amato?" includes some benefits but also company culture. I'll keep them separate: Benefits section for the explicit list, and About the role for the intro and the Why Work list. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "Why Work at Amato?" with specific bullet points. That's real content. Could be a section "Why work here". I'll use
Why work here
as a heading. It's not in the example but it's a section heading. The rules didn't restrict to only those examples. They said "e.g." So I'll include it. Alternatively, I could label it "Benefits" but there are two benefits lists. The explicit "Benefits:" list is more comprehensive. The "Why Work at Amato?" includes some overlapping benefits. I'll keep both: Benefits section for the explicit list, and a "Why work here" section for the company highlights. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Benefits:" explicitly, so Benefits section is warranted. The posting also states "Why Work at Amato?" which is a section. So I'll create a section for that. Let's decide on headings: - About the role (for the intro paragraph) - Why work here (for the Why Work at Amato list) - Benefits (for the explicit benefits list) - Requirements (for What We're Looking For) But "About the role" and "Why work here"