El proceso tomó 1 día. Acudí a una entrevista en Garmin (Olathe, KS) en jun 2010
Entrevista
Initial contact was made by submitting my resume on the Garmin.com careers site. I submitted for two different positions. I was then contacted for a phone interview within a week (they were hiring for several positions at the time). After the phone screening, I was contacted a few days later to request an in person interview. I already had a planned trip to the area, so they did not offer to compensate me for travel for the interview.
My on-site interview began with basic HR and personality questions with the recruiter. They gave me a brief tour of the site and provided lunch. After lunch I was taken to a conference room where I was interviewed by team leads for three different positions. Two of the interviews involved skills tests in programming.
The culture was very relaxed. Most employees were wearing jeans and many even shorts and flip-flops. The people interviewing me took their work very seriously, but were kind and friendly. They gave me the opportunity to ask any questions I had.
Preguntas de entrevista [1]
Pregunta 1
Write an algorithm in any programming language for calculating the amount of change needed. As a follow up, can you modify this algorithm to avoid using the division operator?
You first speak to hr, talk about your resume and experience, normal stuff. The technical started off with basic hr questions and a bit about your resume and experience. Then began to ask basic OOP concepts like Polymorphism, got asked whats difference between pass by reference and pass by value, stuff like that. Then a few coding questions in python.
It was a straight forward interview process, discussed my previous experience, and some general technical questions, and did a programming exercise in a video interview.
A SQL problem and a DSA problem.
Me postulé en línea. Acudí a una entrevista en Garmin (Yarmouth, ME) en ene 2026
Entrevista
HR screening was pretty basic. Technical interview was done remotely. There were two people on the call beside myself. Questions were all technical and didn't bleed into any behavioral questions or assessments.