Pay and benefits are competitive. There are some good people there. The company still has some safe islands where people respect each other.
The company is almost a perfect opposite of “extreme ownership”. Leadership is immature for the challenges it’s facing and it’s not strong enough to admit it and learn.
This ends in deep insecurities, politics, and BS at almost all the levels of the company. Blame is passed left and right.
To hide incompetence, leadership plays out their rank and forces decisions down the chain, rarely explaining their why and not giving any chances for people who are executing the command to provide any input to the plan.
Take ownership. There are no bad teams; only bad leaders. If something goes wrong, own it. Take the blame and use it as a learning opportunity. Work with people at all levels to have a decent plan. Tell the 'why,' and let people work on the 'how' and 'what.' Only this way is it possible for me to have real improvement.
The process took two weeks. The recruiter scheduled an initial call and one round of coding interviews. It was clear from talking to the engineer that they were not interested in hiring for the role, which was not a positive sign that the company's i
This is a typical interview you get at Google or Facebook. It's all the same stuff about algorithms and system design. Basically, it's content you never use in your day-to-day job. I experienced this a few years ago, so I'm not sure if things have
A recruiter first emailed me regarding the job description and the company, and we discussed more on the phone. A couple of days later, I had a phone call with the engineering director and was invited onsite. The first onsite was the technical part.
The process took two weeks. The recruiter scheduled an initial call and one round of coding interviews. It was clear from talking to the engineer that they were not interested in hiring for the role, which was not a positive sign that the company's i
This is a typical interview you get at Google or Facebook. It's all the same stuff about algorithms and system design. Basically, it's content you never use in your day-to-day job. I experienced this a few years ago, so I'm not sure if things have
A recruiter first emailed me regarding the job description and the company, and we discussed more on the phone. A couple of days later, I had a phone call with the engineering director and was invited onsite. The first onsite was the technical part.