Associate Director, Data Engineering

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.  About the Organization The Clinical & Non-Clinical Data Organization at Eli Lilly and Company is responsible for the design, build, and operation of enterprise data platforms that power drug discovery, clinical development, and regulatory submissions. Data Hub is building a robust Data Strategy to make Lilly's Clinical and Non-Clinical data AI-ready and audit-ready, delivering scalable, governed, and reusable data products that accelerate how medicines reach patients. Our data engineering organization sits at the intersection of science, technology, and patient impact — connecting Clinical and Non-Clinical data across the full chain, from ingestion to consumption.

The Associate Director, Data Engineering is a senior product-ownership, platform-management, and people-leadership role that owns the quarterly roadmap and backlog for one or more data engineering delivery teams, the health and cost of the underlying data platform, and the data strategy and AI roadmap for a Databricks-oriented practice. Hands-on data engineering experience is expected and non-negotiable — this is a practitioner who has built pipelines, models, and platforms directly, and stays technically current enough to review architecture and pressure-test build-vs-buy calls first-hand. This role defines and implements the data KPI and metrics framework the organization runs on, enables AI adoption across data teams beyond its own delivery pods, and owns the data products built on the Databricks lakehouse. A further mandate is accelerating data onboarding and access, so new sources and consumers move from request to trusted, governed availability in days, not months. As an M1-level people leader, this individual manages a team of data engineers and/or product owners and partners closely with architecture, platform, and senior business leaders on scope and multi-year direction.

Strategic Leadership & Data/AI Roadmap (Databricks-Oriented) Proactively surface strategic topics to senior leadership based on first-hand data engineering experience — platform constraints, technical debt, build-vs-buy trade-offs, and emerging AI/engineering tooling — rather than waiting to be asked. Define the data strategy and AI roadmap for a Databricks-oriented data engineering team, identifying the data products, lakehouse assets, and AI/ML capabilities that matter most over the next 12–24 months. Own the product roadmap for Databricks-native capabilities — lakehouse architecture, Unity Catalog governance, Delta Live Tables pipelines, MLflow/feature-store patterns— with hands-on proof points, not vendor-slide recommendations. Product Ownership & Roadmap Leadership Own sprint- and quarter-level backlog prioritization applying product-management rigor (RICE/WSJF-style scoring, stakeholder discovery, success metrics) to balance business value, technical debt, effort, and risk. Bring forward strategic topics — informed by direct engineering experience — that shape the roadmap rather than simply respond to it (e.g., platform limitations, emerging AI capabilities). Facilitate PI Planning, backlog grooming, and sprint reviews; serve as the voice of both the internal customer and the platform in delivery ceremonies. Platform Management Own the data platform as a product — define its roadmap,