Parts Inventory Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract from posting. Job title: Parts Inventory Specialist (full-time). Not to repeat as heading. We need sections: - About the role: maybe a short description of role purpose. The posting includes: "This role supports both fulfilling parts requests and receiving inventory activities to help us fulfill our mission to keep equipment healthy for patient care." Also earlier description of BMES. Could put that. - Responsibilities: list of duties from "What You Will Do". That's a bullet list. - Requirements: maybe "What You Will Bring" includes ability to pass drug screen, high school diploma, preferred experience, ability to lift 40 lbs, etc. Could treat as Requirements. - Qualifications: maybe not separate; but we could combine with Requirements? The instruction says use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Skills: maybe "Skilled in active listening and problem solving", "Experience with ERP systems and Microsoft applications", "Excellent verbal and written communication skills". Could be Skills. Benefits: there is a "Benefits & Perks" section with details: Competitive compensation package with salary, incentives, company ownership/equity, and comprehensive benefits (401k match, health, college debt reduction, and more!); Career and professional development; Hybrid culture; Inclusive and diverse community. So we have Benefits. Pay: Not explicitly stated; only "Competitive compensation package". No specific salary. According to rule: do NOT create Pay section unless posting actually states them. It does not give specific pay, just says competitive compensation. That's vague; maybe we should not include Pay because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since Pay is not stated specifically, we should omit Pay section. Schedule: Not mentioned; maybe full-time implied but not explicit schedule. So omit Schedule. Qualifications: Could be separate from Requirements? The posting includes "What You Will Bring" which includes both requirements and qualifications. We could split: Requirements: ability to pass drug screen, high school diploma, ability to lift 40 lbs. Qualifications: Preferred experience with materials, inventory, receiving; Experience with ERP systems and Microsoft applications; Excellent verbal and written communication skills; Positive attitude; Skilled in active listening and problem solving. But the instruction says prefer a few substantive sections over many thin ones. Might combine Requirements and Qualifications into one? But we have headings for both; we could include both if they have content. Let's see. We have: - About the role: we have description. - Responsibilities: list. - Requirements: maybe "Ability to pass a drug screen and background check; High school diploma or GED equivalent; Ability to lift 40 lbs". That's specific. - Qualifications: maybe "Preferred experience with materials, inventory, and/or receiving best practices; Experience with ERP systems and Microsoft applications (Excel, Teams, SharePoint, etc); Excellent verbal and written communication skills; Skilled in active listening and problem solving; Positive “How can I help” attitude". That's specific. - Skills: maybe overlapping with Qualifications; but we could treat Skills as "Skilled in active listening and problem solving; Experience with ERP systems and Microsoft applications; Excellent verbal and written communication skills". However that duplicates. Better to not have Skills if we already have Qualifications covering skills. But we need to follow instruction: use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; we can omit if no real specific content. Since we already have Qualifications covering skills, we could omit Skills to avoid thin sections. But we could also include Skills if we have distinct content. Let's see if we can distinct: Qualifications could be education/experience; Skills could be abilities. The posting includes both. So we could have: Qualifications: High school diploma or GED equivalent; Preferred experience with materials, inventory, receiving; Ability to pass drug screen and background check; Ability to lift 40 lbs. Skills: Skilled in active listening and problem solving; Experience with ERP systems and Microsoft applications; Excellent verbal and written communication skills; Positive “How can I help” attitude. That seems reasonable. Benefits: we have content. Pay: omitted. Schedule: omitted. Now we need to output HTML fragment: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO paragraph, legal authorization, etc. Also remove "Interested? We’d love to hear from you! Submit your resume and an optional cover letter explaining why you’d be a great fit." That's application instructions; remove. Also remove "About PartsSource" section? That's company description; maybe not needed as it's boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About PartsSource" is not explicitly boilerplate but could be considered company overview; but it's substantive? It describes the company; might be considered part of posting but not required for role. However we need to preserve ALL substantive information; does that include company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About PartsSource paragraph? However earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The About PartsSource is not those; it's company description. Might be considered substantive. But we also have a section "About the role" we could include that description. The About PartsSource could be considered company overview; maybe we can include it under About the role? But we already have About the role for role purpose. Could we include a separate section "About the Company"? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like About the Company. So we must either incorporate that info into About the role (maybe as part of role description) or drop it. The instruction says preserve ALL substantive information; we cannot drop it if it's substantive. But we can incorporate it into About the role prose. That would preserve it. Thus About the role paragraph can include both role purpose and company description. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now construct HTML. We'll have:

  About the role

  ... prose ...

  Then

  Responsibilities

  • ... each duty ...
  Then

  Requirements

  • ... each requirement ...
  Then

  Qualifications

  • ... each qualification ...
  Then

  Skills

  • ... each skill ...
  Then

  Benefits

  • ... each benefit ...
  We must not include Pay or Schedule. Now extract specifics. About the role prose: combine: "PartsSource is the leading technology and software platform for managing mission-critical healthcare equipment. Trusted by over 5,000 US hospitals and 15,000 clinical sites, PartsSource empowers providers and service organizations to maximize clinical availability for patient care and automates the procurement of parts, services and training through a unique digital experience. PartsSource team members are deeply committed to our mission of Ensuring Healthcare is Always On®, which is foundational to our success and growth. Our vibrant culture is built upon aligned values, shared ownership, mutual respect, and a passion for collaborating to solve complex customer problems. Bio-Medical Equipment Services (BMES) of Louisville, KY, is looking to hire an experienced full-time Parts Inventory Specialist. BMES is a national biomedical equipment repair depot providing quality service and products involving Patient Monitoring Equipment and Infusion Pumps for hospitals throughout the U.S. and Canada. This role supports both fulfilling parts requests and receiving inventory activities to help us fulfill our mission to keep equipment healthy for patient care." That seems good. Now Responsibilities list from "What You Will Do". The text: "Pulll and timely distribute technician requests for parts, equipment or supplies from on hand stock or disassembled units Disassemble medical equipment and accurately record the individual parts Ensure inventory is organized, labeled, and restocked Assemble various parts kits to be requested by and distributed to technicians Accurately record and track parts movement in the inventory system Communicate effectively with technicians and team members to ensure parts accuracy and timeliness Assist with receiving activities including physical intake of goods, verification against purchase orders, discrepancy communication, items put away, and packaging disposal Assist with regular inventory audits and cycle counts Keep materials area clean and organized Support cross-departmental collaboration and continuous improvement efforts Ensure compliance with BMES policies, procedures, and Quality Management System Assist with various departmental activities and functions as needed" Note there's a typo "Pulll". We must preserve as is? Probably keep exactly as given. We'll keep each line as
• . Now Requirements list: from "What You Will Bring" first few items: "Ability to pass a drug screen and background check High school diploma or GED equivalent Preferred experience with materials, inventory, and/or receiving best practices Ability to lift 40 lbs" But "Preferred experience..." maybe more qualification. However we can treat as Requirement? Let's split: Requirements: ability to pass drug screen, high school diploma, ability to lift 40 lbs. Qualifications: Preferred experience with materials, inventory, receiving; Experience with ERP systems and Microsoft applications; Excellent verbal and written communication skills; Skilled in active listening and problem solving; Positive “How can I help” attitude. But we also have "Preferred experience with materials, inventory, and/or receiving best practices" could be qualification. We'll put that in Qualifications. Now Skills list: "Skilled in active listening and problem solving", "Experience with ERP systems and Microsoft applications (Excel, Teams, SharePoint, etc)", "Excellent verbal and written communication skills", "Positive “How can I help” attitude". However we already put positive attitude in Qualifications; maybe move to Skills. Let's decide: Qualifications: Preferred experience with materials, inventory, receiving; Ability to lift 40 lbs? Actually we already used lift 40 lbs in Requirements. Let's keep lift 40 lbs in Requirements. Qualifications: Preferred experience with materials, inventory, receiving; Experience with ERP systems and Microsoft applications; Excellent verbal and written communication skills; Skilled in active listening and problem solving; Positive “How can I help” attitude. Skills: maybe we could leave empty? Better to not have Skills if we already covered. But we need to decide if we want Skills section. Since we have Qualifications covering many, we could omit Skills to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. But we already have Qualifications heading; we could put all under Qualifications. Then we don't need Skills heading. That seems better: one Qualifications section covering experience, skills, attitude. Thus we will have: - About the role - Responsibilities - Requirements