Most software development companies give you a problem in which you provide a solution using code or pseudo code. What kinds of problems should I expect?

Moved to Breaking In.

I've applied to 2 different companies and their tests were completely different. So it's going to vary depending on where you go and what sort of job you want. One place had some quite low level stuff if I remember correctly, trying to see if you could count the number of set bits in a 32-bit in the most efficient manner, stuff like that. The other was much more high level and tested intermediate C++ knowledge, familiarity with terms, "find as many bugs as you can in this function", that sort of thing.

Mostly a tech interview will be to probe your knowledge. The way in which they do this will vary from company from company. There's not much you can do preparation wise besides having good technical knowledge!

I've been asked about games I liked, and then asked how I think they would have gone about implementing certain things in the game, and how I think those implementations could be improved.

I've also been asked "general knowledge" questions, from computer architecture, to data structures, to algorithmic efficiency.

Tests I've taken have ranged from low-level optimisations, to hand-wavy descriptions of game systems (e.g. what is spatial partitioning), to being told to spot the bugs in some shader code.

Quote: Original post by Kylotan
I've applied to 2 different companies and their tests were completely different. So it's going to vary depending on where you go and what sort of job you want. One place had some quite low level stuff if I remember correctly, trying to see if you could count the number of set bits in a 32-bit in the most efficient manner, stuff like that. The other was much more high level and tested intermediate C++ knowledge, familiarity with terms, "find as many bugs as you can in this function", that sort of thing.

I really hate the 'bits in a 32 bit number' question. It's not a tech question, it's a trivia question. If you happen to know the answer, it's immediate. If not, the chances of getting the optimal solution during an interview (under pressure) are minimal.

It's a terrible question to judge a hire on.

Depends on the interviewer. I didn't have the optimal answer (and I still don't know it off-hand, though I've seen it on this forum), and I got offered the job. They were more interested in how I approached the problem and justified my answer.

Cool, I am interested too

Expect the unexpected. Some companies only requires a small chat (usually the ones who wish to expand fast). Other times you have to go trough tests that lasts for days.

Many interviews start with a written test though (0.5 - 1.5 hours).

Yeah like other people have said, expect the unexpected, each will be different depending on the interviewer.

You should make sure you have your basics down though such as...

* class inheritance issues like - what order do virtual destructors happen in
* arrays and pointers
* basic algorithms like fibanocci sequence, simple searches and sorts.
* matrix and vector math like dot product, cross product, vector projection

All you can do is your best!

You might mess up a few interviews but learn things in the process so dont be discouraged if you have a few bad ones :P

oh and keep trying, there's tons of companies out there. If you get a lot of no's, just keep going, someone is bound to say yes, right? (:

good luck