Senior Lead Automation Engineer

We need to output HTML fragment with sections: Overview (maybe not a heading? 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. We have sections: Overview (maybe treat as About the role?), Responsibilities, Qualifications, Why PM Group? (maybe Benefits? but it's more about company). We need to include only sections with real specific content. The posting includes Overview paragraph(s), Responsibilities (list), Qualifications (list), Why PM Group? (company culture). No explicit Pay, Schedule, Benefits, Skills. So we should not create those sections. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "All of your information is confidential according to EEO guidelines." That's EEO boilerplate; should be removed. Also "RECRUITMENT AGENCIES NEED NOT APPLY" is application instruction; remove. Also "Why PM Group?" includes some corporate responsibility text; we keep that as it's substantive about company. Also "Click here to read more in our 2025 Environmental, Social and Governance Report." That's a link; we might keep? It's part of Why PM Group? but it's a link; we can keep as part of prose. However we should not include navigation boilerplate. It's okay. We need to ensure we don't include headings with filler text. All sections have content. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  (or Overview). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map Overview to About the role. Use

  About the role

  then paragraphs. Then

  Responsibilities

  with
  • items. Then

    Qualifications

    with
    • items. Then maybe

      Why PM Group?

      but that's not in the list; but we could treat as About the company? Not in list. However instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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 are typical. However we should only include sections when posting has real specific content. The posting has "Why PM Group?" which is about company culture; we could include as a section with heading

      About PM Group

      or similar. But to stay safe, we could omit that section? But we would lose substantive info. The instruction: "Prefer a few substantive sections over many thin ones." It didn't forbid adding a section like About the company. However they gave examples; but we can still use

      About PM Group

      . It's not prohibited. However they said "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those exact headings when applicable. For company info, maybe we could incorporate into About the role? But that seems odd. Better to include a section like

      About PM Group

      . It's still a heading; not in the list but still an h3. The instruction didn't say we cannot use other headings; just gave examples. So it's fine. We need to preserve all substantive information: include the overview paragraphs, responsibilities list, qualifications list, and why PM group paragraph(s). Ensure we don't include EEO line or recruitment agencies line. Let's extract overview text: "The Senior Lead Automation Engineer (Connected Automation) position is an exciting opportunity to join PM Group’s quickly growing USA regional team. Together we are sharing knowledge, learning, growing, and continuing to be an integral part of supporting PM Group’s ongoing expansion in the US. This individual will be located out of our Raleigh-Durha, NC area office in Apex, NC (consideration will be given to candidates out of the Burlington, MA and Conshohocken, PA areas). We are executing cutting-edge projects for the Pharmaceutical, Biologics and Cell & Gene Therapy (life sciences) industry – from feasibility through to qualification – for both local and international clients. Together with our clients and partners, we deliver projects that improve the everyday lives of people across the globe. The Senior Lead Automation Engineer (Connected Automation) is a senior-level technical role providing automation design leadership on complex, regulated Life Sciences projects across the PM Group US region. This position plays a key role in leading automation system design, serving as a technical authority, and supporting the successful delivery of GMP-compliant Pharmaceutical, Biologics, and Cell & Gene Therapy facilities—from feasibility through qualification. This role suits an experienced automation professional who enjoys hands-on technical work, client engagement, and mentoring junior engineers, while also contributing to the growth and capability of PM Group’s Connected Automation offering in the US. PM Group is an employee owned, international project delivery firm with a team of 4,000+ people. We are world leaders in the pharma, food, biotech, medical technology and mission critical sectors. From our network of offices in Europe, Asia and the US, we work with the world's leading organizations. We are focused on growing a sustainable business centered on our people, our clients and trade partners." We need to preserve all that. Might be long but okay. Responsibilities list: bullet points under "Responsibilities". Let's extract each bullet: - Technical Leadership & Project Delivery - Lead the end-to-end automation design on Life Sciences and Pharmaceutical projects as part of a multidisciplinary project team - Act as a technical authority for automation system architecture, standards, and best practices - Develop, review, and approve key automation deliverables, including: * Process Descriptions * Functional Descriptions / Functional Design Specifications (FDS) * Control Narratives * Automation system architectures and design documentation - Support projects through design reviews, FAT/SAT, commissioning, and site execution activities - Ensure all automation solutions comply with GMP, GAMP 5, 21 CFR Part 11, and client quality standards - System Design & Vendor Oversight - Perform control system design for PLC, SCADA, and DCS-based systems across all project phases - Review and comment on system integrator and vendor design documentation - Select, coordinate, and manage automation contractors and system integrators throughout the project lifecycle - Maintain strong working relationships with automation vendors and stay current with emerging automation technologies and industry trends - Client Engagement & Communication - Serve as a key point of contact for automation with clients, vendors, and internal stakeholders - Lead and participate in technical discussions, client meetings, and design reviews - Participate in project site visits to monitor, review, and sign off on automation and process control installations - Mentorship & Team Development - Provide technical guidance and mentorship to junior and intermediate Automation Engineers - Perform peer reviews to ensure technical quality, consistency, and adherence to PM Group standards - Support the development and strengthening of PM Group’s Connected Automation capability in the US - Commercial & Business Support - Support automation scope development and proposal generation, including fee and capital budget inputs - Apply commercial awareness to project execution, including value engineering, resourcing, and change control - Collaborate across multiple PM Group offices to deliver projects efficiently and consistently - Industry Engagement - Support and promote PM Group’s Connected Automation services at client meetings and industry events, as appropriate We need to flatten into
      • items. Could keep sub-bullets as separate
      • but maintain hierarchy? Usually just flat list. We'll list each bullet as
      • . For sub-items like "Develop, review, and approve key automation deliverables, including:" we can keep as a
      • then nested list? The instruction: use
        • for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested
          inside
          • . That's okay. Qualifications list: - Bachelor’s Degree in Automation, Electrical, Electronics Engineering, or similar discipline - 10+ years of experience delivering industrial automation projects, preferably within Pharmaceutical, Biopharmaceutical, or Cell & Gene Therapy environments - Strong hands-on experience with: * PLC / DCS-based control systems design * Industrial automation architectures and software design (including S88) * Regulated GMP project delivery * Solid knowledge of industrial communications and networks (e.g., Ethernet/IP, Profinet, Profibus, ControlNet) - Proven ability to lead technical workstreams and interface effectively with clients and multidisciplinary teams - Strong written and verbal communication skills, including preparation of technical specifications and design documentation - Professional Engineer (PE) license preferred (CA, PA, or MA strongly preferred) - Ability to work across multiple offices and client sites as project needs require We'll format similarly. Why PM Group? section: "Why PM Group? As an employee-owned company, we are inclusive, committed and driven. Corporate Responsibility and Sustainability are the heart of our new 2026 business strategy. Click here to read more in our 2025 Environmental, Social and Governance Report. Inclusion and Diversity are core to our culture and values. Wherever we work, we commit to a culture of mutual respect and belonging by building a truly inclusive workplace rich in diverse people, talents and ideas. Valuing the contributions of all our people and respecting individual differences will sustain our growth into the future. PM Group is committed to ensuring our hiring process is fair and accessible to all and will provide candidates with disabilities with reasonable accommodations required to participate in the recruitment process. If you require any assistance in this regard, please let us know." We need to remove EEO line? Actually that line is part of Why PM Group? but it's about accommodations; it's not EEO boilerplate? It mentions providing candidates with disabilities with reasonable accommodations; that's still EEO-related but it's part of company statement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This line is about accommodations; could be considered EEO. Might be safer to remove it? But it's substantive about company's commitment. However it's likely considered EEO boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that sentence. Also the sentence "If you require any assistance in this regard, please let us know." is part of that. We'll remove both. Thus the Why PM Group? paragraph will be: "Why PM Group? As an employee-owned company, we are inclusive, committed and driven. Corporate Responsibility and Sustainability are the heart of our new 2026 business strategy. Click here to read more in our 2025 Environmental, Social and Governance Report. Inclusion and Diversity are core to our culture and values. Wherever we work, we commit to a culture of mutual respect and belonging by building a truly inclusive workplace rich in diverse people, talents and ideas. Valuing the contributions of all our people and respecting individual differences will sustain our growth into the future." We keep that. Now produce HTML. We'll start with

            About the role

            then

            ...overview...

            Then

            Responsibilities

            then