Garmin Interview Questions & Reviews in Arizona
Getting an Interview
- Popular Job Titles:
- Software Engineer (42)
- Software Engineer Intern (10)
- Software Engineer I (7)
- Product Support Specialist (6)
- Senior Software Engineer (4)
- Design Engineer (4)
- Embedded Test Software Engineer (3)
- Cartography Tech (2)
- Internet Applications Developer (2)
- Intern (2)
- Systems Engineer (2)
- Software Engineer II (2)
- Applications Engineer (2)
- Software Engineering Intern (2)
- Mechanical Engineer (2)
- Engineering (2)
- Entry Level Software Engineer (1)
- Communication (1)
- Communications (1)
- Content Specialist (1)
- User Interface Designer (1)
- QA Analyst (1)
- Project Analyst (1)
- Mechanical Engineer I (1)
- Customer Care (1)
- Electrical Engineer Intern (1)
- Production Coordinator (1)
- Electrical Hardware Engineer (1)
- Product Architect (1)
- GIS Technician (1)
Software Engineer Interview (Positive Experience; Difficult Interview)
I applied online and the process took 3 weeks - interviewed at Garmin in April 2014.
Interview Details – Smooth process. I was contacted by HR and the hiring manager. HR call was non technical, and the Hiring manager called me in for a fact to face interview which was very technical
Interview Question – Several questions were somewhat difficult, but not unusually so. The most difficult one involved developing an efficient sort algorithm for a specific data structure. Answer Question
Software Developer Interview (Positive Experience; Average Interview)
I applied through college or university and the process took 2 months - interviewed at Garmin.
Interview Details – Pass the phone screen successfully and got an on site interview notice on the same afternoon.
I did my best and answered all the questions in a good way (At least in my opinion)
It seems that we were all satisfied BUT after more than FOUR weeks, I got the reject email.
Interview Question – Assume you need to optimize a program which has about several Billion lines of code. You can get access to the source code and make modification. So what will to do to make this program run faster? The key thing is it has several Billion lines of code, so it is impossible to analyse the code deeply. View Answers (2)
OEM Software Developer Intern Interview (Positive Experience; Easy Interview)
I applied through an employee referral and the process took a day - interviewed at Garmin in February 2013.
Interview Details – The environment there is pretty nice and pleasant. I was kind of nervous since that was my first interview ever. After talking with the recipient for a while, everything began to go smooth. An OEM manager interviewed me. We firstly talked about project experience on my resume. Then he asked me something about my understanding on OO programming. Then some basic technical questions about string and classes.
Interview Question – Convert a string of number from ASCII to int Answer Question
Senior Software Engineer Interview (Negative Experience; Average Interview)
I applied online and the process took 2 weeks - interviewed at Garmin.
Interview Details – The initial hiring process was very quick and straight to the point. The questions that were asked were behavioral: Why are you looking to change companies? What programming languages do you have experience with?
Interview Question – During the in person interview I was asked a low level programming question. Write a program to parse a 32 bit number and show LSB and MSB? View Answer
Software Engineer Interview (Neutral Experience; Average Interview)
I applied online and the process took 2 weeks - interviewed at Garmin in February 2010.
Interview Details – first round -hr phone interview
second round - tech interview
Interview Question – questions on my projects
questions on multithreading
one puzzle. Answer Question
Interviews for Top Jobs at Garmin