Pros
The facilities are amazing and the Café is really nice and has good food and good prices. The location is good and you don't have to fight traffic to pull in and out of the campus. The scrum rooms are nice and are set up for efficiency and productivity. There are break rooms everywhere. with ice machines, coffee, fridges and microwaves.
Cons
The environment was harsh because of the sensitive culture that is encouraged. There is no criticism, joking or asking hard to answer questions. The team I was on had allot of insecurity about the technology being used, insecurity in general about the project. They did not like a new comer having new ideas or suggestions. They do not like you asking for clarification because you are new and need further insight so you can ramp up to speed. They will misinterpret everything you say and look for ways that could be interpreted as talking down to people. They take things out of context and report you for a single sentence you said that was part of a larger conversation, because they believe it to be insulting. In short you have to be careful with everything you do and say. They have meetings to prepare for meetings. They have too many meetings, which gives a developer about 2 hours to develop if they are lucky. Projects will move along at a snails pace with no since of urgency. If you try to help move it along you are not being a team player. If you do not agree with everyone else's opinion you are not being a team player. If you express opinions, do prototyping, ask questions to the product owner of clarification you are seen as trying to make yourself more important than anyone else on the team and will be reminded that you are not anymore important than anyone else and the project is the most important thing. They say they buy into whole team ownership of the code but then will be told that if you need to modify someone else's code that you need to talk to the author first and get permission. If you point out issues in the code that could result in issues later they will think you are being critical. If you point out issues where other's are not conforming to coding standards, they will think you are being critical. They will think your trying to prove yourself when all your doing is trying to do your job when you do not care about impressing anyone, all you want to do is work and to feel like you contributed. Onboarding was a nightmare. I was promised that I would be given briefings on the architecture. I was promised that I would get to shadow others to learn the business, code and project. I was given a brief demo and explanation of the project that was being rewritten, and that was it. I spent the rest of my time reading going to meetings to prepare for other meetings. No one had time to help me because of meetings that left them to complete their assigned tasks. Other people's time is limited because of meetings, so being able to shadow and get a full understanding of your project may not happen.
