Consumer Data Architect

Eli Lilly and Company•Us, IN

About The Position

The Consumer Data Architect designs and builds the consumer and patient data architecture supporting Lilly Direct in International Business Unit (IBU) markets. The role owns the profile master data model on Reltio, consent and preference data on Syrenis, curated data products on Databricks, and the AWS integration layer connecting these systems to Lilly Direct experiences. The architect defines match and survivorship rules, consent models, and event and API patterns, and creates reference implementations for engineering teams to scale. The role ensures that the architecture supports market-specific privacy laws, data residency, lawful basis, retention, pseudonymization, and consent-driven access requirements. It establishes repeatable technical patterns for onboarding new markets, documents architecture decisions and standards, and reviews engineering work. The position is hands-on, including building configurations, pipelines, and integration code, and setting technical direction for engineers and contractors. Over time, the role is expected to grow toward a lead architect position as Lilly Direct expands internationally, with an emphasis on reusable data contracts and enforceable privacy and consent policies.

Requirements

  • Bachelor's degree in computer science, information technology, management information systems, or a related technical field.
  • At least 7 years of experience in data engineering or data architecture, with demonstrated ownership of a production data platform.

Nice To Haves

  • Hands-on experience designing and configuring a master data management platform, including data modeling, match and merge rules, and survivorship.
  • Hands-on experience with Databricks or a comparable lakehouse platform, including pipeline development and data quality implementation.
  • Experience building on AWS, including API and event-streaming integration patterns.
  • Strong SQL and Python skills, with experience writing production code.
  • Experience applying quality, compliance, and data governance requirements in a regulated environment.
  • Direct experience with Reltio, including entity modeling, match-rule tuning, and Reltio APIs.
  • Experience with a consent and preference management platform such as Syrenis, and understanding of how consent state should flow to downstream systems.
  • Experience with event-streaming platforms such as Kafka for near-real-time data synchronization.
  • Experience with privacy engineering, including pseudonymization, data residency, retention enforcement, and consent-driven access control.
  • Experience with consumer or patient data in more than one country and a working understanding of differing privacy requirements.
  • A track record of writing architecture decisions that engineers follow and leaders understand.
  • Comfort with ambiguity in an operating model that is still being built.

Responsibilities

  • Design and maintain the consumer and patient entity model on Reltio, including match rules, survivorship, golden record definitions, and reference data.
  • Design the consent and preference model on Syrenis, covering consent types, lawful basis, purpose, channel, and retention, and define how consent state is shared with other systems.
  • Design curated profile and consent data products on Databricks, including medallion layers, data quality checks, and access controls.
  • Define API and event patterns on AWS that synchronize Reltio, Syrenis, Databricks, and Lilly Direct experiences, including source-of-truth ownership for attributes.
  • Define repeatable technical patterns for onboarding IBU markets, including data residency, pseudonymization, consent configuration, and integration.
  • Write architecture decision records and design standards, and conduct design reviews against them.
  • Build reference implementations of new patterns, including Reltio configuration, Databricks pipelines, and integration code.
  • Design and implement match tuning and data quality monitoring to maintain trustworthy golden records as data volumes grow.
  • Implement technical controls for Protect Lilly and local privacy requirements, including pseudonymization and consent-driven access.
  • Set technical direction for engineers and contractors, review their work, and own the technical quality of delivered solutions.
  • Develop reusable data contracts and patterns for profile and consent domain knowledge as the international market footprint expands.
  • Advance governance as code by moving privacy and consent controls into enforceable platform policies.

Benefits

  • Company bonus, depending in part on company and individual performance.
  • Company-sponsored 401(k).
  • Pension.
  • Vacation benefits.
  • Medical, dental, vision, and prescription drug benefits.
  • Flexible benefits, including healthcare and/or dependent day care flexible spending accounts.
  • Life insurance and death benefits.
  • Time off and leave of absence benefits.
  • Well-being benefits, including an employee assistance program, fitness benefits, and employee clubs and activities.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service