Field Clinical Manager
Kuala Lumpur, Malaysia · onsite
Salary not posted
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. CTI MD Tech@Lilly Associate Director, CTI - Development, Clinical Dev Management Level: M1 | Job Family: Information Technology About the Organization: CTI - Development owns the digital capability that patients, sites and study teams meet first: consent and data capture, patient engagement, and the systems that get a study designed, started and set up. The portfolio spans Trial Capabilities, Clinical Experience and patient engagement, and AI & Analytics. The organization is mid-transformation, modernizing platforms and scaling AI and agentic use cases while operating under strict GxP/GCP, data integrity and inspection-readiness requirements. Job Description: The Associate Director, CTI - Development, Clinical Dev, leads a team of engineering, product and delivery professionals and owns delivery, technical direction and capability growth across the Trial Capabilities, Clinical Experience and AI & Analytics domains. The role sits where clinical process meets engineering: close enough to the build to lead a design review and challenge an architecture, fluent enough in trial execution to shape how a study team actually works. It owns the demand relationship with clinical development business owners, directs the partner teams delivering a material share of the work, manages allocated budget and contractor capacity against plan, and is expected to set the agenda for AI and agentic adoption rather than wait for direction on it. Hands-on technical experience is expected and non-negotiable: a practitioner who has built and shipped software and integrations directly, and who stays current enough to pressure-test an architecture or a build versus buy call. The role is scoped at the upper end of the band and is expected to grow into responsibility for broader teams as the portfolio expands. Core Responsibilities : Delivery Ownership Own delivery execution across the portfolio (scope, schedule, quality, dependencies, release readiness, production health) for clinical experience and patient engagement products (eConsent, ePRO/eCOA, patient portals and apps) and study start-up capabilities (site activation, study build, CTMS/eTMF integration). Run the standing delivery cadence of operational reviews, backlog grooming, planning cycles (e.g., PI Planning) and release governance as a single portfolio-wide rhythm, and apply product-management rigor to prioritization, scoring business value, technical debt, effort and risk explicitly and agreeing success measures before work starts. Define and implement the portfolio metrics framework: release predictability, defect escape, production reliability, study build and site activation cycle time, and adoption by sites, study teams and patients. Instrument it where stakeholders can see it, not inside a backlog tool. Identify and solve organizational and operational problems and technical challenges across the portfolio, from resourcing conflicts and scope ambiguity to cross-team dependencies, escalating only what falls outside established guidelines and doing so with a recommendation. Technical Direction & Engineering Standards Set and defend the technical direction of the portfolio; review architecture and design, challenge weak decisions, and own standards for APIs, data contracts, interoperability (CDISC, HL7/FHIR) and reuse across clinical platforms. Own the archit
Tools named in this posting
The people who work here are one introduction away.
We show you who they are and write your first message — the insider list for this posting is filling in now. You have one introduction. The rest follows.
People at Eli Lilly you can reach out to
8 of 74 public LinkedIn profiles found in searches for Eli Lilly list Eli Lilly in their headline — those are the ones you can be confident work there. Pick who to reach out to — we'll draft your message; you make the contact. The rest, when shown, are marked Unverified.
Profiles are public pages as indexed by the search engine — we never log in to LinkedIn or copy private data, and anyone can ask to be removed. Ask to be removed →
Kuala Lumpur, Malaysia · onsite
Salary not posted
United States, Remote · remote
Salary not posted
United States, Remote · remote
Salary not posted