yoinka

Veeva Technical Lead - CTI MD Tech (GRA/GSC)

Eli Lilly

Bangalore, Karnātaka, IndiaFull TimeSenior
Sign in to applyVerified 48m ago
Location
Bangalore, Karnātaka, India
Employment
Full Time
Work model
On-Site
Level
Senior
Posted
18h ago

Skills

Python

About this role

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.  Veeva Technical Lead - CTI MD Tech (GRA/GSC)   Global Regulatory Affairs ( GRA)  ·   Global Scientific Communications ( GSC)  ·   CTI-MD   Tech@Lilly   Veeva Vault is the platform underpinning Lilly's regulatory data — every live gateway submission depends on its object model and configuration being understood and   maintained   without disruption. The Veeva Technical Lead (R4), GRA/GSC owns the architecture and technical integrity of Veeva Vault today, while shaping the strategic vision for how regulatory systems integrations around Veeva Vault will evolve as health authority data exchange requirements advance over time. This role connects the two: safeguarding current submissions while architecting the integration patterns, schemas, and access models that position Veeva Vault's existing data as the foundation for whatever regulatory systems architecture comes next — engineered from what already exists, not invented in parallel.   Path/Level: R4 (Veeva Technical Lead)   Key Responsibilities   RIM Data Model Ownership —   serve as the definitive technical authority on Veeva Vault RIM's object model, metadata, and VQL-based data access, ensuring changes preserve the integrity of live submissions.   Submission Continuity & Risk Management —   support and troubleshoot the technical foundation behind active gateway submissions, ensuring configuration and data changes never jeopardize a live submission.   Future-State Architecture Vision —   define and own the strategic vision for how regulatory systems integrations around Veeva Vault should evolve, positioning RIM's existing data model as the foundation that future architecture is engineered from.   Strategic Roadmap & Portfolio Alignment —   connect Veeva Vault architecture decisions to the broader GRA/GSC technology strategy, ensuring investments in the platform align with enterprise AI, agentic, and digital workforce priorities.   Veeva AI & Platform Evolution Tracking —   stay ahead of Veeva's own AI and automation roadmap (Vault AI and related Veeva AI capabilities), assessing how these evolving native capabilities should shape Lilly's build-vs-adopt architecture decisions.   Integration Pattern & Schema Design —   architect schemas and integration contracts, including API- and MCP-based access patterns, that allow RIM data to be consumed reliably by downstream systems and emerging platforms.   Custom Integration Development —   build and maintain custom integrations using the Veeva Vault SDK/APIs and Python-based automation to extend Vault capabilities and streamline manual processes.   Reusable Architecture Patterns —   establish reusable architecture and design patterns around Veeva Vault that accelerate delivery, reduce duplication, and improve long-term sustainability across the RIM ecosystem.   Configuration Governance —   establish and enforce configuration management, validation, and change-control discipline appropriate to a GxP-regulated Vault environment.   Data Pipeline & Systems Reliability —   build and support robust data pipelines and system integrations around Veeva platforms, ensuring reliable, well-governed data flow between Vault and downstream systems.   Cross-Functional Partnership —   partner with regulatory operations, data architecture, and