A lot of smart guys work here, and the atmosphere is generally jovial.
Olathe is a very nice area, and there's no commute to speak of.
Compensation is good for comfortable, middle-class living, and the benefits package is great and takes care of everything you'll need.
The work is interesting (of course, that depends on what you're working on), and new products come along quite frequently.
There is some room for creativity and new, original work, but not much.
Garmin has grown a lot in the past few years, so the company has lost a lot of the atmosphere and feel of being a small organization.
Now, there are lots of meetings for team leaders, and developers working on critical features can expect frequent interruptions from email and conference calls and bug reports. A lot of red tape is being put into place for developers committing changes to shared code, and, although code review is a good thing, it's being implemented in a cumbersome manner. This is mostly due to the outdated source code controls system that's still in use here, and which Garmin seems to be stuck with.
It is also immensely frustrating to be working on a constant stream of products that are just not innovative enough, and not bringing anything new to the table for our customers (well, as far as the PND and cellphone markets go).
Garmin seems slow to pick up on new market trends, and is happy to just keep on pushing out products that are merely a slight variation on a theme. This can be an issue for any developer who actually cares about the products he works on.
Please make innovation a top priority rather than getting products to market as quickly as possible. Garmin needs to start wowing its customers again by bringing new and useful features to its products instead of lagging behind market trends and offering products that are not unique or behind the times.
We claim to be a leader in the GPS industry, but Garmin seems to have fallen back into the pack who are merely following the example of other companies like Apple, Google, etc.. Garmin needs to foster an environment of intense creativity, and dispense with the stifling succession of boring products and development practices which leave little room for innovation among software engineers.
To start off, I am a fresh college graduate (B.S.) in computer science and this was my first corporate interview ever. I simply applied on their website and was contacted in about a week. I received a call from HR to kick off the process. It was abou
Initially contacted by recruiter, exchanged multiple emails, had 2 phone interviews that seemed to be checking to see if I was indeed a human. After that all contact was cut off and I could not get a hold of my HR contact.
Standard behavioral phone screen (approximately 30 minutes) with a few general technical questions at the end. I was asked questions about a language I did not have on my resume, which was a bit unexpected (obviously). The questions were more genera
To start off, I am a fresh college graduate (B.S.) in computer science and this was my first corporate interview ever. I simply applied on their website and was contacted in about a week. I received a call from HR to kick off the process. It was abou
Initially contacted by recruiter, exchanged multiple emails, had 2 phone interviews that seemed to be checking to see if I was indeed a human. After that all contact was cut off and I could not get a hold of my HR contact.
Standard behavioral phone screen (approximately 30 minutes) with a few general technical questions at the end. I was asked questions about a language I did not have on my resume, which was a bit unexpected (obviously). The questions were more genera