Got through code test phase, what's next?

Started by
1 comment, last by omgitsuwanda 10 years, 6 months ago

Hi, I managed to get noticed for a job for a small developer and I had to do a code test. It went smoothly and they have asked me to come in for a face to face interview. I am really not sure what to expect, should I continue to "study" incase they ask me some question or have I gotten past that stage that they now know I am a good engineer and are just seeing if I will work well with them?

I'm sure I will handle anything that is thrown at me , but it would be good to get advice on whether or not I should continue to brush up on low level c++ features or focus on standard interview questions like "Why you want to work with us?" etc.

Advertisement


I am really not sure what to expect, should I continue to "study" incase they ask me some question or have I gotten past that stage that they now know I am a good engineer and are just seeing if I will work well with them?

I'm sure I will handle anything that is thrown at me , but it would be good to get advice on whether or not I should continue to brush up on low level c++ features or focus on standard interview questions like "Why you want to work with us?" etc.

1. Be COMPLETELY knowledgeable about the company and its games. Be prepared to answer questions about those.

2. Be ready to answer the questions:

a. What's your favorite game?

b. Why is that your favorite?

c. What is your five year goal?

d. What is your ten year goal?

e. What is your best attribute?

f. What is your weakness?

3. Have at least three good questions to ask when they say, "do you have any questions for us?"

4. Know the difference between good questions to ask, and bad questions to ask.

Bad questions: "How much vacation time do I get?" "How much sick time do I get?" "Is unused sick leave accruable?" "What benefits do I get?"

Good questions: Ask them which of their games was their favorite, ask which had the most challenges. Ask if they might make a sequel to your favorite of their games. Ask about how much hat-switching goes on (how often someone gets a chance to work outside his usual assigned specialty). Ask about their play balancing process.

Bad questions are selfish questions; good questions show your knowledge of the company and your desire to be a good team contributor.

-- Tom Sloper -- sloperama.com

Thanks alot Tom, some really good advices there

This topic is closed to new replies.

Advertisement