Green Card Data Architect Jobs
Data Architect roles qualify for EB-2 sponsorship when the position requires an advanced degree in computer science, information systems, or a related field, and EB-3 for roles meeting the skilled-worker standard. Employers must complete PERM labor certification before filing your I-140 petition, making early employer alignment on sponsorship timelines essential.
Find Green Card Data Architect JobsOverview
Showing 5 of 853+ Data Architect jobs
See all 853+ Data Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Data Architect roles.
Get Access To All JobsINTRODUCTION
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.
ROLE AND RESPONSIBILITIES
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
MINIMUM QUALIFICATIONS
- 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
PREFERRED QUALIFICATIONS
- 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 different? We'd love to hear from you.
Lilly is dedicated to helping individuals with disabilities to actively engage in the workforce, ensuring equal opportunities when vying for positions. If you require accommodation to submit a resume for a position at Lilly, please complete the accommodation request form for further assistance. Please note this is for individuals to request an accommodation as part of the application process and any other correspondence will not receive a response.
Lilly is proud to be an EEO Employer and does not discriminate on the basis of age, race, color, religion, gender identity, sex, gender expression, sexual orientation, genetic information, ancestry, national origin, protected veteran status, disability, or any other legally protected status.
Our employee resource groups (ERGs) offer strong support networks for their members and are open to all employees. Our current groups include: Africa, Middle East, Central Asia (AMECA), Black Employees at Lilly (BE@Lilly), Chinese Culture Network (CCN), EnAble, Evolve, Lilly Indian Network (LIN), Organization of Latinx at Lilly (OLA), Pride (LGBTQ+ Allies), Veterans Leadership Network (VLN) and Women’s Initiative for Leading at Lilly (WILL).
COMPENSATION
- Salary Range: $129,000 - $231,000
Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance). In addition, Lilly offers a comprehensive benefit program to eligible employees, including eligibility to participate in a company-sponsored 401(k); pension; vacation benefits; eligibility for medical, dental, vision and prescription drug benefits; flexible benefits (e.g., healthcare and/or dependent day care flexible spending accounts); life insurance and death benefits; certain time off and leave of absence benefits; and well-being benefits (e.g., employee assistance program, fitness benefits, and employee clubs and activities). Lilly reserves the right to amend, modify, or terminate its compensation and benefit programs in its sole discretion and Lilly’s compensation practices and guidelines will apply regarding the details of any promotion or transfer of Lilly employees.
INTRODUCTION
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.
ROLE AND RESPONSIBILITIES
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
MINIMUM QUALIFICATIONS
- 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
PREFERRED QUALIFICATIONS
- 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 different? We'd love to hear from you.
Lilly is dedicated to helping individuals with disabilities to actively engage in the workforce, ensuring equal opportunities when vying for positions. If you require accommodation to submit a resume for a position at Lilly, please complete the accommodation request form for further assistance. Please note this is for individuals to request an accommodation as part of the application process and any other correspondence will not receive a response.
Lilly is proud to be an EEO Employer and does not discriminate on the basis of age, race, color, religion, gender identity, sex, gender expression, sexual orientation, genetic information, ancestry, national origin, protected veteran status, disability, or any other legally protected status.
Our employee resource groups (ERGs) offer strong support networks for their members and are open to all employees. Our current groups include: Africa, Middle East, Central Asia (AMECA), Black Employees at Lilly (BE@Lilly), Chinese Culture Network (CCN), EnAble, Evolve, Lilly Indian Network (LIN), Organization of Latinx at Lilly (OLA), Pride (LGBTQ+ Allies), Veterans Leadership Network (VLN) and Women’s Initiative for Leading at Lilly (WILL).
COMPENSATION
- Salary Range: $129,000 - $231,000
Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual performance). In addition, Lilly offers a comprehensive benefit program to eligible employees, including eligibility to participate in a company-sponsored 401(k); pension; vacation benefits; eligibility for medical, dental, vision and prescription drug benefits; flexible benefits (e.g., healthcare and/or dependent day care flexible spending accounts); life insurance and death benefits; certain time off and leave of absence benefits; and well-being benefits (e.g., employee assistance program, fitness benefits, and employee clubs and activities). Lilly reserves the right to amend, modify, or terminate its compensation and benefit programs in its sole discretion and Lilly’s compensation practices and guidelines will apply regarding the details of any promotion or transfer of Lilly employees.
See all 853+ Green Card Data Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Green Card Data Architect Jobs.
Get Access To All JobsTips for Finding Green Card Sponsorship in Data Architect
Document your data architecture credentials precisely
Your PERM application lists your actual education and experience, not a generalized profile. Gather transcripts, degree certificates, and project documentation that map directly to the SOC code your employer will use for the role.
Target employers with active PERM filing history
Companies that have filed PERM applications for data architecture roles before understand the DOL process and are less likely to stall on recruitment steps. Use OFLC Wage Search to verify prevailing wage levels for your target metro areas before negotiating offers.
Clarify whether your role qualifies for EB-2
EB-2 requires the position itself to normally require an advanced degree, not just that you hold one. If your employer writes the job description around a bachelor's degree, you'll be routed into EB-3 even with a master's, so get the degree requirement in writing before PERM is filed.
Search for green card sponsoring roles on Migrate Mate
Filter by EB-2 or EB-3 sponsorship status to find Data Architect openings at employers already willing to sponsor. Migrate Mate surfaces roles specifically tagged for employment-based green card sponsorship, saving you from applying to positions where sponsorship is unavailable.
Anticipate the supervised recruitment timeline
DOL requires employers to run a specific recruitment process before certifying your PERM application. This typically takes four to six months before I-140 filing even begins. Factor this into any timeline discussion with your employer so both parties plan around realistic green card milestones.
Align your O*NET occupation code with your actual duties
PERM filings for Data Architect roles must use an accurate SOC occupation code from O*NET. If your duties span data engineering and architecture, a mismatch between your job description and the selected code can trigger an audit or denial at the DOL level.
Green Card Data Architect: Frequently Asked Questions
Does a Data Architect role qualify for EB-2 or EB-3 green card sponsorship?
Data Architect positions can qualify for either category depending on how the employer defines the role. EB-2 applies when the job normally requires an advanced degree in a field like computer science or information systems. If the posted requirement is a bachelor's degree with several years of experience, EB-3 as a skilled worker is the more common route. Your employer's job description controls the classification, not your credentials alone.
How does green card sponsorship differ from H-1B for a Data Architect?
H-1B visa is a temporary status requiring renewal and tied to an annual lottery. Employment-based green card sponsorship through PERM and I-140 is a path to permanent residency with no annual cap concerns at the EB-3 level for most countries outside India and China. The tradeoff is timeline: PERM and I-140 filing alone can take nine to eighteen months before you even reach adjustment of status, compared to a faster H-1B approval.
What is the PERM process, and what does the employer need to do?
PERM is the DOL labor certification process that requires your employer to advertise the Data Architect role through DOL-mandated recruitment steps, demonstrate no qualified U.S. workers were available, and then file an application with DOL. Only after DOL certifies the application can your employer file an I-140 immigrant petition with USCIS. The entire PERM stage typically runs four to eight months.
How can I find Data Architect jobs that include green card sponsorship?
Most job postings don't explicitly state whether a company will sponsor a green card, which makes it difficult to identify willing employers. Migrate Mate is built specifically for this purpose, letting you filter Data Architect roles by EB-2 or EB-3 sponsorship availability so you only apply to positions where the employer has confirmed sponsorship intent.
Can I change employers after my PERM is filed but before I get my green card?
Portability rules under AC21 allow you to change to a same or similar occupation after your I-140 is approved and your adjustment of status application has been pending for 180 days or more. For Data Architect roles, the key is whether the new position falls under the same or a substantially similar SOC code. Changing employers before these milestones risks losing your priority date and starting PERM over.