Getting an Interview
Getting an Interview
Interviews for Top Jobs at Garmin
- Software Engineer (54)
- Software Engineer I (11)
- Software Engineer Intern (10)
- Product Support Specialist (8)
- Design Engineer (6)
- Senior Software Engineer (5)
- Embedded Test Software Engineer (4)
- Software Developer (3)
- Cartography Tech (3)
- Intern (3)
- Software Engineer II (3)
- Operations (3)
- Applications Engineer (2)
- Software Engineering (2)
- Systems Engineer (2)
- Engineering (2)
- Mechanical Engineer (2)
- Internet Applications Developer (2)
- Software Engineering Intern (2)
- Electrical Engineer Intern (1)
- Software Development (1)
- Design Engineer Intern (1)
- Database Administrator (1)
- Production Supervisor (1)
- Business Development Manager (1)
- Systems Administrator (1)
- Aircraft Systems Engineer (1)
- Aviation Systems/Software Engineer (1)
- Design Certification Engineer (1)
- Embedded Linux Software Engineer (1)
Embedded Test Software Engineer Interview
I applied online. The process took a week – interviewed at Garmin in January 2015.
Phone interview with HR rep.
There were a number of by the book generic interview questions; like, 'tell me how solved a difficult problem'. And why I was interested in working for the company.
There was some discussion about my background and resume, but it didn't seem like the interviewer had the background for a technical discussion.
- There were a number of by the book generic interview questions; like, 'tell me how solved a difficult problem'. And why I was interested in working for the company. Answer Question
Other Interview Reviews for Garmin
Embedded Test Software Engineer InterviewNo OfferNeutral ExperienceAverage InterviewNo OfferNeutral ExperienceAverage Interview
I applied online. The process took a day – interviewed at Garmin (Olathe, KS) in February 2011.
I applied for this position in January 2011 through the Garmin website, and initially did not receive a reply. I was however contacted by a Garmin HR recruiter who had noticed my profile on LinkedIn. After a phone interview with HR, I was invited for an on-site interview in February. I was met in the lobby at 8:00 a.m. and escorted a small conference room near the main entrance. From 8 am to noon, I was interviewed hourly by a representative, or pair of representatives, of various teams within the company. I was given two C/C++ tests, which were probably pretty simple for someone who codes daily. However, since coding has not been in my test engineering career path, and my CS degree is rusty, I did not do very well on these. I found it curious that so much emphasis was placed on C/C++ coding for a testing position, but apparently that is the Garmin development model. I was also asked general lifecycle, testing/QA, FAA regulatory and avionics questions, which I thought I answered well. The Garmin recruiter then took me to lunch in the cafeteria, where I had an opportunity to ask questions and recap my qualifications. I left with hopes of receiving an offer, but 2 days later I received a form rejection notice by email. Attempts to follow up with HR and with persons who interviewed me were unsuccessful. To their credit, everyone was professional and pleasant -- but don't expect any debriefing if you don't get an offer.
- Describe a time when you had a technical disagreement you felt strongly about, with another person on your team, and how you handled this. 2 Answers
Embedded Test Software Engineer InterviewAccepted OfferPositive ExperienceEasy InterviewAccepted OfferPositive ExperienceEasy Interview
I applied through college or university. The process took 1+ week – interviewed at Garmin (Olathe, KS) in May 2010.
Met a recruiter at a career fair. This was followed by a behavioral phone interview. I was then flown out to their campus where I had two hiring managers scheduled to interview me, was given a tour of the site, had a face to face interview with the HR rep who I'd phone interviewed with earlier, and was scheduled last minute for a final interview with a manager who the other managers thought would be a better fit for me.
- I was given two sets of C code, which as far as I could tell printed "Garfield" to sysout. Except one of them printed too much of the string, and would have printed the terminating character at the end of the code. I was asked which one would compile, but both would, so I just walked through each function and explained the outcome to the manager. Answer Question
Embedded Test Software Engineer InterviewNo OfferNeutral ExperienceDifficult InterviewNo OfferNeutral ExperienceDifficult Interview
I applied through college or university. The process took a week – interviewed at Garmin (Kansas, AL) in March 2010.
Consisted of initial Phone HR interview followed by on site interview. Three teams interviewed me in the field of OOPS, C++, Embedded C , memory management and DAta STructures and algorithms.
THe interview lasted for 5 hours totally. The interviewers were very friendly and helpful. There was an initial HR interview on site as well. It consisted of usual questions like where do u see urself in 5 years, what is ur expected salary etc.