Consumer Data Architect
Lilly · United States, Indianapolis IN
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 review.
- Room to grow: The role is built to expand from domain architect for consumer data into a lead architect seat as Lilly Direct scales internationally.
- Purpose: Getting this right means patients can reach Lilly medicines and services safely, and their data is handled the way they were told it would be.
What You'll Be Doing
- Design the Architecture
- Profile MDM: design and maintain the consumer and patient entity model on Reltio, including match rules, survivorship, golden record definition, and reference data, so a single standard holds across IBU markets while allowing for local variation
- Consent: design the consent and preference model on Syrenis, covering consent types, lawful basis, purpose, channel, and retention, and define how consent state is exposed to every system that needs it
- Lakehouse: design the curated profile and consent data products on Databricks, including the medallion layers, data quality checks, and access controls that keep personal data where it is allowed to be
- Integration: define the API and event patterns on AWS that keep Reltio, Syrenis, Databricks, and the Lilly Direct experiences in sync, including which system is the source of truth for each attribute
- Market onboarding: define the repeatable technical pattern for bringing a new IBU market onto the platform, from data residency and pseudonymization through consent configuration and integration
- Standards: write architecture decision records and design standards, then run design reviews against them
- Build and Prove It
- Reference implementations: build the first version of new patterns yourself, including Reltio configuration, Databricks pipelines, and integration code, then hand them to engineers to scale
- Data quality: design and implement the match tuning and quality monitoring that keep the golden record trustworthy as volume grows
- Privacy engineering: implement the technical controls behind Protect Lilly and local privacy requirements, such as pseudonymization and consent-driven access
- Technical direction: set direction for engineers and contractors, review their work, and own the technical quality of what ships
Where This Role Is Headed (2026-2028)
- Evolve: grow from domain architect into a lead architect for consumer data in IBU as more of the execution work is automated and the market footprint expands
- Encode the domain: document profile and consent domain knowledge as data contracts and reusable patterns so other teams, and where it makes sense automated pipelines, can rely on them
- Governance as code: move privacy and consent controls out of manual review and into the platform as enforceable policy
Your Minimum Requirements
- Bachelor's degree in computer science, information technology, management information systems, or a related technical field
- 7+ years in data engineering or data architecture, with demonstrated ownership of a production data platform
What Sets You Apart
- 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 integration patterns such as APIs and event streaming
- Strong SQL and Python; you write production code, not just read it
- Experience applying quality, compliance, and data governance requirements in a regulated environment
- Direct experience with Reltio, including entity modeling, match rule tuning, and the Reltio APIs
- Experience with a consent and preference management platform such as Syrenis, and an 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: 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 how privacy requirements differ
- A track record of writing architecture decisions that engineers followed and leaders understood
- Comfort with ambiguity; the operating model here is still being built
About the Team
This role sits with Consumer Data team supporting Lilly Direct in International Business Units. The team owns the profile and consent data that Lilly Direct experiences depend on in International Business Units markets. As Lilly Direct grows across those markets, the architect in this seat sets the technical patterns that later markets inherit.
Our tech team builds and maintains capabilities using the same technology as the most prominent tech companies in the world, and every solution we deliver serves one purpose: creating medicines that make life better for people around the world. We hire technology professionals from a range of backgrounds so that diverse thinking shapes every product we build, from data-driven drug discovery to connected clinical trials.
Ready to design the data architecture patients trust us with, in markets where the rules are all differen