There were three stages to the process.
First I spoke with a recruiter for approximately 30 minutes to go over general experience and behavior questions. At the end of the call, the recruiter scheduled a technical coding exercise for later in the week. The coding exercise was one simple question and one question about recursive tree traversal.
A few days after the coding test, the recruiter followed up to schedule a 3-hour interview with the development team and managers. During the first 2 hours I was asked a series of technical questions about data structures, OOP patterns, C#, multithreaded computing, and database design. I then did a CoderPad exercise which consisted of a fairly simple coding problem and debugging existing code.
Describe how you would ensure thread safety in a multithreaded environment.
What are examples of object oriented design patterns? List as many as you can along with example applications.
How does scope work in JavaScript?
What are the differences between web socket and HTTP connections?
Compare and contrast various caching options.
The following metrics were computed from 6 interview experiences for the Garmin Software Engineer II role in United States.
Garmin's interview process for their Software Engineer II roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Garmin's Software Engineer II interview process in United States.