Pros: You will get decently good pay. Reputed Company.

Cons: Pathetic work culture, bad work-life balance. You work as labor, just following the manager's orders. All the decision-making on the projects is done by management without much involvement from the engineering ICs, who are just handed over tasks to be completed. There is a lack of transparency between management and the ICs. You don't grow as a person, but only as a resource. Much of the soft skills you gain are not over managing projects, collaboration, innovation, or leadership skills, but over pushing your work to someone else, negotiating on timelines, and the amount of work. This type of work culture is simply not acceptable from a large and reputed organization like Microsoft.

Pros: Good benefits, salary, and equipment.

Cons: Strange culture, out of touch with regular people. Most everyone acts like they are better than the rest of the world.

Pros: Every org at Microsoft is different, so this is specifically for Lync (Skype for Business). * A lot of smart, talented, and experienced engineers from whom I learned a lot. * In general, managers had been promoted from within the org and were very knowledgeable and passionate about the product. * Got to work on very interesting, deep challenges and learned a lot about how to make large, scalable services serving millions of users. * For the most part, there weren't too many tight deadlines or pressure to work an exorbitant number of hours. * A good amount of freedom. Teams were generally left to make a lot of their own technical decisions without much micromanaging from upper management. At least for my team, the leads were always up for a discussion on the best way to do things. * Catered breakfast! Everyday!

Cons: - Difficult to ramp up in the beginning. Tons of different services, endless internal acronyms and code names, not much documentation (or no one remembered where the documentation was, or it hadn't been updated in 5 years). A lot of people had been there for years, so they didn't understand what it's like to be new. - Some managers (unfortunately mine) clearly got to their positions because of their ability to play politics rather than technical skill or leadership ability (or intelligence), and the engineers under them suffer because of it. - A lot of process and overhead that doesn't always make much sense and slows things down. - Dependent on internal tools and infrastructure that can be unreliable and difficult to find documentation on.