The company offers a decent health care package, but you'll need it to deal with the stress of working at Garmin.
There are some fairly competent co-workers, but their best efforts are squandered by management.
Upper management lacks strategic vision. Case in point is the Garmin smartphone debacle. Management can't decide what product strategy to pursue, so they demand that engineering work on all possible combinations, and then they complain when it doesn't come together on time.
Middle management is populated by people who have no clue how to manage people, much less show any leadership traits. Work at Garmin degenerates into a rat race of competing with your fellow co-worker for projects, appreciation, promotions, and ultimately your salary. Favoritism is rampant, and promotions and project assignments are mostly based on the buddy system.
Young recruits straight from college are favored over experienced professionals, as they don't seem to realize how horrible things have become at Garmin.
Hang on to all the cash in the bank, and keep on slapping yourselves on the back for earning it all in the last decade.
In the future, I doubt your company will earn you more than the interest on the cash.
First got a phone interview regarding behavioral skills. After that it was a technical interview. Asked about C++ and different concepts known in C++ programming. Also asked about personal coding projects and experience.
I met a recruiter at a university recruiting fair. The next day I had an interview. The interview was mostly technical. It was a question about strings and arrays. The interviewers were nice.
Applied online. Received a phone call from recruiter a few weeks later for a phone screen. Phone screen was just going over the resume and a couple of behavioral questions focused on technical aptitude. After that I had a technical phone interview wi
First got a phone interview regarding behavioral skills. After that it was a technical interview. Asked about C++ and different concepts known in C++ programming. Also asked about personal coding projects and experience.
I met a recruiter at a university recruiting fair. The next day I had an interview. The interview was mostly technical. It was a question about strings and arrays. The interviewers were nice.
Applied online. Received a phone call from recruiter a few weeks later for a phone screen. Phone screen was just going over the resume and a couple of behavioral questions focused on technical aptitude. After that I had a technical phone interview wi