Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

6 stories

Likes earn the author +10 XP for the first 3 likes each day

GarminSoftware EngineerIntern
Apr 2026

In-Person Technical Test With Eight Mixed Problems

First round was a technical test that was held at the company. There were simple questions about OOP and DSA, logic and SQL. There were 8 problems. 2 of them asked me to describe the OOP principles and to identify which ones are relevant for a described situation. Then there were 2 coding problems about a square matrix (n x n). It was a circular matrix that started the indexing from the middle of…

Onsite0
GarminSoftware Engineer
Reported Mar 2026

Garmin Software Engineer interview with DSA and project discussions

I went through a fairly standard, multi-round software and DSA process over a couple of weeks. It included mostly resume and project discussion, along with one or more light to moderate technical assessments. The recruiter screen lasted about 20 to 45 minutes and focused on my background, why I wanted to work at Garmin, and a few behavioral prompts. In the remote technical interview, which took p…

Technical Screen0
GarminSoftware Engineer
Reported Mar 2026

Garmin Software Engineer interview: career-fair concepts and electronics checks

I interviewed in formats that felt less like a traditional software interview and more like career-fair conversations or quick technical assessments. Some sessions were brief but focused heavily on concepts. At the career fair, I had a general conversation about my resume followed by technical concept questions. The interviewer asked whether I knew specific ideas. After that initial discussion, I…

Onsite0
GarminSoftware Engineer
Reported Aug 2025

Garmin Software Engineer interview with two engineers coding

I interviewed for a Software Engineer role at Garmin through a fairly lightweight, two-step process that took place over a few weeks. The recruiter phone screen covered my background and included behavioral questions about how I work. In the technical interview, two engineers watched me code a solution to a problem and discuss my approach. The process felt straightforward, but I didn't advance be…

RejectedHR Screen0
GarminSoftware Engineer
Reported Jul 2025

Garmin Software Engineer interview with two-hour theory-heavy onsite

I interviewed for a mid-level .NET and Software Engineer type role at Garmin, and I felt the process didn't match my seniority level or the time I put into it. The in-person technical interview lasted two hours and focused heavily on theory rather than problem solving. I missed a few questions but otherwise did okay. Afterward, I was told they really wanted someone senior for a mid-level position…

RejectedOnsite0
GarminSoftware Engineer
Reported Jun 2025

Garmin Software Engineer interview focused on HR, compensation, and fit

I interviewed for a Software Engineer role at Garmin. The first round was mostly about HR, compensation, and fit, and it ended quickly. The HR phone screen covered my resume and behavioral questions, with a strong focus on motivation and discipline. There was no offer. In one case, the salary discussion didn’t align, and in the other, I didn’t continue after the early HR fit check. Location: Olat…

HR Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP