Pros
- Hack weeks teach you a lot and you get to work with the latest technologies developing web applications for real life use cases. If you don't know what hack weeks are, they are like week long hackathons where each team in the company work on their own project and present them on friday. They can be a bit stressful though. - Smart, reliable, and out of the box thinking teammates/colleagues to work with. - Very high 5 digit salaries - FFA food/snacks/drinks
Cons
- The organizational structure is okay on paper but there is too much micromanagement. Expect CEO to mess with your work in a rude way frequently. Expect getting scolded by the CEO for something you worked on closely with the product manager. What is the purpose of a product manager if there is too much micromanagement from CEO? - Poorly managed, rushed and launched projects and yet the developers are to be blamed for failures. - No testing. No development branches. Non-existent SDLC. Code and Fix approach is mistaken for "Continous Integration". Not to mention how CEO brags about how we do "Continous Integration" in his Medium posts. - CEO has serious trust issues with the teams. He explicitly mentioned that people have not been doing their jobs properly and they would have to do their tasks properly if he was to see their progress each week since they knew he would be seeing their work. Do most of the people in the office lack work ethics? I honestly don't think so. - The worst part is, there are absolutely no intentions to bring resolutions to the problems I mentioned above. For example, CEO knows about urgency and amount of the bugs reported from users but still tells the teams to not to write tests...
