Technician Warehouse
Ervin Cable Construction LLC · Broken Arrow, OK · 3 wk ago
ManufacturingFull-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. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, application instructions. We need to preserve all substantive info.
Let's parse the posting:
- Intro: "Discover a more connected career At Ervin Cable Construction, LLC, as a Warehouse Technician, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK"
- Benefits list: "Weekly Paychecks Paid Time Off, Parental Leave, and Holidays Insurance (including medical, prescription drug, dental, vision, disability, life insurance) 401(k) w/ Company Match Stock Purchase Plan Education Reimbursement Legal Insurance Discounts on gym memberships, pet insurance, and much more!"
- What You’ll Do (Responsibilities): list of bullet points.
- What You’ll Need To (Requirements): list of bullet points.
- Physical abilities & exposures: details.
- Why grow your career with us: some prose about training, supportive environment, safety-first culture.
- Building stronger solutions together: EEO statement (should be removed as boilerplate). Also "Our company is an equal-opportunity employer..." remove.
Thus we need sections: About the role (intro), Responsibilities (What You’ll Do), Requirements (What You’ll Need To), maybe Qualifications (could be same as Requirements?), Skills (maybe physical abilities & exposures?), Benefits (list), Pay (maybe Weekly Paychecks?), Schedule (maybe not specified). The posting mentions Weekly Paychecks under benefits, but not explicit schedule. There's no explicit schedule like "full-time", "shift". So we should not create Schedule section unless there is real specific content. Pay: we have Weekly Paychecks mentioned; that is pay frequency. Could be considered Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated. Pay: "Weekly Paychecks" is a statement about pay frequency, so we can include Pay section with that detail. Schedule: not stated, so omit.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Qualifications and Requirements? The posting has "What You’ll Need To" which includes requirements like age, authorization, diploma, driver's license, DOT physical, forklift experience, computer knowledge, physical abilities. That could be Requirements. Qualifications maybe similar; but we can just use Requirements. Skills maybe we can include physical abilities & exposures as Skills? Or we could have a Skills section for "Basic knowledge of computer and inventory control systems" and "Experience operating a forklift and pallet jack is preferred". But those are already in Requirements. Might be better to have Requirements covering all needed qualifications, and Skills maybe not needed. However instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Thus sections:
- About the role: intro paragraph (including work location).
- Responsibilities: list of duties.
- Requirements: list of needed qualifications (including age, authorization, diploma, driver's license, DOT physical, forklift/pallet jack experience preferred, computer knowledge, physical abilities).
- Benefits: list of benefits.
- Pay: weekly paychecks.
We should not include Qualifications or Skills separately if they'd be thin.
Now format: 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. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, application instructions. We need to preserve all substantive info.
Let's parse the posting:
- Intro: "Discover a more connected career At Ervin Cable Construction, LLC, as a Warehouse Technician, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK"
- Benefits list: "Weekly Paychecks Paid Time Off, Parental Leave, and Holidays Insurance (including medical, prescription drug, dental, vision, disability, life insurance) 401(k) w/ Company Match Stock Purchase Plan Education Reimbursement Legal Insurance Discounts on gym memberships, pet insurance, and much more!"
- What You’ll Do (Responsibilities): list of bullet points.
- What You’ll Need To (Requirements): list of bullet points.
- Physical abilities & exposures: details.
- Why grow your career with us: some prose about training, supportive environment, safety-first culture.
- Building stronger solutions together: EEO statement (should be removed as boilerplate). Also "Our company is an equal-opportunity employer..." remove.
Thus we need sections: About the role (intro), Responsibilities (What You’ll Do), Requirements (What You’ll Need To), maybe Qualifications (could be same as Requirements?), Skills (maybe physical abilities & exposures?), Benefits (list), Pay (maybe Weekly Paychecks?), Schedule (maybe not specified). The posting mentions Weekly Paychecks under benefits, but not explicit schedule. There's no explicit schedule like "full-time", "shift". So we should not create Schedule section unless there is real specific content. Pay: we have Weekly Paychecks mentioned; that is pay frequency. Could be considered Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated. Pay: "Weekly Paychecks" is a statement about pay frequency, so we can include Pay section with that detail. Schedule: not stated, so omit.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Qualifications and Requirements? The posting has "What You’ll Need To" which includes requirements like age, authorization, diploma, driver's license, DOT physical, forklift experience, computer knowledge, physical abilities. That could be Requirements. Qualifications maybe similar; but we can just use Requirements. Skills maybe we can include physical abilities & exposures as Skills? Or we could have a Skills section for "Basic knowledge of computer and inventory control systems" and "Experience operating a forklift and pallet jack is preferred". But those are already in Requirements. Might be better to have Requirements covering all needed qualifications, and Skills maybe not needed. However instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Thus sections:
- About the role: intro paragraph (including work location).
- Responsibilities: list of duties.
- Requirements: list of needed qualifications (including age, authorization, diploma, driver's license, DOT physical, forklift/pallet jack experience preferred, computer knowledge, physical abilities).
- Benefits: list of benefits.
- Pay: weekly paychecks.
We should not include Qualifications or Skills separately if they'd be thin.
Now format: Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point exactly as in posting (maybe minor punctuation). Also keep the physical abilities & exposures details as part of Requirements (maybe as a sublist). We'll include them as bullet points under Requirements.
We need to remove boilerplate: EEO, legal, etc. Also remove "Connecting You To Great Benefits" heading? That's just a heading before benefits list; we can incorporate into Benefits section heading.
We need to keep "Work Location: Tulsa, OK" as part of About the role paragraph.
Now craft HTML:
About the role
As a Warehouse Technician at Ervin Cable Construction, LLC, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK
Responsibilities
- Prepare orders for shipment according to pick tickets and customer requirements
- Check and verify inventory to ensure availability of needed stock
- Notify the Supervisor of shortages and packaging material restocking needs
- Package and ship products according to packaging guidelines and practices
- Stock shelves in the warehouse and put away new materials
- Organize pick tickets and cross-check them with packing slips and work orders
- Receive, unload, and inspect shipments; confirm accuracy with packing slips and purchase orders
- Operate dolly, pallet jack, and/or forklift for loading and unloading materials
- Work overtime, travel, and perform on-call/afterhours responsibilities as needed
- Other duties as assigned
Requirements
- Be 18 years of age or older
- Authorization to work in the United States for this company
- High School Diploma, GED equivalent, or relevant work experience
- Valid State driver's license (cannot be Provisional), including an acceptable driving record
- Able to pass a DOT physical exam, resulting in a valid medical card
- Experience operating a forklift and pallet jack is preferred
- Basic knowledge of computer and inventory control systems
- Physical abilities & exposures: Routinely: work at heights, occasional entry into attics and crawl spaces and alone in remote locations, operate vehicle and heavy machinery; squeeze, fine hand motion, bend, stoop, stand, walk, climb stairs, and lift up to 55 pounds without assistance. Occasionally: work in confined spaces or remote locations with arms above shoulder level, lift greater than 55 pounds, squeeze, fine hand motion, and use portable ladder
Benefits
- Weekly Paychecks
- Paid Time Off, Parental Leave, and Holidays
- Insurance (including medical, prescription drug, dental, vision, disability, life insurance)
- 401(k) w/ Company Match
- Stock Purchase Plan
- Education Reimbursement
- Legal Insurance
- Discounts on gym memberships, pet insurance, and much more!
Pay
Weekly Paychecks
But note we already listed Weekly Paychecks in Benefits; but Pay section could just state that pay is weekly. However we might be duplicating. The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay with Weekly Paychecks may be thin. Perhaps we can incorporate Pay into Benefits? But they said to create Pay section only if posting actually states them. It does state Weekly Paychecks under benefits list. Could treat that as part of Benefits, not separate Pay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we include Benefits. Pay is also stated (Weekly Paychecks). But if we already have Benefits section that includes Weekly Paychecks, adding a Pay section may be redundant/thin. Better to omit Pay section and keep Weekly Paychecks within Benefits. However the Benefits list already includes Weekly Paychecks as first item. That satisfies pay info. So we can omit Pay section.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We might also include a short paragraph about "Why grow your career with us" as part of About the role or maybe a separate section like "About the company". But there is no specific heading for that; we could incorporate into About the role as additional prose. However the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also add other headings if appropriate, but we should avoid thin sections. The "Why grow your career with us" is substantive about training, supportive environment, safety-first culture. Could be a section like "About the company" or "Culture". But not in the given list; we could still use for a heading like "Why grow your career with us". The instruction didn't forbid other headings, just gave examples. It said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as needed, but we should prefer few substantive sections. Adding a Culture section may be worthwhile.
Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Why grow your career with us (Culture). That would be 5 sections.
We need to preserve all substantive info, including the "Why grow your career with us" paragraph and "Building stronger solutions together" (EEO) which we remove. So we keep the "Why grow your career with us" paragraph.
Thus:
About the role
As a Warehouse Technician at Ervin Cable Construction, LLC, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK
Responsibilities
...
Requirements
...
Benefits
...
Why grow your career with us
Your career here is more than just a job — it's your pathway to opportunity. Our hands-on training, supportive environment, and responsive leadership connect you to work with purpose. Our commitment to you extends beyond professional development to a safety-first culture that ensures you can do what you do best, with peace of mind.
We should not include the EEO paragraph.
Now ensure we didn't miss any substantive info: The "Connecting You To Great Benefits" heading is just a heading; we turned into Benefits section. The list of benefits we captured.
Check that we included all bullet points from Responsibilities: yes.
Check Requirements: we included all bullet points from "What You’ll Need To" plus physical abilities & exposures. Did we include "Experience operating a forklift and pallet jack is preferred"? Yes. Did we include "Basic knowledge of computer and inventory control systems"? Yes. Did we include "Valid State driver's license (cannot be Provisional), including an acceptable driving record"? Yes. Did we include "Able to pass a DOT physical exam, resulting in a valid medical card"? Yes. Did we include "High School Diploma, GED equivalent, or relevant work experience"? Yes. Did we include "Authorization to work in the United States for this company"? Yes. Did we include "Be 18 years of age or older"? Yes.
We also need to
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point exactly as in posting (maybe minor punctuation). Also keep the physical abilities & exposures details as part of Requirements (maybe as a sublist). We'll include them as bullet points under Requirements. We need to remove boilerplate: EEO, legal, etc. Also remove "Connecting You To Great Benefits" heading? That's just a heading before benefits list; we can incorporate into Benefits section heading. We need to keep "Work Location: Tulsa, OK" as part of About the role paragraph. Now craft HTML:
About the role
As a Warehouse Technician at Ervin Cable Construction, LLC, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK
Responsibilities
- Prepare orders for shipment according to pick tickets and customer requirements
- Check and verify inventory to ensure availability of needed stock
- Notify the Supervisor of shortages and packaging material restocking needs
- Package and ship products according to packaging guidelines and practices
- Stock shelves in the warehouse and put away new materials
- Organize pick tickets and cross-check them with packing slips and work orders
- Receive, unload, and inspect shipments; confirm accuracy with packing slips and purchase orders
- Operate dolly, pallet jack, and/or forklift for loading and unloading materials
- Work overtime, travel, and perform on-call/afterhours responsibilities as needed
- Other duties as assigned
Requirements
- Be 18 years of age or older
- Authorization to work in the United States for this company
- High School Diploma, GED equivalent, or relevant work experience
- Valid State driver's license (cannot be Provisional), including an acceptable driving record
- Able to pass a DOT physical exam, resulting in a valid medical card
- Experience operating a forklift and pallet jack is preferred
- Basic knowledge of computer and inventory control systems
- Physical abilities & exposures: Routinely: work at heights, occasional entry into attics and crawl spaces and alone in remote locations, operate vehicle and heavy machinery; squeeze, fine hand motion, bend, stoop, stand, walk, climb stairs, and lift up to 55 pounds without assistance. Occasionally: work in confined spaces or remote locations with arms above shoulder level, lift greater than 55 pounds, squeeze, fine hand motion, and use portable ladder
Benefits
- Weekly Paychecks
- Paid Time Off, Parental Leave, and Holidays
- Insurance (including medical, prescription drug, dental, vision, disability, life insurance)
- 401(k) w/ Company Match
- Stock Purchase Plan
- Education Reimbursement
- Legal Insurance
- Discounts on gym memberships, pet insurance, and much more!
Pay
Weekly Paychecks
But note we already listed Weekly Paychecks in Benefits; but Pay section could just state that pay is weekly. However we might be duplicating. The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay with Weekly Paychecks may be thin. Perhaps we can incorporate Pay into Benefits? But they said to create Pay section only if posting actually states them. It does state Weekly Paychecks under benefits list. Could treat that as part of Benefits, not separate Pay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we include Benefits. Pay is also stated (Weekly Paychecks). But if we already have Benefits section that includes Weekly Paychecks, adding a Pay section may be redundant/thin. Better to omit Pay section and keep Weekly Paychecks within Benefits. However the Benefits list already includes Weekly Paychecks as first item. That satisfies pay info. So we can omit Pay section. Thus sections: About the role, Responsibilities, Requirements, Benefits. We might also include a short paragraph about "Why grow your career with us" as part of About the role or maybe a separate section like "About the company". But there is no specific heading for that; we could incorporate into About the role as additional prose. However the instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also add other headings if appropriate, but we should avoid thin sections. The "Why grow your career with us" is substantive about training, supportive environment, safety-first culture. Could be a section like "About the company" or "Culture". But not in the given list; we could still use
for a heading like "Why grow your career with us". The instruction didn't forbid other headings, just gave examples. It said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as needed, but we should prefer few substantive sections. Adding a Culture section may be worthwhile. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Why grow your career with us (Culture). That would be 5 sections. We need to preserve all substantive info, including the "Why grow your career with us" paragraph and "Building stronger solutions together" (EEO) which we remove. So we keep the "Why grow your career with us" paragraph. Thus:
About the role
As a Warehouse Technician at Ervin Cable Construction, LLC, you’ll keep everything running smoothly by managing the receipt, storage, and distribution of goods. You’ll ensure orders are filled accurately, track inventory, and follow safety and packaging guidelines, all while working with equipment and handling materials to support the team. Work Location: Tulsa, OK
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Why grow your career with us
Your career here is more than just a job — it's your pathway to opportunity. Our hands-on training, supportive environment, and responsive leadership connect you to work with purpose. Our commitment to you extends beyond professional development to a safety-first culture that ensures you can do what you do best, with peace of mind.
We should not include the EEO paragraph. Now ensure we didn't miss any substantive info: The "Connecting You To Great Benefits" heading is just a heading; we turned into Benefits section. The list of benefits we captured. Check that we included all bullet points from Responsibilities: yes. Check Requirements: we included all bullet points from "What You’ll Need To" plus physical abilities & exposures. Did we include "Experience operating a forklift and pallet jack is preferred"? Yes. Did we include "Basic knowledge of computer and inventory control systems"? Yes. Did we include "Valid State driver's license (cannot be Provisional), including an acceptable driving record"? Yes. Did we include "Able to pass a DOT physical exam, resulting in a valid medical card"? Yes. Did we include "High School Diploma, GED equivalent, or relevant work experience"? Yes. Did we include "Authorization to work in the United States for this company"? Yes. Did we include "Be 18 years of age or older"? Yes. We also need to