Pre-Fab Helper/Welder
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat the job title as a heading (page already shows it).
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
2. **Analyze the Input Text:**
Let me parse the input carefully:
- "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA."
- Job Summary section: long paragraph about working in Pre-Fab Shop, installations, welding, alterations, additions/repairs, measuring, layout, hanging, threading pipe, soldering/braze pipe, setting mechanical equipment, working from ladders, complying with safety policies, maintaining Master Inventory List, advising PMs/Superintendents/Service Technicians/Estimators of material order statuses, travel may be required.
- Qualifications section:
- Recent related commercial electrical experience or equivalent education
- Welding experience
- Experience reading fabrication drawings and blueprints
- Experience bending pipe and running various types of conduit preferred
- High School Diploma/GED
- OSHA 10 or ability to obtain
- Successfully pass pre-employment (post offer) background check, and MVR check when responsibilities require operating motor vehicles.
- Company Overview: IES Commercial, Inc. – DBA IES Electrical, a subsidiary of IES Holdings, Inc. (IES), an equal opportunity/affirmative action employer. IES is traded on the NASDAQ under the symbol IESC. IES Commercial, Inc. operates diverse business units across the United States, each focusing on distinct market segments and geographies, with some business units operating nationally. Safety is Priority One – and our record shows it.
- Benefits: 401(k) Retirement Plan with company discretionary match, flexible medical-dental-vision insurance, short-term/long-term disability insurance, basic life/AD&D insurance, paid holidays, and highly competitive pay in addition to paid-time-off.
Now, I need to map these to the allowed sections using `
`. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's decide on section mapping:
- "About the role" could cover the job summary and company overview, but the rules say include a section ONLY when the posting has real, specific content for it. I need to be careful not to create thin sections.
- "Responsibilities" - the job summary duties.
- "Requirements" - maybe the qualifications? The rules list "Requirements" and "Qualifications" as possible headings. I'll use "Qualifications" for the qualifications list, and maybe "Requirements" for must-haves. But I need to check if the posting has distinct "Requirements" vs "Qualifications". The text has "Qualifications" listed, and then some requirements embedded. I'll use "Qualifications" for the list starting with "Recent related commercial electrical experience..." etc.
- "Skills" - maybe not explicitly separate, but could overlap. The rules say use headings when there's real content. I'll see if there's a distinct "Skills" section. Not really, so I might skip or merge.
- "Benefits" - clearly present, list is specific.
- "Pay" - the benefits section says "highly competitive pay" but doesn't give a specific range. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "highly competitive pay" but that's vague. However, it also says "Benefits: 401(k) Retirement Plan with company discretionary match, flexible medical-dental-vision insurance, short-term/long-term disability insurance, basic life/AD&D insurance, paid holidays, and highly competitive pay in addition to paid-time-off." So Benefits is clearly stated with specific items. Pay is mentioned as "highly competitive pay" which is vague. I'll include Benefits section with the specific benefits, and maybe not create a Pay section since it's not a specific salary range. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Benefits fully, and Pay is mentioned but not specified. I'll include Benefits, and maybe mention pay in a short paragraph or drop it. To be safe, I'll include Benefits section with the listed items, and not create a Pay section unless there's actual pay data.
- "Schedule" - not mentioned, so skip.
- "About the role" - I could combine job summary and company overview, but need to be careful. The rules say "Prefer a few substantive sections over many thin ones." I'll likely have Responsibilities, Qualifications, Benefits. Maybe "About the role" if I can merge summary + company overview meaningfully without filler. But the rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I can have "About the role" if I put the actual job summary and company info under it. But the headings examples are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to choose which to use. I think I'll do: Responsibilities, Qualifications, Benefits. Maybe "About the role" could contain the job summary, but then I'd be using an heading for that. Let's see the original: it has "Job Summary", "Qualifications", "Company Overview", "Benefits". The task says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say I must use all, only use them when there's content. And "Do NOT repeat the job title as a heading (the page already shows it)". So I can't have Pre-Fabrication Helper/Welder>.
Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This gives examples of valid headings. I should use appropriate ones from this list or similar, but only when there's real content.
Let's structure:
- I'll create sections: Responsibilities, Qualifications, Benefits. Possibly "About the role" but I need to check if the job summary and company overview are substantial enough. They are. But I need to map them. Maybe "About the role" can hold the job summary, and then company overview can be part of it or separate. However, the rule "Prefer a few substantive sections over many thin ones" suggests I shouldn't create too many. I'll go with Responsibilities (job summary duties), Qualifications (the qualifications list), and Benefits (the benefits list). I'll drop Company Overview as a separate section maybe, or fold it into Responsibilities or a brief
at the top. But the rules say remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview has "Safety is Priority One – and our record shows it." and the IES Holdings info. I need to remove EEO/equal-opportunity text. The posting says "an equal opportunity/affirmative action employer." That's EEO boilerplate, should be removed. Also "IES is traded on the NASDAQ under the symbol IESC" - that's corporate info, maybe keep? The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the equal opportunity statement. I can keep the company description maybe, but it's not strictly job-related. I'll fold minor metadata into a short
or drop it. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can have a short
at the beginning with location and job type, maybe company name is already in the title but we can't repeat job title. The input starts with "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA." I'll include that as a
at the top, not as a heading.
Let's plan the HTML structure:
- Start with a
containing the job title info? But rule: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say I can't include it in prose, but probably better to just have the description start. I'll put a
with the location and employment type maybe, but careful. Actually, the input has "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA." I'll put that as a
at the very top, maybe without the job title? But the rule says "the page already shows it", meaning I shouldn't add a heading for it. I can include it in a
if needed, but maybe just start with sections. To be safe, I'll omit the very first line or put it in a
without emphasizing it as a heading. The output should be just the HTML fragment with sections. I'll include a
with the location and type if it makes sense, but I'll prioritize the sections.
Let's list the content to include under each valid heading:
**Responsibilities**:
- Works in Pre-Fab Shop performing installations, welding, alterations, additions and/or repairs of electrical systems, conductors, and associated materials and equipment within the commercial electrical construction industry
- Measure, layout, hang, thread pipe, solder/braze pipe and set mechancial equipment
- Works from all types of ladders
- Complies with all company and customer safety policies and procedures
- Maintains Master Inventory List of all materials inbound and outbound and keeps shop supervisor apprised of inventory levels per respective assignments
- Advises Project Managers, Superintendents, Service Technicians, and Estimators of material order statuses
- Travel may be required.
**Qualifications**:
- Recent related commercial electrical experience or equivalent education
- Welding experience
- Experience reading fabrication drawings and blueprints
- Experience bending pipe and running various types of conduit preferred
- High School Diploma/GED
- OSHA 10 or ability to obtain
- Successfully pass pre-employment (post offer) background check, and MVR check when responsibilities require operating motor vehicles.
**
` for prose. - Do NOT repeat the job title as a heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** Let me parse the input carefully: - "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA." - Job Summary section: long paragraph about working in Pre-Fab Shop, installations, welding, alterations, additions/repairs, measuring, layout, hanging, threading pipe, soldering/braze pipe, setting mechanical equipment, working from ladders, complying with safety policies, maintaining Master Inventory List, advising PMs/Superintendents/Service Technicians/Estimators of material order statuses, travel may be required. - Qualifications section: - Recent related commercial electrical experience or equivalent education - Welding experience - Experience reading fabrication drawings and blueprints - Experience bending pipe and running various types of conduit preferred - High School Diploma/GED - OSHA 10 or ability to obtain - Successfully pass pre-employment (post offer) background check, and MVR check when responsibilities require operating motor vehicles. - Company Overview: IES Commercial, Inc. – DBA IES Electrical, a subsidiary of IES Holdings, Inc. (IES), an equal opportunity/affirmative action employer. IES is traded on the NASDAQ under the symbol IESC. IES Commercial, Inc. operates diverse business units across the United States, each focusing on distinct market segments and geographies, with some business units operating nationally. Safety is Priority One – and our record shows it. - Benefits: 401(k) Retirement Plan with company discretionary match, flexible medical-dental-vision insurance, short-term/long-term disability insurance, basic life/AD&D insurance, paid holidays, and highly competitive pay in addition to paid-time-off. Now, I need to map these to the allowed sections using `
`. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's decide on section mapping:
- "About the role" could cover the job summary and company overview, but the rules say include a section ONLY when the posting has real, specific content for it. I need to be careful not to create thin sections.
- "Responsibilities" - the job summary duties.
- "Requirements" - maybe the qualifications? The rules list "Requirements" and "Qualifications" as possible headings. I'll use "Qualifications" for the qualifications list, and maybe "Requirements" for must-haves. But I need to check if the posting has distinct "Requirements" vs "Qualifications". The text has "Qualifications" listed, and then some requirements embedded. I'll use "Qualifications" for the list starting with "Recent related commercial electrical experience..." etc.
- "Skills" - maybe not explicitly separate, but could overlap. The rules say use headings when there's real content. I'll see if there's a distinct "Skills" section. Not really, so I might skip or merge.
- "Benefits" - clearly present, list is specific.
- "Pay" - the benefits section says "highly competitive pay" but doesn't give a specific range. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "highly competitive pay" but that's vague. However, it also says "Benefits: 401(k) Retirement Plan with company discretionary match, flexible medical-dental-vision insurance, short-term/long-term disability insurance, basic life/AD&D insurance, paid holidays, and highly competitive pay in addition to paid-time-off." So Benefits is clearly stated with specific items. Pay is mentioned as "highly competitive pay" which is vague. I'll include Benefits section with the specific benefits, and maybe not create a Pay section since it's not a specific salary range. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Benefits fully, and Pay is mentioned but not specified. I'll include Benefits, and maybe mention pay in a short paragraph or drop it. To be safe, I'll include Benefits section with the listed items, and not create a Pay section unless there's actual pay data.
- "Schedule" - not mentioned, so skip.
- "About the role" - I could combine job summary and company overview, but need to be careful. The rules say "Prefer a few substantive sections over many thin ones." I'll likely have Responsibilities, Qualifications, Benefits. Maybe "About the role" if I can merge summary + company overview meaningfully without filler. But the rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I can have "About the role" if I put the actual job summary and company info under it. But the headings examples are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to choose which to use. I think I'll do: Responsibilities, Qualifications, Benefits. Maybe "About the role" could contain the job summary, but then I'd be using an heading for that. Let's see the original: it has "Job Summary", "Qualifications", "Company Overview", "Benefits". The task says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say I must use all, only use them when there's content. And "Do NOT repeat the job title as a heading (the page already shows it)". So I can't have Pre-Fabrication Helper/Welder>.
Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This gives examples of valid headings. I should use appropriate ones from this list or similar, but only when there's real content.
Let's structure:
- I'll create sections: Responsibilities, Qualifications, Benefits. Possibly "About the role" but I need to check if the job summary and company overview are substantial enough. They are. But I need to map them. Maybe "About the role" can hold the job summary, and then company overview can be part of it or separate. However, the rule "Prefer a few substantive sections over many thin ones" suggests I shouldn't create too many. I'll go with Responsibilities (job summary duties), Qualifications (the qualifications list), and Benefits (the benefits list). I'll drop Company Overview as a separate section maybe, or fold it into Responsibilities or a brief
Pre-Fabrication Helper/Welder>.
Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This gives examples of valid headings. I should use appropriate ones from this list or similar, but only when there's real content.
Let's structure:
- I'll create sections: Responsibilities, Qualifications, Benefits. Possibly "About the role" but I need to check if the job summary and company overview are substantial enough. They are. But I need to map them. Maybe "About the role" can hold the job summary, and then company overview can be part of it or separate. However, the rule "Prefer a few substantive sections over many thin ones" suggests I shouldn't create too many. I'll go with Responsibilities (job summary duties), Qualifications (the qualifications list), and Benefits (the benefits list). I'll drop Company Overview as a separate section maybe, or fold it into Responsibilities or a brief
at the top. But the rules say remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview has "Safety is Priority One – and our record shows it." and the IES Holdings info. I need to remove EEO/equal-opportunity text. The posting says "an equal opportunity/affirmative action employer." That's EEO boilerplate, should be removed. Also "IES is traded on the NASDAQ under the symbol IESC" - that's corporate info, maybe keep? The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the equal opportunity statement. I can keep the company description maybe, but it's not strictly job-related. I'll fold minor metadata into a short
or drop it. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can have a short
at the beginning with location and job type, maybe company name is already in the title but we can't repeat job title. The input starts with "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA." I'll include that as a
at the top, not as a heading. Let's plan the HTML structure: - Start with a
containing the job title info? But rule: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say I can't include it in prose, but probably better to just have the description start. I'll put a
with the location and employment type maybe, but careful. Actually, the input has "IES Commercial, Inc. – DBA IES Electrical, seeking full-time Pre-Fabrication Helper/Welder in Chester, VA." I'll put that as a
at the very top, maybe without the job title? But the rule says "the page already shows it", meaning I shouldn't add a heading for it. I can include it in a
if needed, but maybe just start with sections. To be safe, I'll omit the very first line or put it in a
without emphasizing it as a heading. The output should be just the HTML fragment with sections. I'll include a
with the location and type if it makes sense, but I'll prioritize the sections. Let's list the content to include under each valid heading: **Responsibilities**: - Works in Pre-Fab Shop performing installations, welding, alterations, additions and/or repairs of electrical systems, conductors, and associated materials and equipment within the commercial electrical construction industry - Measure, layout, hang, thread pipe, solder/braze pipe and set mechancial equipment - Works from all types of ladders - Complies with all company and customer safety policies and procedures - Maintains Master Inventory List of all materials inbound and outbound and keeps shop supervisor apprised of inventory levels per respective assignments - Advises Project Managers, Superintendents, Service Technicians, and Estimators of material order statuses - Travel may be required. **Qualifications**: - Recent related commercial electrical experience or equivalent education - Welding experience - Experience reading fabrication drawings and blueprints - Experience bending pipe and running various types of conduit preferred - High School Diploma/GED - OSHA 10 or ability to obtain - Successfully pass pre-employment (post offer) background check, and MVR check when responsibilities require operating motor vehicles. **