Production Test Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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.
We need to decide which sections to include based on content. The posting includes:
- Overview: Who We Are, Why We Are Different, What You Will Get (benefits)
- Summary/Objective: description of role
- Essential Functions (list of duties)
- Working Conditions (description)
- Qualifications (list)
- Competencies (list)
- Supervisory Responsibility (statement)
- Physical Demands (description)
- Position Type/Expected Hours Of Work (full-time salary)
- Travel (minimal)
- Preferred Education And Experience (list)
- Additional Eligibility Qualifications (None)
- Work Authorization/Security Clearance (must be legally authorized)
- Other Duties (note about job description not comprehensive)
- Pay Group : AAP/EEO Statement (EEO boilerplate, we should remove)
- Know Your Rights (boilerplate, remove)
We need to remove EEO/legal boilerplate. Also remove "Other Duties" maybe? It's not boilerplate but it's a generic statement; but it's substantive? It says "Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the Team Member for this job. Duties, responsibilities, and activities may change at any time with or without notice." That's generic but still part of posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other Duties" is not exactly legal boilerplate but it's a standard disclaimer. Might be considered boilerplate? Not sure. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Other Duties" is substantive? It's a disclaimer but still part of job description. I'd keep it as a
maybe under a section like "Additional Information". But we are told to prefer few substantive sections over many thin ones. Could combine many items into sections like "About the role", "Responsibilities", "Requirements", "Benefits", etc. However we must only create sections when posting has real specific content.
We have benefits: "What You Will Get A unique, inclusive and supportive company culture.Comprehensive benefit offerings including medical, dental, vision, 401k with employer match, vacation, and more! Fair and competitive compensation. Career development and mentoring and opportunities to grow.Holiday, personal and vacation days." That's benefits content. So we can have a Benefits section.
We have Pay: Not explicitly stated; only "Fair and competitive compensation." No specific pay. So we should NOT create a Pay section because no specific pay.
Schedule: Position Type/Expected Hours Of Work: "This is a full-time salary position, and hours/days worked are decided by your reporting manager." That's schedule info. So we can create a Schedule section.
We have About the role: Could combine Who We Are, Why We Are Different, Summary/Objective. But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. We could use those exact headings if content matches.
We need to map content:
- About the role: Could include Who We Are, Why We Are Different, Summary/Objective (overview of role and company). That's substantive.
- Responsibilities: Essential Functions (list). Also maybe Working Conditions? But Working Conditions is more about environment; could be part of Responsibilities or separate. But we can put Working Conditions under Responsibilities as a paragraph? Better to keep separate? The instruction: prefer few substantive sections over many thin ones. So we could combine Responsibilities and Working Conditions into one Responsibilities section? But Working Conditions is not a responsibility; it's about environment. Could be its own section but that would be thin. Maybe we can include Working Conditions as a paragraph under Responsibilities.
- Requirements: Qualifications list (proficiency in circuit analysis etc.) plus Preferred Education And Experience (list). Also maybe Competencies? Those are skills/behaviors. Could be Skills section.
- Skills: Competencies list (Communications proficiency, Collaboration, Time Management, Adaptability, Training, Project ownership, Risk management). Also maybe Preferred Education And Experience includes some skills like VB.NET, CAD, scripting, etc. Actually those are under Preferred Education And Experience. So Skills section could include both Competencies and Preferred technical skills.
- Benefits: What You Will Get.
- Schedule: Position Type/Expected Hours Of Work + Travel.
We also have Physical Demands and Supervisory Responsibility. Those could be placed under Requirements or maybe a separate section like "Additional Information". But we need to avoid thin sections. Could incorporate Physical Demands under Requirements? Not exactly. Could add a section "Demands & Supervision"? But not in examples. Might be better to create a section "Physical Demands" if we have content. But instruction says prefer few substantive sections over many thin ones. Physical Demands is a substantive paragraph; could be its own section but that would be thin. However we could combine Physical Demands and Supervisory Responsibility into a section called "Additional Details". But not in examples. The examples are just examples; we can use other headings if needed. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as typical. We could still use other headings if needed. But to follow spirit, we should try to map to those headings.
We have Qualifications heading example; we could use Qualifications for the list of qualifications (proficiency etc.) and maybe also include Preferred Education And Experience there. Skills heading for competencies. Benefits heading for benefits. Schedule heading for schedule. About the role heading for company overview and role summary. Responsibilities heading for essential functions and maybe working conditions.
What about Physical Demands and Supervisory Responsibility? Could be placed under Responsibilities as a paragraph? Or under Qualifications? Not ideal. Could create a section "Working Conditions" but that's not in examples but could be used. However we already have Working Conditions content; we could make a section "Working Conditions". That would be a thin section but it's substantive. The instruction says prefer few substantive sections over many thin ones. So maybe we should merge Working Conditions into Responsibilities.
Physical Demands could be merged into Responsibilities as well? It's about physical demands of job; could be part of Responsibilities or a separate "Physical Demands" section. But to keep few sections, we could add a paragraph under Responsibilities about physical demands.
Supervisory Responsibility: statement that role does not have supervisory responsibility. Could be a note under Responsibilities or Qualifications.
Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to extract content and format.
Let's gather content:
About the role:
- Who We Are: Lippert is a leading, global manufacturer and supplier of highly engineered products and customized solutions, dedicated to shaping, growing and bettering the RV, marine, automotive, commercial vehicle and building products industries. We combine our strategic manufacturing capabilities with the power of our winning team culture to deliver unrivaled customer service, award-winning innovation and premium products to all of our customers.
- Why We Are Different: At Lippert, Everyone Matters. This is not just a tagline or empty promise; it is who we are. We have intentionally created a culture that values and celebrates our team members’ unique and varied backgrounds, perspectives, and experiences. We strive to give our team members a deeper sense of purpose at work, and we continue to build a better work environment by aligning our cultural and business strategies with the needs of our team members.
- What You Will Get (benefits) but we will move to Benefits section.
- Summary/Objective: We are seeking a skilled Production Test Engineer to own the hardware aspects of our in-circuit (ICT) systems. This role is critical for supporting production-intent - high-volume testers in demanding manufacturing environments. Specific ICT platform experience is not required, we provide comprehensive training to ensure success in this role.
We could combine Who We Are, Why We Are Different, Summary/Objective into About the role.
Responsibilities:
- Essential Functions list:
* Serve as the primary technician for ICT hardware setup and initial design, integration, and maintenance.
* Support the development of customer fixtures and adapters tailored to production needs.
* Debug and optimize test parameters of electrical components to meet high-throughput production requirements.
* Troubleshoot test programs and hardware-related failures, leveraging advances diagnostic tools.
* Collaborate with software engineers and manufacturing teams to ensure seamless systems performance.
* Document configuration, procedures, and troubleshooting guidelines.
* Develop and execute preventive maintenance schedules to minimize downtime.
* Manage hardware inventory and spare components for uninterrupted productions.
- Working Conditions: Primarily working indoors, office environment. May sit for several hours at a time. Prolonged exposure to computer screens. Repetitive use of hands to operate computers, printers, and copiers.
- Physical Demands: The physical demands described here are representative of those that must be met by a Team Member to successfully perform the essential functions of this job. While performing the duties of this job, the Team Member is regularly required to talk and hear. This position is very active and requires standing, walking, bending, kneeling, stooping, crouching, crawling, and climbing all day. The Team Member may have to lift and/or move items over 50 pounds. Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, depth perception and ability to adjust focus.
- Supervisory Responsibility: This role does not have any supervisory responsibility upon hiring.
- Other Duties: Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the Team Member for this job. Duties, responsibilities, and activities may change at any time with or without notice.
We could incorporate Working Conditions, Physical Demands, Supervisory Responsibility, Other Duties into Responsibilities section as paragraphs.
Requirements:
- Qualifications list:
* Proficiency in circuit analysis and diagnostic tools (oscilloscopes, multimeters, logic analyzers).
* Strong understanding of datasheet parameters
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. We need to decide which sections to include based on content. The posting includes: - Overview: Who We Are, Why We Are Different, What You Will Get (benefits) - Summary/Objective: description of role - Essential Functions (list of duties) - Working Conditions (description) - Qualifications (list) - Competencies (list) - Supervisory Responsibility (statement) - Physical Demands (description) - Position Type/Expected Hours Of Work (full-time salary) - Travel (minimal) - Preferred Education And Experience (list) - Additional Eligibility Qualifications (None) - Work Authorization/Security Clearance (must be legally authorized) - Other Duties (note about job description not comprehensive) - Pay Group : AAP/EEO Statement (EEO boilerplate, we should remove) - Know Your Rights (boilerplate, remove) We need to remove EEO/legal boilerplate. Also remove "Other Duties" maybe? It's not boilerplate but it's a generic statement; but it's substantive? It says "Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the Team Member for this job. Duties, responsibilities, and activities may change at any time with or without notice." That's generic but still part of posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other Duties" is not exactly legal boilerplate but it's a standard disclaimer. Might be considered boilerplate? Not sure. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Other Duties" is substantive? It's a disclaimer but still part of job description. I'd keep it as a
maybe under a section like "Additional Information". But we are told to prefer few substantive sections over many thin ones. Could combine many items into sections like "About the role", "Responsibilities", "Requirements", "Benefits", etc. However we must only create sections when posting has real specific content. We have benefits: "What You Will Get A unique, inclusive and supportive company culture.Comprehensive benefit offerings including medical, dental, vision, 401k with employer match, vacation, and more! Fair and competitive compensation. Career development and mentoring and opportunities to grow.Holiday, personal and vacation days." That's benefits content. So we can have a Benefits section. We have Pay: Not explicitly stated; only "Fair and competitive compensation." No specific pay. So we should NOT create a Pay section because no specific pay. Schedule: Position Type/Expected Hours Of Work: "This is a full-time salary position, and hours/days worked are decided by your reporting manager." That's schedule info. So we can create a Schedule section. We have About the role: Could combine Who We Are, Why We Are Different, Summary/Objective. But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use