Garmin gave me something valuable: real cross-disciplinary experience, work that actually matters, and proof that internal mobility is possible.
Writing software for avionics that pilots rely on isn't something most engineers can say they have done, and it has been an incredible opportunity.
There was a recent Garmin Aviation-wide return to office mandate.
I applied for an open position in software engineering after attending a career fair at the university I graduated from. About a month later I was called to set up a phone interview. The process in setting it up was very smooth. The interview was se
I was invited to a phone interview with an HR representative. The interview was average in difficulty and was roughly equally split between behavioral and semi-technical questions about programming. I was caught off guard with the technical questions
The interview was pretty laid back, and it was easy to talk and build rapport with the interviewer. It was mostly questions on OOP (mainly C++). It went pretty well in my estimation -- I got just about every question right and wound up going about 15
I applied for an open position in software engineering after attending a career fair at the university I graduated from. About a month later I was called to set up a phone interview. The process in setting it up was very smooth. The interview was se
I was invited to a phone interview with an HR representative. The interview was average in difficulty and was roughly equally split between behavioral and semi-technical questions about programming. I was caught off guard with the technical questions
The interview was pretty laid back, and it was easy to talk and build rapport with the interviewer. It was mostly questions on OOP (mainly C++). It went pretty well in my estimation -- I got just about every question right and wound up going about 15