Consumer Data Architect

BioSpace; Indianapolis (IN); On-site; USD 140,000 - 190,000; Full time

Job summary

Lilly in Indianapolis is seeking a senior data architect to own the end-to-end model for patient data, consent, and master data across markets. You will design the architecture that unifies Reltio, Syrenis, Databricks, and AWS components, guiding data residency, consent rules, and API patterns.

You will implement reference pipelines and review engineering work, collaborating with teams to ensure compliant, scalable data solutions for international business units.

Qualifications

• 5+ years in data architecture and data governance.
• Experience designing entity models, match/survivorship rules, and consent architecture.
• Hands-on with data pipelines, APIs, and event-driven patterns.
• Familiarity with privacy regimes and data residency considerations.
• Strong collaboration with engineers and stakeholders in regulated markets.

Responsibilities

• Own data model and matching survivorship rules for IBU markets.
• Design consent and privacy data models across sources.
• Build reference implementations and review engineering work.
• Define API contracts and data movement patterns between systems.
• Evaluate data residency, retention rules, and regulatory requirements.

Skills

Data architecture

Data modeling

API design

Data governance

Privacy compliance

AWS

Databricks

Reltio

Syrenis

Tools

Reltio

Syrenis

Databricks

AWS

Job description

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.

At Lilly, we believe in the talent of our workforce. One of the best ways to utilize and develop that talent is to use our existing workforce to fill new and/or open positions. If you are looking for a new position within Lilly, you can view and apply to open roles posted in the internal job posting system. You must meet the minimum qualifications outlined in the job description and have/obtain work authorization in the country the position is located in order to be considered. When applying internally for a position, your current supervisor will receive notification that you have applied to the position. We encourage employees to discuss the opportunity with their supervisor prior to applying.

Every patient or consumer record that Lilly Direct creates in an International Business Unit (IBU) market has to be matched, merged, governed, and shared under that market's privacy law. You will design the architecture that makes that happen: profile master data on Reltio, consent and preference data on Syrenis, curated data products on Databricks, and the integration layer on AWS that ties them to the Lilly Direct experiences. You will also build the first version of it with your own hands.

This is a hands-on architecture seat. You own the data model, the match and survivorship rules, the consent model, and the event and API patterns that move data between systems. You write the reference implementations and review what engineers build against them. You are also the person who gets asked why the design is the way it is. Each new IBU market tests whether the architecture bends or breaks. Your job is to make sure it bends.

Why You'll Love This Role

• Whole-stack ownership: You own the design from the Reltio entity model through Syrenis consent records to the Databricks tables analysts actually query. Not one layer of it.
• Hard problems: One profile model, one consent model, many legal regimes. You design for data residency, lawful basis, and retention rules that change at every border.
• You still build: Reference pipelines, match rules, API contracts, and proof-of-concept work are yours to write, not just to