Taro Logo

Software Engineer Interview Experience - United States

March 1, 2012
Negative ExperienceNo Offer

Process

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 its employees fantastically.

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 git-go 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 they 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 incompetence 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

They had to do a logic puzzle.

It wasn't hard and I think the interviewer though it would take me awhile but I did it in about 3 minutes.

Was this helpful?

Interview Statistics

The following metrics were computed from 134 interview experiences for the Garmin Software Engineer role in United States.

Success Rate

25%
Pass Rate

Garmin's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive60%
Neutral25%
Negative14%

Candidates reported having very good feelings for Garmin's Software Engineer interview process in United States.

Garmin Work Experiences