Real, anonymous reports from people who interviewed for Software Engineer at Eli Lilly, newest first and distilled into what to expect across the loop.
I started with an initial phone screening where I felt it went really well. The feedback I got afterward was encouraging: I was viewed as a strong candidate and was likely to move into the final stages.
My first step was a phone call with a recruiter. It was followed by an automated-style rejection message that basically thanked me for applying and for the time I invested, but it never felt like there was any real courtesy or closure beyond that.
The interview process typically involves multiple rounds, including a recruiter call, technical interviews, and an HR round, with some candidates experiencing a panel format. Candidates noted that the process can feel rushed and may include unexpected changes to the role's technical requirements.
Candidates faced technical interviews that included coding problems, often resembling LeetCode challenges, with a focus on data structures and algorithms. The technical rounds were generally perceived as fair but challenging, requiring both problem-solving skills and the ability to articulate past challenges.
Behavioral interviews were common, with a strong emphasis on using the STAR method to articulate past experiences and values. Interviewers sought to understand candidates' collaboration styles and alignment with the company's culture, often linking questions back to the candidate's resume.
The interview atmosphere varied, with some candidates describing it as relaxed and conversational, while others felt it was more formal and structured. Overall, effective communication and the ability to connect past experiences to the role were crucial for success.
Candidates reported mixed experiences with feedback and follow-up communication, with some feeling ghosted or left without closure after interviews. Timeliness and clarity in communication post-interview were highlighted as areas for improvement.
Candidates wished they had prepared more for the potential shifts in technical requirements and the depth of behavioral questions. Familiarity with the company's values and the ability to articulate personal experiences in a structured manner were seen as beneficial.