Technical Lead - Software Developer, Data Foundry

Eli Lilly Eli Lilly · Pharma · San Francisco, CA +4

Scientific Software Developer to build software systems for AI-native drug discovery. This role involves creating prototypes, data pipelines, APIs, MLOps infrastructure, agentic platform components, and lab automation integrations. The work spans architecture, methods, and automation, with a focus on a prototype-to-production model, handing off mature solutions to an enterprise scaling team. Responsibilities include building data pipelines for scientific datasets, developing APIs for LIMS and instruments, implementing MLOps for model deployment and observability, developing agent-ready APIs and infrastructure for closed-loop experimentation, integrating lab automation, and building cloud-native components with DevSecOps practices.

What you'd actually do

  1. Design, build, and maintain data processing pipelines for complex scientific datasets (chemical, biological, HTE, and automation-generated data), ensuring FAIR compliance and machine-actionability.
  2. Develop RESTful APIs and microservices providing unified programmatic access to LIMS, ELNs, instruments, data warehouses (Postgres, Redshift, Snowflake), and analytical databases.
  3. Build ML deployment pipelines—experiment tracking, model versioning (MLflow, W&B), containerized serving, monitoring, and automated retraining.
  4. Develop agent-ready APIs with structured error handling, audit trails, and monitoring supporting agent autonomy and human oversight.
  5. Build integrations connecting lab automation equipment, scheduling systems, and instrument data streams to Data Foundry’s infrastructure with proper metadata and traceability.

Skills

Required

  • Python
  • SQL
  • RESTful APIs
  • data pipelines
  • microservices
  • scientific software development
  • experimental data types
  • scientific workflows

Nice to have

  • Java
  • C#
  • Go
  • TypeScript
  • Rust
  • pharmaceutical or biotech research industry experience
  • discovery workflows
  • MLOps tooling
  • MLflow
  • W&B
  • model registries
  • model serving
  • monitoring/drift detection
  • cloud platforms
  • AWS
  • Azure
  • GCP
  • containerization
  • Docker
  • Kubernetes
  • Git
  • AI agent infrastructure
  • MCP framework

What the JD emphasized

  • AI-native drug discovery
  • agentic platform components
  • agent-ready APIs
  • closed-loop experimentation

Other signals

  • AI-native drug discovery
  • agentic platform components
  • ML deployment pipelines
  • operationalize models as production APIs
  • agent-ready APIs
  • closed-loop experimentation