Automation Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "How To Apply" etc. Also remove "About Us" maybe? The instructions say we should include sections only when posting has real specific content. The posting includes "What We Will Expect From You" (that's like role description). Also "Essential Functions Of The Job" (list). Also "Responsibilities". Also "Qualifications". Also "Physical Demands". Also "What’s In It For You" (benefits). Also "About Us" (company description). Also "Our Vision", "Our Mission", "Our Approach". Those are likely boilerplate? Might be considered company description but not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us", vision, mission, approach might be considered not boilerplate but could be considered company description; but we need to decide if we include them. The allowed headings list does not include "About Us" etc. So we should not create headings for those unless they map to allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those. We have: - About the role: could be the introductory paragraph "What We Will Expect From You" and maybe "Essential Functions Of The Job". We'll combine into a prose
maybe with
- for essential functions.
- Responsibilities: there is a "Responsibilities" section with bullet points.
- Qualifications: there is a "Qualifications" section with bullet points.
- Skills: maybe we can extract from qualifications? But we have no explicit Skills section; we could combine qualifications into Skills? But we should not create a Skills section unless posting actually states them. The posting does not have a separate "Skills" heading; but we could treat qualifications as skills? However instruction: "include a section ONLY when the posting has real, specific content for it". Since there is no explicit Skills section, we should not create one.
- Benefits: there is "What’s In It For You" describing benefits. So we can create Benefits section.
- Pay: posting includes Pay: $80k-$120k. So we should include Pay section.
- Schedule: posting includes Schedule: Mon-Fri. So include Schedule section.
- Requirements: maybe we can treat Qualifications as Requirements? But we have Qualifications heading allowed. The posting has "Qualifications". So we can use that heading. Requirements maybe not needed if we have Qualifications. But we could also include Requirements if there are any explicit requirements separate from qualifications. The posting includes "Essential Functions Of The Job" maybe considered requirements? But we already have About the role. We'll not create Requirements unless there is explicit content. The posting does not have a separate "Requirements" heading besides Qualifications. So we skip Requirements.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". The Pay section: we have actual range $80k-$120k. Also note FLSA: Exempt. Should we include that? It's metadata; maybe include in Pay section or a short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- items.
About the role: include the paragraph "What We Will Expect From You" and maybe the essential functions list. We'll keep the prose and then a
- for essential functions.
Responsibilities: list bullet points.
Qualifications: list bullet points.
We must not include Physical Demands? That's substantive but not under allowed headings. Could we fold it into About the role or Responsibilities? It's about physical demands; maybe we can include in About the role as a note. But we must preserve all substantive info; we could add a
- . Responsibilities section: - Work closely with Process Engineering and Production teams to deploy and improve process control automation. - Identify top operational losses and execute improvements to eliminate inefficiencies. - Ensure that gains achieved from automation projects are sustained over time. - Continuously identify opportunities to improve process control and automation through new tools, technologies, and process improvements. Qualifications: - Bachelor’s Degree in Electrical or Automation Engineering - 5+ years of hands-on industrial and/or manufacturing experience - Capability to program and troubleshoot complex PLC, HMI, and components - Experience with automation, process control, or other manufacturing and E&I equipment - Project management experience with the ability to manage multiple projects - Leadership of a team to develop, manage and execute projects - The ability to read and understand operating procedures, manuals and drawings - Strong time management and organizational skills Physical Demands: we need to preserve. Physical Demands Must wear and maintain company required Personal Protective Equipment including, but not limited to: FR pants/ long-sleeve shirt, safety glasses, hard hat, safety-toe boots, hearing protection, and glovesPhysically able to perform the following job essential functions, inclusive of but not limited to: crouching, kneeling, bending, walking long distances, lifting/pushing/pulling/carrying up to 50 pounds, work at heights, continuous work in confined spaces, ascend/ descend/ work from: stairs/ladders/scaffolding.Must have the ability to work continuously in an environment inclusive of but not limited to: dust, loud noise(s), walk on uneven or slippery surfaces, outdoors, heat/cold, poorly illuminated areas. We need to format as a paragraph. Benefits: "What’s In It For You We offer a competitive compensation and benefits package, including a bonus. The starting salary is based on the candidate's experience, education, and market pay for the role in the region. As a team member at Verbio North America, you’ll also enjoy: Comprehensive benefits package beginning day one, including health, dental, vision, and life insurance.Company paid short & long-term disability coverage as well as AD&D.G
under About the role after essential functions describing physical demands. However the instruction says we should not create sections unless posting has real specific content for it. It didn't say we cannot include extra paragraphs inside sections. So we can include physical demands as a paragraph within About the role or maybe a separate section? Since there is no allowed heading for Physical Demands, we should not create a heading for it. So we can incorporate it into About the role as a
. Similarly, "About Us", vision, mission, approach are company description; we could incorporate into About the role? But that might be too much and not directly about the role. However the instruction says remove boilerplate; those might be considered boilerplate? Not exactly EEO but could be considered company overview. Safer to omit them, as they are not required headings and might be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not explicitly say to remove company overview. But we should preserve ALL substantive information; company overview is substantive but not about the role. However the allowed headings do not include a section for company overview. The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding other headings not in list? 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 but maybe we should only use those headings. Safer to stick to those headings only. So we will not include About Us etc. Thus final HTML:
About the role
In this role, you will work closely with the Process Engineering and Production teams to support and enhance process control automation across the facility. You will maintain and improve DCS and PLC platforms, troubleshoot automated equipment, and help identify and resolve technical issues through root cause analysis. Using PLC software and process control tools, you will support automation projects, improve machine functionality, and help eliminate inefficiencies while ensuring automation improvements are successfully implemented and sustained. This position reports directly to the Engineering Manager.
Essential Functions
?? Not allowed heading. We need to embed essential functions as a list under About the role maybe as- . But we need a heading? Could we just put
- directly after the paragraph without a heading? 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 we should follow that pattern. However essential functions is a list of duties; we could treat it as part of About the role and just include a
- after the paragraph. That seems okay.
Thus About the role section will have a paragraph then a
- of essential functions.
Then after that, maybe a
for Physical Demands. Then
Responsibilities
with- .
Then
Qualifications
with- .
Then
Benefits
with- (or
plus
- ).
Then
Pay
withcontaining salary range and FLSA. Then
Schedule
withMon-Fri. We must not repeat job title as heading. Good. Now ensure we preserve all substantive info from each section. Let's extract exact text. From posting: "What We Will Expect From You In this role, you will work closely with the Process Engineering and Production teams to support and enhance process control automation across the facility. You will maintain and improve DCS and PLC platforms, troubleshoot automated equipment, and help identify and resolve technical issues through root cause analysis. Using PLC software and process control tools, you will support automation projects, improve machine functionality, and help eliminate inefficiencies while ensuring automation improvements are successfully implemented and sustained. This position reports directly to the Engineering Manager." That's the paragraph. Essential Functions Of The Job list: - Maintain and support DCS and PLC platforms. - Utilize PLC software to enhance, modify, and troubleshoot machine functions and capabilities. - Provide engineering support to operations by troubleshooting automated equipment, resolving technical issues, and performing root cause analysis. - Implement process automation solutions on DCS platforms in coordination with site teams and external vendors. - Develop, manage, execute, and support the start-up of automation projects. We need to keep each as
or drop it. So FLSA is minor metadata; we can include in a short p maybe under Pay or separate? Probably include in Pay section as a note. Schedule: Mon-Fri. Benefits: need to list all benefits described: "competitive compensation and benefits package, including a bonus. The starting salary is based on the candidate's experience, education, and market pay for the role in the region. As a team member at Verbio North America, you’ll also enjoy: Comprehensive benefits package beginning day one, including health, dental, vision, and life insurance. Company paid short & long-term disability coverage as well as AD&D. Generous vacation, holiday, and sick time with additional leave plans 11 paid holidays 5 sick/personal days Paid vacation time Company contribution of 3% safe harbor and 2% profit sharing in accordance with the contribution and vesting schedule Advancement and bonus opportunities Career Development: on-the-job training and skills development." We need to preserve all that. Could format as