I still keep thinking about their company policy: employees were expected to play their game every day. Can you imagine if McDonalds said they expected staff to eat at least one meal every day in-store?
I still keep thinking about their company policy: employees were expected to play their game every day. Can you imagine if McDonalds said they expected staff to eat at least one meal every day in-store?
I have also worked in games on smaller teams and considered it a responsibility to play the game to make sure that everything I could influence worked well (or I changed it so that it did) or that I could evaluate other parts of the game versus user expectation/current state of the art. Maybe things are different on larger teams/projects.
It's extremely involved.
If the latter, then that's a good, and perfectly reasonable expectation. If the former, nope.
Leave aside for a second that it doesn't scale into large companies - for the product people and engineers working directly on the product, it doesn't seem like such an unreasonable expectation. If you come from the school of thought of "I'm a professional, I clock in at 9 and clock out at 5, here strictly for the paycheck, strict separation of life and work" then OK, it's not a fit for you. Thankfully, not every company has to be a fit for everybody.
The expectation as explained to us was for all staff, regardless of role.
Clearly that culture (everyone must play the product) doesn't scale when you need to hire into roles that have nothing to do with the product itself.