Controls Integration Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. First paragraph: "Join the Home for Entrepreneurs Pioneer your career! Körber is the home for passionate people who innovate, collaborate and love what they do. Entrepreneurial spirit is our joint DNA. We develop future technologies and support talents to deploy their skills and reach their full potential. Together, we aim for being the first to do the right thing at the right time. Join the home for entrepreneurs!" This is generic marketing fluff, but it's part of the posting. Should we include? It's not a section heading; it's introductory prose. We can put it in a

maybe under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have a description of role: "The Controls Integration Manager leads the controls integration and commissioning function for material handling and parcel automation systems, ensuring successful deployment, validation, and operational readiness across multiple projects. This role provides technical and people leadership for a team of Controls Engineers, establishes commissioning standards and best practices, and drives execution excellence through effective resource planning, risk management, and cross-functional collaboration. The Controls Integration Manager is accountable for commissioning performance, team development, and continuous improvement initiatives that enhance reliability, scalability, and customer satisfaction." Then "Your Role in Our Team" bullet list (actually lines). Those are responsibilities. Then "Your Profile" list of qualifications/experience/skills. Then "Education And Experience Qualifications" with bullet points. Then travel requirement, eligibility, etc. We need to map to sections: - About the role: could be the introductory paragraph describing the role (the first paragraph after the marketing fluff). Or we could combine marketing fluff into About the role? Probably About the role should contain a summary of the role. We'll put the paragraph describing the Controls Integration Manager role. - Responsibilities: the bullet list under "Your Role in Our Team". Those are duties. - Requirements: maybe the "Your Profile" list (experience, knowledge, abilities). Could be considered requirements. - Qualifications: the "Education And Experience Qualifications" bullet list (degree, years experience, leadership experience, travel, work authorization). Could be qualifications. - Skills: maybe we could extract specific technical skills from Your Profile (knowledge of PLC, vision, networks, etc.) but those are already in Requirements. Might be redundant. We could combine Requirements and Skills? But instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (which includes experience, knowledge, skills), Qualifications (education, experience, travel, auth). Benefits, Pay, Schedule: we need to check if posting mentions any benefits, pay, schedule. It mentions travel up to 50% of year, but that's not a benefit; it's a requirement. No explicit benefits, pay, or schedule (like working hours). So we should NOT include Benefits, Pay, Schedule sections because they lack specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we omit those. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications. We need to use

for each section heading. Then content: use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections. We must not repeat job title as heading. The job title is "Controls Integration Manager". We must not put that as a heading. We must not put Job ID/requisition numbers as headings; none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the marketing fluff at start? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The marketing fluff may be considered boilerplate? It's not legal/EEO, but it's generic marketing. However it's part of the posting; but maybe it's considered fluff that can be omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove marketing fluff. But we might keep it as part of About the role? However the About the role section should be substantive; we could include that fluff as a paragraph. But it's not really about the role; it's about the company. Could be considered "About the role" but it's more about company. However we could still include it as part of About the role. The instruction: "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, not company marketing. But we can include both. We need to decide: keep the marketing fluff? It's not duplicated lines, not legal, not application instructions. It's substantive? It's vague but still part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. However we could place it in a

  under About the role before the role description. Thus About the role will have two paragraphs: first the marketing fluff, then the role description. Now Responsibilities: list each bullet from "Your Role in Our Team". Let's extract them: - Direct commissioning strategy and execution across multiple projects to ensure successful delivery, operational readiness, and customer acceptance - Build, lead, and develop a high-performing team of Controls Engineers through coaching, performance management, workforce planning, and technical mentorship - Establish commissioning methodologies, testing standards, and validation processes that drive consistency and quality across projects - Align staffing, project priorities, and resource allocation to achieve commissioning objectives and business commitments - Provide technical leadership and escalation support for complex controls integration challenges - Review and approve control system designs, PLC code, and HMI interfaces developed by the team prior to deployment and on-site testing - Drive continuous improvement initiatives through root-cause analysis on recurring field issues and implement corrective actions back into design and commissioning standards - Report commissioning status, risks, and schedule health to Engineering and Program leadership; escalate resourcing or scope risks early - Drive development of reusable controls architectures, PLC software standards, commissioning tools, and engineering methodologies to improve project execution, scalability, and quality - Provide technical and resource planning leadership during project development by defining controls integration and commissioning scope, staffing requirements, schedules, and execution strategies - Own the development, implementation, and governance of safety, quality, controls integration, and commissioning standards across all projects and engineering activities - Accountable for employee performance, talent development, succession planning, and workforce capability within the Controls Integration team We need to keep each as

  . Now Requirements: from "Your Profile". Let's extract each bullet: - Proven experience leading teams of controls or commissioning engineers on large, complex material handling or industrial automation projects - Strong track record developing and executing commissioning and test plans, including sequencing, dependencies, and acceptance criteria - Advanced knowledge of industrial automation architectures, controls platforms, and systems integration principles including experience with Rockwell Automation Studio 5000 and Siemens TIA Portal PLC programming and troubleshooting - Experience with machine vision, sensing technologies, and industrial automation applications - Working knowledge of industrial network architecture and protocols, including Ethernet/IP, and familiarity with Profinet, Profibus, EtherCAT, or Modbus TCP - Ability to evaluate, approve, and guide technical solutions across PLC, HMI, vision, instrumentation, and networking technologies - Demonstrated ability to manage staffing schedules, project timelines, and budgets across concurrent commissioning projects - Strong root-cause analysis and structured troubleshooting skills across controls, electrical, and mechanical system boundaries - Excellent verbal and written communication skills, with the ability to lead on-site teams and represent Engineering to customers and internal stakeholders - Proven supervisory and leadership skills, including coaching, performance management, and technical mentorship - Ability to operate effectively in a high-paced, deadline-driven environment and deliver results on schedule - Working knowledge of applicable industrial automation and electrical safety standards, including IEC 61131-3 programming principles, ISA-88 modular control concepts, ISA-95 integration architectures, and NFPA 70E electrical safe-work practices Now Qualifications: from "Education And Experience Qualifications": - Bachelor’s degree or equivalent in Computer Engineering, Electrical Engineering, Controls Engineering, or a related field (required) - Minimum 8 years of progressively responsible experience in industrial automation, controls engineering, system integration, or material handling systems - Minimum 3 years of experience leading technical teams, supervising employees, or managing commissioning resources - Travel as required, up to 50% of the year, to support on-site commissioning oversight, team deployment, and customer go-live activities - Eligible applicants must be currently authorized to work in the United States on a full-time basis. The employer will not sponsor applicants for work visas for this position. Also there is a line: "Apply now and join our team! Ready for your next step? Click on ‘Apply now’ to get started right away! As long as the position is advertised, you can apply at any time." That's application instructions; we must remove. Then EEO/diversity statement: "We value diversity and therefore welcome all applicants - regardless of gender, nationality, ethnic or social origin, religion/belief, disability, age, sexual orientation and identity, and any other protected status." That's EEO boilerplate; remove. Then "You can find out more about our culture here Culture at Körber - it's worth taking a look! If you have any questions or technical problems, please send us an e-mail to jobs@koerber.com. Paoline Palm is the responsible person for this job advertisement. We work with permanent partners and therefore ask recruitment consultants to refrain from contacting us by e-mail or telephone." That's contact info; maybe considered boilerplate? It's not legal/EEO but it's contact instructions; could be considered application instructions? Probably remove. Then the long paragraph about Körber vision, Life 2035, etc. That's company marketing; maybe we could keep as part of About the role? But it's quite generic and not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive? It's about company vision; could be considered fluff but still part of posting. However it's quite long and not directly about the role. The instruction about sections: we should not create sections with filler. If we include this in About the role, it would be a lot of filler. Might be considered boilerplate? It's not legal/EEO, but it's still generic marketing. The instruction didn't explicitly say to remove marketing fluff, only cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should keep it. However we need to avoid filler/placeholder text like "commensurate with experience", "not specified", etc. This is not placeholder; it's actual content about company vision. So we should keep it. But we need to decide where to put it. Could be part of About the role as a second paragraph after the role description. However the About the role section might become very long with company vision. That's okay. Alternatively we could create a separate section like "About Körber" but not in allowed headings list. The instruction only gave examples of headings; we could still use other headings? It says use

  for section headings (e.g. About the