Senior Engineer - Industrial Automation

We need to produce HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must preserve all substantive information. We need to parse the posting. Content: - Intro paragraph about Haskell, culture, etc. That's "About the role" maybe? Actually it's about company culture. Could be "About the role" or maybe "About Haskell". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the intro paragraph. - Then "In this role, you will serve as the lead technical resource..." That's responsibilities. So we can put under Responsibilities. - Then there is a list of Job Responsibilities with many bullet-like sentences. We need to convert to

• . The content includes many sentences separated by periods. We need to preserve all substantive info. We'll break each sentence into list items? The instruction: Use
  • for any list of duties/requirements/benefits. So we should treat the responsibilities as a list. We'll split by sentences (or by clear delineations). We'll need to ensure we don't lose info. - Then there is "Professional Development", "Leadership", "Travel" subsections within responsibilities? Actually after responsibilities list, there are sections: Professional Development, Leadership, Travel. Those could be separate subheadings? But instruction only allows certain headings; we could incorporate them under Responsibilities as sub-items? Or we could create separate sections like "Professional Development", "Leadership", "Travel" but those are not in the allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. So we should embed those details under Responsibilities as list items. - Then "Education & Years of Experience:" that's Requirements/Qualifications. We'll put under Requirements or Qualifications. The instruction: Use headings like Requirements, Qualifications. We need to decide which to use. Probably "Requirements" for education and experience, and "Qualifications" for preferred qualifications like PE license, etc. Or we could combine. But we need to avoid thin sections. Let's create "Requirements" for education and years of experience, and "Qualifications" for the list of needed skills/experience (PE license preferred, etc). Then "Skills" maybe for specific technical skills? But we already have qualifications list includes many skills. Could combine. Better: Use "Requirements" for education and years of experience. Use "Qualifications" for the list of needed competencies (PE license preferred, Electrical Design..., PLC & HMI Programming experience, ability to develop drawings, etc). Use "Skills" maybe for soft skills? But we have many soft skills listed: ability to work independently, adjust to changing timelines, etc. Could put those under Skills. However we might end up with many sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one section called "Qualifications". Or we could have "Requirements" (education/experience) and "Qualifications" (skills and competencies). That seems reasonable. - Then "At Haskell, we offer a comprehensive benefits package, including health insurance, retirement plans, professional development opportunities, and more." That's Benefits. So we create Benefits section. - Then "Environmental Factors and Physical Requirements:" etc. That's not in allowed headings; could be part of Requirements? But it's about physical demands. Could be included under Requirements as additional info. However we already have Requirements for education/experience. Could add a subsection? But we cannot add new headings. Could incorporate into Requirements as a paragraph. - Then EEO boilerplate etc must be removed. - Also there is "Job Responsibilities:" heading in the text; we should not duplicate as heading; we will treat as content. We need to preserve all substantive information. Let's extract. Intro paragraph: "At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact." That's about the role/company. Now responsibilities: The paragraph after that: "In this role, you will serve as the lead technical resource for all automation scopes of work related to a project and be responsible for coordination of design activities across multiple disciplines, vendors and/or subcontractors. You will work directly with customer and project leadership to develop and implement automation deliverables. Additionally, you will execute a project from beginning to end, including budget development and estimating, vendor scope development, conducting plant surveys, proposal development, execution of conceptual design work, execution of detailed design, programming, project management and startup. You may manage a small team of automation engineers working under your supervision for both design and startup aspects of a project. Additionally, you will provide project reporting to project and discipline leadership, including deliverable completion tracking and budget projections." Then there is a heading "Job Responsibilities:" followed by many bullet-like sentences. We'll treat all responsibilities as list items. Let's list them: - Application of Knowledge of Design (Conceptual Design) - Prepare and update control system basis of design and network architectures. - Understand and determine customer needs and define services needed to provide an effective project. - Develop automation content for proposals. - Develop automation design, hardware, and install budgets. - Detailed Design - Design low voltage (typically 480VAC and lower) power and control systems for automated process or packaging applications including control system panels, motor control center design, safety systems, and automation network design utilizing accepted practices and company or client standards. - Prepare scopes of work, bills of material, specifications, and other necessary project documents. - Review, check, modify, and develop control system drawings. - Develop functional specifications/sequence of operations. - Develop PLC programs utilizing company or client standards. - Develop HMI programs utilizing company or client standards. - Develop data collection and reporting software (For process only). - Review equipment specifications and line layouts (For packaging only). - Work closely with the simulation team to develop emulations (For packaging only). - Support the development & implementation of an acceptance test plan for the equipment at vendor’s facility and for the installed system at customer’s facility. - Participate in design reviews and vendor coordination meetings; present design and other technical information, and generally works with the project team throughout the overall design process. - Design Project Execution - Supervises the staff assigned to the projects, ensuring optimal staff utilization. - Oversees the work performed by the assigned staff. - Provides direction for what is to be included in design and programming deliverables. - Works with project Lead Associate to ensure that project schedule will be met and complete deliverables are provided for each submission. - Develops project within provided design budget. - Construction/Startup Support - Answer RFIs (Request for Information). - Supervision of construction and check-out of control system panels and components in client’s facilities. - Provide informal control system operation and maintenance training to client personnel. - Commission control system: conduct point to point checks, perform trial performance runs, and perform performance runs with product. - Document and maintain proper records of all design changes made during installation and startup work, to serve as a basis for the development of as-installed control system drawings and documents. - Update and maintain installation punch list to track contractor progress/issues. - Provide ongoing technical and troubleshooting support as requested by clients as on-going support after startup. - Supervise installation and start-up teams. - Professional Development - Pursuit of a P.E. License is encouraged. - Leadership - Manages assigned staff on the project. - Provides coaching/mentoring of assigned staff promoting individual growth. - Provide department managers with input on personnel assigned to your projects concerning their performance as appropriate. - Engages the entire team while working with all team members. - Flexible and willing to quickly move between projects as needed to meet the project schedule. - Travel - Flexibility for travel for installations and onsite startup is required. Average travel expectation is up to 20%. Some periods of heavy travel should be expected. Now Education & Years of Experience: "Bachelor of Science degree in Electrical Engineering, Mechanical Engineering, or equivalent required. 10 years of industry related experience required." Then "To thrive in this role, you'll need:" followed by list: - PE license preferred. - Electrical Design of Automation and 480V Power Systems knowledge - PLC & HMI Programming experience (Rockwell, others) - Ability to develop drawings using appropriate design software and provide verbal instructions to define design requirements. - Ability to safely use basic electrical tools required for troubleshooting electrical circuits. - Proficiency with Microsoft Office/365 software. - Experience in PLC and HMI programming is required. - Ability to work independently. - Ability to adjust to changing timelines and meet deadlines. - Ability to understand and adhere to both company and client design standards. - Excellent skills in time management, organization, and analytics. - Must be able to communicate in an objective and concise manner with supervisor(s), project managers, process and packaging engineers, suppliers, clients, and others, both orally and in writing, as related to job duties. - Must exhibit sound inter-personal skills and maintain amiable professional relationships with all company, client, and related business personnel. - Must be self-motivated with regard to the completion of assigned tasks and in obtaining new work from supervisors. - Basic understanding of hydraulics, fluid flow, pneumatics, and electric circuits. (Hydraulics and fluid flow knowledge applies to the process automation discipline only) Note there is duplication: "Experience in PLC and HMI programming is required." and earlier "PLC & HMI Programming experience (Rockwell, others)" and "Develop PLC programs..." etc. We'll keep both but could deduplicate? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. There's duplication of PLC/HMI programming experience. We should keep one instance. Let's see: "PLC & HMI Programming experience (Rockwell, others)" and later "Experience in PLC and HMI programming is required." They are similar but not identical; one says experience, the other says required. Both convey requirement. Could be considered duplicate. We'll keep one that says required maybe. But we need to preserve substantive info; removing one may lose nuance (preferred vs required). The first says experience (Rockwell, others) (maybe preferred). The second says required. So we could keep both but note they are similar. However instruction: remove duplicated lines. If they are essentially same, we can keep one. Let's keep the one that says "Experience in PLC and HMI programming is required." as it's more definitive. We'll drop the earlier "PLC & HMI Programming experience (Rockwell, others)" maybe. But we also have "Develop PLC programs utilizing company or client standards." and "Develop HMI programs utilizing company or client standards." Those are different tasks, keep. Now Benefits: "At Haskell, we offer a comprehensive benefits package, including health insurance, retirement plans, professional development opportunities, and more." Environmental Factors and Physical Requirements: We'll incorporate into Requirements maybe as a paragraph. We must remove EEO boilerplate etc. Now produce HTML. Structure:

    About the role

    Intro paragraph.

    Responsibilities

    • ... each responsibility as list item.
    We need to decide granularity: each bullet sentence as
  • . Could group subheadings