Real, anonymous reports from people who interviewed for Software Engineer at John Deere, newest first and distilled into what to expect across the loop.
After applying, I moved through a recruiter touchpoint pretty quickly, and not long after I ended up in a panel-style interview with engineers. The overall vibe felt efficient and organized: the questions were fairly general but spread across a few different areas, and I had to talk through how I approach work and decision-making across the software side.
I started with a standard phone screen, then the recruiter sent my profile forward to the hiring manager. After that, I moved into a one-on-one discussion, and then I ended up with what felt like a longer set of panel interviews—two separate one-hour sessions, with two interviewers in each.
The interview process typically begins with a phone screen followed by multiple rounds of interviews, often including both technical and behavioral assessments. Candidates noted that the process can stretch over several weeks, with some experiencing a more intense sequence of interviews close together.
Candidates faced a variety of technical assessments, including coding challenges and discussions about data structures, algorithms, and specific technologies like React. The technical interviews often required clear communication of thought processes and problem-solving approaches rather than just coding proficiency.
Behavioral interviews were a significant component, with a strong emphasis on the STAR method to structure responses. Candidates were expected to provide specific examples of past experiences, focusing on situational fit and competencies relevant to the role.
Many candidates experienced panel-style interviews where multiple interviewers asked questions in a structured format. While this setup aimed to evaluate depth and collaboration, some candidates found the repetition of questions across panels to be frustrating.
Communication skills were heavily assessed throughout the process, with interviewers looking for clarity and the ability to articulate thoughts effectively. Candidates noted that collaborative coding sessions were part of the technical rounds, emphasizing teamwork.
The overall difficulty of the interview process was described as moderate to high, with candidates reflecting on the need for specificity in their examples. Many expressed a desire for clearer feedback after the interviews, as several left without offers and felt uncertain about their performance.