Senior Process Engineer, Lilly Medicine Foundry

We need to output HTML fragment with sections: About the role? The posting includes "About The Lilly Medicine Foundry" and "Organizational Overview". Also "Responsibilities", "Basic Requirements", "Additional Preferences", "Other Information", "Pay" (compensation), "Benefits". No schedule. We must not repeat job title. Use

for section headings. Use

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

  for prose. Remove boilerplate: EEO, legal, accommodation request, etc. Also remove duplicated lines. Keep substantive info. We need to preserve all substantive information: description of Lilly, the Medicine Foundry investment, facility overview, role description, responsibilities list, basic requirements, additional preferences, other information (location), compensation range, bonus, benefits list. We must not include sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: About the role? Could combine "About The Lilly Medicine Foundry" and "Organizational Overview" into an "About the role" or maybe separate sections: "About the Lilly Medicine Foundry" and "Organizational Overview". The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings but we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those standard headings, but we can also include other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we can use those headings as appropriate. Probably we should map content to those headings: About the role (description of company and role), Responsibilities, Requirements (basic requirements), Qualifications (maybe additional preferences?), Skills (maybe additional preferences?), Benefits, Pay. Schedule not present, so omit. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation and benefits, so include Pay and Benefits. We need to avoid repeating job title. Not needed. We need to remove boilerplate: EEO statements, accommodation request, etc. Also remove duplicated lines (like repeated EEO). Also remove navigation/cookie/legal etc. Not present. We need to preserve all substantive info: The description about Lilly, the Medicine Foundry investment, facility overview, role description, responsibilities list (bullet points), basic requirements, additional preferences, other information (location), compensation range, bonus, benefits list. We need to format responsibilities as

  • . Same for basic requirements? It's a list of items: BS or MS..., Minimum of 2 years..., Qualified applicants must be authorized... That's a list; we can use
    • . Additional preferences also list. Other Information: location info (Initial location at Parkwood West, Indianapolis. Permanent location at the new Lilly Medicines Foundry in Lebanon, Indiana.) That's prose; can be

      . Pay: 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). That's prose; maybe we can put in

      . Benefits: list of benefits: 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). Also note Lilly reserves right to amend... That's maybe boilerplate but it's part of benefits description; we can include but maybe it's considered legal? It's about benefits modification; could be considered boilerplate but it's part of benefits description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits modification statement might be considered legal boilerplate; but it's part of benefits description. Safer to include? Might be considered legal. I'd include the benefits list but omit the sentence about Lilly reserves right to amend... as it's legal. Keep the list. Now structure:

      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 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.

      Then maybe a subsection about Lilly Medicine Foundry? Could incorporate into About the role. But we could also add a separate

      About the Lilly Medicine Foundry

      but the instruction says use those example headings; but not strictly forbidden to add others? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those. So we incorporate the Medicine Foundry info into About the role paragraph. Add Organizational Overview also into About the role. Thus About the role paragraph will be long but okay. Then Responsibilities:

      Responsibilities

      • Provides technical assessment and support for production operations in the areas of developing and sustaining process knowledge, process and equipment support, process optimization, equipment capability and asset management, and engineering business systems.
      • Serves as a process engineer supporting small molecule drug substance active pharmaceutical ingredient (API) manufacturing.
      • Perform impact and risk assessments for unit operations
      • Learn the lab and plant design for the reactors including automation recipes and procedures.
      • Ensure that people and their environment are safe and that company policies concerning safety are followed.
      • Ensure processing equipment remains compliant with internal Quality System requirements, applicable engineering standards, and cGMP requirements.
      • Assesses rig fit by receiving the technical data package for new processes and performing modeling, simulations and/or experimental work as required to ensure heat and mass transfer are acceptable when scaling to the plant.
      • Active engagement and communication with: HSE, Quality Assurance, Tech Services, Development, Operations, FUME/C&Q, Automation, Maintenance, Environmental Monitoring, and Manufacturing.
      • Author, review, or approve high-quality technical reports and regulatory submissions dealing with the work performed by the department. Ensure that records and technical notebooks are adequately maintained.
      • Demonstrate engagement and employ a quality approach in all endeavors by proactively identifying quality issues and communicating appropriately.
      • Develop or review plans and timetables for project work.
      Note: Some items are sentences; we need to keep them as is. Then Requirements (Basic Requirements):

      Requirements

      • BS or MS in Chemical Engineering or related engineering degree
      • Minimum of 2 years of experience within a pharmaceutical, biotech, chemical manufacturing, or CMO environment or other relevant batch manufacturing process.
      • 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.
      But the last item includes a sentence about visa sponsorship; that's substantive. Keep. Then Qualifications? Could be Additional Preferences. We could map Additional Preferences to Qualifications or Skills. The instruction includes Qualifications and Skills as possible headings. We could put Additional Preferences under Qualifications. Or we could split: Qualifications for educational/experience, Skills for technical/soft skills. Let's decide: Use Qualifications for the "Additional Preferences" list (deep technical interest, familiarity with unit operations, ability to work in team, experience with software, analytical skills, communication skills, ability to work on own initiative, understanding of process control systems, creativity, guidance/mentoring, flexibility). Use Skills maybe for software experience? But we can combine. Better: Use Qualifications for the list of additional preferences (since they are qualifications/preferences). Use Skills for the software experience and analytical/problem-solving skills etc. But the instruction says we can use those headings; we need to include a section only when posting has real specific content. We have content for both. Let's create:

      Qualifications

      • Supported manufacturing and/or development activities for active pharmaceutical ingredients, intermediates, or other chemicals
      • Deep technical interest and understanding in the field of Chemical Engineering
      • Familiarity with unit operations including but not limited to chemical reactions, distillation, phase separation, filtration, drying
      • Ability to work well in a team environment incorporating a variety of functional relationships and desire to be point of accountability
      • Ability to work on own initiative and as part of a Process Team consisting of a diverse group of management, production, science and engineering professionals
      • Understanding of process control systems
      • Creativity to identify improvement opportunities and the tenacity/initiative to see them implemented
      • Guidance/mentoring of others through processes
      • Flexibility to meet business needs
      Then Skills:

      Skills

      • Experience with any of the following software packages: DeltaV, Dynochem, Aspen, and/or electronic lab notebooks
      • Strong analytical and problem-solving skills
      • Strong oral and written communication skills for a diverse audience, e.g., both operations staff and management
      Now Other Information: location. Could be under About the role or a separate section like "Location". Not in the list but we could put under About the role as a paragraph. However we already have a big About the role paragraph; we could add location info there. But maybe better to add a separate

      Other Information

      but not in the list; risk of being considered filler. 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. ...)". It implies we should use those headings for sections; but we could still use other headings if needed? Safer to incorporate location into About the role or maybe under "About the role" we already have a paragraph; we can add another paragraph after that about location. Thus About the role will have multiple paragraphs: first the generic Lilly description