Automotive Service Director

We need to output HTML fragment with sections: About the role? The posting includes description about company, location, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content: - About the role: description of job, location, company overview. Could be "About the role" section. - Responsibilities: list of duties. - Requirements: list of requirements. - Qualifications: maybe not separate; but we have "Requirements" includes qualifications. Could combine? The instruction: Use headings for those categories if content exists. We have "Requirements:" list. Also "Strong communication skills..." etc. Could treat as Requirements. - Skills: maybe not separate; but we could extract skills from requirements: Strong communication skills, technical automotive knowledge, ability to manage others, etc. Could create Skills section. - Benefits: list of benefits: Free Health Insurance option, Dental, Vision, Short and Long Term Disability, 401k with company matching, Earned Paid Vacations and Holiday Pay, PTO Days 90 days from hire date, Employee appreciation celebrations, Career advancement opportunities, promote from within, Employee Discounts, Family owned and operated, Long term job security, Competitive pay and bonus structure, Paid Training. - Pay: Not explicitly stated; only "Competitive pay and bonus structure". That's vague; we should not create Pay section unless posting actually states them. It says "Competitive pay and bonus structure" but no numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits we have explicit list, so include Benefits. For Pay, we have only "Competitive pay and bonus structure" which is vague but still states pay exists. However instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay and bonus structure, which is a statement about pay. Might be considered stating pay. But they also say prefer a few substantive sections over many thin ones. Could include Pay with that statement? Might be considered filler? It's not specific numbers, but it's still a statement. The instruction about not emitting heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay and bonus structure" is not exactly filler but still vague. Might be okay. However they said "Prefer a few substantive sections over many thin ones." Could combine Pay into Benefits? But Benefits already list. Could create a Pay section with that statement. - Schedule: "Work Days: Monday to Friday Rotating weekends". That's specific schedule. So include Schedule. - Qualifications: maybe we can treat Requirements as qualifications; but we have separate Requirements heading. Could also have Qualifications separate if we want, but we can just use Requirements. - Skills: we could extract skills from requirements: Strong communication skills, technical automotive knowledge, ability to manage others, valid driver's license, etc. Could create Skills section. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, etc. At end there is "Our Commitment to You Krause Auto Group is proud to be an equal opportunity employer..." That's boilerplate; remove. Also remove duplicated lines, application instructions, cookie/navigation/legal. Now produce HTML fragment. Structure:

About the role

... description ...

Responsibilities

• ... each duty ...

Requirements

• ... each requirement ...

Skills

• ... each skill ...

Benefits

• ... each benefit ...

Pay

Competitive pay and bonus structure.

Schedule

Work Days: Monday to Friday with rotating weekends.

We need to ensure we preserve all substantive information. Let's extract. About the role: The posting includes: "Lead Operations | Build High-Performing Teams | Drive Long-Term Growth Krause Auto Group Anderson, SC Anderson Ford is looking for an experienced Automotive Service Director to join our team! We are locally owned and operated, located just south of Greenville, SC. The Krause Auto Group has been in business for over 30 years, and we contribute our longevity to our focus on both customer and employee satisfaction. Our employees are not just a number. We acknowledge and support every employee regardless of position and care for everyone individually. We love to help people grow, promote from within, and celebrate individual success stories! We offer great opportunities to grow with our company portfolio which consists of 14 brands (BMW, Mercedes, Ford, Lincoln, Hyundai, Genesis, Honda, Nissan, Lamborghini, Aston Martin, Rolls Royce, Koenigsegg, Mclaren, and Lotus) across 5 states (Georgia, South Carolina, North Carolina, Texas and Florida)". That's about the role/company. We'll put that in

. Responsibilities list: from "Responsibilities Ensure customers receive prompt, courteous, and effective service Serve as a liaison between technicians and customers Take ownership of customers’ experience by carrying out additional assignments, enabling the dealership to leave a positive impression with the customer Distribute work between technicians Prioritize required services Ensure customers have a positive dealership experience Provide concierge support for all owner inquiries, whether via phone or in person, to ensure the customer does not get mishandled Spend quality time building relationships with the customers Assist the Service Director in any other duties" We need to split into list items. Let's list: - Ensure customers receive prompt, courteous, and effective service - Serve as a liaison between technicians and customers - Take ownership of customers’ experience by carrying out additional assignments, enabling the dealership to leave a positive impression with the customer - Distribute work between technicians - Prioritize required services - Ensure customers have a positive dealership experience - Provide concierge support for all owner inquiries, whether via phone or in person, to ensure the customer does not get mishandled - Spend quality time building relationships with the customers - Assist the Service Director in any other duties Now Requirements: after "REQUIREMENTS:" we have list: - Strong communication skills to deal with customers, employees and vendors. - Ford Experience a plus - Technical automotive knowledge - Demonstrated ability to manage others - Valid driver's license with clean driving record. - At least 2 years of automotive service advisor and automotive customer service experience - A hard-working can-do attitude - Excellent interpersonal and management skills - Must be authorized to work in the U.S. without sponsorship - Must pass pre-employment background check, MVR, and drug screening We'll list each as

. Skills: we could extract from requirements: Strong communication skills, Technical automotive knowledge, Demonstrated ability to manage others, Valid driver's license with clean driving record, At least 2 years of automotive service advisor and automotive customer service experience, A hard-working can-do attitude, Excellent interpersonal and management skills, Ford Experience a plus (maybe skill). But we might duplicate. Better to keep Skills separate but not duplicate too much. Could list skills like: Strong communication, Technical automotive knowledge, Ability to manage others, Interpersonal and management skills, Customer service experience, Hard-working attitude, etc. But we risk duplication. However instruction: preserve ALL substantive information; do not invent or summarize away detail. If we create Skills section, we need to ensure we don't lose any info from Requirements. Could keep Requirements as is, and Skills could be a subset but that would duplicate info. Duplication is allowed? Not prohibited but might be considered redundant. However they said "Prefer a few substantive sections over many thin ones." So maybe we should not create Skills if it's thin. Could combine Skills into Requirements. But we have to use headings only when posting has real specific content for it. The posting does not have a separate "Skills" heading; it's embedded in Requirements. So we should not create a Skills section unless we have explicit skills list separate. Since it's not explicit, better to omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check Benefits list: we need to extract all benefits. From "What we offer:" list: - Free Health Insurance option - Available Dental, and Vision Insurance Available (maybe "Dental and Vision Insurance Available") - Short and Long Term Disability Insurance - 401k with company matching contribution available - Earned Paid Vacations and Holiday Pay - PTO Days 90 days from hire date - Employee appreciation celebrations - Career advancement opportunities, promote from within - Employee Discounts on products and services - Family owned and operated - Long term job security - Competitive pay and bonus structure - Paid Training Note: "Competitive pay and bonus structure" appears also in Pay; we might duplicate. But we can keep it in Benefits as part of benefits list; Pay section could be omitted if we consider it covered. However we need to decide: The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits explicitly. Pay is stated as "Competitive pay and bonus structure". That's a statement about pay. Could create Pay section with that sentence. But then Benefits also includes that same phrase; duplication might be okay but maybe better to not duplicate. Could move that phrase to Pay only and remove from Benefits. However Benefits list includes many items; we could keep Pay separate and not include that phrase in Benefits. Let's see if the benefits list originally includes "Competitive pay and bonus structure" as a bullet. Yes it's in the "What we offer:" list. So it's part of benefits. If we create Pay section, we could still keep it in Benefits but it's duplicate. Might be okay but they said prefer few substantive sections over many thin ones. Having both Pay and Benefits may be thin. However Benefits is substantive with many items; Pay is just one line. Could combine Pay into Benefits and omit Pay section. But then we would not have a Pay section, which is okay because we only create sections when posting has real specific content for it. The posting does have specific content about pay ("Competitive pay and bonus structure") which is specific enough? It's vague but still a statement. However we could treat it as part of Benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so we could create them. But we also have Benefits already. Having both may be okay. However they said prefer a few substantive sections over many thin ones. Pay section would be thin (just one line). Might be better to omit Pay and keep that info in Benefits. But then we are not creating a Pay section, which is fine because we are not required to create it; we only create if we want. The instruction does not require us to create Pay section if we have the info elsewhere. It just says don't create it unless posting actually states them. So we can choose to not create Pay section; we just need to ensure we preserve the info somewhere. We'll keep it in Benefits. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check Schedule: "Work Days: Monday to Friday Rotating weekends". We'll put in

. Now ensure we removed boilerplate: The final paragraph about equal opportunity employer etc removed. Now produce HTML. We need to wrap each section with

heading and content. For About the role: we need a paragraph summarizing the description. We'll include the description as one or multiple paragraphs. Use

. Let's craft:

Lead Operations | Build High-Performing Teams | Drive Long-Term Growth Krause Auto Group Anderson, SC Anderson Ford is looking for an experienced Automotive Service Director to join our team! We are locally owned and