
One candidate for an Eli Lilly DevOps platform role reports a fast, unannounced technical call covering networking, Python, shell scripting, Kubernetes StatefulSets and a live AWS three-tier design, and received no offer.
$108K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The interview account we have for Eli Lilly's DevOps platform track describes a technical screen with rapid-fire questions and almost no warm-up. The candidate says nobody introduced themselves, no one explained the rounds or the role, and the first question came as soon as they joined the call.
About 45 minutes went to one interviewer. A second person then joined without an introduction and moved to Kubernetes. The candidate reports questions on on-premises and cloud networking, a Python coding problem, basic shell scripting, and the definition of a Kubernetes StatefulSet. The largest task was designing a three-tier web application on AWS, talked through live.
The candidate found the content reasonable and described the Python question as the easiest part. The difficulty came from the pace: there were no pauses, no hints and no clarification when they stalled. They received no offer and could not say why.
If you are preparing, rehearse short spoken answers to fundamentals. Practice basic shell commands aloud and explain stateful versus stateless workloads in Kubernetes. Be ready to compare networking on-premises and in the cloud. Sketch a standard AWS three-tier layout and narrate it in a few minutes. This is one candidate's account, so other interviewers or rounds may be run differently.
Synthesized from 1 candidate report 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.
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
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| String Palindromes | |
| Your Strengths and Weaknesses | |
| Hurdles In Data Projects | |
| Digit Accumulator | |
| Greatest Common Denominator | |
| Concentric Circles | |
| LRU Cache 1 | |
| Sum to Zero | |
| Flatten JSON | |
| Processing Large CSV | |
| Valid Anagram | |
| K Nearest Entries | |
| Second Highest Sales | |
| DDoS Attack Response | |
| Search Linked List | |
| Why Do You Want to Work With Us | |
| Common Prefix | |
| Moving Window | |
| Three Indexes Adding Zero | |
| Pipeline Transformation Failures | |
| Possible Triangles | |
| Marketing Workflow Optimization | |
| Concurrent LLM Serving | |
| Distributed Authentication Model | |
| Azure Kubernetes Infrastructure | |
| Maximal Substring | |
| Scalable Data Pipelines | |
| Stakeholder Communication | |
| SFTP Pipeline |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports joining the call with no introductions, no overview of the rounds and no explanation of the role. Questions began immediately and ran for about 45 minutes with one interviewer. Expect to move quickly into technical material rather than a conversational opening.
Topics reportedly included networking both on-premises and in the cloud, a Python coding question and shell scripting. The candidate found the content basic, with Python the easiest part, but the pace made the shell questions harder. Practice giving concise spoken answers without long pauses.
A second interviewer reportedly joined without introduction and took over with Kubernetes questions. One question the candidate recalls was what a StatefulSet is. The candidate says interviewers did not clarify questions or give hints when they stalled, so be ready to define core concepts clearly and quickly.
The largest request was to design a three-tier web application on AWS and walk through it live while organizing thoughts. The candidate reports no offer and does not know the reason. This is one account, so the number of rounds and timing beyond this call are not established.