If you're starting out, GoDaddy is an awesome first company. You get a good balance of "do grunt work to get better" and work-life balance, not getting overwhelmed. Other engineers are generally helpful and supportive, so you won't feel like an idiot or feel like you're bothering somebody by asking for help.
If you are terminal in your career (e.g., senior software engineer), GoDaddy is also a great place to work. As long as you get your work done (bonus: most of the work you do isn't challenging anyway), you have good work-life balance and decent benefits. GoDaddy is hands down one of the best places to rest and vest.
After Blake took over and instituted culture change, the company has made great strides in hiring diverse software engineers. You should definitely apply here if you are a woman, LGBTQ, or an underrepresented minority.
Fast promotions: With a supportive manager and if you do enough "visible" work (or if you're really lucky and are on a high-profile team), you can get promoted relatively fast. I have seen new college grads become senior software engineers after 2 years.
Eroding benefits - for example, first, PPO100 got axed, then PPO90 wasn't fully covered (but PPO80 was), then -- surprise surprise, PPO80 wasn't fully covered either.
Pay - despite what management tells you, your pay is just a bit under market. I wasn't significantly underpaid, but just enough to make the stay vs leave calculus favor staying.
Product - some teams toot their own horn but ship really underwhelming product/features.
Silos - company-wide, each location generally operates as its own silo (e.g. SF vs Sunnyvale, Scottsdale vs Gilbert vs Tempe) as well as each org (hosting, domains, productivity, etc.). Even within orgs, in general, teams operate siloed off from each other.
WLB - some people really live up to the company value of "live passionately" to the point where sometimes you wonder if they're even pulling their own weight.
Fast promotions - should someone with only 2 years of experience really be a senior software engineer?
Ship more meaningful product lines and SKUs instead of relying on acquisitions and non-GAAP financial results to improve the share price.
1. Applied online 2. Had a 1:1 with an engineering lead that included behavioral questions and a brain-teaser/algorithm coding exercise on HackerRank. 3. Was ghosted. The interview itself wasn't terrible, but I was disappointed that the FizzBuzz/a
They had me take a rather rudimentary IQ test with a large number of questions and limited time. Then, I was given a simple problem to solve. When I solved the problem in about 30 seconds, the interviewer falsely accused me of already being acquaint
The process was very quick, lasting only about a week. Phase 1: A brief talk with the recruiter about the position, your work, your expectations, and the company. Phase 2: HackerRank test. Phase 3a: Algo whiteboard interview. Phase 3b: Technical int
1. Applied online 2. Had a 1:1 with an engineering lead that included behavioral questions and a brain-teaser/algorithm coding exercise on HackerRank. 3. Was ghosted. The interview itself wasn't terrible, but I was disappointed that the FizzBuzz/a
They had me take a rather rudimentary IQ test with a large number of questions and limited time. Then, I was given a simple problem to solve. When I solved the problem in about 30 seconds, the interviewer falsely accused me of already being acquaint
The process was very quick, lasting only about a week. Phase 1: A brief talk with the recruiter about the position, your work, your expectations, and the company. Phase 2: HackerRank test. Phase 3a: Algo whiteboard interview. Phase 3b: Technical int