Process Controls Engineer - Allentown PA or LaPorte TX
Air Products · La Porte, TX · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. No job title heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
First paragraph: "At Air Products, we reimagine what’s possible..." That's about company, maybe "About the role"? Actually "About the role" could be description of role and location. The posting says: "We have an immediate opening for a Process Controls Engineer working either out of our Global HQ in Allentown, PA or out of our regional engineering office in LaPorte, TX. Ability to travel ~20%-40%, mainly in the Americas, mostly US domestic (East to West Coast). On-Call required: The team shares 24/7/365 support for these facilities, ~15 member team rotation."
That's about role location, travel, on-call. Could be part of "About the role". Also later: "Automation Support Engineers in this group work closely..." That's also description.
We need to preserve all substantive info, not invent.
We need sections: maybe About the role (description), Responsibilities (list), Requirements (maybe combine with Qualifications?), Skills (list), Benefits (list). Pay and Schedule only if stated. Pay: they mention "competitive pay" but not specific numbers; that's vague. According to rule: do NOT include Pay section unless posting actually states them (specific). "competitive pay" is not specific; we should not create Pay section. Schedule: they mention on-call rotation, travel %, but not schedule like shift times. Could we consider Schedule section? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (list). So include Benefits. Schedule: they mention on-call required, team shares 24/7/365 support, rotation. That's schedule info. Could be considered schedule. But they didn't give specific shift times. However "On-Call required: The team shares 24/7/365 support for these facilities, ~15 member team rotation." That is schedule info. Might be acceptable to include Schedule section with that detail. But rule says: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state on-call requirement and rotation, which is schedule-related. So we can include Schedule.
Pay: only "competitive pay" vague; better not include Pay.
Now we need to extract content.
About the role: combine paragraphs describing role, location, travel, on-call, team, facilities supported.
Responsibilities: list from "Key Job Responsibilities" bullet points (though not bullet but sentences). We'll make
- .
Requirements: maybe "Minimum Hiring Requirements" list: BS degree, 5+ years experience, ability to travel 20%-40%, flexibility to be on call, valid driver's license and good driving record. Also "This role is a Safety Sensitive Position. Pass pre-employment and random drug tests." That's also requirement.
Qualifications: maybe duplicate of requirements? Could combine. But we need to avoid thin sections. Could have Requirements section covering education, experience, travel, on-call, driver license, drug test. Skills: "Required Skills / Abilities" list: BS degree (already), experience in process automation systems and instrumentation, hands-on knowledge of automation systems, control panels and field instrumentation, strong communication skills. Could be Skills.
But we have overlapping content. We need to preserve all info, not repeat unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but better to avoid redundancy. However we must include all info; we can place each piece in appropriate section, maybe some overlap is okay but we should try to avoid repeating same sentence in multiple sections. Let's think.
We could structure:
- About the role: description of role, location, travel, on-call, team, facilities supported.
- Responsibilities: list of duties.
- Requirements: education, experience, travel %, on-call, driver license, drug test.
- Skills: process automation systems experience, hands-on knowledge, strong communication.
- Benefits: list.
- Schedule: on-call rotation details? But we already have on-call in Requirements and Schedule maybe duplicate. Could move on-call details to Schedule and keep Requirements without on-call? But Requirements includes ability to travel 20%-40% and flexibility to be on call. That's a requirement. So we could keep on-call in Requirements and not duplicate in Schedule. However Schedule section could be omitted if we consider on-call covered. But rule: only create Schedule if posting actually states them. It does state on-call requirement and rotation. So we could include Schedule with that detail, but then we would have duplicate info. Might be okay but better to avoid duplication. Perhaps we can put on-call details in Schedule and mention travel% in Requirements. But the posting says "Ability to travel ~20%-40%, mainly in the Americas, mostly US domestic (East to West Coast)." That's a requirement. So we can put travel in Requirements. On-call requirement and rotation could go to Schedule.
Thus:
About the role: description of role, location, team, facilities.
Responsibilities: list.
Requirements: BS degree, 5+ years experience, ability to travel 20%-40%, valid driver's license and good driving record, safety sensitive position requiring pre-employment and random drug tests.
Skills: experience in process automation systems and instrumentation, hands-on knowledge of automation systems, control panels and field instrumentation, strong communication skills for investigating, troubleshooting and presenting technical information.
Benefits: list.
Schedule: On-call required: team shares 24/7/365 support for these facilities, ~15 member team rotation.
We should also include maybe "Ability to travel ~20%-40%, mainly in the Americas, mostly US domestic (East to West Coast)." Already in Requirements.
Now we need to ensure we don't include boilerplate like EEO, veteran statement, etc. Remove those.
Also remove "Founded in 1940..." etc.
Now produce HTML.
We'll use
for each section heading. Inside sections, use
for prose,
- for lists. We need to preserve all substantive info. Let's extract exact sentences. About the role: From posting: "We have an immediate opening for a Process Controls Engineer working either out of our Global HQ in Allentown, PA or out of our regional engineering office in LaPorte, TX. Ability to travel ~20%-40%, mainly in the Americas, mostly US domestic (East to West Coast). On-Call required: The team shares 24/7/365 support for these facilities, ~15 member team rotation. Automation Support Engineers in this group work closely with our operating facilities as the experts in DCS and PLC automation system design and support, as well as process instrumentation and control devices, to keep our plants operating safely and providing product to our customers. The facilities we support produce and deliver Liquid and Gaseous Oxygen, Nitrogen, Helium, Carbon Dioxide and Hydrogen by direct pipeline, or liquid bulk transportation." We could keep that as prose. But we moved travel to Requirements and on-call to Schedule. So About the role should exclude those? Might be okay to keep them but then duplicate. Let's keep About the role as general description without travel and on-call specifics, but we need to preserve all info; if we omit them from About the role, we still have them elsewhere, so all info preserved. Good. Thus About the role: "We have an immediate opening for a Process Controls Engineer working either out of our Global HQ in Allentown, PA or out of our regional engineering office in LaPorte, TX. Automation Support Engineers in this group work closely with our operating facilities as the experts in DCS and PLC automation system design and support, as well as process instrumentation and control devices, to keep our plants operating safely and providing product to our customers. The facilities we support produce and deliver Liquid and Gaseous Oxygen, Nitrogen, Helium, Carbon Dioxide and Hydrogen by direct pipeline, or liquid bulk transportation." Now Responsibilities: list from "Key Job Responsibilities". The sentences: - Supporting the instrumentation and process control system needs of new and existing industrial gas facilities in North and South America that supply Oxygen, Nitrogen, Helium, Carbon Dioxide and Hydrogen to our customers. - Troubleshooting urgent and immediate operational needs for remote facilities; everything from Process Instrumentation, to DCS and PLC control logic, to Engineering and Operator Control Stations. - Safely implementing improvement projects with multi-disciplinary teams, and supporting maintenance outages for routine PM tasks, productivity modifications or obsolete equipment upgrades. - Supporting the improvement and optimization of existing assets, addressing instrumentation and process control system obsolescence challenges, and meeting organizational goals for safety, operational cost, and performance. We'll make each a
- .
Requirements: list:
- Bachelor of Science degree in Chemical, Electrical or Mechanical Engineering is required.
- 5+ years of work experience in process automation systems and/or instrumentation engineering is required.
- Ability to travel 20%-40%, mainly US domestic (East to West Coast) and Canada. (Note posting says "mainly US domestic (East to West Coast) and." maybe typo; we keep as given.)
- A valid drivers' license and a good driving record are required.
- This role is a Safety Sensitive Position. Pass pre-employment and random drug tests.
We could combine into
- . Skills: from "Required Skills / Abilities": - Experience in process automation systems and instrumentation. - Hands-on knowledge of automation systems, control panels and field instrumentation. - Strong communication skills for investigating, troubleshooting and presenting technical information to other engineering teams and site operations teams. Also note Bachelor of Science degree already in Requirements; we could omit duplication. But the skill list includes that as first bullet? Actually "Required Skills / Abilities" starts with "Bachelor of Science degree in Chemical, Electrical or Mechanical Engineering." then experience etc. Since we already have degree in Requirements, we could still include it in Skills but that duplicates. Better to omit duplicate degree from Skills to avoid redundancy. However we must preserve all substantive info; if we omit degree from Skills, it's still present in Requirements, so info preserved. Good. Thus Skills list as above. Benefits: list from "Affordable Medical, Dental and Vision Insurance (day 1 of employment)" etc. We need to preserve each benefit item as
- .
Let's extract:
- Affordable Medical, Dental and Vision Insurance (day 1 of employment)
- 401k with 100% vested company core and match
- Paid Vacation, holidays + sick time
- Paid Parental leave (Up to 8 weeks)
- Backup Child and Adult Care benefit
- Adoption assistance
- Flexible spending accounts (medical, dependent daycare)
- Life Insurance (AD&D- Paid for by Air Products), Supplemental AD&D
- Legal Plan & Identity theft coverage
- EAP (Employee Assistance Program)
- Many more supplemental benefits available
We'll keep as list.
Schedule: On-call required: The team shares 24/7/365 support for these facilities, ~15 member team rotation.
We could phrase as
On-call required: The team shares 24/7/365 support for these facilities, ~15 member team rotation.
Now ensure no boilerplate: remove veteran statement, EEO, etc. Now produce HTML. We'll output:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
On-call required: The team shares 24/7/365 support for these facilities, ~15 member team