Garmin·Software Engineer

Garmin Software Engineer interview experience

No offer

Medium

Negative

Olathe, KSPosted Mar 2026 · Candidate report, summarized by Dataford

My process got delayed significantly because I had to reschedule multiple times, and the interview ended up taking about two months longer than I first expected.

When I finally sat down, it began by walking through my resume in detail, and they asked quite a few questions that went beyond surface-level buzzwords. I had to talk about concurrency concepts like threads and semaphores, and I also got specific questions about clubs and projects.

About halfway through, the interview shifted into short Leetcode-easy style questions. It wasn’t one long coding ordeal so much as a sequence of smaller tasks that tested whether my fundamentals and coding habits matched what they were looking for. The interviewer also left time for me to ask questions at the

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Garmin Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Garmin interview guidesEvery role we cover at this company