Real, anonymous reports from people who interviewed for Software Engineer at Garmin, newest first and distilled into what to expect across the loop.
I went through a fairly standard, multi-round software/DSA process with mostly resume-project discussion plus one or more light to moderate technical assessments over a couple of weeks.
I interviewed in formats that felt less like a classic software interview and more like career-fair or on-the-spot technical assessments, with some sessions being quick but concept-heavy.
The initial recruiter screen typically involves a conversation about the candidate's background, motivations for applying to Garmin, and behavioral questions. This step can vary in length but generally lasts between 20 to 60 minutes.
Candidates can expect multiple technical interviews that may include coding tasks, conceptual questions, and discussions about past projects. The difficulty of these interviews can vary, with some candidates noting high-pressure scenarios and a focus on foundational knowledge.
Onsite interviews often involve a panel of interviewers and can include both technical and behavioral assessments. These sessions may be lengthy and cover a range of topics, including practical engineering scenarios.
Candidates report mixed experiences regarding communication throughout the interview process, with some experiencing delays and a lack of clear feedback. This can lead to frustration and uncertainty about their standing in the process.
A strong understanding of technical fundamentals, particularly in areas like data structures, algorithms, and electronics, is crucial. Candidates noted that preparation in these areas significantly impacted their performance.
Candidates often leave interviews without offers, citing various reasons such as misalignment in expectations, high competition, or the need for stronger technical skills. Preparing for a rigorous technical assessment is advised.