Questions entretien chez Garmin | Glassdoor.fr

Questions entretien chez Garmin

Entretiens chez Garmin

404 Avis sur les entretiens

Expérience

Expérience
59%
24%
17%

Obtenir un entretien

Obtenir un entretien
63%
22%
6%
6
1
1
1

Difficulté

2,7
Moyenne

Difficulté

Difficile
Moyenne
Facile
  1. Utile (25)  

    Entretien de Configuration Management Engineer

    Candidat à l'entretien anonyme - Olathe, KS (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. J'ai passé un entretien à Garmin (Olathe, KS (États-Unis)) en juin 2017.

    Entretien

    About two weeks after applying online on the Garmin website I was called by a recruiter who set-up a phone interview, which took place two days later. The phone interview was a basic screening call with a member from the HR department. There were questions that you would encounter in a basic interview about strengths, weaknesses, greatest challenge, resolving conflicts, etc. There was some technical questions that mostly focused on explaining basic programming concepts, much like on a test or quiz from college classes. Lastly, I was asked if I had any other offers from other companies.

    About a week after the phone interview I received an email asking to schedule an on-site interview at Garmin in Olathe, Kansas. It was also requested of me to provide my latest performance review documents from my current employer, as well as two references.

    The on-site interview lasted 2.5 hours and consisted of three parts; an HR interview, a technical interview, and a tour. The HR interview was with the same person who performed my phone interview and spent most of the time explaining to me how the benefits work, and asking if I had any questions about the benefits programs. This interview lasted about 30 minutes.

    The technical interview was with three software developers; one was a manager, and the other two worked under the manager. This interview lasted about 1.5 hours and consisted of several questions, the important ones I have listed in the Interview Questions portion. In addition to the questions I listed, there were multiple programming concept questions, similar to the ones asked during the phone interview.

    Something very important to note is that Garmin uses only C++ and not any other languages. When they asked my language set, I listed the 8 to 10 that I use in my current job, and the Garmin developers were not familiar with any of them (they only knew C++). Yet, they were adamant that I prove my proficiency in OOP, specifically C++, and were not concerned with much else. It gave the appearance, to me, that the software development at Garmin might be behind the times, and not moving forward with the industry.

    After the technical interview was a tour of the campus that lasted about 30 minutes, after which I was dismissed. The building is very old with low lighting, and most offices are in the middle of the buildings without windows. There are often 3 to 4 employees sharing a small interior office. It was not very inviting.

    I hope this experiences and observation is helpful to others.

    Questions d'entretien d'embauche


  2. Utile (2)  

    Entretien de Associate Software Engineer

    Candidat à l'entretien anonyme - Chanhassen, MN (États-Unis)
    Aucune offre d'embauche
    Expérience neutre
    Entretien dificile

    Candidature

    J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien à Garmin (Chanhassen, MN (États-Unis)) en décembre 2018.

    Entretien

    Applied online, emailed by recruiter for a phone screen. 35 min call to tell me about Garmin and ask me basic questions.

    50 min technical screen call with Sr. Engineer Manager. Tell me about yourself, what technology are you most familiar with, tell me more about those, tell me about these technologies I see on your resume, technologies used in your projects and at internships, etc. Do you do testing with your code? He asked pretty good technical questions, not too difficult but not easy. Everything went really well and I was excited to hear that they wanted me to come onsite for a 3 hour interview.

    I went onsite in Chanhassen, starting with a 30 min tour/benefits discussion with the office manager. The office looked very new, but the layout is terrible. It was highwall cubicles and dead silent for all their 40 employees. I didn't see a single person. I was surprised that we weren't the only two in the building. She took me to a conference room where I was met by an IT Manager (the one I had a phone screen with), Product Manager, Software Engineer, and an offsite software engineer called in. They started with basic behavioral questions read off of a script: What did you do when somebody didn't do their work? When was a time you couldn't work with somebody? Next, basic tech questions read off of a script: What is HTML? CSS? Do you know what relational databases are? The call-in guy asked: abstract class vs interface in Java? What are your specialties and what do you shine in? Why do you like software development? Why do you want to work at Garmin? In all, it was an hour.

    For the next 1.5 hours, the call-in guy left and a software engineer walked in. This is where things started to get stressful and tiring. First whiteboard question: You are given two version numbers, write methods that check if one is up to date and tell you which one is newer. It seemed simple but I struggled to understand the wording of the question, like what were the inputs and what the purpose was. Did you want me to return a yes/no match, return the version number that is correct, return the incorrect one, or what? I eventually wrote a class that handled version numbers correctly according to their specifications. The next whiteboarding question was: Write methods to calculate the running average, where you are given two inputs, one is an array of ints, the other is the grouping number. This one was really easy and I wrote it fairly quickly with one minor mistake that got fixed in a second. The next whiteboard question was: explain the best algorithm to calculate the highest rolling average from the start of a matrix to the end of the matrix, but rules: can only move right and down and must go from top left corner to bottom right corner. The nature of this question was confusing...write methods? They said no, just explain how you would solve this. I explained some algorithmic ideas, time complexity, the difficulty of the problem, but this wasn't what they were looking for. They said you need to keep track of each average as you go through the matrix. They were only looking for their version of the answer. The last question was to design a recipe website with database, server, frontend, etc. Followed by changing requirements.

    In all, the 2.5 hours of technical questions was way too long and painful. I've never seen a company give a technical interview longer than 1.5 hours and more than 2 whiteboarding questions. It seemed like they are looking for developers that are very technically smart and want to work independently. It's not a very collaborative environment, each team works in big cubicles scattered throughout the office. They do a mixture of agile and waterfall. However, they are very up to date with technology, which impressed me. I didn't feel like a fit for Garmin at this office.

    Questions d'entretien d'embauche

  3.  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme - Olathe, KS (États-Unis)
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien à Garmin (Olathe, KS (États-Unis)) en juillet 2019.

    Entretien

    Phone Call with HR after a week of application. Interview with Team Leads one week later. There would have been on site interview for which they decided not to proceed with me as they were specially looking for someone with experience in Aviation with a CS degree and an experience of 1-3 years.

    Questions d'entretien d'embauche

    • How have you resolved any conflicts at your work? How have you shown leadership at work? Why did you apply for this role? Describe your current role and few questions related to technologies that I said I used.   Répondre à cette question

  4. Utile (3)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche

    Candidature

    J'ai postulé en ligne. J'ai passé un entretien à Garmin.

    Entretien

    The phone interview was mostly technical. The questions that I was asked have already been posted. I will be interviewing in person. I will tell more when I'm completely done with the interview process.

    Questions d'entretien d'embauche


  5. Utile (5)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 2 semaines. J'ai passé un entretien à Garmin.

    Entretien

    Applied through a career fair. I was contacted by a recruiter and completed two initial interviews that were mostly behavioral. (Times you worked on a team? A situation where you didn't know how to solve a problem... how did you solve it? etc) Then I completed a technical interview. The technical interview involved them asking about my experiences, general questions about programming, then going to the board for a few problems.

    Questions d'entretien d'embauche


  6. Utile (6)  

    Entretien de Software Engineer

    Employé anonyme - Kansas City, MO (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Entretien facile

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris +4 semaines. J'ai passé un entretien à Garmin (Kansas City, MO (États-Unis)) en octobre 2014.

    Entretien

    The hiring process was very simple. I met up with a representative at a career fair at my school and then applied online. About a week later, I got an email to set up a phone interview. After that phone interview, I got another email to set up an onsite interview. Unfortunately, I was unable to go to the onsite interview, so it was done over Skype with a panel of people from Garmin. They asked a few behavioral questions and a few technical questions. All said, it was fairly easy and actually quite enjoyable.

    Questions d'entretien d'embauche

    Négociation

    I probably was able to negotiate, but chose not to.


  7. Utile (6)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien à Garmin en octobre 2014.

    Entretien

    I applied online. I heard back within the week and scheduled a 45 minute phone interview. I did not realize how technical phone interview was, and was not prepared for the questions, so they did not continue the process. The interview began with very basic questions, but moved into more complex questions about object oriented programming and C++. If I were to do it over, I would have reviewed different terms related to C++.

    Questions d'entretien d'embauche

    • What is function overloading and overwriting?   1 réponse
  8. Utile (7)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Offres d'embauche déclinées
    Expérience positive
    Difficulté moyenne

    Entretien

    Very smooth process, good HR and kind, knowledgeable senior members that interview. Interview was fairly long but very enjoyable, talked with 2 different people about past experience + what to get out of garmin. A lot of conceptual coding questions, a bit of algorithmic coding questions. Overall very smooth, good experience, great company, great office, great work environment

    Questions d'entretien d'embauche

    • What are the premium differences between java and c and why might you use c over an object oriented language   Répondre à cette question

  9. Utile (3)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience négative

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien à Garmin en mars 2012.

    Entretien

    Got called by a recruiter. Got a phone screen. They flew me to Olathe and I was interviewed by 4 groups. At the time the money the recruiter was quoting me was not what I would have wanted but I needed a job so I went through the process. I'm going to say that one of the best things that ever happened to my career was not getting an offer there. About 3 weeks later I got an offer that was 50% higher than what I would have accepted there. The company that made the offer was not only a much larger company, one that is truly on the leading edge of technology but also a company that treats it's employees fanstastically.

    I answered their technical questions correctly. However, one of the developers who interviewed me was openly hostile to me. He grilled me about polymorphism in C++ and I patiently explained to him about base classes, virtual functions, function signatures, and overriding methods. Even though my explanation was correct he wrote in his comments that I was confused. He took a completely hostile approach from the gitgo with his opening comments. He may or may not work there any longer but he probably does. The amusing part about this is that I have my doubts that they really write a lot of code in C++.

    Also there was a form for reimbursement of incidental expenses. I filed the form but I never received a cent.

    My impression of the software development teams was that they are competent but probably lack decent leadership which means that there are probably not as productive as they could be. Of course some of the groups that I interviewed with have probably cut back (like consumer electronics), not sure about the OEM (car infotainment work), and some are probably doing well like the marine equipment and avionics.

    I think one should expect less pay than industry norms when working there. I would put them in the average category. Some interesting work perhaps but a fair amount of incompetance in managing resources.

    They also asked me to bring a sample of my code. They never asked to look at it in the five hours I was there. Today, git might be something they use now to review your code samples.

    Questions d'entretien d'embauche

    • They had do a logic puzzle. It wasn't hard and I think the interview though it would take me awhile but I did it in about 3 minutes.   Répondre à cette question

  10. Utile (5)  

    Entretien de Software Engineer

    Employé anonyme - Olathe, KS (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris 4 semaines. J'ai passé un entretien à Garmin (Olathe, KS (États-Unis)) en janvier 2013.

    Entretien

    Initial hiring process is started by filling an application through their online system. Even at job fairs at college and such, that's how it works. If your resume attracts attention, and they don't lose you in their paperwork (as happened to me the first time) then you get a phone interview. Having a friend on the inside to speak on your behalf can cut the change of being overlooked, since their HR hiring people are scatterbrained. If you pass the phone interview, then you are invited to Garmin for a tour, and a series of interviews with the departments looking for new hires. They ask you to bring code you have written for them to review, but only 2 out of the 10 or so people I interviewed with actually looked at it. If the general consensus among those you interview with is good, then you are offered a job. You get to choose preferences for department, and as far as I can tell, you get the most preferred department that also wanted you.

    Questions d'entretien d'embauche

    • The in-person interviews at Garmin that follow the phone interview are done by engineers, and the interviews are very technical. Keep in mind that most of Garmin deals mostly in C, and plan for a technical interview accordingly. The hardest questions was probably about the minimum number of bits required to encode information about a street in a GPS system (including speed limit as a multiple of 5, up to a certain limit, and several other bits of info they give you).   1 réponse

    Négociation

    They did not seem open to negotiation, but mine was an interview for an entry-level position, so that may have affected it.


Ne manquez aucun emploi que aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.