Garmin Interview Questions

Updated Apr 13, 2015
Updated Apr 13, 2015
181 Interview Reviews

Interview Experience

Interview Experience

52%
28%
19%

Getting an Interview

Getting an Interview

57%
25%
8%

Interview Difficulty

2.8
Average

Interview Difficulty

Hard

Average

Easy

Candidate Interview Reviews

Sort: Popular Date Difficulty
  1.  

    Software Engineer Interview

    No Offer
    Negative Experience
    Easy Interview
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied online. The process took 4+ weeksinterviewed at Garmin.

    Interview

    Applied online had initial phone interview a few days later then never heard from them again. Emailed the recruiter and HR person just to see if position had been filled or if I was not being considered ...not even a courtesy response

    Interview Questions

  2. Helpful (1)  

    Content Specialist Interview

    No Offer
    Negative Experience
    Easy Interview
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied online. The process took 2+ monthsinterviewed at Garmin (Olathe, KS) in June 2014.

    Interview

    I was contacted by HR about three weeks after I applied for the job. We set up the HR interview for the following week. The time came and past. Three hours after it was supposed to happen, I emailed HR to ask if I misunderstood the time of the meeting. They told me the interview did not populate on their calendar and asked to set up another conversation. After, what I thought, a successful basic HR phone interview, I was told I would receive an email the following week informing me wether I made it to the next phase or not. It has been 6 weeks, three email followups and two voicemail inquiries--nothing.

    Interview Questions

    • The interview was just a guided tour of what was on my resume. Nothing outrageous or alarming.   Answer Question
  3.  

    Internet Applications Developer Interview

    Accepted Offer
    Positive Experience
    Average Interview
    Accepted Offer
    Positive Experience
    Average Interview

    Application

    I applied online. The process took 2+ monthsinterviewed at Garmin.

    Interview

    Interview through invitation. One HR round, One technical round. Both has easy standard questions based on what you have on resume. Technical questions on technologies listed. Some open ended discussion on design patterns and framework

    Negotiation

    Not much negotiation

  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5.  

    Embedded Linux Software Engineer Interview

    No Offer
    Neutral Experience
    Average Interview
    No Offer
    Neutral Experience
    Average Interview

    Application

    I applied online. The process took 1+ weekinterviewed at Garmin.

    Interview

    past the HR screening very easily,then scheduled phone interview next week, started at 8 am, which is very early,i wasn't fully awake at that moment,and i didn't perform very well,so i didn't get the job . but i think overal the interview wasn't very hard,a software engineer probably can get all the answers right

    Interview Questions

    • my position was mainly focused on navigation systems, so i did pretty good on them but they also want you to have a very high software skills, at that time i wasn't good enough.   Answer Question
  6. Helpful (1)  

    Software Engineer Intern Interview

    Accepted Offer
    Positive Experience
    Average Interview
    Accepted Offer
    Positive Experience
    Average Interview

    Application

    I applied online. The process took 4 weeksinterviewed at Garmin (Manhattan, KS) in April 2014.

    Interview

    Originally applied through website for the intern position at their Manhattan Kansas office (Kansas State University has a program with Garmin working out of one of KSU's research facilities). I was contacted about a week and a half later requesting times I would be available to speak with a recruiter. The overhead recruiter and I scheduled a time for the following week to conduct a one hour phone interview with a university recruiting person. The recruiter called me about an hour before the interview asking to reschedule to a later date because her daughter got sick and in turn, got her sick too. It was no big deal for me, as I applied for the position almost 5 months before it would have started so there was definitely no rush.

    We rescheduled the interview to be the following Friday (now four weeks since applying). The first interview was purely asking about items that were on my resume, basic questions regarding how much I knew about the structure and content of the Kansas State version of the Software Internship (it is a in-school position, part time, in parallel with schoolwork during the fall and spring). The first interview went very well and taught me a lot about the opportunities I would have as an in school intern. This was definitely a non technical, "tell me about yourself" interview. At the end of the discussion, my recruiter wanted to set me up right away to meet with the head of the Manhattan area coordinator and advisor to conduct a more technical interview. Due to the previous delays for sickness and the rush to get things done before the school year was over, she penciled me in for the following Monday.

    The technical interview seemed almost as informal as the first one for the most part. In my first interview, I was instructed to bring examples of projects I had done myself, or things that had been developed in concordance with a team to highlight my abilities as a programmer and to demonstrate my aptitude for learning code. My technical interviewer seemed surprised that I had brought him projects to demonstrate (an iOS app I had built on my own and a rebuild of the 1980's Pac-Man). He seemed really interested in the projects I had shown, which definitely relaxed the environment of the generally more stressful technical interview.

    Most of my experience in coding has been in high class languages (object oriented) like Java, C#, and Objective-C, so when I was handed code in regular C, I got really worried. Surprisingly, the coding questions he asked seemed almost like a joke. The first was a simple method that added numbers together in two different ways and I was asked to find why the code was outputting the wrong answer. The answers were fairly straight forward (a semicolon after a for loop statement but before the brackets enclosing the contents of the for loop). However, some questions were more difficult. Coming from higher languages to be run on computers, questions about memory conservation and processing speed were not my forte. My interviewer allowed me to ask questions about anything in the code to allow me to work through a solution based on how he was answering my questions. For instance, I wasn't totally familiar with pointers in C, so when it came time to debug code containing pointers, he answered my questions willingly so I could form a conclusion, which was a great way to keep my from getting discouraged for not recognizing an error right away, but also demonstrated my ability to problem solve. He seemed very impressed to see that I was still able to work through to correct answers without a detailed knowledge of the C language directly.

    I received a call about 3 days later from the recruiter from the first interviewer describing my offer, and even offering me a position during the summer before the fall when I was supposed to start, if I was interested. It was a fun process and a little nerve racking at times while I waited for calls back, but the people were awesome and really got me excited about the environment I would be in and the opportunities I would have as a Garmin intern.

    Interview Questions

    • Lots of questions on memory issues in C. Since Garmin works with a lot of small embedded systems, it would be a good idea to have a strong knowledge of lower level languages and tricks to coding in a low memory, low processing power environment.

      For instance, examining a section of code and listing each step you could take to save memory.
       
      1 Answer

    Negotiation

    I had very limited experience in comparison to other applicants so I was initially going to request less than their offer, so there was not much need to negotiate. I would recommend understanding the average pay for the position you are applying to and evaluate your experience compared to who else may be applying. If you probably have way more experience, ask for the high end of the curve.

  7.  

    Software Engineer Interview

    No Offer
    Positive Experience
    Difficult Interview
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied online. The process took 3 weeksinterviewed at Garmin (Chandler, AZ) in April 2014.

    Interview

    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 Questions

    • 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
  8.  

    Design Engineer Intern Interview

    Accepted Offer
    Accepted Offer

    Interview

    Went to job fair, was scheduled for an on-campus interview the next day.

    Interview consisted of technical and behavioral questions.

    Was extended offer within 3 weeks.

    Interview Questions

    • Finding output of a series of logic gates because I had forgotten functionality of some.   Answer Question
  9.  

    Software Engineer Intern Interview

    Declined Offer
    Average Interview
    Declined Offer
    Average Interview

    Application

    I applied through college or university. The process took 4 weeksinterviewed at Garmin.

    Interview

    Phone interview with HR person followed by on site interview with engineers. Mostly C related questions. Also asked several questions about project experience, how I would deal with problems etc. Was impressed with the company but received better offers from other companies. Asked to look at code on a piece of paper and explain what it did.

    Interview Questions

    Reasons for Declining

    Better offer from another company

  10.  

    Software Engineer Interview

    No Offer
    Positive Experience
    Easy Interview
    No Offer
    Positive Experience
    Easy Interview

    Application

    I applied online. The process took 2 weeksinterviewed at Garmin in March 2014.

    Interview

    They sent me an email asking for a transcript and a phone interview with an HR person. The interview was supposed to be between half an hour to an hour.

    Interview Questions

    • There were no technical questions - just standard interview questions   Answer Question
  11. Helpful (1)  

    Marketing Interview

    Accepted Offer
    Negative Experience
    Difficult Interview
    Accepted Offer
    Negative Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took 3+ monthsinterviewed at Garmin.

    Interview

    terribly long process - multiple meetings
    have to give power point presentation on a topic that they choose

    Negotiation

    Study and know the products and company very well.
    be patient.

See What Garmin Employees Are Saying

 Former QA Specialist in San Francisco, CA

Pros: “Great Benefits, one of my best professional experiences overall, great environment for learning even though the company is extremely conservative. Respected work.life balance. Good people…” Full Review

Work at Garmin? Share Your Experiences

Garmin

 
Click to Rate
or

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.