Pros
They're a big name, so will look good on your CV. If you're in a good team, it can be an acceptable job.
Cons
Your success, happiness and progression will be hugely affected by what team you're on. Some people are content with theirs, a lot aren't - due to a combination of micro-management by managers who don't know how to handle people with a little consideration, fear tactics and passive aggressive comments when trying to get people to go above and beyond otherwise their roles could be made redundant, or they may score unfavourably in the mid and end year review process. Unless you are friends with the right people, take credit for other people's work or are willing to actively try to compete against your teammates in a last man standing culture, you'll be left disappointed. Some of the senior experienced developers are truly despicable towards others and younger ones in their early years, sometimes picking and choosing when to give advice and answers to questions, but other times ignorantly ignoring them and co sciously participating in their struggles to learn, understand and grow. It's a form of coding snobbery, and it's rife. The managers sweep it all under the rug. They'll pressure you into the office even if you have a huge commute, and will get you to do lots of earlier, lates and some weekends by trying to dangle a carrot of potentially more money and promotion, but really, it's a mirage go get you to produce for them, so that they can take credit and ultimately get their pay rises.