Pros
Very knowledgeable coworkers. Interesting consumer projects like HDTVs. Also exciting being part of a huge corporation who makes waves at events like CES or in online publications like CNET. Work equipment is never in short supply if needed, so from an engineering standpoint they will provide you with what you need to get the job done. Most developers are easy to work with and development managers are constantly on the ball when it comes to submitted defects.
Cons
Information sharing could be much better despite the utilization of some tools like Microsoft Sharepoint. Very little documentation, such as functional specifications, are created or updated for even the riskiest modules. For SQA, this is an exercise in frustration because what you think is a defect is actually a "new feature." And often you are asked to compromise on obvious bugs because the development team desperately wants to meet a closed-defect milestone. Also, at times development exerts too much influence on SQA activities. SQA should be a separate entity working WITH development towards a common goal, not working FOR development. Also hours can be RIDICULOUS often requiring 60-70 hour weeks, with no compensation, just a measly "thank you" from upper management. And did I mention they're charging for coffee and tea? Way to annoy your workers who work long hours with no overtime, Sony. Since we're on the topic of pay, Sony's average salary for Software QA is far below the San Diego average. I make less than the average SQA pay in San Diego.
