Parts Coordinator

We need to output HTML fragment only, with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include sections only when posting has real specific content. Must preserve all substantive info. We need to parse the job description. Job Title: Parts Coordinator (not heading). Job Description: We are seeking a Parts Coordinator who will engage in telephone and personal interaction with both internal and external customers and vendors. The role involves obtaining serial numbers and necessary information to look up parts, with a typical volume of 20-30 inbound calls from customers and 20-30 outgoing calls to vendors. The position requires daily tracking reports and backorder follow-up, processing orders to fulfill all customer needs, and researching and sourcing the correct parts. Then "Responsibilities" list bullet points. Then "Essential Skills" list bullet points. Then "Additional Skills & Qualifications" list bullet points. Then "Work Environment" prose. Then "Job Type & Location" prose. Then "Pay And Benefits" includes pay range and benefits list. Then "Workplace Type" prose. Then "Application Deadline" maybe not needed? It's metadata; we can include maybe in a short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Application deadline is metadata; we can include in a short

  maybe under a generic heading? But we should not create a heading unless there's real specific content for that section. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include a short

  for metadata like "Application Deadline: Sep 28, 2026." but not as a heading. Or we could drop it. Probably better to include as a short

  after other sections. Also "About Aston Carter" is boilerplate about company; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aston Carter" seems like company description; not required? It's not boilerplate like EEO, but it's still about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company description. However, "About Aston Carter" might be considered boilerplate? It's not EEO, but it's still generic. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description may be considered substantive? It's not about the job. Might be considered fluff. But we can keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove company description. However, we might consider it as not substantive to the role. But to be safe, we could keep it as a short

  maybe under a heading "About the Company"? But we are not supposed to create headings unless there's real specific content. The posting does have "About Aston Carter" section with specific content about the company. That could be considered substantive. However, the instruction about sections: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. They didn't list "About the Company". So maybe we should not create a heading for that. Instead we could fold that info into a short

  under maybe "About the role"? But that seems odd. Better to omit it, as it's not required for the job. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the company description, are we losing substantive information? It's not about the job duties, but it's still part of the posting. However, the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove company description. But the examples of headings are limited to job-related sections. I'd lean to omit the "About Aston Carter" section, as it's not directly about the role and could be considered boilerplate. Many similar tasks omit company description. I'll omit it. Now we need to decide which sections to include. We have: - About the role: The initial job description paragraph(s) before Responsibilities. That's substantive. So we can have

  About the role

  with a

  containing that prose. - Responsibilities: list bullet points. - Requirements: maybe we can combine Essential Skills and Additional Skills & Qualifications? The instruction says use headings like Requirements, Qualifications, Skills. We have Essential Skills (maybe Requirements) and Additional Skills & Qualifications (maybe Qualifications). We also have Skills separate? Could combine. We need to avoid thin sections. Prefer a few substantive sections over many thin ones. So we could have: - About the role - Responsibilities - Requirements (combining Essential Skills and Additional Skills & Qualifications) - Benefits - Pay - Schedule (maybe from Work Environment: flexible hours) - Workplace Type? Not in list but we could include as a short

  under About the role? Or maybe we can include a section "Work Environment" but not in the examples. 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 says "Use

  for section headings (e.g ...)". It implies we should use those headings for those categories. It doesn't say we cannot add others, but better to stick to those. However, we have Work Environment info about team size, flexible hours, work culture, training. That could go under Schedule (flexible hours) and maybe under About the role? Or we could create a "Work Environment" heading but it's not in the examples; risk of being considered extra. Better to incorporate into Schedule and maybe About the role. Schedule: The posting says "Work hours are flexible between 7 AM to 5 PM or 8 AM to 5 PM, depending on what works best." That's schedule info. Pay: The pay range $23.00 - $26.00/hr. Benefits: list of benefits. We also have Job Type & Location: "This is a Contract to Hire position based out of Ashland, VA." That's substantive; maybe we can put under About the role or a separate section? Not in examples. Could be part of About the role. Workplace Type: "This is a fully onsite position in Ashland,VA." Could be part of About the role. Application Deadline: we can drop or include as short

  maybe at end. Now we need to ensure we don't repeat job title as heading. Good. We need to use

  • for any list of duties/requirements/benefits. Thus: - Responsibilities: list of duties (the bullet points under Responsibilities). Use
    • . - Requirements: list of skills/qualifications (Essential Skills + Additional Skills & Qualifications). Use
      • . - Benefits: list of benefits (the bullet list under Pay And Benefits). Use
        • . Pay: just a

          with the pay range. Schedule:

          with flexible hours. About the role:

          with the initial description plus maybe job type/location/workplace type. We need to preserve all substantive information. Let's extract all substantive info: From Job Description paragraph: - Seeking a Parts Coordinator who will engage in telephone and personal interaction with both internal and external customers and vendors. - Role involves obtaining serial numbers and necessary information to look up parts. - Typical volume: 20-30 inbound calls from customers and 20-30 outgoing calls to vendors. - Position requires daily tracking reports and backorder follow-up. - Processing orders to fulfill all customer needs. - Researching and sourcing the correct parts. Responsibilities bullet points: - Interact with internal and external customers and vendors to obtain necessary information for parts lookup. - Conduct daily tracking reports and follow up on backorders. - Process customer orders by phone, fax, or email to fulfill their needs. - Research and source correct parts for internal and external customers. - Manage and assist customers with process disruptions, such as parts on backorder or incorrectly shipped parts. - Receive inventory and branch transfers into the ERP system as needed. - Assist with various inter-departmental issues as they arise. Essential Skills bullet points: - Experience in inventory management. - Strong customer service skills. - Proficient data entry skills. - Experience in administrative support. - Order entry experience. Additional Skills & Qualifications bullet points: - Experience with Quickware or any ERP system. - Background in construction parts or automotive parts is helpful. - 5 years of experience in parts management or as a parts counter person in any industry. - Excellent follow-up and communication skills. - Ability to lift up to 15 lbs. Work Environment paragraph: - The team comprises two members in Ashland and around eight in Fredericksburg. - Work hours are flexible between 7 AM to 5 PM or 8 AM to 5 PM, depending on what works best. - The work culture is supportive, with a smaller team and hands-on management. - Initial training will be conducted by other team members. Job Type & Location: - This is a Contract to Hire position based out of Ashland, VA. Pay And Benefits: - Pay range: $23.00 - $26.00/hr. - Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. - Benefits are subject to change and may be subject to specific elections, plan, or program terms. - If eligible, the benefits available for this temporary role may include the following: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type: - This is a fully onsite position in Ashland,VA. Application Deadline: - This position is anticipated to close on Sep 28, 2026. Now we need to decide sections. We'll have:

          About the role

          ... combine initial description, job type/location, workplace type, work environment details (team size, flexible hours, work culture, training). But we also have separate Schedule section for flexible hours; we could keep flexible hours in Schedule and not duplicate. However, we need to preserve all info; we can mention flexible hours in Schedule section and not repeat in About the role. But we can still mention team size, work culture, training. Thus About the role paragraph: include seeking Parts Coordinator, telephone interaction, obtaining serial numbers, typical call volume, daily tracking reports, backorder follow-up, processing orders, researching/sourcing parts, contract to hire based out of Ashland, VA, fully onsite, team comprises two members in Ashland and around eight in Fredericksburg, supportive work