Pros
Interesting tasks. During my work, I created the first version of water in the World of Tanks, programmed lighting effects and system of decals. Now I'm working on a project to improve clients physics. In the nearest future, I'm planning to develop an entity component system. It's not necessary to become a manager. I tried to be a team lead, but it was not very exciting for me. My tasks included maintaining the stability of the tank client and managing a team of 6 people. When I finally realized that management is not for me, I talked to my superiors and switched to clients physics. Freedom of action and promotion of initiative. If the idea is reasonable, it will be brought into the backlog and sent to work. Of course, it depends on the complexity of development, but in general, it's not difficult to bring a reasonable idea to life. Competitive salary.
Cons
If you are not initiative, you will be bored. Interesting tasks go to those who suggested them. The team has grown very much in the last years. This imposes some restrictions to creativity - you need to negotiate with everyone how and what should work. In a small team, you are making something by yourself, and then you put everyone to the notice. Now you need to explain in advance. On the other hand, this makes one think about viability and many useless ideas fall off by themselves. Huge code legacy. The "Tanks" engine exist for almost 10 years. That means that there's a lot of code written by different people at different times and with different styles. Sometimes it's difficult to understand what and why was written. Any changes require serious analysis and rework. But sometimes it's even fun - to rewrite the code better than it was written before you.
