Taro Logo

Software Engineer Interview Experience - United States

December 30, 2014
Positive ExperienceGot Offer

Process

Interview was 2 part. The first part was a getting to know you phone interview, that assessed your knowledge of the company, your interests, anything that was on your resume, pretty standard interview. An in person interview was scheduled for a week later. The in person interview was more technically focused. There was a lot of discussion about previous projects, embedded systems, and more about the company itself. A programming assignment was given with 3 problems. They were all written in C. The first problem was a program the draws an exponential function on a Cartesian plane.

There is a semicolon after the for loop that causes the function to run incorrectly. You are asked to explain what the program does, find the problem, then explain what it actually does with the added semicolon. The next two assignments are adding programs. An array is values is to be added. In the first problem the variable "int total" is not instantiated to 0, so it will have a crazy value. In the second instance pointers are used for the program. In the for loop where total would be incremented the pointer "p" was not dereferenced with an "*"

Questions

The question over the pointer is tricky, and many young developers (including myself) have difficulty understanding and using pointers effectively.

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