Garmin logo

Garmin Embedded Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 28 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
71.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Garmin.

Showing 3 of 28
Garmin logo
Garmin

Embedded Software Engineer

Engineering · nearly a year ago

Intern Average Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The recruiter was pleasant and inquired about my past projects, emphasizing the importance of knowing my own work well. They showed significant interest in my career aspirations within Garmin, asking multiple times about the specific field I aimed to pursue, even though I had already applied for a particular role.

Confirmed questions1 question
  • Can you tell me about a significant mistake you've made and how you resolved it?
Garmin logo
Garmin

Embedded Software Engineer

Engineering · a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

The process started with a 30-minute phone call with HR. Following that, there was a technical interview which included a 30-minute segment on coding concepts like what an OS, semaphore are, and the difference between compile and execution. The second part of this technical interview was a 30-minute coding challenge where I had to write code to solve problems such as adding digits in a float.

Confirmed questions6 questions
  • Can you tell me why you're interested in working at Garmin?
  • How do you think you stand out from other applicants?
  • What is an operating system?
Garmin logo
Garmin

Embedded Software Engineer

Engineering

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Recruiter call
Interview formats
Behavioral Technical Coding

First, there was a basic behavioral phone chat with a recruiter. Then, a technical interview with the hiring manager covering OS basics and coding concepts like pointers and double pointers. We reviewed a code snippet and I had to logic through it and fix some syntax errors. Next, another technical interview with the team lead, focusing more deeply on OS and coding, including writing some code. There were also more behavioral questions, like why I'm interested in Garmin. Right after that, the recruiter gave a quick overview of benefits and next steps if an offer were to come.

Confirmed questions8 questions
  • Can you explain what pointers are and in which scenarios a double pointer would be beneficial?
  • Please provide an explanation using exponential drawing code.
  • I found an error with a semicolon after the for loop in this code snippet. Can you fix it and explain your reasoning?

Garmin Embedded Engineer Interview Questions

Quoted word for word from Garmin interview reports.

Given an integer, count the number of set bits (binary ones) in it.

Read reports

Implement a function to convert a string to an integer, handling various test cases.

Read reports

What is the largest difference obtainable between any two elements within a given array?

Read report

What's the difference between stack and heap memory in C?

Read report

How can you modify an integer by inserting a digit to create the largest possible number?

Read report

Could you write some code to figure out how to sum the digits in a floating-point number?

Read report

Formats, difficulty and experience

Across all 28 Garmin interview reports.

Interview formats

Behavioral 42.4%
Technical 31.8%
Coding 22.7%
System Design 1.5%
Presentation 1.5%

Interview difficulty

Easy 17.9%
Average 78.6%
Difficult 3.6%

Candidate experience

Positive 71.4%
Neutral 21.4%
Negative 7.1%