Started with basic behavioral phone interview with a recruiter. After that was a technical interview with a hiring manager where you go over basics of OS and coding (pointers + double pointers). Looked at a snippet of code and logic'd through it fixing some syntax errors. After that was a technical interview with the team lead I would be working for. This was much more in depth of OS and coding where you work write your own. As well as more behavioral questions and why you want to work for Garmin. Straight after that was a quick rundown with the recruiter about benefits and what to follow up with if you get an offer.
Explain pointers and when you could use a double pointer.
Follow exponential drawing code. (Error with semicolon after the for loop.) And reason through it.
What is a mutex and semaphore? How are they used?
Basic buffer operations in OS. How to handle deadlock and context switch.
Coding question on the use of pointers and passing by reference (* and &) using a class. Class c1, *c2, &c3.
Coding question about parsing through Cstring in C. Turn a string into an integer and output it based on test cases.
The following metrics were computed from 2 interview experiences for the Garmin Embedded Software Engineer role in Chandler, Arizona.
Garmin's interview process for their Embedded Software Engineer roles in Chandler, Arizona is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Garmin's Embedded Software Engineer interview process in Chandler, Arizona.