Controls Engineer x 2

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. No job title heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. Let's parse the posting. Job#: 3047875 (metadata, drop). Job Description: Controls Engineer Location: Arden Hills, Minnesota (Onsite) Role Overview This position supports the full product lifecycle of burn-in systems by customizing power delivery systems to meet customer expectations. Responsibilities include producing schematics, selecting machine control hardware, creating design verifications, and troubleshooting with Production and Purchasing to resolve issues. This role reports to the Machine Automation and Controls Department. We need sections: About the role (maybe from Role Overview). Responsibilities (list). Requirements (maybe education/experience). Qualifications (maybe required and preferred). Skills (maybe from skills). Benefits (from Everforth Apex Benefits Overview). Pay (none given). Schedule (none given). Physical Demands maybe not needed; but not a required heading. Could include under Requirements? Probably not. We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits are stated, so include Benefits section. Pay not stated, so omit. Schedule not stated, omit. We need to include only sections with real content. Let's extract content. About the role: "This position supports the full product lifecycle of burn-in systems by customizing power delivery systems to meet customer expectations. Responsibilities include producing schematics, selecting machine control hardware, creating design verifications, and troubleshooting with Production and Purchasing to resolve issues. This role reports to the Machine Automation and Controls Department." We could also include Role Overview sentence. Responsibilities: list bullet points from "Key Responsibilities" section. Let's list them: - Help lead the full product lifecycle of the power delivery system, including conceptualization, prototype development, testing, and final design. - Produce system schematics, panel layouts, wire lists, bills of materials, and procedures to support operations. - Work with senior engineers to select and specify machine control hardware, including programmable logic controllers and related I/O devices. - Support custom power delivery systems to meet customer expectations and lead conversations with customers to clarify power requirements. - Create design verifications and manufacturing tests to confirm the functionality of electrical components and systems. - Troubleshoot with Production and Purchasing to solve unforeseen problems with product design, implementation, and components. - Partner with Sales and Field Service to support customer issues and develop necessary Engineering and Field Change Orders. - Work with a cross-functional team to determine the root cause of errors and develop a corrective action plan. - Lead initial and ongoing design reviews. - Perform all other related duties as requested or assigned. We need to keep all substantive info; no fluff. Required Qualifications: Education: A Bachelor’s degree in Electrical Engineering or a related field is required. Experience: 2+ years of experience in industrial system design and power control is required. Preferred Qualifications: list bullet points. - Experience with the automation of industrial electromechanical systems. - Knowledge of ERP Systems and Manufacturing Systems. - Hands-on experience with industrial power systems. - Knowledge of Electrical Safety Standards such as NFPA 79, NFPA 70, IEC 60204, SEMI S22, or UL508. - Experience designing and developing electromechanical assemblies. - Experience with international low voltage ( ... cut off? The text: "Experience with international low voltage ( " seems incomplete; but we must preserve as is. Probably it's "Experience with international low voltage (". We'll keep exactly as appears: "Experience with international low voltage (". Might be missing closing parenthesis but we keep. Skills: list bullet points. - Understanding of modern electronic systems and component materials. - Capacity to analyze a problem from multiple perspectives and explore creative solutions. - Good verbal and written communication skills. - Ability to multi-task in a fast-paced environment. Benefits: from Everforth Apex Benefits Overview. Let's extract: "Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide." We should keep that as prose or list? It's a paragraph; we can put in

. Could also bullet but not required. We'll put in

. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. Also remove "Physical Demands" section? Not a required heading; but could be included under Requirements? Not needed. We'll omit. Also remove "Everforth Apex is a world-class IT services company..." that's boilerplate about company; maybe considered not substantive? It's description of company; could be considered part of About the role? Might be considered boilerplate but it's about company benefits and culture. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may be considered not boilerplate but could be considered fluff. However it's substantive info about the employer. The instruction says "Prefer a few substantive sections over many thin ones." Could include under About the role or a separate section like "About the company". But we only have allowed headings list; we could put under About the role. But we already have About the role content; we could append company description there. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can only use those headings. So we can put company description under About the role or maybe Benefits? Better under About the role. Thus About the role paragraph: combine role overview and company description. Let's craft About the role: "This position supports the full product lifecycle of burn-in systems by customizing power delivery systems to meet customer expectations. Responsibilities include producing schematics, selecting machine control hardware, creating design verifications, and troubleshooting with Production and Purchasing to resolve issues. This role reports to the Machine Automation and Controls Department. Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico." We should not include the virtual recruiter stuff, application instructions, etc. Remove that. Now Responsibilities as

• . Requirements: Education and Experience. Qualifications: maybe combine Required and Preferred? But we have both Required Qualifications and Preferred Qualifications headings? The allowed headings include Qualifications (maybe cover both). We could put Required under Qualifications and Preferred also under Qualifications? But we have separate headings for Requirements and Qualifications. Usually Requirements = education/experience; Qualifications = skills etc. But we also have Skills heading. So we can put Education/Experience under Requirements. Then Skills under Skills. Preferred qualifications maybe also under Qualifications? But we have Qualifications heading allowed. We could put Preferred Qualifications under Qualifications. However we also have Skills separate. Let's decide: - Requirements: Education and Experience. - Qualifications: Preferred Qualifications list. - Skills: Skills list. That seems logical. Now Benefits section. Now ensure we don't include any headings with empty content. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  Education: A Bachelor’s degree in Electrical Engineering or a related field is required.

  Experience: 2+ years of experience in industrial system design and power control is required.

  Qualifications

  • Experience with the automation of industrial electromechanical systems.
  • Knowledge of ERP Systems and Manufacturing Systems.
  • Hands-on experience with industrial power systems.
  • Knowledge of Electrical Safety Standards such as NFPA 79, NFPA 70, IEC 60204, SEMI S22, or UL508.
  • Experience designing and developing electromechanical assemblies.
  • Experience with international low voltage (

  Skills

  • Understanding of modern electronic systems and component materials.
  • Capacity to analyze a problem from multiple perspectives and explore creative solutions.
  • Good verbal and written communication skills.
  • Ability to multi-task in a fast-paced environment.

  Benefits

  Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide.

  Check for any leftover boilerplate: we removed EEO, legal, virtual recruiter, application instructions, duplicated EEO, etc. Check for any placeholders like "commensurate with experience" - none. Check for any "N/A", "TBD" - none. Check for duplicate lines: we didn't duplicate. Now ensure we didn't include Job ID or location as heading. Location is in the initial line but we didn't include it anywhere. Should we include location? Not a heading; could be included in About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we could fold into About the role