Hey folks! After two phone interviews I've got an onsite interview with my first game company.
(suitably stoked) I'm fully aware that an onsite interview is mostly to see how you fit in with the team. So, what I want to ask all you grizzled veterans is what would YOU look for during an onsite interview? What kind of questions would you recommend I ask while I'm there?
So far I'm making a note to pay attention to lighting conditions, what kind of a break room they have (is there a fridge, microwave), ask about how flexible hours are, try to see if anybody is using a tablet (I use one for everything, so I'd want one). I plan to take a look at the general safety of the area though I don't expect any problems from that quarter.
Thanks in advance for any advice
Replies
Interesting question though, I've honestly never though about it a great deal. I work in a very nice studio at the moment and the only thing that "bothers" me is the air conditioning, or rather the employees use of it (we have controls on the walls so anyone can change it, which might not be the best idea).
I used to work in an office where a programmer was so poorly situated that he had to wear fingerless gloves. It's going to be one of those "can't please everyone" sort of things, but if I was being super picky I might factor it in, as it's pretty tough to work when you've got mountain cold winds blasting the back of your neck because one guy needs to "cool off a little quicker"
Tablet's are a must, I would expect any studio to give their artists one.
Chairs... very god damn important, if they use something you'd expect to find in a poorly funded college classroom, you're going to have a bad [back] time.
Edit.
Oh... and yeah, in most cases you're brought in for an interview purely just to see if you'd work well with others and/or are sane enough. (there are always exceptions to this "rule", of course) so it might be a good idea to ease off on things you might not naturally enquire about.
I won't ask this question, it could be construed that you're scared of....crunch. It's a valid question IF you're not desperate getting this position from this particular company.
I suggest asking instead, if the company offers free dinners in case a project you're in goes into...overtime mode. Yeah...probably best not to mention the c-word.
Basically I'd ask questions that would make me look like I'm committed to this company and improving my skillset/level while Im there. Such as...would they subsidize part-time eduction/workshop training (like Gnomon online workshops or free trips to conferences and such).
Shit like that...just not questions that would make you look "high maintenance". But if you're a bonafide "rockstar"...lol...shurrre, why not.
Yeah.
agreed, if there honest and not shady they will tell you the truth :thumbup:
That's genius asking about subsidizing further training, and not something I would have thought of on my own.
At my old place everyone would go to get coffee at one of several local coffee shops rather than drink the coffee at work, because going out to get coffee is really a ritual - you go with some friends and you bitch about work and socialize and it gives you a break from the office.
The questions I would definitely ask all come down to "what's in it for me, and what are you looking for?"
Ask what the core hours are. Core hours is not # of hours per day, it's the hours you're required to be there. Everyone is going to expect the 8 hour minimum, but a lot of places will have core hours of 10-5 with a break for lunch, and you're expected to either come in earlier or stay later to hit your 8, so you are flexible in that regard. Some places have even more flexible work environments - my last job let you choose your own hours entirely (with the caveat that you had to be there for meetings - it meant meetings were always scheduled a day in advance which was nice. We had a guy who lived on a 30 hour day or so which was funny because he'd rotate between being an early morning guy to a late night guy).
Ask what is expected of you in a daily, weekly, and project-wide basis. What are your responsibilities, who are you working with, what tools are you working with, what is the organizational structure/who are the leads, etc.
Ask about their bonus structure. Ask what their crunch policy is, and how well they feel they manage crunch.
Overall, in my opinion, the best questions to ask are the ones that help you figure out how you fit in and whether you'd like it there. They'll ask all the questions they need to figure out your qualifications, etc, you don't need to invent a question that shows off how cool you are. Asking questions that are designed to help you figure out if it is a good fit for you shows more interest and desire than any number of "How would you like to know how great I am?" type questions.
Dont get me wrong,asking questions is a good thing,but dont get too caught up in it,typically a 2nd interview is to see if they like you,if you come off unnatural it could be a huge disservice to you.
This sounds very familiar
Our programmer can't stand working in the cold, and our boss can't stand working in what everyone else in the office considers to be "average" temperatures.
So we all get to freeze, yay. And the boss ain't even in the room half the time! So we switch it back to normal temperature but when he comes back, he switches back to freezer temperature again.
The good thing is that I don't personally mind the cold that much... but it bothers the programmer a lot!
Don't ask stuff you actually don't care about, it will show. Maybe you think that having a microwave is the most important thing in the world, but it's kinda stupid to ask. Any company with actual humans in it will have basic shit like that. Asking stuff is good, asking stupid stuff makes you look stupid.
Good luck man! It's a great feeling getting some attention!
2. What are your core hours?
3. What is your policy on crunch?
4. How are projects financed?
5. What does the current dev cycle end on this project?
6. What types of ways are you looking to grow the company?
7. Are there any other projects you're working on?
8. Do you tend to promote from within or look outside the studio?
9. How are reviews done for employees, annually? bi-annually?
10. How are art critiques handled?
11. How do you handle your bug tracking?
12. What are your tools like?
13. Where is the game at in terms of overall completion of functionality?
14. What is your PTO policy? Are you able to come in la little ate/leave early and make up the time to make appointments (this is especially important when you're moving)
15. What is the company culture like? Do people go out together, does the company host socials?
16. Who would I be reporting to? (always good to see if there is a billion managers)
17. How big of a team will I be directly working with?
18. How open are you to letting me branch into other aspects of my discipline, or will I be doing the same work day in and day out until project ship?
19. What is your employee retention rate? (do a lot of people leave the studio?)
20. How often do you playtest your game? (if people don't play it, it won't be fun)
Those are a few I came up with off the top of my head in exactly 3 minutes. Just the tip of the iceberg of questions I try to ask or at least get a good idea about. Granted, you don't want to constantly be asking questions. Get to know the people working there too, be friendly and courteous. If you don't like the people you will be working with, then none of the above questions even matter!
Good Luck!
An unexpected question that can derail you from your mock interview practice. For example: They may ask you what are your personal hobbies (NEVER GO WITH VIDEO GAMES AND LEARNING HOW THEY WERE MADE.)
They also might ask you stuff like:
Suppose you are dumped in an on going project, How would you handle that.
What would you require to start a project.
What are your key goals.
Where do you see yourself five years from now.
What if matrix...(ok that one they may not ask..-.-)
At the end they may ask you if you have any questions for them:
You can ask them stuff like:
What is the work flow, what type of tools they use. How does the project progresses like what phases does it go through? What documentations are required for each phase.
and stuff like that.
But I can't imagine a place that would starve people of the greatest source of creativity. You would probably be beating people away from the pot with a stick. You might be able to discourage them by drinking directly from the pot, like a dog. And the chair you start out with probably won't be any good. People have a way of cannibalizing a work station when someone leaves.
The chair you find sitting in your cube on day one will more than likely be the worst possible chair in the company. But this is good, because you do NOT have to put up with it, if its in really bad shape you can normally ask to have it replaced which everyone else was too busy swapping for minor upgrades and didn't think to ask for a new one.
Just watch out because the cannibals are watching you unwrap it...
Yes... yes we are :poly141:
Isnt that like up to them? I mean project participants would get cubicles, project manager and their assistants get side offices and so on?