Senior Automation Engineer - Site Based, Redmond, WA

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Sections present: - About Us (but we have "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "About Us" description: "At Just Evotec Biologics, we believe that curiosity is the spark..." That's about the company. Could map to "About the role"? Actually "About the role" is more about the role description. The posting includes "The Role: Your challenge…in our journey" and then description. So we can put that under "About the role". Also there is "About Us" earlier; but we can combine? Probably better to put company description under "About the role"? The instruction says use those headings; we can decide to put company description under "About the role" or maybe we can omit if not specific? But we need to preserve all substantive info. So we need to include company description somewhere. Could put under "About the role" as a paragraph. Then "What You’ll Do" is responsibilities -> Responsibilities section. Then "Who You Are" maybe qualifications? Actually "Who You Are" describes personal attributes; could go under Skills or Qualifications? Probably "Qualifications" for education and experience; "Skills" for technical skills; "Requirements" maybe for education and experience? The instruction lists both Requirements and Qualifications separate. We need to decide mapping. We have "Education And Qualification Requirements" with bullet list of education/experience combos and then list of requirements (robust background, strong expertise, etc). That seems like qualifications and requirements. We have "Why Join Us" which includes benefits, growth opportunities, flexible work environment, inclusive culture, innovative projects, etc. That maps to Benefits section (maybe also Pay). There's also Pay info: "The base pay range for this position at commencement of employment is expected to be $125,000 to $155,000; this is a salary exempt role. Base salary offered may vary depending on the individual’s skills, experience and competitive market value. Additional total rewards include discretionary annual bonus, comprehensive benefits to include Medical, Dental and Vision, short-term and long-term disability, company paid basic life insurance, 401k company match, generous paid time off and paid holiday, wellness and transportation benefits." So Pay section: include salary range and mention of bonus etc? Actually bonus etc is part of total rewards; but Benefits section can include benefits details. Pay section should include salary range. Benefits section: list benefits (medical, dental, vision, disability, life insurance, 401k match, PTO, holidays, wellness, transportation). Also maybe mention flexible work environment? That's more about schedule? There's "Flexible Work Environment: We offer flexible work options to help you balance your professional and personal life. This is a site based role." That could go under Schedule? Actually schedule refers to work schedule (full-time, part-time, shift). Flexible work options could be schedule. We'll put under Schedule. Also "Inclusive Culture", "Innovative Projects", "A Place for Big Ideas", "Growth Opportunities" could be part of Benefits or maybe separate but we only have those headings. We could incorporate them into Benefits as bullet points. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement, etc. Also remove "Are You Still Curious?" etc? That's motivational but maybe considered boilerplate? It's part of the posting but not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Are You Still Curious?" is not legal boilerplate; it's more motivational. Might keep? It's not duplicated. Could keep as part of "About the role" or "Why Join Us"? It's at end. Might be considered fluff but not prohibited. Safer to keep? It's not EEO. It's not application instructions. It's a call to apply. Might be considered application instruction? It says "Take the leap and apply today." That's application instruction. So we should remove that. Also "Let your curiosity guide your career—#BeCurious and explore the endless possibilities at Just Evotec Biologics!" That's also application encouragement. Remove. Also remove "Evotec (US) Inc. is an Equal Opportunity Employer..." etc. Now structure:

About the role

... combine company description and role overview.

We need to preserve all substantive info: The company description paragraph, the role description paragraphs (The Role: Your challenge…). Also maybe the "As Senior Automation Engineer – Global MSAT at Just Evotec Biologics, you'll have the freedom..." etc. Let's extract: About Us paragraph: "At Just Evotec Biologics, we believe that curiosity is the spark that drives innovation and success. As a forward-thinking team, we thrive on challenging the status quo, learning from each other, and pushing the boundaries of what’s possible. We're on a mission to create a place where curiosity isn't just encouraged—it’s celebrated. Are you someone who asks questions, seeks answers, and isn't afraid to go deeper? #BeCUREious with us and see where your curiosity can take you!" The Role paragraph: "We’re looking for a passionate and curious Senior Automation Engineer – Global MSAT to join our team. If you’re excited by new challenges, solving complex problems, and learning every step of the way, you might just be the perfect fit. In this role, you’ll have the opportunity to drive impactful projects, collaborate with bright minds, and explore uncharted territories. As Senior Automation Engineer – Global MSAT at Just Evotec Biologics, you'll have the freedom to ask the hard questions, think outside the box, and find creative solutions that push us forward. It’s a role where your curiosity will fuel both your personal growth and the success of the team. The ideal candidate will ensure the AVEVA PI platform aligns with organizational objectives, complies with data governance protocols, and provides advanced reporting and analytics capabilities. This is a dynamic, highly technical role demanding deep expertise in AVEVA PI (including PI Asset Framework and PI Vision), as well as strong proficiency in process control systems, OT architecture, and integration with distributed control systems such as DeltaV. As a member of the Global MSAT Automation team, this role will oversee the design, deployment, standardization, and lifecycle management of the AVEVA PI infrastructure to support OT and process control systems across global operations. The position includes defining and maintaining integration strategies between PI and process control platforms, supporting global automation standards, and contributing to the development of a scalable, flexible, and reconfigurable cGMP manufacturing platform focused on continuous processing. This role also contributes to the governance and evolution of automation systems (including DeltaV), supporting global alignment across the J.POD manufacturing network. The successful candidate will bring experience in automation lifecycle management, software development lifecycle (SDLC) practices, and validated system environments, along with expertise in integrating data historians with control systems to enable advanced analytics, process optimization, and predictive control strategies." We can combine these into About the role. Now Responsibilities: "What You’ll Do" list items. Need to convert each sentence starting with a verb into

. Let's extract bullet points: - Oversee the comprehensive deployment of the AVEVA PI system, encompassing planning, configuration, validation, and rollout across international sites. - Architect, standardize, and sustain the PI system framework, utilizing PI AF and PI Vision to meet process control, data management, and visualization requirements. - Lead the continuous development of the AVEVA PI ecosystem by integrating new data sources, use cases, and business-driven enhancements, including advanced analytics and reporting. - Define and implement integration strategies between AVEVA PI and process control systems (e.g., DeltaV, SCADA, DCS), enabling real-time data access and operational insights. - Support governance and lifecycle management of automation platforms, including maintaining alignment of global standards and change management practices across sites. - Participate in defining and improving global software development lifecycle (SDLC) processes for automation and data systems. - Collaborate with global MSAT and site automation teams to ensure alignment with manufacturing platform objectives and automation strategies. - Ensure seamless OT infrastructure integration, maintaining secure and reliable connectivity between PI systems and process control environments. - Implement and uphold data governance and management standards to ensure data integrity, consistency, and accessibility. - Develop reporting, visualization, and analytics tools using AVEVA PI to deliver actionable insights to stakeholders. - Participate in the design and implementation of process control strategies, including batch tracking, process limits, and data-driven or predictive control approaches. - Provide technical guidance and support to global teams, resolving issues and ensuring system reliability and performance. - Collaborate with cross-functional groups, including IT, OT, and engineering, to align PI and automation systems with company objectives. - Develop and improve technical documentation including specifications, SOPs, and training materials. - Author and execute validation protocols (IQ/OQ/PQ) and test scripts for automation and data systems. - Lead or support technical root cause analyses, incident investigations, and troubleshooting of process control and data integration issues. - Manage CAPAs and change controls, collaborating with the site Manufacturing Technical Services (MTS) team to implement updates. - Serve as a key member of the New Product Introduction (NPI) team, ensuring automation, PI data integration, and MES readiness for new processes. - Provide technical oversight or support for projects involving third-party system integrators or vendors. - Offer technical support to manufacturing sites as needed, focusing on process control, automation systems, and data infrastructure. - Stay informed on advancements in AVEVA PI, process control technologies, and OT systems to propose innovative solutions. - Partner with diverse teams, including manufacturing, process engineering, data scientists, utility operations, maintenance, quality assurance, and validation, to drive operational enhancements. That's a lot; we keep all. Now Requirements / Qualifications / Skills. We have "Education And Qualification Requirements" with education/experience combos and then list of requirements. We need to split into sections: Requirements, Qualifications, Skills. The instruction says use those headings if there is real specific content. We have content for each. We could map: - Requirements: Education and experience combos (Bachelor’s or Masters degree ... etc). Also maybe "Robust background in control system automation..." etc could be Requirements. - Qualifications: maybe "Strong expertise in AVEVA PI system architecture..." etc. - Skills: maybe "Proficiency in scripting or programming languages (e.g., Python, SQL)" etc. But we need to avoid duplication. Let's parse the list after education: "Robust background in control system automation, including design, installation, programming, and validation of automated processes. Strong expertise in AVEVA PI system architecture, configuration, and development (PI AF, PI Vision, integrations). Experience integrating AVEVA PI with process control systems such as DeltaV (preferred), SCADA, or DCS platforms. Knowledge of FDA CFR 21 Part 11 compliance requirements. Proven track record of completing projects successfully using strong engineering and project management expertise. Experience supporting or defining automation standards, governance, and change management in a global manufacturing environment. Familiarity with software development lifecycle (SDLC) practices for automation systems. Demonstrated proficiency in OT system architecture and industrial data infrastructure. Prior experience with computer software validation. Involvement in global teams or Centers of Excellence. Experience applying GAMP5 risk-based methodologies for validated process automation system changes. Participation in regulatory inspections or audit support. Familiarity with single-use technologies and systems. Experience with automation platforms such as DeltaV, Siemens