Retail Parts Pro Store 6846

We need to output only HTML fragment, no /. Use

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. Content: - Intro: "What is a Retail Parts Pro? Professional level sales position capable of supporting advanced functions of the DIY business. The role has expert knowledge of store systems, advanced automotive system knowledge and part knowledge. This role has the ability for advanced identification, trouble shooting and project assistance for DIY customers. The role has the ability to source from numerous places including special order, FDO, second source, etc. The role has in-depth knowledge of the store inventory and maintenance processes. Position is full time." That's about the role. - Primary Responsibilities: list bullet points. - Secondary Responsibilities: list bullet points. - Success Factors: list bullet points. - Essential Job Skills Necessary for Success as a Retail Parts Pro: list bullet points. - Prior Experience that Sets a Retail Parts Pro up for Success: bullet points. - Education Certificates, Licenses, Registrations: bullet points. - Physical Demands: statement about compliance. - Compensation Range: details. - Benefits: description. - EEO etc: boilerplate to remove. - Also mention "California Residents Click Below For Privacy Notice" - remove. - Also "We are an Equal Opportunity Employer..." remove. - Also "Compensation Range" includes pay details. - Benefits: description. - Schedule? Not explicitly given; only "Position is full time." That could be schedule? It says full time, but not schedule details like shift. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It states compensation range, so Pay section is okay. Benefits: yes. Schedule: only says full time, but not specific schedule like "Monday-Friday 9-5". Might be considered schedule info? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Position is full time." That's schedule info (full-time). So we could include Schedule section with that detail. However they said prefer a few substantive sections over many thin ones. Could combine schedule into About the role? But they want sections for each heading if content exists. We'll include Schedule with "Position is full time." We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy notice, etc. We must preserve all substantive information. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which sections to include: About the role, Responsibilities (maybe combine primary and secondary?), Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we have many lists: Primary Responsibilities, Secondary Responsibilities, Success Factors, Essential Job Skills, Prior Experience, Education Certificates, Physical Demands. We could map: - About the role: intro paragraph. - Responsibilities: combine Primary and Secondary Responsibilities (maybe also Success Factors? but Success Factors are more like attributes). Could treat Success Factors as Skills or Qualifications. - Requirements: maybe Prior Experience and Education Certificates. - Qualifications: maybe ASE certification preferred, driver's license. - Skills: Essential Job Skills (knowledge, abilities). - Benefits: description. - Pay: compensation range. - Schedule: full time. We need to ensure we don't create empty sections. Let's extract content. About the role paragraph: "What is a Retail Parts Pro? Professional level sales position capable of supporting advanced functions of the DIY business. The role has expert knowledge of store systems, advanced automotive system knowledge and part knowledge. This role has the ability for advanced identification, trouble shooting and project assistance for DIY customers. The role has the ability to source from numerous places including special order, FDO, second source, etc. The role has in-depth knowledge of the store inventory and maintenance processes. Position is full time." We could split: About the role (excluding schedule) and Schedule separate. But schedule is just "Position is full time." Could be included in About the role as a sentence. But they said schedule section only if posting actually states them. It does state full time, but we could keep it in About the role. However they want to use headings for sections; we could still include Schedule heading with that sentence. But they said prefer a few substantive sections over many thin ones. So maybe better to not create a separate Schedule section; just include full time in About the role. But then we would not have a Schedule section, which is okay because we only create sections when there is real specific content. The schedule content is minimal but still specific. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full time, so we could create Schedule. But they also say "Prefer a few substantive sections over many thin ones." So maybe we combine schedule into About the role to avoid thin section. I'd lean to not create Schedule section, as it's thin. But we need to follow instruction: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The schedule content is specific: "Position is full time." That's real specific. So we could include Schedule heading with that sentence. However that would be a thin section (just one sentence). The instruction says prefer a few substantive sections over many thin ones. So maybe better to incorporate schedule into About the role to avoid thin section. I'd choose to incorporate schedule into About the role. Thus sections: About the role (includes intro + full time), Responsibilities (primary+secondary), Requirements (prior experience + education), Qualifications (ASE cert preferred, driver's license), Skills (essential job skills), Benefits, Pay. We need to ensure we don't repeat content. Let's extract each. About the role: Combine: "What is a Retail Parts Pro? Professional level sales position capable of supporting advanced functions of the DIY business. The role has expert knowledge of store systems, advanced automotive system knowledge and part knowledge. This role has the ability for advanced identification, trouble shooting and project assistance for DIY customers. The role has the ability to source from numerous places including special order, FDO, second source, etc. The role has in-depth knowledge of the store inventory and maintenance processes. Position is full time." That's a paragraph. Responsibilities: Primary Responsibilities list: - Provide GAS2 selling experience for DIY customer visits and phone calls - Achieve personal / store sales goals and service objectives - Manage DIY services including battery installation, testing, wiper installs, etc. - Ensure high standards of customer service and store appearance standards - Key holder responsibilities (task assignment and completion, safety, open/close duties) Secondary Responsibilities list: - Assist in store inventory processes including truck put away, shoot outs, cycle counts, back stock, etc. - Store Cleanliness including floors, bathrooms, facing, dusting, parking lot - Provide DIY services including battery installation, testing, wiper installs, etc. Note that "Provide DIY services including battery installation, testing, wiper installs, etc." appears both primary and secondary; we should preserve all info, but we can combine duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are substantive? It's repeated; we could keep both but it's redundant. Safer to keep as is, but we could combine to avoid duplication while preserving info? The instruction says do not summarize away detail; combining duplicates might be considered summarizing? It's still same detail, but we are removing duplicate line. Might be considered removing duplicate info, which could be okay? Safer to keep both entries, even if duplicate. We'll keep both. Thus responsibilities list will have 8 items (including duplicate). We'll put them in

  • . Requirements: Prior Experience that Sets a Retail Parts Pro up for Success: - 3-5 years of prior automotive parts experience - Proven sales ability with past experience in fulfillment of customer transactions Education Certificates, Licenses, Registrations: - Must have a valid driver's license - ASE Certification Preferred, But Not Required We could also include Physical Demands? That's more like a requirement but it's a statement about compliance. Could be included in Requirements as a note. But it's not a list; it's a sentence: "We comply with all applicable federal, state, and local laws." That's boilerplate? It's a legal statement; maybe we should remove as boilerplate? It's not EEO but it's a compliance statement. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal compliance statement; could be considered legal boilerplate. I'd remove it. Thus Requirements section will have two sub-lists? Could combine into one list with items: "3-5 years of prior automotive parts experience", "Proven sales ability with past experience in fulfillment of customer transactions", "Must have a valid driver's license", "ASE Certification Preferred, But Not Required". That seems okay. Qualifications: maybe we already included driver's license and ASE cert in Requirements. But we need a Qualifications section per headings list. Could treat Qualifications as "ASE Certification Preferred, But Not Required" and "Valid driver's license". But we already used them. Might be better to split: Requirements = Prior Experience; Qualifications = Education/Certificates/Licenses; Skills = Essential Job Skills. Let's follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus: - About the role: intro + full time. - Responsibilities: primary + secondary responsibilities. - Requirements: Prior Experience (3-5 years, proven sales ability). - Qualifications: Education Certificates, Licenses, Registrations (valid driver's license, ASE Certification Preferred, But Not Required). - Skills: Essential Job Skills Necessary for Success as a Retail Parts Pro (list of skills). - Benefits: description. - Pay: compensation range. - Schedule: maybe we omit as we included full time in About the role. But we could still add Schedule with "Position is full time." but that duplicates. I'd omit Schedule to avoid thin section. Now we need to extract Skills list: Essential Job Skills Necessary for Success as a Retail Parts Pro: - Working knowledge of automotive systems, and diagnostic ability to include: internal engine, suspension, brakes, electronic, exhaust, etc. - Speak and write English (Spanish a plus); communicate effectively and build strong relationships with customers, peers and management - Ability to read and interpret documents such as safety rules, operating and maintenance instructions, parts catalogs, and procedure manuals; ability to write simple correspondence - Understand and execute instructions furnished in written, oral, or diagram form - Successfully complete the Parts Knowledge Assessment - Use basic math accurately: add, subtract, multiply, and divide in all units of measure, using whole numbers, common fractions, and decimals - Use Microsoft software effectively (Word, Excel required) - Strong organizational skills - Ability to work an assortment of days, evenings, and weekends as needed Also Success Factors list maybe could be considered skills but we already have Skills section. Could we incorporate Success Factors into Skills? The instruction says preserve all substantive information; we could add them as part of Skills. But we already have a Skills section; we could merge Success Factors into Skills to avoid another thin section. However the headings list includes Skills; we could put both Essential Job Skills and Success Factors under Skills. That would preserve all info. Success Factors list: - Friendly communication - Ability to locate and stock parts - Safety knowledge and skills - Operating inventory systems and store equipment - Parts and automotive system knowledge skills - Operating POS and Parts lookup systems - Expert at testing and diagnostic equipment for DIY services - ASE P2 certified or ASE ready equivalent - Advanced solution, project and product quality recommendation ability - Advanced parts lookup and sourcing - Advanced selling skills for DIY We should include these