Cycle Counter
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. Let's extract content: - Intro paragraph: "United. Inspired. Performance unites us, innovation inspires us, and commitment drives us to keep moving forward. All new thinkers are welcome. We are looking for candidates who want to develop, grow, and dare to think new. Innovation is an important part of our DNA. If you appreciate an environment where you get to think new and constantly evolve, you will thrive here. Join Our Team as a Cycle Counter at Epiroc!" This is like an overview; could be "About the role" maybe. But we need to decide sections. We have "Responsibilities:" then a list of duties. We have "Knowledge/Education:" then bullet-like sentences. We have "Skills and Abilities:" then bullet-like sentences. We have "About us." then description of company. We have "Work Type: This position will be based onsite at our Milwaukie, OR facility. This job opening is not eligible for immigration/work visa sponsorship. Shift Timings: 1st shift". That's metadata; we can fold into a short
maybe under "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with work type and shift timings. We have no explicit Pay, Benefits, Schedule details besides shift timings (1st shift). Schedule could be considered shift timings; but we should only create Schedule section if posting actually states them. It does state "Shift Timings: 1st shift". That's schedule info. So we could include a Schedule section with that. However instruction: Prefer a few substantive sections over many thin ones. Could combine schedule into About the role? But schedule is separate info; maybe we can include a short
under About the role. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state shift timings, so we could create a Schedule section. But we need to see if it's substantive enough: just "1st shift". That's thin. Might be better to fold into About the role paragraph. Similarly, Benefits: none mentioned. Pay: none. Thus we likely have sections: About the role (intro + work type/shift), Responsibilities, Knowledge/Education (maybe as Requirements/Qualifications), Skills and Abilities (Skills), About us (Company overview). Could also combine Knowledge/Education and Skills and Abilities into Requirements and Skills sections. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those that have content. We have content for About the role (intro + work type/shift). Responsibilities (list). Requirements (knowledge/education). Qualifications maybe same as requirements? Could combine. But we have both Knowledge/Education and Skills and Abilities; we could map Knowledge/Education to Requirements, Skills and Abilities to Skills. Qualifications maybe not needed separately. Thus sections: About the role, Responsibilities, Requirements, Skills. Also maybe About us (company description) could be under About the role? But we could add a section "About the company" but not in allowed headings list. Allowed headings are only those listed; we cannot invent new headings like About us. So we must either omit that info or fold into About the role. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. Likely we should only use those headings. So we need to incorporate company description into About the role or maybe under Responsibilities? Better to put in About the role.
Thus About the role will contain: introductory paragraph, work type/shift, and company overview.
Responsibilities: list of duties.
Requirements: knowledge/education.
Skills: skills and abilities.
We must not repeat the job title as a heading. The job title is "Cycle Counter". We'll not use that as heading.
We must not include boilerplate like EEO etc. Remove those.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- or
- High school diploma or GED required.
- Prior experience with cycle counting, inventory control, warehouse operations, material handling, or inventory movements preferred.
- Experience using ERP/MRP systems in a manufacturing or distribution environment is preferred; experience with Infor Syteline or M3 is a plus.
- Forklift or powered industrial truck certification required when operating applicable equipment; ability to obtain and maintain company authorization is acceptable at hire.
- Ability to read, write, communicate, and perform the calculations necessary to complete inventory-control work accurately.
? The knowledge/education is sentences; could be