Interviewed with 2 groups - Marine and Aviation. First was with one guy, then two. Each went through a lot of questions about my experience/studies, then went onto more technical questions.
They also asked a lot about what I would like to be doing, which looking back I probably was too specific about. They want people to do low-level machine code/C, and I felt more comfortable with high-level Java/C#. I had experience with low-level, just not as much.
What is a pointer? Make a pointer and point it to a specific memory location. (marine)
Problem areas in a piece of code involving threading. He had a piece of paper with a big of code on it, discuss where the problems exist and how to resolve them. Stuff like "critical section". (marine)
Had a piece of paper with some code on it that would print a line, you had to describe the line, then point out problems with the code and how to make it better. There was a error in the for loop where it ended with a semicolon (like for (......); ) that was just to see if you were paying attention. They also wanted you to point out to make it more efficient (replace the calls to power()) and to conserve memory. (aviation)
The following metrics were computed from 2 interview experiences for the Garmin Software Engineer Intern role in Manhattan, Kansas.
Garmin's interview process for their Software Engineer Intern roles in Manhattan, Kansas is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Garmin's Software Engineer Intern interview process in Manhattan, Kansas.