Test Engineer I
Banner Engineering · Plymouth, MN · 3 wk ago
On-siteEngineering$74k–$105k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Why Work at Banner?" intro, then Position Summary, What You’ll Be Doing (responsibilities), What You Bring To The Table (requirements/qualifications), What To Expect At Work (Physical Demands, Working Environment), Pay And Benefits, Core Values maybe? The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. We should not repeat job title. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, Core Values maybe not needed? It says include a section ONLY when posting has real, specific content for it. Core Values is present but maybe not a standard heading; we could include as a section? The allowed headings list includes Benefits, Pay, Schedule, etc. Core Values not listed but we could still use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. We should not repeat job title. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, Core Values maybe not needed? It says include a section ONLY when posting has real, specific content for it. Core Values is present but maybe not a standard heading; we could include as a section? The allowed headings list includes Benefits, Pay, Schedule, etc. Core Values not listed but we could still use for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we can also use other headings if needed? Probably better to stick to those. So we need sections: About the role (maybe from Position Summary and Why Work at Banner?), Responsibilities (What You’ll Be Doing), Requirements (What You Bring To The Table - required), Qualifications (maybe Preferred?), Skills (maybe combine), Benefits, Pay. Schedule not present, so omit.
We need to preserve all substantive information. So we need to include details from each section.
Let's extract:
Why Work at Banner? (intro) - we can put under About the role.
Position Summary: "Test Engineer plays a key role in supporting continuous improvement of test systems at our global manufacturing facilities. This position will work within a multidisciplinary team to maintain, improve, and design test solutions working independently with direction from their manager. The ideal candidate brings strong problem-solving skills and a proven ability to understand electronics and mechanical design, as well as programming concepts and technologies."
What You’ll Be Doing: list of responsibilities (bulleted). We'll convert to - .
What You Bring To The Table: includes required and preferred. We'll separate Required under Requirements, Preferred under Qualifications or Skills. The instruction: Use headings Requirements, Qualifications, Skills. We can put required under Requirements, preferred under Qualifications, and maybe skills under Skills (but we could merge). Let's do: Requirements (required), Qualifications (preferred), Skills (maybe list of skills like proficiency in software development, etc). But we have overlapping. To avoid duplication, we can put required under Requirements, preferred under Qualifications, and maybe skills under Skills (like Intermediate proficiency with Microsoft Office Suite, Strong problem-solving skills, etc). However many of those are already in required/preferred. To keep it simple, we can have Requirements (required), Qualifications (preferred), and Skills (maybe list of technical skills like Python, C#, C++, TestStand, LabVIEW, etc). But we already have those in responsibilities. Might be redundant but okay.
Better: Use Requirements for required, Qualifications for preferred, and Skills for technical skills (like proficiency in software development using environments such as C#, C++, Python, or Visual Basic; Experience developing, improving, and troubleshooting test systems; etc). But that duplicates.
Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But they said use headings for those. We could have Requirements (including both required and preferred) and Skills (maybe list of technical skills). But we need to follow instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Requirements and Qualifications. We'll include both.
Now Pay And Benefits: includes Base Pay Range and list of benefits. We'll create Pay section with pay range, Benefits section with list.
Schedule: not present, omit.
Now we need to remove boilerplate: EEO statement, Core Values maybe not needed but could be included under About the role? It's not boilerplate but it's values. Could include under About the role as extra paragraph. But instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Core Values is specific content, but not a standard heading. We could add a section Core Values
with list. However the instruction gave examples but didn't restrict to only those. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add Core Values if we want. But to keep few sections, maybe we can incorporate Core Values into About the role paragraph.
We'll also need to remove duplicated lines: there is repeated "Reasonable accommodations may be made to support individuals with disabilities." appears twice (under What You Bring To The Table and under Physical Demands). We'll keep only one instance? The instruction: remove duplicated lines. So we should keep only one occurrence. We'll keep it under Requirements maybe? Actually it's under What You Bring To The Table (required) and also under Physical Demands. We'll keep one, maybe under Requirements.
Also duplicated "Banner Engineering is an equal opportunity employer..." etc. That's boilerplate EEO, remove.
Also "This job description reflects management’s assignment..." remove.
Now produce HTML.
Structure:
About the role
... (combine Why Work at Banner? and Position Summary)
Responsibilities
- ... each responsibility
Requirements
- ... required items
Qualifications
- ... preferred items
Skills
- ... maybe technical skills list? Could combine with responsibilities? But we already have responsibilities list. Maybe we can put skills like proficiency in software development, intermediate MS Office, strong problem-solving, etc. But many are already in requirements. To avoid duplication, we could omit Skills section if content is thin. But we have some skills not captured elsewhere: "Intermediate proficiency with Microsoft Office Suite." That's a skill. Also "Strong problem-solving skills" appears in required. "Ability to plan and prioritize multiple projects." That's a skill. "Working understanding of microcontrollers/microprocessors". That's skill. So we can put those under Skills.
But we must ensure we don't duplicate content already in Requirements or Qualifications. Let's extract required list:
Required:
- Bachelor’s degree in Electrical Engineering, Computer Engineering, Physics, or a related technical field.
- 2+ years of experience in electrical test, process, or systems engineering.
- Proficiency in software development using environments such as C#, C++, Python, or Visual Basic.
- Experience developing, improving, and troubleshooting test systems on the production floor.
- Demonstrated ability to analyze electrical schematics and circuit designs to understand circuit functionality, identify critical test points, and develop effective electrical test systems for new and existing products.
- Experience supporting manufacturing processes, with a strong understanding of process flow and the ability to identify issues and improve product quality and throughput.
- Proven ability to conceptualize, design, and support the development of test systems that improve efficiency, quality, and process repeatability.
- Strong problem-solving skills with the ability to diagnose electrical, mechanical, and process-related issues.
- Intermediate proficiency with Microsoft Office Suite.
Preferred:
- Strong knowledge of analog and digital circuits.
- Test software development experience using TestStand or LabVIEW.
- Strong applied statistical skills to analyze test and manufacturing data, identify process variation, and support yield and continuous improvement efforts.
- Experience with automated test instrumentation, measurement systems, and/or motion control.
- Previous experience with Lean manufacturing and/or continuous improvement.
- Comfortable collaborating with operators, technicians, engineers, and cross-functional teams to improve quality and yield.
- Working understanding of microcontrollers/microprocessors
- Ability to plan and prioritize multiple projects.
Now Skills: maybe we can list technical skills like Python, C#, C++, TestStand, LabVIEW, etc. But those are already in required (proficiency in software development using environments such as C#, C++, Python, or Visual Basic) and preferred (TestStand or LabVIEW). Could still list them.
But to avoid duplication, we could make Skills section list specific tools/languages: Python, C#, C++, TestStand, LabVIEW, etc. However the required already mentions proficiency in software development using environments such as C#, C++, Python, or Visual Basic. So listing them again is duplication but maybe acceptable? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original? But we should remove duplicated lines. The duplicated lines are identical sentences repeated. Listing skills again is not identical lines but similar content. Might be okay but could be considered summarizing? Safer to not duplicate; we can incorporate those into Requirements and Qualifications and not have a separate Skills section. However the instruction expects we may use Skills heading if we have content. But we can omit Skills if we think it's thin. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills and put those details under Requirements/Qualifications.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: list from Pay And Benefits: 401(k) with match, Student Loan 401(k) match program, Medical, Dental, and Vision Insurance Plans, HSA (Health Savings Account) with company contribution, Paid Time Off (PTO), Sales and Profit Sharing Eligibility, Flexible work hours, Life Insurance, Paid Parental Leave, Pet Insurance.
Pay: Base Pay Range: $74,470.00 - $105,064.00. Also note that final offers based on factors.
We'll put Pay section with that range and note.
Now About the role paragraph: combine Why Work at Banner? and Position Summary.
Why Work at Banner? text: "For over 50 years, Banner Engineering has been at the forefront of industrial automation. We offer products and solutions including award-winning sensors, wireless solutions, machine safety, indication and LED lighting. From Fortune 500 leaders to innovative startups, Banner's award-winning products and solutions are helping companies around the world increase efficiency, reduce costs, safeguard equipment, and protect personnel. Our commitment to innovation shows through a continuous, market-driven evolution of products and technology. With engineers employed in nearly every major department, engineering is in our DNA. Banner is a rapidly growing company that offers many personal development opportunities, an excellent benefits package, and a collaborative team of employees who are passionate about what they do."
Position Summary: "Test Engineer plays a key role in supporting continuous improvement of test systems at our global manufacturing facilities. This position will work within a multidisciplinary team to maintain, improve, and design test solutions working independently with direction from their manager. The ideal candidate brings strong problem-solving skills and a proven ability to understand electronics and mechanical design, as well as programming concepts and technologies."
We'll combine into a paragraph or two paragraphs. Use
for prose.
Now Responsibilities list: extract each bullet from "What You’ll Be Doing". Let's list them:
- Develop, improve, and maintain automated test programs using Python, C#, C++, TestStand, LabVIEW, or similar languages and platforms.
- Upgrade and overhaul existing test systems to improve quality, process control, and operator usability.
- Analyze operator interactions within test sequences to reduce manual steps and optimize test flow.
- Define test requirements, plans, and procedures based on existing test equipment and/or product specifications.
- Analyze test data to support root-cause investigations, improve yield, and drive
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we can also use other headings if needed? Probably better to stick to those. So we need sections: About the role (maybe from Position Summary and Why Work at Banner?), Responsibilities (What You’ll Be Doing), Requirements (What You Bring To The Table - required), Qualifications (maybe Preferred?), Skills (maybe combine), Benefits, Pay. Schedule not present, so omit.
We need to preserve all substantive information. So we need to include details from each section.
Let's extract:
Why Work at Banner? (intro) - we can put under About the role.
Position Summary: "Test Engineer plays a key role in supporting continuous improvement of test systems at our global manufacturing facilities. This position will work within a multidisciplinary team to maintain, improve, and design test solutions working independently with direction from their manager. The ideal candidate brings strong problem-solving skills and a proven ability to understand electronics and mechanical design, as well as programming concepts and technologies."
What You’ll Be Doing: list of responsibilities (bulleted). We'll convert to - .
What You Bring To The Table: includes required and preferred. We'll separate Required under Requirements, Preferred under Qualifications or Skills. The instruction: Use headings Requirements, Qualifications, Skills. We can put required under Requirements, preferred under Qualifications, and maybe skills under Skills (but we could merge). Let's do: Requirements (required), Qualifications (preferred), Skills (maybe list of skills like proficiency in software development, etc). But we have overlapping. To avoid duplication, we can put required under Requirements, preferred under Qualifications, and maybe skills under Skills (like Intermediate proficiency with Microsoft Office Suite, Strong problem-solving skills, etc). However many of those are already in required/preferred. To keep it simple, we can have Requirements (required), Qualifications (preferred), and Skills (maybe list of technical skills like Python, C#, C++, TestStand, LabVIEW, etc). But we already have those in responsibilities. Might be redundant but okay.
Better: Use Requirements for required, Qualifications for preferred, and Skills for technical skills (like proficiency in software development using environments such as C#, C++, Python, or Visual Basic; Experience developing, improving, and troubleshooting test systems; etc). But that duplicates.
Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But they said use headings for those. We could have Requirements (including both required and preferred) and Skills (maybe list of technical skills). But we need to follow instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Requirements and Qualifications. We'll include both.
Now Pay And Benefits: includes Base Pay Range and list of benefits. We'll create Pay section with pay range, Benefits section with list.
Schedule: not present, omit.
Now we need to remove boilerplate: EEO statement, Core Values maybe not needed but could be included under About the role? It's not boilerplate but it's values. Could include under About the role as extra paragraph. But instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Core Values is specific content, but not a standard heading. We could add a section Core Values
with list. However the instruction gave examples but didn't restrict to only those. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add Core Values if we want. But to keep few sections, maybe we can incorporate Core Values into About the role paragraph.
We'll also need to remove duplicated lines: there is repeated "Reasonable accommodations may be made to support individuals with disabilities." appears twice (under What You Bring To The Table and under Physical Demands). We'll keep only one instance? The instruction: remove duplicated lines. So we should keep only one occurrence. We'll keep it under Requirements maybe? Actually it's under What You Bring To The Table (required) and also under Physical Demands. We'll keep one, maybe under Requirements.
Also duplicated "Banner Engineering is an equal opportunity employer..." etc. That's boilerplate EEO, remove.
Also "This job description reflects management’s assignment..." remove.
Now produce HTML.
Structure:
About the role
... (combine Why Work at Banner? and Position Summary)
Responsibilities
- ... each responsibility
Requirements
- ... required items
Qualifications
- ... preferred items
Skills
- ... maybe technical skills list? Could combine with responsibilities? But we already have responsibilities list. Maybe we can put skills like proficiency in software development, intermediate MS Office, strong problem-solving, etc. But many are already in requirements. To avoid duplication, we could omit Skills section if content is thin. But we have some skills not captured elsewhere: "Intermediate proficiency with Microsoft Office Suite." That's a skill. Also "Strong problem-solving skills" appears in required. "Ability to plan and prioritize multiple projects." That's a skill. "Working understanding of microcontrollers/microprocessors". That's skill. So we can put those under Skills.
But we must ensure we don't duplicate content already in Requirements or Qualifications. Let's extract required list:
Required:
- Bachelor’s degree in Electrical Engineering, Computer Engineering, Physics, or a related technical field.
- 2+ years of experience in electrical test, process, or systems engineering.
- Proficiency in software development using environments such as C#, C++, Python, or Visual Basic.
- Experience developing, improving, and troubleshooting test systems on the production floor.
- Demonstrated ability to analyze electrical schematics and circuit designs to understand circuit functionality, identify critical test points, and develop effective electrical test systems for new and existing products.
- Experience supporting manufacturing processes, with a strong understanding of process flow and the ability to identify issues and improve product quality and throughput.
- Proven ability to conceptualize, design, and support the development of test systems that improve efficiency, quality, and process repeatability.
- Strong problem-solving skills with the ability to diagnose electrical, mechanical, and process-related issues.
- Intermediate proficiency with Microsoft Office Suite.
Preferred:
- Strong knowledge of analog and digital circuits.
- Test software development experience using TestStand or LabVIEW.
- Strong applied statistical skills to analyze test and manufacturing data, identify process variation, and support yield and continuous improvement efforts.
- Experience with automated test instrumentation, measurement systems, and/or motion control.
- Previous experience with Lean manufacturing and/or continuous improvement.
- Comfortable collaborating with operators, technicians, engineers, and cross-functional teams to improve quality and yield.
- Working understanding of microcontrollers/microprocessors
- Ability to plan and prioritize multiple projects.
Now Skills: maybe we can list technical skills like Python, C#, C++, TestStand, LabVIEW, etc. But those are already in required (proficiency in software development using environments such as C#, C++, Python, or Visual Basic) and preferred (TestStand or LabVIEW). Could still list them.
But to avoid duplication, we could make Skills section list specific tools/languages: Python, C#, C++, TestStand, LabVIEW, etc. However the required already mentions proficiency in software development using environments such as C#, C++, Python, or Visual Basic. So listing them again is duplication but maybe acceptable? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original? But we should remove duplicated lines. The duplicated lines are identical sentences repeated. Listing skills again is not identical lines but similar content. Might be okay but could be considered summarizing? Safer to not duplicate; we can incorporate those into Requirements and Qualifications and not have a separate Skills section. However the instruction expects we may use Skills heading if we have content. But we can omit Skills if we think it's thin. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills and put those details under Requirements/Qualifications.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: list from Pay And Benefits: 401(k) with match, Student Loan 401(k) match program, Medical, Dental, and Vision Insurance Plans, HSA (Health Savings Account) with company contribution, Paid Time Off (PTO), Sales and Profit Sharing Eligibility, Flexible work hours, Life Insurance, Paid Parental Leave, Pet Insurance.
Pay: Base Pay Range: $74,470.00 - $105,064.00. Also note that final offers based on factors.
We'll put Pay section with that range and note.
Now About the role paragraph: combine Why Work at Banner? and Position Summary.
Why Work at Banner? text: "For over 50 years, Banner Engineering has been at the forefront of industrial automation. We offer products and solutions including award-winning sensors, wireless solutions, machine safety, indication and LED lighting. From Fortune 500 leaders to innovative startups, Banner's award-winning products and solutions are helping companies around the world increase efficiency, reduce costs, safeguard equipment, and protect personnel. Our commitment to innovation shows through a continuous, market-driven evolution of products and technology. With engineers employed in nearly every major department, engineering is in our DNA. Banner is a rapidly growing company that offers many personal development opportunities, an excellent benefits package, and a collaborative team of employees who are passionate about what they do."
Position Summary: "Test Engineer plays a key role in supporting continuous improvement of test systems at our global manufacturing facilities. This position will work within a multidisciplinary team to maintain, improve, and design test solutions working independently with direction from their manager. The ideal candidate brings strong problem-solving skills and a proven ability to understand electronics and mechanical design, as well as programming concepts and technologies."
We'll combine into a paragraph or two paragraphs. Use
for prose.
Now Responsibilities list: extract each bullet from "What You’ll Be Doing". Let's list them:
- Develop, improve, and maintain automated test programs using Python, C#, C++, TestStand, LabVIEW, or similar languages and platforms.
- Upgrade and overhaul existing test systems to improve quality, process control, and operator usability.
- Analyze operator interactions within test sequences to reduce manual steps and optimize test flow.
- Define test requirements, plans, and procedures based on existing test equipment and/or product specifications.
- Analyze test data to support root-cause investigations, improve yield, and drive
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Requirements and Qualifications. We'll include both.
Now Pay And Benefits: includes Base Pay Range and list of benefits. We'll create Pay section with pay range, Benefits section with list.
Schedule: not present, omit.
Now we need to remove boilerplate: EEO statement, Core Values maybe not needed but could be included under About the role? It's not boilerplate but it's values. Could include under About the role as extra paragraph. But instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Core Values is specific content, but not a standard heading. We could add a section Core Values
with list. However the instruction gave examples but didn't restrict to only those. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add Core Values if we want. But to keep few sections, maybe we can incorporate Core Values into About the role paragraph.
We'll also need to remove duplicated lines: there is repeated "Reasonable accommodations may be made to support individuals with disabilities." appears twice (under What You Bring To The Table and under Physical Demands). We'll keep only one instance? The instruction: remove duplicated lines. So we should keep only one occurrence. We'll keep it under Requirements maybe? Actually it's under What You Bring To The Table (required) and also under Physical Demands. We'll keep one, maybe under Requirements.
Also duplicated "Banner Engineering is an equal opportunity employer..." etc. That's boilerplate EEO, remove.
Also "This job description reflects management’s assignment..." remove.
Now produce HTML.
Structure:
About the role
About the role
... (combine Why Work at Banner? and Position Summary)
Responsibilities
- ... each responsibility
Requirements
- ... required items
Qualifications
- ... preferred items
Skills
- ... maybe technical skills list? Could combine with responsibilities? But we already have responsibilities list. Maybe we can put skills like proficiency in software development, intermediate MS Office, strong problem-solving, etc. But many are already in requirements. To avoid duplication, we could omit Skills section if content is thin. But we have some skills not captured elsewhere: "Intermediate proficiency with Microsoft Office Suite." That's a skill. Also "Strong problem-solving skills" appears in required. "Ability to plan and prioritize multiple projects." That's a skill. "Working understanding of microcontrollers/microprocessors". That's skill. So we can put those under Skills.
But we must ensure we don't duplicate content already in Requirements or Qualifications. Let's extract required list:
Required:
- Bachelor’s degree in Electrical Engineering, Computer Engineering, Physics, or a related technical field.
- 2+ years of experience in electrical test, process, or systems engineering.
- Proficiency in software development using environments such as C#, C++, Python, or Visual Basic.
- Experience developing, improving, and troubleshooting test systems on the production floor.
- Demonstrated ability to analyze electrical schematics and circuit designs to understand circuit functionality, identify critical test points, and develop effective electrical test systems for new and existing products.
- Experience supporting manufacturing processes, with a strong understanding of process flow and the ability to identify issues and improve product quality and throughput.
- Proven ability to conceptualize, design, and support the development of test systems that improve efficiency, quality, and process repeatability.
- Strong problem-solving skills with the ability to diagnose electrical, mechanical, and process-related issues.
- Intermediate proficiency with Microsoft Office Suite.
Preferred:
- Strong knowledge of analog and digital circuits.
- Test software development experience using TestStand or LabVIEW.
- Strong applied statistical skills to analyze test and manufacturing data, identify process variation, and support yield and continuous improvement efforts.
- Experience with automated test instrumentation, measurement systems, and/or motion control.
- Previous experience with Lean manufacturing and/or continuous improvement.
- Comfortable collaborating with operators, technicians, engineers, and cross-functional teams to improve quality and yield.
- Working understanding of microcontrollers/microprocessors
- Ability to plan and prioritize multiple projects.
Now Skills: maybe we can list technical skills like Python, C#, C++, TestStand, LabVIEW, etc. But those are already in required (proficiency in software development using environments such as C#, C++, Python, or Visual Basic) and preferred (TestStand or LabVIEW). Could still list them.
But to avoid duplication, we could make Skills section list specific tools/languages: Python, C#, C++, TestStand, LabVIEW, etc. However the required already mentions proficiency in software development using environments such as C#, C++, Python, or Visual Basic. So listing them again is duplication but maybe acceptable? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original? But we should remove duplicated lines. The duplicated lines are identical sentences repeated. Listing skills again is not identical lines but similar content. Might be okay but could be considered summarizing? Safer to not duplicate; we can incorporate those into Requirements and Qualifications and not have a separate Skills section. However the instruction expects we may use Skills heading if we have content. But we can omit Skills if we think it's thin. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills and put those details under Requirements/Qualifications.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: list from Pay And Benefits: 401(k) with match, Student Loan 401(k) match program, Medical, Dental, and Vision Insurance Plans, HSA (Health Savings Account) with company contribution, Paid Time Off (PTO), Sales and Profit Sharing Eligibility, Flexible work hours, Life Insurance, Paid Parental Leave, Pet Insurance.
Pay: Base Pay Range: $74,470.00 - $105,064.00. Also note that final offers based on factors.
We'll put Pay section with that range and note.
Now About the role paragraph: combine Why Work at Banner? and Position Summary.
Why Work at Banner? text: "For over 50 years, Banner Engineering has been at the forefront of industrial automation. We offer products and solutions including award-winning sensors, wireless solutions, machine safety, indication and LED lighting. From Fortune 500 leaders to innovative startups, Banner's award-winning products and solutions are helping companies around the world increase efficiency, reduce costs, safeguard equipment, and protect personnel. Our commitment to innovation shows through a continuous, market-driven evolution of products and technology. With engineers employed in nearly every major department, engineering is in our DNA. Banner is a rapidly growing company that offers many personal development opportunities, an excellent benefits package, and a collaborative team of employees who are passionate about what they do."
Position Summary: "Test Engineer plays a key role in supporting continuous improvement of test systems at our global manufacturing facilities. This position will work within a multidisciplinary team to maintain, improve, and design test solutions working independently with direction from their manager. The ideal candidate brings strong problem-solving skills and a proven ability to understand electronics and mechanical design, as well as programming concepts and technologies."
We'll combine into a paragraph or two paragraphs. Use
for prose. Now Responsibilities list: extract each bullet from "What You’ll Be Doing". Let's list them: - Develop, improve, and maintain automated test programs using Python, C#, C++, TestStand, LabVIEW, or similar languages and platforms. - Upgrade and overhaul existing test systems to improve quality, process control, and operator usability. - Analyze operator interactions within test sequences to reduce manual steps and optimize test flow. - Define test requirements, plans, and procedures based on existing test equipment and/or product specifications. - Analyze test data to support root-cause investigations, improve yield, and drive