Automation Engineer, CSP

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Key info: - Introduction: description of company, but not needed as a heading? Could be "About the role" maybe includes intro. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "Job posting end date: 10/30/2026" maybe minor metadata; could be placed in a short

. Also remove "Get in touch Want to rise above the possible with us? Click "Apply now" to submit your application." That's application instructions, remove. Also remove "Metso is committed to pay equity..." etc maybe boilerplate; but some of that may be considered benefits? It's about compensation transparency; but we can keep if it's substantive? Probably it's boilerplate; but we can keep "Compensation information is shared in line with local legislation and applicable recruitment practices." Might be considered minor metadata; we can drop. We need to include sections only when posting has real specific content. Let's extract: - About the role: Could be the introductory paragraph describing role: "We are looking for an Automation Engineer, SVS to join our Services Business Line, Screening & Crushing Solutions team. In this role, you will design and develop automation and electrical solutions for crushing and screening equipment, supporting product development, modernization projects, and customer installations. Your work will help improve equipment performance, safety, sustainability, and lifecycle value while supporting Metso's automation and digital services strategy. You will report to the Lead Automation Engineer. This role is based in Brookfield, WI with hybrid working options available. This role includes approximately 20% travel to customer sites and project locations, both domestically and internationally." That's substantive. So we can have

About the role

then a

with that text. - Team you will belong to: Could be under About the role or separate? Could be "Team you will belong to" as a heading? Not in the list but we could incorporate into About the role or maybe as a separate section like "Team". But instruction only gives examples; we can use other headings if needed? It 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. Safer to stick to those categories. So we can incorporate team description into About the role or Responsibilities. - Responsibilities: The "What You’ll Do" bullet list. So we can have

Responsibilities

then

• items. - Requirements/Qualifications/Skills: The "What You’ll Bring" includes education, experience, etc. Could split into Requirements (education, experience) and Skills (specific technical skills). But we can combine into Requirements or Qualifications. The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide based on content. We have: Bachelor's degree in Electrical Engineering, Automation Engineering, Industrial Engineering, or a related discipline. Minimum of 3 years of experience in process automation, manufacturing automation, or industrial control systems. Experience developing and troubleshooting PLC-based automation solutions. Experience designing and troubleshooting HMI applications and industrial communication networks. Knowledge of electrical system design, including electrical schematics, control panels, and component selection. Strong communication skills in English, both written and verbal, with the ability to collaborate effectively across cross-functional teams. Ability to work independently, manage priorities, and deliver quality results with limited supervision. Experience with EPlan, hydraulic and lubrication control systems, and project delivery in manufacturing or custom-engineered systems (nice to have). We could treat first two as Requirements (education, experience). Then the rest as Skills (technical skills, communication, etc). Or we could have Qualifications (education+experience) and Skills (technical). Let's do:

  Requirements

  with education and years experience.

  Skills

  with the rest. But also there is "What's In It For You" which includes benefits: purpose-led work, wellbeing, rewards, flexibility, growth, culture, plus specific USA benefits: Competitive benefits plan, Healthy living rewards, Mental wellbeing services, Annual leave starting at 15 days per calendar year, Engagement surveys, Global incentive program tied to business and performance targets. We can make a Benefits section. Pay and Schedule: Not explicitly given. No salary range, no schedule details besides hybrid working options and 20% travel. Schedule could be inferred? Not explicit. So we should not create Pay or Schedule sections unless posting actually states them. It does not state pay, so omit Pay. Schedule: It mentions hybrid working options, but not specific schedule; maybe we could include Schedule? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state hybrid working options (flexibility) and travel percentage. That's more about work arrangement, not schedule. Could be considered Schedule? But it's not explicit like "full-time", "part-time", "shift". Safer to omit Schedule section; we can include flexibility under Benefits. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to preserve all substantive information; do not invent or summarize away detail. Must keep all details from the posting. Let's extract each piece precisely. About the role paragraph: We'll combine the intro and team description maybe. Original text: "Introduction We are looking for an Automation Engineer, SVS to join our Services Business Line, Screening & Crushing Solutions team. In this role, you will design and develop automation and electrical solutions for crushing and screening equipment, supporting product development, modernization projects, and customer installations. Your work will help improve equipment performance, safety, sustainability, and lifecycle value while supporting Metso's automation and digital services strategy. You will report to the Lead Automation Engineer. This role is based in Brookfield, WI with hybrid working options available. This role includes approximately 20% travel to customer sites and project locations, both domestically and internationally. Team you will belong to You will join a team of automation and electrical engineering professionals focused on developing innovative automation solutions for crushing and screening equipment. Our team plays a key role in advancing Metso's modernization and digitalization initiatives, helping customers improve operational performance, safety, and sustainability across their installed equipment base. We collaborate closely with product management, service teams, customers, engineering partners, suppliers, and other technical specialists around the world. Our team operates in a global environment and values open communication, collaboration, accountability, continuous learning, and practical problem-solving." We need to preserve all that. So we can combine into one paragraph or multiple

  tags. Use

  for prose. Thus About the role section will have maybe two paragraphs: first paragraph covering role basics, second paragraph covering team. Now Responsibilities: list from "What You’ll Do". Items: - Design and develop automation solutions for crushing and screening equipment modernization and product development projects. - Develop, test, troubleshoot, and optimize PLC programs, HMI applications, and industrial communication networks. - Support electrical system design activities, including schematics, panel layouts, component selection, and control system architecture. - Prepare technical documentation, installation instructions, specifications, and automation upgrade packages. - Collaborate with external engineering partners on electrical drawings, control logic development, HMI configuration, and project documentation. - Participate in product validation, factory acceptance testing, commissioning, and customer startup activities. - Provide technical support during equipment upgrades, troubleshooting, and operational improvement initiatives. - Contribute to the development of standardized automation products and evaluate new technologies related to connectivity, digital services, and machine optimization. Make each as

• . Now Requirements: education and experience. - Bachelor's degree in Electrical Engineering, Automation Engineering, Industrial Engineering, or a related discipline. - Minimum of 3 years of experience in process automation, manufacturing automation, or industrial control systems. We could keep as
  • . Now Skills: rest of What You’ll Bring. - Experience developing and troubleshooting PLC-based automation solutions. - Experience designing and troubleshooting HMI applications and industrial communication networks. - Knowledge of electrical system design, including electrical schematics, control panels, and component selection. - Strong communication skills in English, both written and verbal, with the ability to collaborate effectively across cross-functional teams. - Ability to work independently, manage priorities, and deliver quality results with limited supervision. - Experience with EPlan, hydraulic and lubrication control systems, and project delivery in manufacturing or custom-engineered systems (nice to have). Make as
    • . Now Benefits: from "What's In It For You" and USA benefits. Paragraph: "At Metso, you will combine meaningful work with opportunities to learn, grow, and make an impact in a supportive and inclusive environment. You’ll be part of a global team where collaboration, wellbeing, and continuous learning are part of everyday work. We support your growth and wellbeing by offering:" Then bullet list: - Purpose-led work: Contribute to enabling sustainable modern life and transforming the industry. - Wellbeing: Access to wellbeing programs, occupational healthcare, and supportive services. - Rewards: Competitive compensation and performance-based incentives. - Flexibility: Hybrid working options to support balance and productivity. - Growth: Learning pathways, mentoring, internal mobility, and global collaboration opportunities. - Culture: A caring, collaborative, and inclusive workplace committed to helping you thrive. Then USA-specific benefits: - Competitive benefits plan - Healthy living rewards - Mental wellbeing services - Annual leave starting at 15 days per calendar year - Engagement surveys - Global incentive program tied to business and performance targets We could combine all into a single
      • list, preserving each item. We need to ensure we don't repeat boilerplate like "Metso is committed to pay equity..." etc. Remove that. Also remove "Get in touch..." etc. Also remove "Metso is an equal opportunity employer..." etc. Also remove "Metso is a frontrunner..." etc (company description) maybe considered boilerplate; but some of that is in the intro earlier? The initial paragraph about world depends on rocks etc is also company description; but we might consider that as part of About the role? It's not specific to the role; it's generic company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The generic company description at start might be considered boilerplate? It's not legal/EEO, but it's generic marketing. However it's part of the posting; but the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The generic description might be considered substantive? It's about the company mission. Might be okay to keep. But we already have About the role section; we could include that as a separate "About Metso" but not in allowed headings. Could incorporate into About the role as extra paragraph. However the instruction says prefer a few substantive sections over many thin ones. So we could add a paragraph about Metso mission in About the role before role specifics. Let's see: The beginning: "Our world depends on rocks, minerals, metals and other raw materials – the building blocks of modern society. As an industry leader, Metso helps transform these essential materials to enable sustainable modern life. Our solutions and services support everything from renewable energy and electrification to the infrastructure and digital economy shaping our future. Together, we help our customers meet growing demand while driving the industry toward a more sustainable use of the earth’s natural resources. Join nearly 18,000 Metsonites worldwide, each bringing unique expertise and experience