Software Engineer applicants have rated the interview process at Garmin with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 62% positive. To compare, the company-average is 60.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 22 days to get hired, when considering 189 user submitted interviews for this role. To compare, the hiring process at Garmin overall takes an average of 25 days.
Common stages of the interview process at Garmin as a Software Engineer according to 189 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 17%
Skills test: 16%
Group panel interview: 13%
Drug test: 6%
Presentation: 6%
Personality test: 5%
Background check: 5%
IQ intelligence test: 2%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Garmin (Olathe, KS) in Jan 2018
Interview
Applied online, heard back the next day to set up a phone interview. Phone interview consisted mainly of questions about my resume, past experience, side projects, company and team expectations, salary, etc. Heard back a couple days later, and had 3 onsite interviews scheduled. 2 of the interviews were 2 on 1 (one technical with engineers/architects, and the other behavioral with two manager/team leads), and the 3rd was with HR. Was given a tour of the facility as well.
Interview questions [1]
Question 1
What is the difference between a hashmap and a map?
There was an initial phone interview with the recruiter. That was on the informational/behavioral side. Then there was a brief phone interview with the manager of the team. I was asked a variety of technical questions. After that, there was an on-site interview. There I met the manager and the manager's manager. They asked specific technical questions in different areas of programming and then gave me a coding exercise.
Interview questions [1]
Question 1
What's the difference between a monolith and microservices?
You first speak to hr, talk about your resume and experience, normal stuff. The technical started off with basic hr questions and a bit about your resume and experience. Then began to ask basic OOP concepts like Polymorphism, got asked whats difference between pass by reference and pass by value, stuff like that. Then a few coding questions in python.
It was a straight forward interview process, discussed my previous experience, and some general technical questions, and did a programming exercise in a video interview.
A SQL problem and a DSA problem.