Eli Lilly Software Engineer interview typically runs 3 rounds: recruiter screen, hiring manager call, and onsite interviews. The process usually takes about 1 month and is conversational, with a mix of behavioral and light technical discussion.
$131K
Avg. Base Comp
$187K
Avg. Total Comp
4-5
Typical Rounds
3-6 weeks
Process Length
Across the experiences we’ve seen, Eli Lilly seems to care less about dazzling candidates with hard technical puzzles and more about whether you can explain real work clearly, connect it to business impact, and show you’d be a steady teammate. Multiple candidates said the conversations were surprisingly project-driven and conversational, with interviewers digging into what they actually built, what they contributed, and why they wanted to join Lilly specifically. That pattern matters: the strongest signal here is not just technical competence, but whether your background feels authentic and relevant to a healthcare environment where context and communication matter.
We also see a consistent emphasis on structured storytelling. Candidates repeatedly mentioned STAR-style questions, conflict scenarios, and prompts about working with others or impressing teammates, which tells us Lilly is screening for emotional intelligence as much as technical readiness. Even when coding came up, it was described as approachable—general LeetCode-style problems, DSA basics like binary search or dynamic programming, and a few role-specific checks—often with interviewers willing to help if someone got stuck. The non-obvious make-or-break factor here is composure: candidates who could think out loud, stay concise, and tie their answers back to concrete projects tended to come away feeling the process was smooth and fair.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Eli Lilly And Company process.
What stood out to me most was how much of the process was conversational rather than intensely technical. I first heard back about a month after applying online, and the hiring manager set up a short 20-minute call where I had to walk through a problem I had solved in a previous role using a PPT. That round felt more like explaining my thinking and impact than being grilled on code, especially since the job description had already been removed from the website by then, which made the whole thing feel a little less straightforward.
After that, the process moved on to campus recruiting. I spoke with two recruiters about my background, why I wanted to work at Eli Lilly, and what I hoped to do there. The on-site portion was two separate one-on-one interviews, about an hour each, with two employees. Those were mostly behavioral and company-focused, with a lot of questions about my experience and fit. I also remember being asked about a conflict with a coworker, and there were several questions about the company itself. One interviewer also pushed into technical territory and asked about OOP concepts, collections, and a framework, but it still felt pretty light compared with a traditional software engineering loop.
The overall vibe was friendly and smooth, and I even got to interact with employees at lunch, which made the process feel welcoming. At the same time, I felt like they asked a lot of questions overall, so it helped to be ready to talk clearly about past projects and why Eli Lilly specifically. I ended up declining the offer, but the experience itself was positive and not especially stressful.
Prep tip from this candidate
Be ready to present a past project clearly in a short slide-based explanation, and practice answering company-fit questions like why Eli Lilly and what you want to do there. It also helps to review basic OOP, collections, and a framework you’ve used, since those came up alongside the behavioral rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Eli Lilly And Company
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Loan Model | |
| String Palindromes | |
| Client Solution Pushback | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Weighted Keys | |
| Hurdles In Data Projects | |
| Cumulative Distribution | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| P-value to a Layman | |
| Last Transaction | |
| Detecting ECG Tachycardia Runs | |
| Always Excited Users | |
| Brain Cancer Treatment Outcomes | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| Cumulative Reset | |
| Rider Discount | |
| Digit Accumulator | |
| Time Difference | |
| Search Linked List | |
| Common Prefix | |
| Greatest Common Denominator | |
| Count Transactions | |
| Subscription Retention |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically first hear back after applying online or meeting the team at a career fair. In some cases, campus recruiting or recruiter outreach moves the process forward quickly, and the first conversation is used to confirm background, interest in Eli Lilly, and general fit.
This stage is conversational and focused on your background, motivation for joining Eli Lilly, and what you hope to do in the role. Candidates reported speaking with recruiters about their experience and why they wanted to work at the company, with an emphasis on communication rather than deep technical screening.
A hiring manager may ask you to walk through a past problem or project you solved, sometimes using a presentation. The discussion centers on your thinking, impact, and the technical details of your most relevant work rather than a formal coding assessment.
This round blends STAR-format behavioral questions with technical problem solving. Candidates were asked about teamwork, conflict, and company fit, along with coding questions and DSA topics such as binary search, dynamic programming, and an egg-drop style problem; interviewers were generally willing to help and keep the conversation moving.
The final stage consisted of two one-on-one interviews with employees from different parts of the site. These were mostly behavioral and company-focused, with questions about projects, collaboration, and Eli Lilly specifically, though one interviewer also asked light technical questions around OOP concepts, collections, and a framework. Some candidates also interacted with employees at lunch, which contributed to the friendly, welcoming feel.
After the final rounds, candidates received an offer decision. The overall process was described as smooth and professional, with outcomes communicated after the interview loop concluded.
