Cares more about the bottom line than it's games or employees.
QA Tester / Content Writer (Former Employee) – San Francisco, CA – May 9, 2013
The creative teams I worked with at Glu were some of the most talented in the industry. I was constantly amazed at the quality of work they put out.
Sadly, the upper management preferred to simply copy other games rather than take any risks. On top of that, the budget was constantly strangled, making it harder to bring in talent to create the very games the company relied on. I saw several employees quit after simply burning out, and these were people who LOVED making games.
At the cost of one Executive Producer, the company could have hired two designers, artists... people who, you know, make games.
Instead the company became increasingly top heavy and bloated, rather than the small, competitive, game studio it could have been.
Work location and office size were constantly cramped in San Francisco. Noise was a constant distraction with no cube walls. Complaints were often ignored by executives who didn't really seem to care, because they all had offices.
Towards the end, entire departments were being forced to fit into tiny conference rooms due to short sighted planning.
free train pass. benefits were okay. stable income.
terrible office. execs did not listen to anyone. bottom line trumps workplace happiness.
Productive and fun work place with ping pong table and snackage
customer service (Current Employee) – Long Beach, CA – December 19, 2015
One of the best groups of people I have ever had the pleasure to work with. The employees at this company do a great job at having fun and making sure everyone feels apart of the team and gets the job done.
free lunches, awesome events, great coworkers, overtime
Software Tester - iOS (Former Employee) – Kirkland, WA – June 4, 2015
My day would start by attending team stand up which allowed me to gauge what work needed to be done over the course of the day. From there I would either create test cases/test plans for upcoming work or I would begin testing the day's content. I would use Jira to track any bugs written against the branch. If bugs were fixed during the day, I would kick off a new build and handle bug regressions for the team. I would attend any and all meetings that the QA Lead was invited to. Towards the end of the day the QA Lead, the Producer, the Lead Engineer and I would do a bug triage to determine what bugs would be fixed during the sprint.
Free snacks and Beverages
Contract agency they use is terrible and out of state.