Order Picker 2nd Shift (3:00pm-11:00pm Mon-Fri)
Havis, Inc. · Warminster, PA · 3 wk ago
On-siteManagement$24/hrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate.
We need to parse the posting.
Job Title: Order Picker 2nd Shift (3pm-11pm Mon-Fri) **Up to $24/hr.** Department: Shipping Accountability: This Position Reports to the Shipping Supervisor
Responsibilities: bullet list.
Requirements: bullet list.
Work Environment – Manufacturing: bullet list (but not required sections; maybe we can include under "Work Environment" but not in allowed headings list; we could either omit or include as part of Responsibilities? The instruction: Use headings only from list; we can include other headings? It says use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate.
We need to parse the posting.
Job Title: Order Picker 2nd Shift (3pm-11pm Mon-Fri) **Up to $24/hr.** Department: Shipping Accountability: This Position Reports to the Shipping Supervisor
Responsibilities: bullet list.
Requirements: bullet list.
Work Environment – Manufacturing: bullet list (but not required sections; maybe we can include under "Work Environment" but not in allowed headings list; we could either omit or include as part of Responsibilities? The instruction: Use headings only from list; we can include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate; we could also include other headings if needed? But likely they want only those headings. However we have info like "Work Environment – Manufacturing" which is not in list; we could incorporate into Responsibilities or Requirements? Probably better to include as a separate section but not in allowed list? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: 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 create any heading we think appropriate, but they gave examples. Safer to stick to those headings; we can embed work environment details under Responsibilities or Requirements? Might be better to create a "Work Environment" heading even if not in examples, but risk violating instruction. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also add others if needed? The phrase "e.g." indicates examples, not exhaustive. So we can add Work Environment.
But they also say "Prefer a few substantive sections over many thin ones." So we might combine.
We have Pay: "**Up to $24/hr.**" Also later: "Competitive pay commensurate with education, skills, and experience". That's vague; we should not include Pay section if content is filler like "commensurate with experience". The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section if the only pay info is "Up to $24/hr." That's specific. So we can include Pay section with that detail.
Schedule: "2nd Shift (3pm-11pm Mon-Fri)" is specific. So we can include Schedule section.
Benefits: The posting lists: "Company offers Health, Dental, Vision and 401(k) Plan with employer match 100% employer paid STD, LTD and Life & ADD benefits Generous paid time off (PTO) and holiday benefits". That's specific. So Benefits section.
About the role: Could include department, reporting line, company description. The "Company Details" paragraph is substantive. Could be About the role or maybe a separate "Company Overview". But we can put under About the role.
Responsibilities: bullet list.
Requirements: bullet list.
Qualifications: maybe overlapping with Requirements; but we have Requirements list includes education, ability to lift, etc. Could treat Requirements as Qualifications. But we have both Requirements and Qualifications headings allowed. We could split: Requirements = hard skills, Qualifications = education/experience. But we risk thin sections. Better to combine into Requirements (or Qualifications). Since we have both headings allowed, we could make Requirements for the bullet list of abilities, and Qualifications for education (HS diploma/GED). But the bullet list includes both. Let's see: Requirements bullet list includes: Able to read and interpret quality documents; Able to apply common sense reasoning; Able to safely operate a forklift and other material handling equipment; High School Diploma, GED or equivalent experience; Employee must regularly be able to lift and move up to 50lbs; Employee must occasionally be able to lift and move up to 100lbs; Able to tolerate long periods of standing.
We could split: Qualifications = High School Diploma, GED or equivalent experience. Requirements = the rest. But that seems arbitrary.
Given instruction to prefer few substantive sections over many thin ones, we can just have Requirements section containing all bullet points. And skip Qualifications.
Skills: maybe not separate; we could treat abilities as skills. But we already have Requirements.
Thus sections: About the role (including department, reporting, company description), Responsibilities, Requirements, Benefits, Pay, Schedule.
We must not include filler like "Competitive pay commensurate with education, skills, and experience" - we will not include that line in Pay section; we will only include the specific "$24/hr". However we must preserve ALL substantive information; we cannot omit the "Competitive pay commensurate..." line because it's substantive? It's somewhat generic but still info. The rule says do not invent or summarize away detail. So we must keep that line too. But we cannot put it under Pay heading if it's filler? It's not exactly filler; it's a statement about pay being competitive and commensurate. It's not a specific number but still info. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests we should not create a Pay section if the only content is such placeholder. But we have both specific "$24/hr" and the generic statement. So we can include both; the section will have substantive content (the $24/hr) plus the generic statement. That's okay.
Thus Pay section will contain both lines.
Schedule: we have shift timing.
Benefits: we have list.
Now we need to format.
We must not include markdown code fences. Just raw HTML.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: 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 create any heading we think appropriate, but they gave examples. Safer to stick to those headings; we can embed work environment details under Responsibilities or Requirements? Might be better to create a "Work Environment" heading even if not in examples, but risk violating instruction. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also add others if needed? The phrase "e.g." indicates examples, not exhaustive. So we can add Work Environment.
But they also say "Prefer a few substantive sections over many thin ones." So we might combine.
We have Pay: "**Up to $24/hr.**" Also later: "Competitive pay commensurate with education, skills, and experience". That's vague; we should not include Pay section if content is filler like "commensurate with experience". The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section if the only pay info is "Up to $24/hr." That's specific. So we can include Pay section with that detail.
Schedule: "2nd Shift (3pm-11pm Mon-Fri)" is specific. So we can include Schedule section.
Benefits: The posting lists: "Company offers Health, Dental, Vision and 401(k) Plan with employer match 100% employer paid STD, LTD and Life & ADD benefits Generous paid time off (PTO) and holiday benefits". That's specific. So Benefits section.
About the role: Could include department, reporting line, company description. The "Company Details" paragraph is substantive. Could be About the role or maybe a separate "Company Overview". But we can put under About the role.
Responsibilities: bullet list.
Requirements: bullet list.
Qualifications: maybe overlapping with Requirements; but we have Requirements list includes education, ability to lift, etc. Could treat Requirements as Qualifications. But we have both Requirements and Qualifications headings allowed. We could split: Requirements = hard skills, Qualifications = education/experience. But we risk thin sections. Better to combine into Requirements (or Qualifications). Since we have both headings allowed, we could make Requirements for the bullet list of abilities, and Qualifications for education (HS diploma/GED). But the bullet list includes both. Let's see: Requirements bullet list includes: Able to read and interpret quality documents; Able to apply common sense reasoning; Able to safely operate a forklift and other material handling equipment; High School Diploma, GED or equivalent experience; Employee must regularly be able to lift and move up to 50lbs; Employee must occasionally be able to lift and move up to 100lbs; Able to tolerate long periods of standing.
We could split: Qualifications = High School Diploma, GED or equivalent experience. Requirements = the rest. But that seems arbitrary.
Given instruction to prefer few substantive sections over many thin ones, we can just have Requirements section containing all bullet points. And skip Qualifications.
Skills: maybe not separate; we could treat abilities as skills. But we already have Requirements.
Thus sections: About the role (including department, reporting, company description), Responsibilities, Requirements, Benefits, Pay, Schedule.
We must not include filler like "Competitive pay commensurate with education, skills, and experience" - we will not include that line in Pay section; we will only include the specific "$24/hr". However we must preserve ALL substantive information; we cannot omit the "Competitive pay commensurate..." line because it's substantive? It's somewhat generic but still info. The rule says do not invent or summarize away detail. So we must keep that line too. But we cannot put it under Pay heading if it's filler? It's not exactly filler; it's a statement about pay being competitive and commensurate. It's not a specific number but still info. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests we should not create a Pay section if the only content is such placeholder. But we have both specific "$24/hr" and the generic statement. So we can include both; the section will have substantive content (the $24/hr) plus the generic statement. That's okay.
Thus Pay section will contain both lines.
Schedule: we have shift timing.
Benefits: we have list.
Now we need to format.
We must not include markdown code fences. Just raw HTML.
We'll produce something like:
About the role
About the role
Department: Shipping. This position reports to the Shipping Supervisor. Havis is at the forefront of revolutionizing industries ... (the company details paragraph).
But we need to ensure we preserve all substantive info from company details. Let's copy the company details paragraph exactly as given, but we can trim extra whitespace. Company Details Havis is at the forefront of revolutionizing industries by unlocking the full potential of technology to drive productivity and enhance safety through innovative mobility solutions. We take pride in being the trusted partner of choice for technology providers, enabling them to move business forward in a wide range of industries, such as Retail & Hospitality, Public Safety, Energy & Utilities, Warehouse & Distribution, Field Operations, Transportation & Logistics, Healthcare, and Military Defense. Havis designs and manufactures market-leading Computing, Mounting, Power, and Transport Solutions. Our engineering and product development centers serve as the backbone of our commitment to excellence. With a team of highly-skilled engineers who have a deep understanding of design, manufacturing processes, and cutting-edge technologies, Havis consistently delivers products that set our market and industry standards and exceed customer expectations. Our state-of-the-art manufacturing facilities complement our engineering capabilities, allowing us to bring our design concepts to life with precision and efficiency. Our focus on quality and rigorous testing protocols ensures that our products are built to withstand the demands of real-world applications. We are a dynamic and customer-focused company that continuously strives to meet and exceed the evolving needs of our valued customers. We firmly believe that collaboration lies at the heart of successful partnerships, and we actively engage with our clients to understand their unique requirements, challenges, and goals. By fostering open lines of communication, we work together to develop innovative solutions that drive safety, productivity, and, ultimately, customer satisfaction. Havis collaborates with partners and customers to provide product information, installation support, updates on industry testing and validation requirements to solve diverse challenges in the field. Havis, Inc. - Website: www.havis.com Headquartered in Warminster, PA ISO 9001 and 14001 Certified - Quality Management System Fast growing company in a niche, growing marketplace We need to keep that as a paragraph. Now Responsibilities: bullet list. We'll produce- Read and analyze the order to be fulfilled ... etc. Requirements: bullet list. Benefits: we need to list: Health, Dental, Vision and 401(k) Plan with employer match; 100% employer paid STD, LTD and Life & ADD benefits; Generous paid time off (PTO) and holiday benefits. We can make a
- with those items.
Pay: we need to include "**Up to $24/hr.**" and "Competitive pay commensurate with education, skills, and experience". We'll keep the bold markup? The original had **Up to $24/hr.** which is markdown bold. In HTML we can keep as plain text "Up to $24/hr." maybe without markdown. We'll just output as text.
Schedule: "2nd Shift (3pm-11pm Mon-Fri)". We'll output as paragraph.
Now ensure we don't include any boilerplate like "Prepared by: Human Resources Approved by: Shipping Supervisor". That's metadata; we can drop it per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. This is minor metadata; we can drop it. Also we should not include "Work Environment – Manufacturing:" section; we could incorporate into Responsibilities or Requirements? The bullet list includes Machinery, Chemicals, Dust, Noise, Protective clothing. That's substantive info about work environment. We could add a section "Work Environment" but not in examples; but we could add under Responsibilities as an extra bullet? However the bullet list under Work Environment is separate from Responsibilities. It might be better to include a "Work Environment" heading. Since 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 they gave examples. Safer to include as a separate heading "Work Environment". It's substantive.
Thus we add a section Work Environment with bullet list.
Now we must ensure we don't create any heading with filler. All sections have real content.
Now produce HTML.
Let's craft.
We'll start with About the role
...
ThenResponsibilities
- ...
Requirements
- ...
Work Environment
- ...
Benefits
- ...
Pay
Up to $24/hr. Competitive pay commensurate with education, skills, and experience.
ThenSchedule
2nd Shift (3pm-11pm Mon-Fri)
Make sure no extra blank lines? It's fine. Now check we didn't miss any substantive info: Department line included in About the role. Reporting line included. Company details included. Responsibilities bullet list includes all 5 bullets. Requirements bullet list includes all 7 bullets. Work Environment bullet list includes Machinery, Chemicals, (See SDS), Dust, Noise, Protective clothing and equipment may be