(I'm not gonna just compalain about the cons here. Wherever applicable, I'll indicate how you can use these cons to your advantage, if your conscience / opportunity at company allows. See points mentioned in '=>')
[1] Clearly not an engineering-oriented company. Very few (I repeat, very few) people get to work on good-technology. Most developers work on projects involving only editing XML files, adding PHP array entries, editing CSS, integrating animation/image files into front-end code etc. Only products that US office doesn't want transitions to India office. The other way around, products that's technologically cool built out of India office gets transitioned to US. Around 60-80% of the developers here can be quickly replaced by front-end developers or multi-media chaps (who just have an NIIT course on CSS/JS/Flash).
=> Keep your expectations clear. Don't come here to work on cool technologies or anything. Earn salary and leave.
[2] Lacks dignity of labour. Clearly, following is the tiered system one would notice within a week of joining:
1st-grade employees: Product Managers, Producers, UI Designers, Artists
2nd-grade employees: Developers, Engineering Managers
3rd-grade employees: QA
Typically for all the good things that happen in your product, Product Managers and Producers get credit. For any bad things, blame typically goes to developers and QA. General Managers almost always listen only to Product Managers or Producers. As a developer, I get deeply hurt sometimes. Can't imagine what would our QA be feeling every day!
=> If you want to join Zynga as developer, come with clear expectations that you're not respected like in other companies. Then you'll feel better.
[3] Product Managers and producers call the shots in almost all teams (to know what a 'producer' role means, you may have to google a bit). As a developer, you'll have little to no freedom to disagree with them. Engineering managers are powerless here - there is little they're able to do, even if they want to. This has a direct negative impact on developer's work-life balance, severely. A freshly graduated MBA can make 7 to 10 year experienced developers and their engineering manager dance to his/her tunes. Unfortunately, Product Managers in India Studio are very short-sighted (focus is on that particular month's revenue, sometimes that week's - instead of thinking long-term). This attitude is obviously bad for company as well as developers. Developers end-up working for short-term goals and hence sub-standard projects.
=> You can expect a good hike / promotion if you're in good terms with Product Managers and Producers in your team. Their quarterly feedback on you matters a lot (I repeat, a lot)!!! If you're into developing features, do whatever they tell you to, howsoever foolish it might seem or howsoever damaging their decisions is on product - don't question. Also, don't spend unnecessary effort in impressing these Engineering Manager fellows with your good programming skills or hard work or anything. If possible, move out of feature development and work on some platform stuff with an architect directly.
[4] There is lot of office politics (a lot) - this is not a general statement that one passes in any software company, but a bit more severe. This one involves a lot of people across roles. There are multiple nexuses in office.
=> If your conscience allows you, be part of one such nexus. Be in good books of key people in your team and company HR. Never (I repeat, never) provide correct feedback about these key people in your team to HR.
