Taro Logo

Resistant to change, sign-on trap, ineffective leadership but solid compensation

Software Development Engineer
Current Employee
Has worked at Garmin for 2 years
March 11, 2020
Kansas City, Kansas
2.0
Doesn't RecommendNeutral OutlookApproves of CEO
Pros
  • The compensation is pretty good for the area.
  • The 401(k) match starts at 10%, but vests 20% per year until 5 years. So if you leave in your second year, you'll keep 20% of the match they gave.
  • In my experience, I rarely worked more than 40 hours a week.
Cons
  • Management is resistant to change and values seniority over technical value (i.e. you must "prove yourself" before you're allowed to have any ideas).
  • WFH policy exists but is pretty inflexible. You'll be in the office 90% of the time.
  • Tons of micromanagement
  • "Excellent performance" is defined as doing exactly what you're told as quickly as you can.
  • Agile in name only. Zero developer autonomy.
  • Low to no ownership over the end user experience. No cross-functionality. I've never even met the users of the project I work on.
  • Company focus is on churning out as many new devices as possible rather than investing in a few good ones.
  • You'll spend 80-90% of your time doing maintenance rather than development.
  • Huge amount of tech debt from an ancient inherited codebase - constant production issues.
  • Possibly racist recruitment? The office is disproportionately Indian.
  • It seems like the software engineers are treated as a cost center rather than a driver of value.
Advice to Management

Have your more successful technical leads and managers shadow and audit the others. Some real rotten ones ruin the bunch. Don't tell your engineers they can't have ideas until they're more senior and have proved themselves.

Evaluate things on their technical value. Garmin will never be a leading technology company until you bring development practices out of an eon ago. Let people WFH because they're adults.

Was this helpful?

Garmin Interview Experiences