Advisor - Scientific Machine Learning & Agentic Workflows Engineer

$130K - $211K Indianapolis, IN, US Mid Level AI/ML Engineer

Interested in this AI/ML Engineer role at Eli Lilly?

Apply Now →

Skills & Technologies

JaxPythonPytorchRag

About This Role

AI job market dashboard showing open roles by category

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.

Organization Overview:

At Eli Lilly and Company, we unite caring with discovery to make life better for people around the world. Lilly is a leader in global healthcare and has been discovering and developing medicines that help improve lives for more than 140 years. Our 50,000 employees around the world work as a team to bring breakthrough medicines to patients who need them. We are looking for motivated, highly skilled scientists and engineers to help us continue to bring breakthrough medicines to patients.

Delivery, Devices, and Connected Solutions (DDCS) sits within Lilly's Product Research & Development organization. We are a diverse team of scientists and engineers responsible for discovering, designing, and developing patient-centric drug delivery solutions across a broad range of modalities — from injection devices to novel routes of administration and nanomedicines. DDCS drives the drug delivery innovation agenda across early and late development to meet the needs of an expanding portfolio that spans small molecules, biologics, and nucleic acid therapeutics.

DDCS is organized around a matrix model with strong disciplinary and functional horizontals supporting innovation and commercialization verticals. Our vision is to get our medicines to more patients faster by accelerating reach and scale, guided by three strategic pillars: Delivery Systems, Robust & Sustainable, and Patient Experience + Outcomes.

Computational Modeling & Simulation (M&S) is a disciplinary horizontal within DDCS that builds and applies predictive models spanning molecular to system scales. M&S outputs inform device architecture, formulation and delivery-system design, and development strategy — reducing empirical iteration, quantifying risk, and building mechanistic understanding of how our delivery systems perform in real use. The scope of the capability spans continuum-scale multiphysics (CFD and FEA), molecular and mesoscale simulation, and scientific machine learning, working closely with Formulation Sciences, Device Engineering, Analytical Sciences, Manufacturing, Quality, and Regulatory.

Position Overview:

This role builds hybrid physics-and-data models — and the agentic software layer that puts them in the hands of working scientists. It has two connected halves. The first is scientific machine learning: physics-informed networks, operator learning, multi-fidelity surrogates, Bayesian calibration, and gray-box system identification that accelerate or extend physics-based simulation. The second is AI engineering: agentic workflows that plan, set up, execute, and post-process modeling and simulation tasks by calling real solvers and real data, so that a scientist can move from question to credible answer without hand-assembling every step.

The role sits within the Computational Modeling & Simulation team in DDCS and works across the programs that the team supports. This is not a standalone research role: the models and tools are built with and for the drug product, device, and process development functions across Product Research & Development that use them. You will independently design, implement, validate, and support the workflows you build, working closely with the DDCS AI Application Development and Data Sciences functions on architecture, platform choices, and compliance.

Key Responsibilities:

Scientific Machine Learning Development

  • Independently design, train, and validate SciML models — physics-informed neural networks, operator-learning architectures (e.g., DeepONet, Fourier neural operators), and Gaussian-process or multifidelity surrogates — against high-fidelity simulation and experimental data.
  • Apply Bayesian calibration and uncertainty quantification to deliver predictions with a defensible confidence statement rather than a point estimate.
  • Apply gray-box identification and symbolic-regression methods to infer unknown parameters or missing mechanisms from sparse experimental data.

Agentic Modeling Workflow Engineering

  • Design and build LLM-based agentic workflows that plan, set up, execute, monitor, and post-process modeling tasks by calling real tools — solvers (e.g., Abaqus, COMSOL, Ansys, OpenFOAM, LAMMPS, GROMACS), meshing and geometry utilities, HPC schedulers, and internal data services.
  • Implement the tool interfaces, APIs, and retrieval layers that connect agents to DDCS model libraries, simulation archives, and structured data sources.
  • Define and enforce human-in-the-loop checkpoints at the points where a modeling decision requires expert judgment rather than automation.
  • Package workflows so that a scientist who is not a software developer can use them reliably and unaided.

Credibility, Traceability, and Guardrails

  • Ensure every agent-executed run emits a complete provenance record: inputs, geometry and discretization, solver and library versions, convergence evidence, random seeds, and the human approvals applied.
  • Design for deterministic replay — any result that informs a decision must be reproducible from its recorded provenance, within a documented tolerance.
  • Build evaluation harnesses — benchmark problems with known solutions, regression tests, and reliability metrics — that quantify how often a workflow produces the right answer.
  • Define credibility practice: defining defensible practice and credibility frameworks for hybrid physics-ML models in the spirit of ASME V&V 40 and the FDA's 2023 guidance on assessing computational model credibility.

Software Engineering, Deployment, and Cross-Functional Delivery

  • Write maintainable, tested code; treat version control, code review, CI/CD, and containerization as defaults.
  • Deploy and operate workflows on HPCs and approved cloud environments, instrumented for observability, latency, and cost.
  • Deploy in partnership with the functions that will use the output — device engineering, drug product and process development, analytical sciences, manufacturing, quality, and regulatory — so that tools fit existing development workflows, data sources, and decision timelines rather than requiring users to change how they work.
  • Apply business judgment when setting priorities: understand the portfolio, program milestones, and decision gates the modeling supports, and direct effort toward the questions where a faster or better answer changes a development decision.
  • Make and defend practical trade-offs on build versus buy, model fidelity versus cost and turnaround time, and automation versus expert review, keeping total cost of ownership and the needs of downstream users in view.
  • Apply responsible AI, security, and data-handling controls across the workflow lifecycle, in partnership with IT, Quality, and Information Security.

Partnership, Enablement, and Communication

  • Work as an embedded member of cross-functional development teams, engaging directly with drug product, device, and process development colleagues to frame the problem and agree what a useful answer looks like before choosing a method.
  • Partner with continuum and molecular modeling scientists to identify where surrogates and agentic workflows create real value — and where a direct simulation or an experiment remains the better answer.
  • Collaborate with the DDCS Digital Transformation team on architecture, reusable patterns, and platform choices; contribute to GxP and 21 CFR Part 11 considerations where workflows touch regulated systems.
  • Train and support users, and report adoption quantitatively.

Basic Qualifications:

  • PhD in applied mathematics, computer science, machine learning, computational mechanics or physics, chemical, mechanical, or biomedical engineering, or a related field
  • Doctoral research centered on scientific machine learning — physics-informed learning, operator learning, surrogate modeling, or hybrid mechanistic-ML methods.
  • Demonstrated experience developing SciML models and validating them against physics-based simulation or experimental data.
  • Strong Python software engineering, including PyTorch or JAX, and Git-based collaborative development.
  • Hands-on experience building LLM-enabled workflows including multi-step agent orchestration and either tool and function calling or retrieval-augmented generation (RAG).
  • Experience running computational work on HPC clusters or cloud infrastructure.
  • Peer-reviewed publications or open-source contributions in scientific machine learning.

Additional Preferences:

  • A working practice grounded in evaluation, provenance, and reproducibility, and the ability to explain to both technical and business audiences what these methods can and cannot do.
  • Neural operator methods, multifidelity modeling, Bayesian UQ and calibration, active learning, or Bayesian optimization applied to engineering or biomedical problems.
  • Gray-box identification, symbolic regression, or discovery of pharmacokinetic, pharmacodynamic, or transport models from sparse data.
  • Experience with agent frameworks and tool-interoperability standards (e.g., tool-calling APIs, graph-based agent orchestration, Model Context Protocol) and with production deployment practice (containers, CI/CD, observability).
  • Familiarity with commercial or open-source simulation solvers and their scripting interfaces and input/output formats.
  • Awareness of model credibility practice for regulated products (ASME V&V 40; FDA credibility assessment guidance) and of GxP and 21 CFR Part 11 requirements for computerized systems.
  • Front-end or full-stack experience sufficient to build usable interfaces for scientific tools.
  • Domain exposure to drug delivery, medical devices, combination products, or biomedical transport problems.

Other Information:

  • Travel: 0–10%
  • Location: Indianapolis, IN; Lilly Technology Center – North (LTC-N)

Lilly is dedicated to helping individuals with disabilities to actively engage in the workforce, ensuring equal opportunities when vying for positions. If you require accommodation to submit a resume for a position at Lilly, please complete the accommodation request form (https://careers.lilly.com/us/en/workplace-accommodation) for further assistance. Please note this is for individuals to request an accommodation as part of the application process and any other correspondence will not receive a response.

Lilly is proud to be an EEO Employer and does not discriminate on the basis of age, race, color, religion, gender identity, sex, gender expression, sexual orientation, genetic information, ancestry, national origin, protected veteran status, disability, or any other legally protected status.

Our employee resource groups (ERGs) offer strong support networks for their members and are open to all employees. Our current groups include: Africa, Middle East, Central Asia (AMECA), Black Employees at Lilly (BE@Lilly), Chinese Culture Network (CCN), EnAble, Evolve, Lilly Indian Network (LIN), Organization of Latinx at Lilly (OLA), Pride (LGBTQ+ Allies), Veterans Leadership Network (VLN) and Women’s Initiative for Leading at Lilly (WILL).

Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is

$130,500 - $211,200

Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance). 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).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.

#WeAreLilly

Salary Context

This $130K-$211K range is below the median for AI/ML Engineer roles in our dataset (median: $175K across 1356 roles with salary data).

View full AI/ML Engineer salary data →

Role Details

Company Eli Lilly
Title Advisor - Scientific Machine Learning & Agentic Workflows Engineer
Location Indianapolis, IN, US
Category AI/ML Engineer
Experience Mid Level
Salary $130K - $211K
Remote No

About This Role

AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.

Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.

Across the 8,943 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Eli Lilly, this role fits into their broader AI and engineering organization.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

What the Work Looks Like

A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

Skills Required

Jax (1% of roles) Python (16% of roles) Pytorch (5% of roles) Rag (6% of roles)

Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.

Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.

Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

Compensation Benchmarks

AI/ML Engineer roles pay a median of $212,000 based on 11,866 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200. This role's midpoint ($170K) sits 19% below the category median. Disclosed range: $130K to $211K.

Across all AI roles, the market median is $213,380. Top-quartile compensation starts at $264,148. The 90th percentile reaches $319,310. For comparison, the highest-paying categories include AI Safety ($253,100) and Research Engineer ($252,000). By seniority level: Entry: $110,408; Mid: $193,200; Senior: $228,700; Director: $272,250; VP: $235,000.

Eli Lilly AI Hiring

Eli Lilly has 5 open AI roles right now. They're hiring across AI/ML Engineer. Based in Indianapolis, IN, US. Compensation range: $143K - $246K.

Location Context

Across all AI roles, 6% (521 positions) offer remote work, while 8,351 require on-site attendance. Top AI hiring metros: New York (2,878 roles, $221,000 median); San Francisco (2,416 roles, $263,811 median); Los Angeles (1,340 roles, $210,000 median).

Career Path

Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.

From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.

The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.

What to Expect in Interviews

Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.

When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

AI Hiring Overview

The AI job market has 8,943 open positions tracked in our dataset. By seniority: 175 entry-level, 4,132 mid-level, 3,268 senior, and 1,368 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (521 positions). The remaining 8,351 roles require on-site or hybrid attendance.

The market median for AI roles is $213,380. Top-quartile compensation starts at $264,148. The 90th percentile reaches $319,310. Highest-paying categories: AI Safety ($253,100 median, 57 roles); Research Engineer ($252,000 median, 419 roles); AI Engineering Manager ($251,622 median, 51 roles).

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

The AI Job Market Today

The AI job market spans 8,943 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (6,739), AI Product Manager (403), AI Software Engineer (402). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.

The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (175) are outnumbered by mid-level (4,132) and senior (3,268) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,368 positions, representing the bottleneck between technical execution and organizational strategy.

Remote work availability sits at 6% of all AI roles (521 positions), with 8,351 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.

AI compensation is structured in clear tiers. The market median sits at $213,380. Top-quartile roles start at $264,148, and the 90th percentile reaches $319,310. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.

Category matters for compensation. AI Safety roles lead at $253,100 median, while Prompt Engineer roles sit at $141,440. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.

The most in-demand skills across all AI postings: Python (1,422 postings), Aws (808 postings), Azure (638 postings), Rag (555 postings), Gcp (457 postings), Pytorch (433 postings), Claude (341 postings), Kubernetes (337 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.

Frequently Asked Questions

Based on 11,866 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $212,000. Actual compensation varies by seniority, location, and company stage.
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
About 6% of the 8,943 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
Eli Lilly is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from AI/ML Engineer positions include ML Architect, AI Engineering Manager, Principal ML Engineer. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.