Principal - Engineer - Automation (Data & Platforms integration)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. We need to preserve all substantive info. Let's parse the posting. First paragraph: "At Lilly, the work is demanding because patients are waiting..." This is about company description. Could be "About the role"? Actually it's about company. Could be "About the role" or "About Lilly". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and put the company description there. But we must not repeat job title as heading. Job title is "Principal Automation Engineer – Data and Integration Platforms". Not to be used as heading. We need to include Responsibilities section: there is a "Responsibilities" heading in the posting. We'll keep that. Key Deliverables: maybe part of responsibilities? Could be separate but we can include under Responsibilities. Qualifications: there is "Basic Qualifications" and "Additional Skills/Preferences". Also "Additional Information". We'll need to map to sections: Requirements, Qualifications, Skills maybe. Pay: there is "Actual compensation will depend..." and "The anticipated wage for this position is $66,000 - $171,600". Also mention bonus and benefits. So we can have Pay section with that wage range and bonus info. Benefits: there is a paragraph about comprehensive benefit program. So Benefits section. Schedule: there is "Full-time equivalent employees also will be eligible for a company bonus". Not schedule. There's "Potential for travel (less than 20% - could be domestic and/or international)". That's not schedule. No explicit schedule like hours. So we should not create Schedule section unless posting actually states them. It doesn't. So omit Schedule. Also we need to include maybe "Qualifications" heading for basic qualifications and additional skills. We need to avoid boilerplate: EEO, accommodation request, etc. Remove those. Also remove duplicated lines: there is repeated "At Lilly, we unite caring with discovery to make life better for people around the world." We'll keep only once. We need to preserve all substantive information: company description, role description, responsibilities, key deliverables, qualifications, additional skills/preferences, travel info, compensation, benefits. Let's extract substantive content. Company description (About the role): - At Lilly, the work is demanding because patients are waiting. We unite caring with discovery to help make life better for people around the world, knowing that every decision, every detail, and every day matters. Headquartered in Indianapolis, Indiana, our over 50,000 employees around the globe take on complex challenges to discover and deliver life-changing medicines, strengthen how health is understood and managed, and support the communities we serve. This is hard, urgent, selfless work—but it’s work worth doing. If you’re driven by purpose and ready to bring your best to work that truly matters for patients, we invite you to join us. At Lilly, we unite caring with discovery to make life better for people around the world. We are a global healthcare leader, headquartered in Indianapolis, Indiana. Our 40,000 employees around the world work to discover and bring life-changing medicines to those who need them, improve the understanding and management of disease, and give back to our communities through philanthropy and volunteerism. We give our best effort to our work, and we put people first. We’re looking for people who are determined to make life better for people around the world. Lilly is currently constructing an advanced manufacturing facility for production of API molecules located in Houston, TX. This facility is intended to provide APIs for current and future products, including new modalities. This is a unique opportunity to be a part of the site technical team for the startup of a greenfield manufacturing site, and the successful candidate will help to build the Processes, the facility and the culture to enable a successful startup into GMP manufacturing operations. We might trim duplication: there are two similar paragraphs about Lilly uniting caring with discovery. We'll combine but keep substance. Responsibilities: The posting has a "Responsibilities" heading then a paragraph describing the role. Let's capture that. Responsibilities paragraph: "The Principal Automation Engineer – Data and Integration Platforms is a mid-level automation engineering position that requires a deep understanding of process data historians, system integration, Lilly’s computer system validation practices, cGMP standards related to computer systems, and data integrity as they relate to pharmaceutical manufacturing. This role will support the design and delivery of site data historian system, key integration platforms, and the system administration of site servers. This role will also be integral in the design and delivery of data historian and integration platforms including design, validation plans, system integrator selection and oversight, and developing the site administrative procedures that ensure they remain in a validated state. This role will also support, as a secondary responsibility, related site automation platforms including process automation servers and the DeltaV DCS. Lilly Houston is part of Lilly’s Drug Substance (Active Pharmaceutical Ingredient) network. During the design and delivery of the project this role will be integrated into the corporate automation team GPACE (Global Process Automation & Control Engineering) and then transition fully to a site-based process team position. During delivery, this role will collaborate with Lilly Quality, A&E firms, system integrators, Emerson, and corporate and site engineering peers. Post-project delivery, this role will support GMP manufacturing operations in the central engineering function supporting site process teams with Data Historian and integration services as well as system administration and platform upgrades. This role will require significant collaboration, creativity and resilience as the site grows to a full scale GMP manufacturing site through start up." Key Deliverables: list bullet points after "Key Deliverables". We'll treat as part of Responsibilities or separate? Could be separate section but we can include under Responsibilities as a list. Key Deliverables bullet points: - Champion a strong safety culture, mentor and coach others, and utilize engineering and automation fundamental principles in design and problem solving. - Become a subject matter expert on Lilly’s Aveva PI Data Historian reference architecture. - Support the design, delivery, validation, and system management of the site Data Historian and related system integration platforms. - Lead and direct system integrations and OEM’s on the design and installation of the Aveva PI platforms, data centers, and associated site infrastructure. - Collaborate with Lilly’s Quality organization, Corporate Engineering, and Global Facilities Delivery to develop Computer System qualification and testing strategies. - Ensure CSV documents comply with Corporate Quality Standards and Practices, local templates, and electronic document management system properties. - Participate in basic and detailed design that also includes staffing, statements of work, supplier management, and delivery strategies computer system validation. - Develop and build capabilities within the Houston site automation team. - Support the development of site procedures related to computer system validation and administration practices. - Provide technical oversight during development of equipment and process system User Requirements and related Design Review/Qualification documentation to ensure equipment and systems are appropriate for intended purpose. Basic Qualifications: - Bachelor’s degree in engineering or related applicable discipline required. - 5+ years of experience in Aveva PI Data Historian administration including hardware design, software integration, and system procedures. - Experience with Windows Servers and virtual environments. - Qualified applicants must be authorized to work in the United States on a full-time basis. - Lilly will not provide support for or sponsor work authorization or visas for this role, including but not limited to F-1 CPT, F-1 OPT, F-1 STEM OPT, J-1, H-1B, TN, O-1, E-3, H-1B1, or L-1. Additional Skills/Preferences: - 3+ years of experience in pharmaceutical manufacturing preferred. - Other manufacturing experience will be considered. - Strong analytical, writing, and critical thinking skills. - Experience with Kneat Validation software, Veeva Vault, or similar package. - Ability to collaborate with others. Additional Information: - Potential for travel (less than 20% - could be domestic and/or international) to support system, factory acceptance testing, and training. Compensation/Pay: - Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. - The anticipated wage for this position is $66,000 - $171,600. - Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance). Benefits: - Lilly offers a comprehensive benefit program to eligible employees, including eligibility to participate in a company-sponsored 401(k); pension; vacation benefits; eligibility for medical, dental, vision and prescription drug benefits; flexible benefits (e.g., healthcare and/or dependent day care flexible spending accounts); life insurance and death benefits; certain time off and leave of absence benefits; and well-being benefits (e.g., employee assistance program, fitness benefits, and employee clubs and activities). - Lilly reserves the right to amend, modify, or terminate its compensation and benefit programs in its sole discretion and Lilly’s compensation practices and guidelines will apply regarding the details of any promotion or transfer of Lilly employees. We should not include EEO etc. Now produce HTML with sections: About the role, Responsibilities, Key Deliverables (maybe as part of Responsibilities but we can make separate heading if content exists). The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Key Deliverables into Responsibilities as a list under Responsibilities. But we already have a Responsibilities paragraph; we can add a

for Key Deliverables under Responsibilities heading. Similarly, Qualifications: we have Basic Qualifications and Additional Skills/Preferences. Could combine into Qualifications section with two sublists? Or separate Requirements and Qualifications? The instruction list includes Requirements, Qualifications, Skills. We could have Requirements (basic qualifications) and Skills (additional skills/preferences). Or combine. Let's decide: Use sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That covers. Requirements: Basic Qualifications. Skills: Additional Skills/Preferences plus maybe travel info? Travel could be under Additional Information but not a standard heading; we could put under Responsibilities or a separate "Additional Information" but not in list. Since we prefer few sections, maybe include travel under Responsibilities as a note? But it's not a responsibility. Could add a short paragraph under Responsibilities? Might be better to have a separate "Additional Information" heading but not in the allowed list; but we can still use

for any heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could still use other headings but better to stick to those. Travel info could be placed under Responsibilities as a note, but it's not a responsibility. Could add a short paragraph under "Additional Information" but that heading not in list; maybe we can omit travel? But we must preserve ALL substantive information. So we need to include travel info somewhere. Could add a

under Responsibilities or under Benefits? Not appropriate. Could add a separate section "Additional Information" but that's not in the examples; but 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 says use

for section headings (e.g. those). It might be okay to use other headings as long as they are

. Safer to add a section "Additional Information" as

. It's not in the list but still a heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings when applicable, but we can also use other headings if needed? It says "Use

for section head