Mixed Modality (Oligonucleotide) Scientist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Overview: description of Lilly, mission, etc. Could be "About the role"? Actually "Overview" is generic; we can treat as "About the role" maybe. But we need to decide headings: The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have:
- Overview (company description) -> could be "About the role" or maybe "About Lilly". But they said "About the role" is an example; we can use that heading for overview of role and company.
- Organization And Position Overview: details about Lilly Medicine Foundry, PTE team, role context. Could be part of "About the role" as well.
- Responsibilities: list of duties.
- Basic Requirements: education/experience, work authorization.
- Additional Preferences: preferred qualifications/skills.
- Other Information: location, travel, compensation, benefits.
We need to decide which sections to output.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state compensation: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $67,500 - $173,800 Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance)." So we have Pay info. Also benefits: "In addition, 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)." So we have Benefits.
Schedule? Not explicitly mentioned; maybe full-time implied but not explicit schedule. So we should not create Schedule section.
We need to avoid filler like "commensurate with experience" etc. The compensation is specific range, so we can include Pay.
We need to include Benefits section with list.
We need to include Responsibilities as - .
We need to include Requirements (maybe Basic Requirements) as
- .
We need to include Additional Preferences maybe as Skills or Qualifications. The instruction says we can have Qualifications, Skills sections. We could combine Additional Preferences into Skills or Qualifications. Since they ask to prefer few substantive sections over many thin ones, we might combine Requirements and Additional Preferences into a single "Requirements" or "Qualifications" section? But they are distinct: Basic Requirements (must have) and Additional Preferences (preferred). Could we have two sections: Requirements and Qualifications? Or Requirements and Skills? The instruction list includes Requirements, Qualifications, Skills as possible headings. We could use Requirements for basic requirements, Qualifications for additional preferences, or Skills for additional preferences. Let's decide: Use Requirements for basic requirements (education/experience, work auth). Use Qualifications for additional preferences (skills, knowledge). Or we could combine both into Requirements but that might be thin? Actually we have enough content for both.
We also have Overview/Organization And Position Overview content; we can put under "About the role". That seems appropriate.
We need to remove boilerplate: EEO statements, accommodation request, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove the hashtags #WeAreLilly etc. Also remove the lines about Lilly is an EEO/Affirmative Action Employer etc. Also remove the accommodation request form link. Also remove the employee resource groups list? That's also EEO/boilerplate; likely remove. Also remove the line about Lilly reserves the right to amend compensation etc. That's also boilerplate legal; remove.
We need to preserve all substantive information: company mission, overview, Lilly Medicine Foundry details, PTE team description, responsibilities, basic requirements, additional preferences, location, travel, compensation, benefits.
We must not invent or summarize away detail. So we need to keep specifics like "evaluating and facilitating the transfer of oligonucleotide manufacturing processes", etc.
We need to format as HTML fragment only, no /, no markdown fences.
Let's craft.
Structure:
About the role
... overview of Lilly, mission, Lilly Medicine Foundry, PTE team context ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic requirements ...
Qualifications
- ... additional preferences ...
Pay
... compensation details ...
Benefits
- ... benefit items ...
We need to ensure we don't include Schedule.
Now we need to extract precise content.
Overview: The posting starts: "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. Overview 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."
We can condense but must preserve all substantive information; we cannot invent or summarize away detail. However we can rephrase as prose but must keep all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the details, but we can rephrase? It says do not invent or summarize away detail. Summarizing away detail would be removing details. Rephrasing while preserving details is okay. So we can combine into a paragraph that includes all points.
We need to include: Lilly mission, caring+discovery, patients waiting, over 50k employees, discover/deliver life-changing medicines, strengthen health understanding/management, support communities, hard urgent selfless work, work worth doing, driven by purpose, invite to join. Then overview repeats similar: global healthcare leader, headquartered Indianapolis, employees discover/bring life-changing medicines, improve understanding/management of disease, give back via philanthropy/volunteerism, give best effort, put people first, looking for people determined to make life better.
We can combine.
Then Organization And Position Overview: "Lilly recently announced a $4.5 billion investment to create the Lilly Medicine Foundry, a new center for advanced manufacturing and drug development, Lebanon, Indiana. The first-ever facility of its kind, combining research and manufacturing in a single location, the Medicine Foundry will allow Lilly to further develop innovative solutions to optimize manufacturing processes and increase capacity for clinical trial medicines, while also reducing costs and environmental impact. The Process Translation and Execution (PTE) team translates API/DS process knowledge into clinical supply readiness, oversees technology transfer, implements phase-appropriate control strategies, and ensures right-first-time clinical manufacturing for a variety of modalities, including synthetic molecules, biologics, peptides, oligonucleotide, and bioconjugates (ADC, ARC, etc.) Through cross-functional collaboration, PTE influences process design, revolutionizes clinical manufacturing, builds capabilities in emerging technologies and aligns with corporate and Lilly Research Labs (LRL) goals, drives scientific excellence and innovation to accelerate manufacturing advancements and propels the site toward long-term business success. In the Foundry Construction and Project Delivery/Startup Phase (2025 to 2028), roles will be fluid and dynamic as we build a new organization, design and implement the necessary systems and business processes required to enable operational readiness, support the project delivery, and build the site culture. Success will require significant collaboration, creativity, and resilience as the Lilly Medicine Foundry transitions from design to startup and ultimately to steady-state operations and continuous improvement. This period presents a unique opportunity for learning, growth, and making a lasting impact. We are seeking passionate and agile scientist to join the PTE team and help bring the Lilly Medicine Foundry’s vision to life."
We need to keep all that.
Responsibilities: list of duties. Let's extract each bullet:
- "In this role, the Mixed Modality (Oligonucleotide) Principal Scientist will be responsible with evaluating and facilitating the transfer of oligonucleotide manufacturing processes, under appropriate supervisory guidance, from development laboratories to pilot plant operations (including kilo-scale and isolator production environments). This enables the successful transition to early-phase cGMP manufacturing of grams to kilogram quantities of API required for clinical trial supply."
- "Oversee the successful transfer of new oligonucleotide processes from development to manufacturing; ensure scalability and process fit to plant; apply scientific knowledge to troubleshoot production issues and implement new technologies or procedures."
- "Assess and scale-up synthesis and purification methods from early phase process research and development labs"
- "Familiarity with performing oligonucleotide procedures, such as solid phase synthesis, preparative chromatography, TFF, & lyophilization."
- "Evaluate the safety of the incoming procedures in collaboration with the safety group and process engineering."
- "Analyze analytical data to make fact-based decisions."
- "Efficient with summarizing and presenting chemistry and challenges."
- "Lead familiarization executions to ensure plant readiness of process steps including synthesis, cleavage, purification, TFF, & lyophilization at the Lilly Medicine Foundry."
- "Perform use-tests of key in-process materials and document Definitive Lab Trials of processes to confirm plant readiness."
- "Documentation: Author, review technical documents, including tech transfer plan, standard operating procedures (SOPs), batch records, campaign summary reports, and deviation reports."
- "Process improvement: Apply scientific knowledge to identify areas for improvement and implement new technologies or procedures. Lead process-related investigations, assess deviations, and support CAPAs; collaborate closely with CMC, Product R&D, Manufacturing, and Quality teams; provide on-floor support for critical operations and train/mentor junior scientists and technicians in PTE activities."
We need to keep each as separate - . Some are sentences; we can keep them.
Basic Requirements:
- "B.S. or M.S. in Chemistry, Biochemistry, Chemical/Biochemical Engineering, or a related discipline."
- "B.S. with 10+ years or M.S. with
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Overview: description of Lilly, mission, etc. Could be "About the role"? Actually "Overview" is generic; we can treat as "About the role" maybe. But we need to decide headings: The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have:
- Overview (company description) -> could be "About the role" or maybe "About Lilly". But they said "About the role" is an example; we can use that heading for overview of role and company.
- Organization And Position Overview: details about Lilly Medicine Foundry, PTE team, role context. Could be part of "About the role" as well.
- Responsibilities: list of duties.
- Basic Requirements: education/experience, work authorization.
- Additional Preferences: preferred qualifications/skills.
- Other Information: location, travel, compensation, benefits.
We need to decide which sections to output.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state compensation: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $67,500 - $173,800 Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance)." So we have Pay info. Also benefits: "In addition, 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)." So we have Benefits.
Schedule? Not explicitly mentioned; maybe full-time implied but not explicit schedule. So we should not create Schedule section.
We need to avoid filler like "commensurate with experience" etc. The compensation is specific range, so we can include Pay.
We need to include Benefits section with list.
We need to include Responsibilities as - .
We need to include Requirements (maybe Basic Requirements) as
- .
We need to include Additional Preferences maybe as Skills or Qualifications. The instruction says we can have Qualifications, Skills sections. We could combine Additional Preferences into Skills or Qualifications. Since they ask to prefer few substantive sections over many thin ones, we might combine Requirements and Additional Preferences into a single "Requirements" or "Qualifications" section? But they are distinct: Basic Requirements (must have) and Additional Preferences (preferred). Could we have two sections: Requirements and Qualifications? Or Requirements and Skills? The instruction list includes Requirements, Qualifications, Skills as possible headings. We could use Requirements for basic requirements, Qualifications for additional preferences, or Skills for additional preferences. Let's decide: Use Requirements for basic requirements (education/experience, work auth). Use Qualifications for additional preferences (skills, knowledge). Or we could combine both into Requirements but that might be thin? Actually we have enough content for both.
We also have Overview/Organization And Position Overview content; we can put under "About the role". That seems appropriate.
We need to remove boilerplate: EEO statements, accommodation request, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove the hashtags #WeAreLilly etc. Also remove the lines about Lilly is an EEO/Affirmative Action Employer etc. Also remove the accommodation request form link. Also remove the employee resource groups list? That's also EEO/boilerplate; likely remove. Also remove the line about Lilly reserves the right to amend compensation etc. That's also boilerplate legal; remove.
We need to preserve all substantive information: company mission, overview, Lilly Medicine Foundry details, PTE team description, responsibilities, basic requirements, additional preferences, location, travel, compensation, benefits.
We must not invent or summarize away detail. So we need to keep specifics like "evaluating and facilitating the transfer of oligonucleotide manufacturing processes", etc.
We need to format as HTML fragment only, no /, no markdown fences.
Let's craft.
Structure:
About the role
... overview of Lilly, mission, Lilly Medicine Foundry, PTE team context ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic requirements ...
Qualifications
- ... additional preferences ...
Pay
... compensation details ...
Benefits
- ... benefit items ...
We need to ensure we don't include Schedule.
Now we need to extract precise content.
Overview: The posting starts: "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. Overview 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."
We can condense but must preserve all substantive information; we cannot invent or summarize away detail. However we can rephrase as prose but must keep all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the details, but we can rephrase? It says do not invent or summarize away detail. Summarizing away detail would be removing details. Rephrasing while preserving details is okay. So we can combine into a paragraph that includes all points.
We need to include: Lilly mission, caring+discovery, patients waiting, over 50k employees, discover/deliver life-changing medicines, strengthen health understanding/management, support communities, hard urgent selfless work, work worth doing, driven by purpose, invite to join. Then overview repeats similar: global healthcare leader, headquartered Indianapolis, employees discover/bring life-changing medicines, improve understanding/management of disease, give back via philanthropy/volunteerism, give best effort, put people first, looking for people determined to make life better.
We can combine.
Then Organization And Position Overview: "Lilly recently announced a $4.5 billion investment to create the Lilly Medicine Foundry, a new center for advanced manufacturing and drug development, Lebanon, Indiana. The first-ever facility of its kind, combining research and manufacturing in a single location, the Medicine Foundry will allow Lilly to further develop innovative solutions to optimize manufacturing processes and increase capacity for clinical trial medicines, while also reducing costs and environmental impact. The Process Translation and Execution (PTE) team translates API/DS process knowledge into clinical supply readiness, oversees technology transfer, implements phase-appropriate control strategies, and ensures right-first-time clinical manufacturing for a variety of modalities, including synthetic molecules, biologics, peptides, oligonucleotide, and bioconjugates (ADC, ARC, etc.) Through cross-functional collaboration, PTE influences process design, revolutionizes clinical manufacturing, builds capabilities in emerging technologies and aligns with corporate and Lilly Research Labs (LRL) goals, drives scientific excellence and innovation to accelerate manufacturing advancements and propels the site toward long-term business success. In the Foundry Construction and Project Delivery/Startup Phase (2025 to 2028), roles will be fluid and dynamic as we build a new organization, design and implement the necessary systems and business processes required to enable operational readiness, support the project delivery, and build the site culture. Success will require significant collaboration, creativity, and resilience as the Lilly Medicine Foundry transitions from design to startup and ultimately to steady-state operations and continuous improvement. This period presents a unique opportunity for learning, growth, and making a lasting impact. We are seeking passionate and agile scientist to join the PTE team and help bring the Lilly Medicine Foundry’s vision to life."
We need to keep all that.
Responsibilities: list of duties. Let's extract each bullet:
- "In this role, the Mixed Modality (Oligonucleotide) Principal Scientist will be responsible with evaluating and facilitating the transfer of oligonucleotide manufacturing processes, under appropriate supervisory guidance, from development laboratories to pilot plant operations (including kilo-scale and isolator production environments). This enables the successful transition to early-phase cGMP manufacturing of grams to kilogram quantities of API required for clinical trial supply."
- "Oversee the successful transfer of new oligonucleotide processes from development to manufacturing; ensure scalability and process fit to plant; apply scientific knowledge to troubleshoot production issues and implement new technologies or procedures."
- "Assess and scale-up synthesis and purification methods from early phase process research and development labs"
- "Familiarity with performing oligonucleotide procedures, such as solid phase synthesis, preparative chromatography, TFF, & lyophilization."
- "Evaluate the safety of the incoming procedures in collaboration with the safety group and process engineering."
- "Analyze analytical data to make fact-based decisions."
- "Efficient with summarizing and presenting chemistry and challenges."
- "Lead familiarization executions to ensure plant readiness of process steps including synthesis, cleavage, purification, TFF, & lyophilization at the Lilly Medicine Foundry."
- "Perform use-tests of key in-process materials and document Definitive Lab Trials of processes to confirm plant readiness."
- "Documentation: Author, review technical documents, including tech transfer plan, standard operating procedures (SOPs), batch records, campaign summary reports, and deviation reports."
- "Process improvement: Apply scientific knowledge to identify areas for improvement and implement new technologies or procedures. Lead process-related investigations, assess deviations, and support CAPAs; collaborate closely with CMC, Product R&D, Manufacturing, and Quality teams; provide on-floor support for critical operations and train/mentor junior scientists and technicians in PTE activities."
We need to keep each as separate - . Some are sentences; we can keep them.
Basic Requirements:
- "B.S. or M.S. in Chemistry, Biochemistry, Chemical/Biochemical Engineering, or a related discipline."
- "B.S. with 10+ years or M.S. with
- .
We need to include Additional Preferences maybe as Skills or Qualifications. The instruction says we can have Qualifications, Skills sections. We could combine Additional Preferences into Skills or Qualifications. Since they ask to prefer few substantive sections over many thin ones, we might combine Requirements and Additional Preferences into a single "Requirements" or "Qualifications" section? But they are distinct: Basic Requirements (must have) and Additional Preferences (preferred). Could we have two sections: Requirements and Qualifications? Or Requirements and Skills? The instruction list includes Requirements, Qualifications, Skills as possible headings. We could use Requirements for basic requirements, Qualifications for additional preferences, or Skills for additional preferences. Let's decide: Use Requirements for basic requirements (education/experience, work auth). Use Qualifications for additional preferences (skills, knowledge). Or we could combine both into Requirements but that might be thin? Actually we have enough content for both.
We also have Overview/Organization And Position Overview content; we can put under "About the role". That seems appropriate.
We need to remove boilerplate: EEO statements, accommodation request, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove the hashtags #WeAreLilly etc. Also remove the lines about Lilly is an EEO/Affirmative Action Employer etc. Also remove the accommodation request form link. Also remove the employee resource groups list? That's also EEO/boilerplate; likely remove. Also remove the line about Lilly reserves the right to amend compensation etc. That's also boilerplate legal; remove.
We need to preserve all substantive information: company mission, overview, Lilly Medicine Foundry details, PTE team description, responsibilities, basic requirements, additional preferences, location, travel, compensation, benefits.
We must not invent or summarize away detail. So we need to keep specifics like "evaluating and facilitating the transfer of oligonucleotide manufacturing processes", etc.
We need to format as HTML fragment only, no /, no markdown fences.
Let's craft.
Structure:
About the role
... overview of Lilly, mission, Lilly Medicine Foundry, PTE team context ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic requirements ...
Qualifications
- ... additional preferences ...
Pay
... compensation details ...
Benefits
- ... benefit items ...
- . Some are sentences; we can keep them. Basic Requirements: - "B.S. or M.S. in Chemistry, Biochemistry, Chemical/Biochemical Engineering, or a related discipline." - "B.S. with 10+ years or M.S. with