Electro-Mechanical Assembler & Welder
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must include sections only when posting has real specific content. We need to parse the job posting.
We have: Job Title: Electro-Mechanical Assembler & Welder (not to be repeated as heading). Department: RWS Assembly. Position Summary: ... (some prose). Then FLSA: Non-exempt (metadata). Then Job Duties And Responsibilities (list). Then Education/Experience & Skills (list). Then Working Conditions (some prose). Then equal opportunity boilerplate (to remove). Also mention SIG SAUER description at top (company overview) - that is boilerplate? It's about company, not job specifics; we should remove cookie/navigation/legal/EEO etc. The company overview may be considered boilerplate but it's not navigation/legal; but it's generic description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company overview is not explicitly listed, but it's not part of job duties. However, we need to preserve ALL substantive information; does company overview count as substantive? It's about the company, not the job. Might be considered boilerplate but not explicitly prohibited. However typical job postings include company overview; but the instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It doesn't say remove company overview. But we might keep a brief "About the role" section? Actually "About the role" is a heading we can use for position summary. The company overview could be placed under "About the role" or maybe we can omit as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
We need sections: About the role (position summary), Responsibilities (duties), Requirements (education/experience), Skills (maybe combine with requirements?), Qualifications (maybe same as requirements). Benefits, Pay, Schedule only if present. The posting mentions shifts: 8,10,12 hours; overtime; regular on-site attendance; but no explicit pay or benefits. So we can include Schedule section (since shifts mentioned). Benefits not mentioned, so omit. Pay not mentioned, omit.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none present). Must preserve all substantive information.
Let's extract substantive content:
Company overview: SIG SAUER, Inc. is a leading provider... (the paragraph). Might be considered substantive but not job-specific. Could be placed under "About the role" or maybe a separate "About the company" but we don't have heading for that. Since we only allowed headings list, we could not add a custom heading. So we could incorporate into About the role paragraph.
Position Summary: The Electro-Mechanical Assembler & Welder is responsible for providing technical support to Engineers, other Technicians, and production team members in optimizing production processes within the RWS business unit. This position will perform high-quality welding operations, interpret technical drawings and specifications, and ensure welded assemblies meet quality, safety and performance standards. The Electro-Mechanical Assembler & Welder will be detail oriented and apply the ability to create work instructions, adjust tooling, diagnose issues, and optimize assembly lines for new processes or products. They will communicate with cross functional groups and have a general understanding of Quality Assurance procedures, manufacturing principles, and some knowledge of lean manufacturing concepts. Working independently and in a team environment, the Electro-Mechanical Assembler & Welder will collaborate with employees across all departments.
That's prose.
Job Duties And Responsibilities: list of items (starting with "Assemble electro-mechanical components...").
Education/Experience & Skills: list of items (starting with "High School diploma or equivalent required...").
Working Conditions: paragraph about repetitive tasks, standing, shifts, lifting, etc.
Also FLSA: Non-exempt (metadata) - we can fold into a short
maybe under About the role or as a note. But instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include FLSA as a short paragraph.
We must not include EEO boilerplate (the last paragraph about equal employment opportunities). Remove that.
Also remove duplicated lines (none visible). Remove application instructions (none). Remove cookie/navigation/legal etc.
Now decide sections:
- About the role: could include company overview + position summary + FLSA? Might be too much. Better: About the role = position summary (prose). Could also include brief company overview as part of About the role? Might be okay.
- Responsibilities = list of duties.
- Requirements = education/experience (maybe combine with skills). But we have separate Education/Experience & Skills section; we could split into Requirements (education/experience) and Skills (technical skills). However we must not create thin sections; we could combine into one "Requirements" section that includes both education/experience and skills as a list. But we need to follow instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to use. We could use Responsibilities, Requirements, Skills, Schedule. That's four sections.
We need to ensure we don't create sections with filler text. All have content.
Thus:
About the role
... position summary plus maybe company overview? We'll include position summary only; we can also incorporate a brief note about SIG SAUER being a leading provider etc. But that's not about the role. Might be okay to include as context. However the instruction says preserve ALL substantive information; company overview is substantive about the company, not the role. If we omit it, we lose some substantive info. But maybe it's considered boilerplate? Not sure. The instruction didn't list company overview as boilerplate to remove. So we should keep it. Where to put? Could be a separate section "About the company" but not allowed heading. Could fold into About the role as a preamble. That would be okay: About the role includes both company overview and position summary. That would preserve info.
Thus About the role paragraph: combine the company overview paragraph (starting with "SIG SAUER, Inc. is a leading provider...") and the position summary paragraph. We'll make one
containing both sentences (maybe two sentences). Ensure we don't repeat job title.
Then Responsibilities:
- each duty.
Then Requirements: maybe education/experience. But we also have skills list. Could split: Requirements (education/experience) and Skills (technical). That would be two sections, both substantive. That's okay.
Thus:
Requirements
High School diploma or equivalent required, related experience and/or training, or an equivalent combination of education and experience, and 2-5 years of assembly experience. Electromechanical assembly is preferred. 2-5 years of tig welding experience is required.
But also we have other requirements like experience with electromechanical systems, CAD programs, ability to learn new computer programs, etc. Those could be considered Skills. So we separate.
Thus Skills section: list of skills: Experience with electromechanical systems such as mechanical assemblies, PCBAs, wiring, and embedded hardware. Hands-on experience with electrical debugging tools including multimeter, oscilloscope and hardware bring-up. Experience with cable harness fabrication, printed circuit boards and soldering. Experience with machining processes, 3D printing or additive manufacturing is preferred. Experience with CAD programs such as SolidWorks, Inventor, AutoCAD, or relevant. Ability to learn new computer programs such as Excel, VISO, SolidWorks, and Oracle. High attention to detail. Ability to read and edit blueprints as needed for manufacturability. Display a positive attitude, behave in a professional manner and is self-motivated. Open to specific training and certification and/or continued education, and to performing cross training for other job responsibilities. Ability to work independently and within a team environment. Proficient in writing and math, and ability to follow verbal and written direction. Must be able to clearly, concisely, and accurately convey ideas and information to others, both verbally and in written form. Communicate effectively to supervision regarding problems and corrective action.
We could also include FLSA as a short p under About the role or separate? Probably fold into About the role as a short sentence.
Working Conditions: we need a Schedule section (since we have shift info). Also we have other working conditions like standing, lifting, etc. Could be part of Schedule? But Schedule heading is for schedule specifics; we could also include working conditions under Schedule or maybe we create a "Working Conditions" section but not in allowed headings list. The allowed headings list includes Schedule, Benefits, Pay, etc. Not Working Conditions. So we must fold working conditions into Schedule section or maybe into About the role? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't forbid creating a section not in the list; but the list is examples. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we can use those headings; we could also use other headings if needed? The examples are just examples; but to be safe, we should stick to those headings. So we need to fit working conditions into Schedule or maybe into About the role. Since Schedule is about shift hours, we can include both shift details and physical demands under Schedule. That would be okay.
Thus Schedule section:
Shifts are 8 hours, 10 hours, and 12 hours. Regular on-site attendance and punctuality is required. May be required to work overtime or alternate shifts, or in other functional areas, and/or facilities based on business needs. Work is primarily standing (90+% of the shift) except for lunch and break periods. Frequent standing, sitting, stooping, squatting, walking, and stair climbing can be expected along with frequent lifting and/or moving of tooling, parts containers, and materials up to 40 pounds. Must be able to reach with hands and arms, bend and kneel frequently at a minimum of 50% of the shift, as well as undergo repetitive wrist, hand, elbow, shoulder, and ankle motions. Must demonstrate proficient fine motor skills, ability to grip, reach, pull, turn, and use tools to torque fixtures in various machinery or in the assembly, machining, or testing of parts. Specific vision abilities required may include close vision, distance vision, peripheral and depth perception, and the ability to focus on fine print. Must wear required Personal Protective Equipment (PPE) where required. Must comply with all work exposure EH&S training requirements and adhere to SIG SAUER Inc. security mandates.
We should also include FLSA Non-exempt maybe as a short p under About the role or Schedule. Let's put under About the role as a sentence: "FLSA status: Non-exempt."
Now ensure we don't repeat any content inadvertently.
Let's craft HTML.
We'll output:
About the role
SIG SAUER, Inc. is a leading provider and manufacturer of firearms, electro-optics, ammunition, airguns, suppressors, remote controlled weapons stations, and training. For over 250 years SIG SAUER, Inc. has evolved, and thrived, by blending American ingenuity, German engineering, and Swiss precision. Today, SIG SAUER is synonymous with industry-leading quality and innovation which has made it the brand of choice amongst the U.S. Military, the global defense community, law enforcement, competitive shooters, hunters, and responsible citizens. Additionally, SIG SAU
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none present). Must preserve all substantive information. Let's extract substantive content: Company overview: SIG SAUER, Inc. is a leading provider... (the paragraph). Might be considered substantive but not job-specific. Could be placed under "About the role" or maybe a separate "About the company" but we don't have heading for that. Since we only allowed headings list, we could not add a custom heading. So we could incorporate into About the role paragraph. Position Summary: The Electro-Mechanical Assembler & Welder is responsible for providing technical support to Engineers, other Technicians, and production team members in optimizing production processes within the RWS business unit. This position will perform high-quality welding operations, interpret technical drawings and specifications, and ensure welded assemblies meet quality, safety and performance standards. The Electro-Mechanical Assembler & Welder will be detail oriented and apply the ability to create work instructions, adjust tooling, diagnose issues, and optimize assembly lines for new processes or products. They will communicate with cross functional groups and have a general understanding of Quality Assurance procedures, manufacturing principles, and some knowledge of lean manufacturing concepts. Working independently and in a team environment, the Electro-Mechanical Assembler & Welder will collaborate with employees across all departments. That's prose. Job Duties And Responsibilities: list of items (starting with "Assemble electro-mechanical components..."). Education/Experience & Skills: list of items (starting with "High School diploma or equivalent required..."). Working Conditions: paragraph about repetitive tasks, standing, shifts, lifting, etc. Also FLSA: Non-exempt (metadata) - we can fold into a short
maybe under About the role or as a note. But instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include FLSA as a short paragraph. We must not include EEO boilerplate (the last paragraph about equal employment opportunities). Remove that. Also remove duplicated lines (none visible). Remove application instructions (none). Remove cookie/navigation/legal etc. Now decide sections: - About the role: could include company overview + position summary + FLSA? Might be too much. Better: About the role = position summary (prose). Could also include brief company overview as part of About the role? Might be okay. - Responsibilities = list of duties. - Requirements = education/experience (maybe combine with skills). But we have separate Education/Experience & Skills section; we could split into Requirements (education/experience) and Skills (technical skills). However we must not create thin sections; we could combine into one "Requirements" section that includes both education/experience and skills as a list. But we need to follow instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to use. We could use Responsibilities, Requirements, Skills, Schedule. That's four sections. We need to ensure we don't create sections with filler text. All have content. Thus:
About the role
... position summary plus maybe company overview? We'll include position summary only; we can also incorporate a brief note about SIG SAUER being a leading provider etc. But that's not about the role. Might be okay to include as context. However the instruction says preserve ALL substantive information; company overview is substantive about the company, not the role. If we omit it, we lose some substantive info. But maybe it's considered boilerplate? Not sure. The instruction didn't list company overview as boilerplate to remove. So we should keep it. Where to put? Could be a separate section "About the company" but not allowed heading. Could fold into About the role as a preamble. That would be okay: About the role includes both company overview and position summary. That would preserve info. Thus About the role paragraph: combine the company overview paragraph (starting with "SIG SAUER, Inc. is a leading provider...") and the position summary paragraph. We'll make one
containing both sentences (maybe two sentences). Ensure we don't repeat job title. Then Responsibilities:
- each duty.
Then Requirements: maybe education/experience. But we also have skills list. Could split: Requirements (education/experience) and Skills (technical). That would be two sections, both substantive. That's okay.
Thus:
Requirements
High School diploma or equivalent required, related experience and/or training, or an equivalent combination of education and experience, and 2-5 years of assembly experience. Electromechanical assembly is preferred. 2-5 years of tig welding experience is required.
But also we have other requirements like experience with electromechanical systems, CAD programs, ability to learn new computer programs, etc. Those could be considered Skills. So we separate. Thus Skills section: list of skills: Experience with electromechanical systems such as mechanical assemblies, PCBAs, wiring, and embedded hardware. Hands-on experience with electrical debugging tools including multimeter, oscilloscope and hardware bring-up. Experience with cable harness fabrication, printed circuit boards and soldering. Experience with machining processes, 3D printing or additive manufacturing is preferred. Experience with CAD programs such as SolidWorks, Inventor, AutoCAD, or relevant. Ability to learn new computer programs such as Excel, VISO, SolidWorks, and Oracle. High attention to detail. Ability to read and edit blueprints as needed for manufacturability. Display a positive attitude, behave in a professional manner and is self-motivated. Open to specific training and certification and/or continued education, and to performing cross training for other job responsibilities. Ability to work independently and within a team environment. Proficient in writing and math, and ability to follow verbal and written direction. Must be able to clearly, concisely, and accurately convey ideas and information to others, both verbally and in written form. Communicate effectively to supervision regarding problems and corrective action. We could also include FLSA as a short p under About the role or separate? Probably fold into About the role as a short sentence. Working Conditions: we need a Schedule section (since we have shift info). Also we have other working conditions like standing, lifting, etc. Could be part of Schedule? But Schedule heading is for schedule specifics; we could also include working conditions under Schedule or maybe we create a "Working Conditions" section but not in allowed headings list. The allowed headings list includes Schedule, Benefits, Pay, etc. Not Working Conditions. So we must fold working conditions into Schedule section or maybe into About the role? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't forbid creating a section not in the list; but the list is examples. It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we can use those headings; we could also use other headings if needed? The examples are just examples; but to be safe, we should stick to those headings. So we need to fit working conditions into Schedule or maybe into About the role. Since Schedule is about shift hours, we can include both shift details and physical demands under Schedule. That would be okay. Thus Schedule section:
Shifts are 8 hours, 10 hours, and 12 hours. Regular on-site attendance and punctuality is required. May be required to work overtime or alternate shifts, or in other functional areas, and/or facilities based on business needs. Work is primarily standing (90+% of the shift) except for lunch and break periods. Frequent standing, sitting, stooping, squatting, walking, and stair climbing can be expected along with frequent lifting and/or moving of tooling, parts containers, and materials up to 40 pounds. Must be able to reach with hands and arms, bend and kneel frequently at a minimum of 50% of the shift, as well as undergo repetitive wrist, hand, elbow, shoulder, and ankle motions. Must demonstrate proficient fine motor skills, ability to grip, reach, pull, turn, and use tools to torque fixtures in various machinery or in the assembly, machining, or testing of parts. Specific vision abilities required may include close vision, distance vision, peripheral and depth perception, and the ability to focus on fine print. Must wear required Personal Protective Equipment (PPE) where required. Must comply with all work exposure EH&S training requirements and adhere to SIG SAUER Inc. security mandates.
We should also include FLSA Non-exempt maybe as a short p under About the role or Schedule. Let's put under About the role as a sentence: "FLSA status: Non-exempt." Now ensure we don't repeat any content inadvertently. Let's craft HTML. We'll output:About the role
SIG SAUER, Inc. is a leading provider and manufacturer of firearms, electro-optics, ammunition, airguns, suppressors, remote controlled weapons stations, and training. For over 250 years SIG SAUER, Inc. has evolved, and thrived, by blending American ingenuity, German engineering, and Swiss precision. Today, SIG SAUER is synonymous with industry-leading quality and innovation which has made it the brand of choice amongst the U.S. Military, the global defense community, law enforcement, competitive shooters, hunters, and responsible citizens. Additionally, SIG SAU
- each duty.
Then Requirements: maybe education/experience. But we also have skills list. Could split: Requirements (education/experience) and Skills (technical). That would be two sections, both substantive. That's okay.
Thus: