Free lunch. For those that don't care, you can have as flexible a work schedule as you want.
For those that do care, having an open vacation policy is a bad thing. You end up working all the time because a handful do all the work and the majority goof off. And there is no vacation balance that builds up so management actually sees who is working all the time.
Another con is that the company is still acting like a start-up in terms of communication, but not understanding that we are too big for everyone to know what is going on.
So, management needs to communicate more, which they don't. Stuff is broken all the time, and nobody seems to care.
Develop a better means of communicating with your employees.
Have some clear focus and direction.
And take the time to do things right.
Giving only lip service to diversity. The culture seems cliquey, and the interview process was very disorganized. They said they are looking for diverse candidates, which I am not, but the interviewer went on to say something negative about someone
I sat down with a "staff engineer" who asked me a very open-ended, philosophical question, expecting one very specific answer. Then, they put me on HackerRank and gave me a very simple LeetCode question. They wouldn't let me write two lines before i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte
Giving only lip service to diversity. The culture seems cliquey, and the interview process was very disorganized. They said they are looking for diverse candidates, which I am not, but the interviewer went on to say something negative about someone
I sat down with a "staff engineer" who asked me a very open-ended, philosophical question, expecting one very specific answer. Then, they put me on HackerRank and gave me a very simple LeetCode question. They wouldn't let me write two lines before i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte