Pros
1- Huge amount of holidays 2- Good behavior of people(mostly) 3- Opportunity to learn the business of telecom domain(might be helpful in future too) 4- Very clear hierarchy and you can reach to anyone with a call or mail.
Cons
1)- Very chaotic environment, too much dependencies. 2)- Everyone is involved in everything and no one knows what to do exactly that is why they spend most of the time fixing bugs. 3)-Obsolete technologies, For .NET projects they still use VS 2008(can u believe), even Microsoft has stopped supporting it. 4)-Very old methodology and a long SDLC cycle. So slow process ultimately. 5)- Nothing to learn technically(atleast in wireline). Even good managers can't help there. 6)-Work-life balance for most of them sucks(again wireline). I have seen people working for 13- 14 hours daily that too on weekends for continuous 6 months and counting...' and most people stay just because everyone is staying, going early will mark a bad impression. 7)-Nothing extra if u work night shift for a regular project or extra hours. (Night shift allowance only for those who work daily) 8)-They don't even know the meaning of resource management. 9)-You will die but not get response on mail or chat even if something important from other teams or sometimes from team members sitting on the other location. 10)- No one will give fruitful training about the project when someone joins. One most important thing I missed is coding standard is just pathetic, actually they dont follow any standard just write the code, no description no comments no code reviwes. They keep on adding same code again just not to change someone else's code. Verizon is a mixture of Service and Product based companies and thus it's actually like a RAITA. They will advertise with their revenue and compare the salary with TCS and Infosys. These all cons apply mostly for Wireline teams. Wireless is going good so it might not be the case.