Senior Quality Technician , Certified Welding Technician
Lozier Corporation · Middlebury, IN · 4 wk ago
Quality AssuranceFull-time
We need to output HTML fragment with sections: Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, there is introductory text about Lozier, then "Middlebury Office Hourly/Salary Want to learn more..." then "Benefits And Schedule" with details. Then "Position Summary" then "ESSENTIAL JOB FUNCTIONS – (depending On Area Of Assignment)" then list of functions. Then "Certified Welding Inspector" (maybe a subrole). Then "Job Qualifications" with Education, Experience, Active AWS CWI required. Then "Required Skills" list. Then "Certified Weld Inspector" repeated. Then "Preferred Skills". Then "SPECIAL DEMANDS". Then more boilerplate.
We need to extract substantive content.
We need sections: About the role (maybe position summary?), Responsibilities (essential job functions), Requirements (maybe job qualifications?), Qualifications (maybe education/experience?), Skills (required skills), Benefits, Pay, Schedule.
We need to avoid duplication and filler.
Let's extract:
About the role: Could be the "Position Summary" paragraph: "The Senior Quality Technician plays a pivotal role..." That's a prose description.
Responsibilities: The list under "ESSENTIAL JOB FUNCTIONS – (depending On Area Of Assignment)" includes many bullet-like sentences. Also the "Certified Welding Inspector" sublist maybe part of responsibilities? It seems like a separate role but still part of job functions. We'll treat them as responsibilities.
Requirements: Could be the "Job Qualifications" section: Education, Experience, Active AWS CWI certification required.
Qualifications: Might be overlapping with Requirements. But we need to decide: maybe Requirements = mandatory (education, experience, certification). Qualifications = preferred? However guidelines: Use headings only when posting has real specific content. We can combine maybe.
But we have both "Job Qualifications" and "Required Skills" and "Preferred Skills". So we can map:
- Requirements: Education, Experience, Certification (Active AWS CWI).
- Qualifications: maybe not needed separate; but we could put "Qualifications" as the same as Requirements? Might be redundant. Better to have Requirements for mandatory, Qualifications for preferred? But we have "Preferred Skills" separate.
We could do:
- Requirements: Education, Experience, Certification.
- Qualifications: (maybe not needed) but we could skip if no distinct content besides what's in Requirements. However there is "Job Qualifications" heading with Education, Experience, Active AWS CWI certification required for CWI positions. That's basically requirements. So we can put that under Requirements.
- Skills: Required Skills list.
- Benefits: list from "Benefits And Schedule": includes shift times, bonus potential, $6000 annually for second shift differential, PTO, paid holidays, competitive benefits package (medical, dental, vision first day), Onsite Health Clinic, 401(k) with employer match, Employee Assistance Program, Educational Assistance Program, Career Development Programs, Casual dress, Relocation benefits available, Monday thru Thursday schedule supporting 10 hour shifts, Friday thru Saturday schedule supporting 12 hour shifts.
But note schedule details also belong to Schedule section. So we need to separate Benefits and Schedule.
Pay: The posting mentions "Additional $6000 annually, for second shift pay differential ($230.77 on bi-weekly paycheck). Additional second shift hourly shift differential." Also "Company bonus potential." So we have pay info: base? Not given. But we have differential and bonus potential. So we can include Pay section with that info.
Schedule: The shift times: 1st shift 5:00am – 3:30pm, 2nd shift 3:30pm – 2:00am, 1st shift Weekend Friday, Saturday, Sunday 6:00am – 6:30pm, 2nd shift Weekend Friday, Saturday, Sunday 6:30pm – 7:00am. Also Monday thru Thursday schedule supporting 10 hour shifts, Friday thru Saturday schedule supporting 12 hour shifts. That's schedule info.
Thus we will have sections: About the role (Position Summary), Responsibilities (Essential Job Functions + Certified Welding Inspector tasks), Requirements (Education, Experience, Certification), Skills (Required Skills), Benefits, Pay, Schedule.
We should not repeat job title as heading. No Job ID etc.
We need to output only HTML fragment, using
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, there is introductory text about Lozier, then "Middlebury Office Hourly/Salary Want to learn more..." then "Benefits And Schedule" with details. Then "Position Summary" then "ESSENTIAL JOB FUNCTIONS – (depending On Area Of Assignment)" then list of functions. Then "Certified Welding Inspector" (maybe a subrole). Then "Job Qualifications" with Education, Experience, Active AWS CWI required. Then "Required Skills" list. Then "Certified Weld Inspector" repeated. Then "Preferred Skills". Then "SPECIAL DEMANDS". Then more boilerplate.
We need to extract substantive content.
We need sections: About the role (maybe position summary?), Responsibilities (essential job functions), Requirements (maybe job qualifications?), Qualifications (maybe education/experience?), Skills (required skills), Benefits, Pay, Schedule.
We need to avoid duplication and filler.
Let's extract:
About the role: Could be the "Position Summary" paragraph: "The Senior Quality Technician plays a pivotal role..." That's a prose description.
Responsibilities: The list under "ESSENTIAL JOB FUNCTIONS – (depending On Area Of Assignment)" includes many bullet-like sentences. Also the "Certified Welding Inspector" sublist maybe part of responsibilities? It seems like a separate role but still part of job functions. We'll treat them as responsibilities.
Requirements: Could be the "Job Qualifications" section: Education, Experience, Active AWS CWI certification required.
Qualifications: Might be overlapping with Requirements. But we need to decide: maybe Requirements = mandatory (education, experience, certification). Qualifications = preferred? However guidelines: Use headings only when posting has real specific content. We can combine maybe.
But we have both "Job Qualifications" and "Required Skills" and "Preferred Skills". So we can map:
- Requirements: Education, Experience, Certification (Active AWS CWI).
- Qualifications: maybe not needed separate; but we could put "Qualifications" as the same as Requirements? Might be redundant. Better to have Requirements for mandatory, Qualifications for preferred? But we have "Preferred Skills" separate.
We could do:
- Requirements: Education, Experience, Certification.
- Qualifications: (maybe not needed) but we could skip if no distinct content besides what's in Requirements. However there is "Job Qualifications" heading with Education, Experience, Active AWS CWI certification required for CWI positions. That's basically requirements. So we can put that under Requirements.
- Skills: Required Skills list.
- Benefits: list from "Benefits And Schedule": includes shift times, bonus potential, $6000 annually for second shift differential, PTO, paid holidays, competitive benefits package (medical, dental, vision first day), Onsite Health Clinic, 401(k) with employer match, Employee Assistance Program, Educational Assistance Program, Career Development Programs, Casual dress, Relocation benefits available, Monday thru Thursday schedule supporting 10 hour shifts, Friday thru Saturday schedule supporting 12 hour shifts.
But note schedule details also belong to Schedule section. So we need to separate Benefits and Schedule.
Pay: The posting mentions "Additional $6000 annually, for second shift pay differential ($230.77 on bi-weekly paycheck). Additional second shift hourly shift differential." Also "Company bonus potential." So we have pay info: base? Not given. But we have differential and bonus potential. So we can include Pay section with that info.
Schedule: The shift times: 1st shift 5:00am – 3:30pm, 2nd shift 3:30pm – 2:00am, 1st shift Weekend Friday, Saturday, Sunday 6:00am – 6:30pm, 2nd shift Weekend Friday, Saturday, Sunday 6:30pm – 7:00am. Also Monday thru Thursday schedule supporting 10 hour shifts, Friday thru Saturday schedule supporting 12 hour shifts. That's schedule info.
Thus we will have sections: About the role (Position Summary), Responsibilities (Essential Job Functions + Certified Welding Inspector tasks), Requirements (Education, Experience, Certification), Skills (Required Skills), Benefits, Pay, Schedule.
We should not repeat job title as heading. No Job ID etc.
We need to output only HTML fragment, using for headings, - for lists,
for prose.
We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We have none.
We need to ensure we don't include boilerplate like EEO, etc. We'll exclude the final paragraphs about "The above job description is meant to describe..." etc.
Now craft content.
About the role: Use the Position Summary paragraph(s). There's also introductory paragraph about Lozier? That's company overview, not about the role. The instruction: "About the role" heading should contain role-specific info. The company overview maybe not needed. But we could include it as part of About the role? The rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects a description of the role. The company overview is not about the role but could be considered part of About the role? Might be okay to include but it's not role-specific. However we must preserve ALL substantive information; we cannot omit company overview if it's substantive? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not about the role. However the headings are prescribed; we could put company overview under About the role as a paragraph. That seems acceptable.
Thus About the role will include the company overview paragraphs (first few paragraphs) plus the Position Summary.
Let's extract company overview:
"About Lozier Every day, millions of people interact with Lozier products without even realizing it. From the shelving in retail stores to the storage systems powering warehouses and online fulfillment, our products keep retail moving. If you’ve shopped in a store or ordered online, chances are you’ve experienced what we build. For 70 years and counting, Lozier Corporation has been the industry leader trusted by top brands across the country. Headquartered in Omaha, Nebraska, with facilities nationwide, we combine innovation, advanced manufacturing, and a people-centric culture to shape the future of retail. At Lozier, you’ll join a team that designs industry-leading solutions, builds products retailers and warehouses depend on, and be part of a company that prioritizes growth and development of its workforce. Middlebury Office Hourly/Salary Want to learn more about our culture and what it's like to work at Lozier? Watch this short Come Work With Me video to hear directly from a team member about their experiences and what makes our company a great place to build a career."
That's a bit messy; there is "Middlebury Office Hourly/Salary Want to learn more..." which seems like a call to action. We should keep it? It's not boilerplate; it's about learning more. Might be considered part of About the role. We'll keep.
Now Responsibilities: list essential job functions and Certified Welding Inspector tasks.
Essential job functions list:
- Champion Lozier’s Mission, Vision, and Core Values by demonstrating the behaviors that contribute to Lozier’s success.
- Conduct detailed inspections and tests on raw materials, in-process components, and finished products to ensure they meet established quality standards and specifications.
- Develop, implement, and maintain quality control processes, procedures, and documentation to ensure compliance with industry standards and regulatory requirements.
- Analyze quality data and generate reports to identify trends, root causes, and areas for improvement.
- Collaborate with cross functional teams to resolve quality issues and implement corrective actions.
- Provide training, guidance, and mentorship to team members and other staff on quality control procedures and best practices.
- Lead and participate in internal and external audits to ensure compliance with relevant standards.
- Utilize statistical process control (SPC) and other quality tools to monitor and improve manufacturing processes.
- Assist in the development and revision of quality policies, procedures, and work instructions.
- Investigate customer complaints and non-conformance issues, determining root causes, and recommending corrective and preventive actions.
- Stay current with industry trends, advancements, and best practices in quality assurance and control.
- Demonstrate regular attendance and timeliness in reporting to work, meetings, and completing assignments.
- Ability to work and interact well with others.
Then Certified Welding Inspector tasks:
- Perform specialized welding inspection activities, including visual and dimensional inspection of welded components.
- Interpret applicable welding codes, customer specifications, and quality requirements.
- Make final determinations regarding weld conformance to applicable AWS and customer requirements.
- Verify welding procedures and welder qualifications, as applicable.
- Identify and document weld discontinuities and nonconformances.
- Exercise stop-work authority when welding does not meet established quality or customer requirements.
- Collaborate cross functionally to drive welding-related corrective actions and process improvements.
- Provide technical guidance and mentorship to technicians performing welding inspection duties.
We'll combine these as responsibilities.
Requirements: Education, Experience, Certification.
From "Job Qualifications":
Education: Associate degree in quality management, quality assurance, manufacturing, or another related field is preferred.
Experience: Minimum of 7 years of experience in a quality, manufacturing and/or engineering role within a manufacturing environment, if degreed. Minimum of 9 years of experience in a quality, manufacturing and/or engineering role within a manufacturing environment, if non-degreed.
Active AWS Certified Welding Inspector (CWI) certification is required for CWI positions.
Thus requirements: Associate degree preferred (but not required?), experience minimums, CWI certification required for CWI positions. We'll keep as is.
Skills: Required Skills list:
- Strong knowledge of quality systems, standards, and methodologies.
- Proficient in the use of quality inspection tools and equipment.
- Excellent analytical and problem-solving skills with a keen attention to detail.
- Strong communication and interpersonal skills, with the ability to effectively collaborate with cross-functional teams.
- Experience with quality management software and data analysis tools.
- Ability to read and interpret engineering drawings, specifications, and technical documents.
Also there is "Certified Weld Inspector Active AWS Certified Welding Inspector (CWI) certification." That's a requirement, not skill.
Preferred Skills list:
- Quality certifications such as Certified Quality Technician (CQT) or Six Sigma Green Belt.
- Previous experience in manufacturing environment.
- Experience in use of Oracle software.
We could put Preferred Skills under Skills? But we have separate headings only for Skills; we could include both required and preferred under Skills, maybe differentiate with subheadings? Not allowed; we must use only headings. Could we include both required and preferred as separate under Skills heading? That's okay.
But we also have "SPECIAL DEMANDS" which includes physical demands and travel. That could be part of Requirements or maybe we could add a section? Not in prescribed headings. Could incorporate into Requirements or maybe under Responsibilities? Probably better to include under Requirements as additional requirements. However the instruction says to use headings only from list; we can't add new heading. So we need to fold special demands into an existing section, perhaps Requirements or Responsibilities. Since it's about physical demands, maybe under Requirements (as they are job requirements). We'll include a or
under Requirements.
Now Benefits: list from Benefits And Schedule.
Let's extract benefits:
- Company bonus potential.
- Additional $6000 annually, for second shift pay differential ($230.77 on bi-weekly paycheck). Additional second shift hourly shift differential.
- PTO (Paid Time Off) plus paid holidays.
- Competitive benefits package (Eligible for medical, dental, and vision benefits on the first day of employment).
- Onsite Health Clinic.
- for lists,
for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We have none. We need to ensure we don't include boilerplate like EEO, etc. We'll exclude the final paragraphs about "The above job description is meant to describe..." etc. Now craft content. About the role: Use the Position Summary paragraph(s). There's also introductory paragraph about Lozier? That's company overview, not about the role. The instruction: "About the role" heading should contain role-specific info. The company overview maybe not needed. But we could include it as part of About the role? The rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects a description of the role. The company overview is not about the role but could be considered part of About the role? Might be okay to include but it's not role-specific. However we must preserve ALL substantive information; we cannot omit company overview if it's substantive? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not about the role. However the headings are prescribed; we could put company overview under About the role as a paragraph. That seems acceptable. Thus About the role will include the company overview paragraphs (first few paragraphs) plus the Position Summary. Let's extract company overview: "About Lozier Every day, millions of people interact with Lozier products without even realizing it. From the shelving in retail stores to the storage systems powering warehouses and online fulfillment, our products keep retail moving. If you’ve shopped in a store or ordered online, chances are you’ve experienced what we build. For 70 years and counting, Lozier Corporation has been the industry leader trusted by top brands across the country. Headquartered in Omaha, Nebraska, with facilities nationwide, we combine innovation, advanced manufacturing, and a people-centric culture to shape the future of retail. At Lozier, you’ll join a team that designs industry-leading solutions, builds products retailers and warehouses depend on, and be part of a company that prioritizes growth and development of its workforce. Middlebury Office Hourly/Salary Want to learn more about our culture and what it's like to work at Lozier? Watch this short Come Work With Me video to hear directly from a team member about their experiences and what makes our company a great place to build a career." That's a bit messy; there is "Middlebury Office Hourly/Salary Want to learn more..." which seems like a call to action. We should keep it? It's not boilerplate; it's about learning more. Might be considered part of About the role. We'll keep. Now Responsibilities: list essential job functions and Certified Welding Inspector tasks. Essential job functions list: - Champion Lozier’s Mission, Vision, and Core Values by demonstrating the behaviors that contribute to Lozier’s success. - Conduct detailed inspections and tests on raw materials, in-process components, and finished products to ensure they meet established quality standards and specifications. - Develop, implement, and maintain quality control processes, procedures, and documentation to ensure compliance with industry standards and regulatory requirements. - Analyze quality data and generate reports to identify trends, root causes, and areas for improvement. - Collaborate with cross functional teams to resolve quality issues and implement corrective actions. - Provide training, guidance, and mentorship to team members and other staff on quality control procedures and best practices. - Lead and participate in internal and external audits to ensure compliance with relevant standards. - Utilize statistical process control (SPC) and other quality tools to monitor and improve manufacturing processes. - Assist in the development and revision of quality policies, procedures, and work instructions. - Investigate customer complaints and non-conformance issues, determining root causes, and recommending corrective and preventive actions. - Stay current with industry trends, advancements, and best practices in quality assurance and control. - Demonstrate regular attendance and timeliness in reporting to work, meetings, and completing assignments. - Ability to work and interact well with others. Then Certified Welding Inspector tasks: - Perform specialized welding inspection activities, including visual and dimensional inspection of welded components. - Interpret applicable welding codes, customer specifications, and quality requirements. - Make final determinations regarding weld conformance to applicable AWS and customer requirements. - Verify welding procedures and welder qualifications, as applicable. - Identify and document weld discontinuities and nonconformances. - Exercise stop-work authority when welding does not meet established quality or customer requirements. - Collaborate cross functionally to drive welding-related corrective actions and process improvements. - Provide technical guidance and mentorship to technicians performing welding inspection duties. We'll combine these as responsibilities. Requirements: Education, Experience, Certification. From "Job Qualifications": Education: Associate degree in quality management, quality assurance, manufacturing, or another related field is preferred. Experience: Minimum of 7 years of experience in a quality, manufacturing and/or engineering role within a manufacturing environment, if degreed. Minimum of 9 years of experience in a quality, manufacturing and/or engineering role within a manufacturing environment, if non-degreed. Active AWS Certified Welding Inspector (CWI) certification is required for CWI positions. Thus requirements: Associate degree preferred (but not required?), experience minimums, CWI certification required for CWI positions. We'll keep as is. Skills: Required Skills list: - Strong knowledge of quality systems, standards, and methodologies. - Proficient in the use of quality inspection tools and equipment. - Excellent analytical and problem-solving skills with a keen attention to detail. - Strong communication and interpersonal skills, with the ability to effectively collaborate with cross-functional teams. - Experience with quality management software and data analysis tools. - Ability to read and interpret engineering drawings, specifications, and technical documents. Also there is "Certified Weld Inspector Active AWS Certified Welding Inspector (CWI) certification." That's a requirement, not skill. Preferred Skills list: - Quality certifications such as Certified Quality Technician (CQT) or Six Sigma Green Belt. - Previous experience in manufacturing environment. - Experience in use of Oracle software. We could put Preferred Skills under Skills? But we have separate headings only for Skills; we could include both required and preferred under Skills, maybe differentiate with subheadings? Not allowed; we must use only
headings. Could we include both required and preferred as separate
- under Skills heading? That's okay.
But we also have "SPECIAL DEMANDS" which includes physical demands and travel. That could be part of Requirements or maybe we could add a section? Not in prescribed headings. Could incorporate into Requirements or maybe under Responsibilities? Probably better to include under Requirements as additional requirements. However the instruction says to use headings only from list; we can't add new heading. So we need to fold special demands into an existing section, perhaps Requirements or Responsibilities. Since it's about physical demands, maybe under Requirements (as they are job requirements). We'll include a
or
- under Requirements.
Now Benefits: list from Benefits And Schedule.
Let's extract benefits:
- Company bonus potential.
- Additional $6000 annually, for second shift pay differential ($230.77 on bi-weekly paycheck). Additional second shift hourly shift differential.
- PTO (Paid Time Off) plus paid holidays.
- Competitive benefits package (Eligible for medical, dental, and vision benefits on the first day of employment).
- Onsite Health Clinic.