Pros
Ability to work with young and friendly colleagues
Cons
- The management didn't have a clear system on how to run things , and were not familiar with the whole software engineering process. That resulted in confusion between priorities , a handful of people running multiple projects simultaneously and unmet deadlines. - There was a common situation of the management expecting things that were never discussed with the team, and setting unrealistic goals where there was no clear path on how to get there due to lack of technical knowledge. - It was a common situation to agree on a feature ,design it , spend hours and hours to develop it, and then a manager would casually walk by and decide that it wouldn't fit the project's vision, and terminate it. -Because of the unclear picture the management had regarding the developers role, a developer was expected to build websites, be a back-end developer , maintain the server, do SEO and Adwords campaigns, build a computer, and also sometimes carry computer boxes , open them with a screwdriver , and then repackaging them for transportation. -The management would scold the employees if someone was coming 10 minutes late , but would expect that no one should leave after the 8 hours finished . Sarcastic comments were often made about how no one stayed after the shift ended, but extra-hour payment was scarce and had to be constantly requested , otherwise it would be "forgotten". - After hours messaging was constant , and immediate response and addressing of issues was expected, without regard of the employees personal time. -The upper management has hired for project managers a collection of friends with no prior expertise in the field, which results in all the the aforementioned confusion. -Because of the quick expansion of the company, a lot of new hires were made which led to all of the employees working in a very small space with minimum personal space.