Sr Automation Engineer

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Preserve all substantive info. We need to parse the job description. Job Title: Sr Automation Engineer (but we don't output heading for title). The description includes: - Job Description paragraph: "The Systems Engineer designs, programs, and supports industrial control and monitoring systems for natural gas gate stations and plant operations. This role focuses on PLC and HMI development, SCADA infrastructure, and communications systems to ensure safe, reliable, and efficient delivery of natural gas. The Systems Engineer collaborates with cross-functional teams to define system requirements, implement solutions, and maintain high standards of performance, compliance, and operational integrity." That's prose; could be under "About the role" heading. Responsibilities: list of bullet points (starting with "Collaborate with internal organizations..." etc). We'll put under

Responsibilities

with

• each. Requirements: maybe "Essential Skills" and "Additional Skills & Qualifications". The instructions: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have "Essential Skills" list (hands-on experience with SCADA, proficiency in PLC programming, etc). Also "Additional Skills & Qualifications" list (experience with C++, familiarity with natural gas distribution, etc). Also "Work Environment" (hybrid-flexible, travel, mileage reimbursement, etc). Also "Job Type & Location" (Permanent position based out of Springfield, VA). Also "Pay And Benefits" (pay range $114000 - $183000/yr, plus mention PTO, Holiday, & Bonuses, Company has been in business 174 years). Also "Workplace Type" (fully onsite position in Springfield,VA). Also "Application Deadline" (position anticipated to close on Sep 30, 2026). Also "About Actalent" (company description). Also EEO etc (to remove). Also "San Francisco Fair Chance Ordinance", etc (legal boilerplate to remove). Also "Use of Artificial Intelligence (AI)" (maybe remove as boilerplate? It's about hiring process; could be considered boilerplate but maybe keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The AI use statement might be considered legal boilerplate; better to remove. Also "If you would like to request a reasonable accommodation..." is accommodation request; could be considered EEO/legal; remove. Thus we need to keep substantive info: job description, responsibilities, essential skills, additional skills & qualifications, work environment, job type & location, pay and benefits, workplace type, application deadline, about Actalent (maybe as "About the company"? Not a specified heading; we could put under "About the role"? Actually "About the role" is for role description; we already have that. "About Actalent" is company info; could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description. But we don't have a heading for company; we could put under a generic

  About the company

  but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must use those headings only? It says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples, not exclusive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. Could also add other headings if needed? The instruction: "IMPORTANT: 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 other headings, but the examples given are those. Safer to stick to those headings. Thus we need to map content to those headings. - About the role: includes job description paragraph. - Responsibilities: list. - Requirements: maybe "Essential Skills" could be considered requirements. Or we could split: Requirements (mandatory) and Qualifications (preferred). The posting has "Essential Skills" (maybe requirements) and "Additional Skills & Qualifications" (maybe qualifications). So we can put Essential Skills under

  Requirements

  and Additional Skills & Qualifications under

  Qualifications

  . - Skills: maybe we could combine? But we already used Requirements and Qualifications. The heading Skills could be used for technical skills list? But we already have those. Could we put "Essential Skills" under Skills and "Additional Skills & Qualifications" under Qualifications? But we need to follow the instruction: Use headings for those sections. It didn't say we must use all; we can use only those that have content. So we could use Requirements for Essential Skills, Qualifications for Additional Skills & Qualifications, and maybe Skills for something else like "Hands-on experience with SCADA systems, ..."? That's duplicate. Better to follow the examples: they gave About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should try to fill each if possible. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: maybe the "Essential Skills" (these are requirements). Could also include "Bachelor’s degree in Electrical Engineering, Computer Science, Information Systems, or a related field." and "Experience in Electrical Engineering, Electronics, Computer Systems, or a closely related technical discipline." Those are requirements. - Qualifications: maybe the "Additional Skills & Qualifications" list. - Skills: maybe we could list specific technical skills like "PLC programming, HMI development, SCADA, communication protocols, MS SQL, etc." But that overlaps with Requirements. Could we put a combined list under Skills? But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in the source? But we should not repeat same content unnecessarily? It didn't forbid duplication, but better to avoid redundancy. However we could split: Requirements for education and experience, Qualifications for additional nice-to-haves, Skills for technical proficiencies. Let's examine the source: Essential Skills list: - Hands-on experience with SCADA systems, including designing, integrating, and managing PLC-based SCADA infrastructure. - Proficiency in PLC programming using vendor-specific industrial programming languages. - Strong understanding of process control systems and industrial automation for gate stations and plant operations. - Experience implementing and supporting communication infrastructure across cellular, radio, and other media. - Working knowledge of communication protocols such as UDP, TCP/IP, Modbus, and BSAP. - Ability to develop and maintain HMI applications using vendor-specific programming tools. - Experience with MS SQL and ANSI SQL for database administration, data archiving, and reporting. - Experience in Electrical Engineering, Electronics, Computer Systems, or a closely related technical discipline. - Bachelor’s degree in Electrical Engineering, Computer Science, Information Systems, or a related field. - Ability to troubleshoot complex control, communication, and data issues in an industrial environment. - Strong analytical and problem-solving skills applied to process control and automation challenges. Additional Skills & Qualifications list: - Experience with C++ or similar programming languages for automation-related development. - Familiarity with natural gas distribution, storage, or energy infrastructure operations. - Experience developing operation and maintenance procedures and technical documentation, including wiring schematics. - Exposure to cross-functional project work and coordination with IT, operations, and engineering teams. - Ability to evaluate new products and technologies and provide recommendations based on testing and analysis. - Strong communication skills to collaborate effectively with technical and non-technical stakeholders. - Interest in working within an organization focused on delivering clean, affordable natural gas and innovative energy solutions. Thus we could map: - Requirements: Education + core experience (Bachelor's degree, experience in EE/CS, ability to troubleshoot, analytical skills). Could also include the core technical skills? But we might put those under Skills. - Qualifications: Additional Skills & Qualifications list. - Skills: The technical proficiencies list (SCADA, PLC programming, process control, communication infrastructure, protocols, HMI, MS SQL). That seems appropriate. Thus we have content for all headings. Now Benefits: The posting mentions "PTO, Holiday, & Bonuses, Company has been in business 174 years." Also mileage reimbursement for required travel (under Work Environment). Also maybe "Mileage reimbursement is provided for required travel." That's a benefit. Also maybe "PTO, Holiday, & Bonuses". Also "Company has been in business 174 years." That's not a benefit per se but could be under Benefits. Also maybe "Workplace Type" is not benefit. So we can include Benefits section with mileage reimbursement, PTO, Holiday, Bonuses, and maybe note company longevity. Pay: The pay range $114000 - $183000/yr. Schedule: The posting mentions "Work Environment: This is a hybrid-flexible position that involves regular travel to field locations, gate stations, and plant sites as needed, with an approximate 50/50 split between office and field work." Also "Workplace Type: This is a fully onsite position in Springfield,VA." There's a contradiction: hybrid-flexible vs fully onsite. But we need to preserve all info. For Schedule heading, we could include the hybrid-flexible description and the 50/50 split. Also maybe mention travel. The Workplace Type could be separate but we don't have a heading for that; maybe we can include under Schedule or Benefits? The instruction: Use headings for those sections; we could put workplace type under Schedule? Not ideal but we have to include all substantive info. Could we add another heading like "Workplace Type"? Not in examples but maybe allowed. However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could include Workplace Type as a

  as well, but it's not in the list. Might be considered extra but still okay. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add other headings if needed. But to follow the spirit, we could incorporate workplace type into Schedule or Benefits. Let's see: Schedule could include work schedule details (hybrid-flexible, 50/50 split, travel). Workplace type (fully onsite) is more about location than schedule. Could be under "About the role"? Not ideal. Maybe we can add a heading "Work Environment" but not in list. However the instruction says to use those headings for section headings; maybe they expect us to only use those headings and any other content should be placed under those headings. So we need to fit workplace type somewhere. Could be under Benefits? Not really. Could be under About the role? Could add a sentence about location. The job description already mentions location in "Job Type & Location". We could incorporate that into About the role or maybe under Requirements? Not great. Alternatively, we could create a heading "Job Type & Location" but not in list. Might be okay. But to be safe,