- Biggest one is obviously salary. It's true the pay is extremely low compared to Industry standard but are you really going to complain about that when you suck at coding and have 0 QA experience? If you applied to this job, that means you are most likely trying to get your foot out of the door and build experience. You learn so much here IF you take advantage of their resources and in my opinion that is much more valuable than pay because this is what leads you to landing higher paying jobs. I left SQA to work at Blizzard Entertainment but then moved on to another job as an SDET II and am now making 110k. Take advantage of their resources!
- Constantly changing projects: Not sure if this is a con but it could be for some people because you have to learn new domain knowledge and adjust in a somewhat fast paced environment. However, this does expose you to new tools and does give you more experience with what it's like in working with different teams. Whether it is your pods or if you're onsite, a new dev team, you learn a lot about the SDLC and also how you approach situations with "bad" teammates which will help you in interviews for future jobs.
- Late reviews/Pay raises: All of my reviews got delayed and so that was unfortunate at the time but I know some guys waited several months longer than me so I shouldn't complain. As for pay increase, although this can be a touchy subject, I was pretty open about it. My first jump was from 33k to 38k and then to 50k which was much higher than my peers but was still laughable.
- Acknowledgement/Bonuses: The idea of rewarding a good employee is great; however, SQA does this pretty poorly. And I don't want to sound cocky but I did receive the SQA Technical Achievement award but whenever they gave a bonus it's literally just an extra day's worth of pay or a gift card. I actually only received this once but I felt I excelled at my job. I also had gone out of my way very frequently to help other pods with their automation; however, it did feel like it went unnoticed most of the time.
- PDCI: For the guys that are new and have no idea what this is, it is essentially their in house tool for a lot of things such as the requests/tickets you will create and work on as well as to build test cases that can be synced to your automation. I know they were building PDCI 2.0 at the time that I left and so I really hope they fixed all of the inconveniences and bugs of its predecessor.
- George: To be honest, I liked George to an extent. I get it, he can micromanage and be rude at times but I respected him. He can be intimidating and you'll know if he's around when the atmosphere shifts. He also does show favoritism and can be uptight at times.