Talking about interview and such, can you tell me more about demo reels for programmers (not artists) ? From what i have seen, most programmers seems to show a few seconds of a selected set of projects they worked on.

What should I put in and NOT put in ? What do you like to see personally ? How long should it last ? Should it have annoying music :-) ? What if we are coming out from school and have no experience on on real games, are school/personal projects worth showing in a reel ?

Thanks!

Mat

In response to your questions, I’m not saying every PhD should make more money than someone with a MS or BS, and that’s absolutely not true in reality. It’s just an observation when I compare my colleagues in grad school to my classmates in undergrads, the quality of people are much higher in grad school. Of course, I’m talking about averages in a large pool of samples. There are extremely sharp people in my undergraduate classes as well who never went to grad school and are very successful in what they do.

Personally, when I decided to go to grad school, I wanted to stay in academia, so getting a PhD was really the only option. Besides I really like what I do, I think there’s also an expectation that when I graduate with an advanced degree, I should earn more money than when I just graduated from college, otherwise it doesn’t really make sense. Of course I don’t expect people to just pay me more because I have an advanced degree, but rather for what I have learned during my time in grad school. But you are right, having a PhD doesn’t really say anything, it’s really what you have to offer should be considered in a job interview.

And interestingly, I learned much more outside classes than what I learned in classes. I think there’s a big gap between what the computer industry is looking for and the current CS curriculum being taught in schools. Parallel computing was rarely taught when I was an undergrad, and now all the hardware are expected to be used in parallel. Recently I read Stanford is offering an iPhone programming course, I was quite impressed. They have been doing a pretty good job to stay up to date. I want to make a game for iPhone myself, when I find the time to do it I’m sure the market will be flooded.

Thank you so much for your insights, they are very valuable.

The same goes for someone with 20 years of programming experience and a resume thick as a phone book. I’ve seen enough experienced people with impressive resumes have no appreciable skills whatsoever that I know you cannot take resumes at face value.

Only an interview (or a trusted reference) can tell you that these people have the skills needed for the job!

Now, there is a reason people ask questions about linked lists and other (seemingly trivial) fundamentals: a large number of people we interview in the industry have no clue! They didn’t retain a single thing from the classes they took. Often they cannot even list what classes were part of their curriculum! And even when they retained something, it is memorized facts and they cannot explain them, argue about them, or even apply them. PhD’s are no different in this aspect from BS or MS students. I see them flunk interviews as well as those with BS degrees or no degree at all; sometimes PhD’s flunk more spectacularly.

You shouldn’t be amused that PhD’s are asked how to implement a linked list, you should be sad or disgusted. Because that’s how poor some candidates are that we see (PhD’s included). Trust me, we ask some very tricky questions (beyond your hair simulation problem) in interviews, but first we need to make sure they can actually implement simple data structures and describe basic algorithms.

As for interviews, we don’t do a 20-30 minute interview. We do 60-90 minutes on the phone as a phone screen. If they pass the phone screen we have a whole day interview, consisting of 3-4 hours of in-depth technical questioning, and the remaining time is social screening. And we check references. (And, it goes without saying, I expect candidates to check us out equally thoroughly to make sure we are the right choice for them.)

Not everyone is this bad of course, but there are sufficiently many who match this bleak picture I’m painting that this is a reality and not something I’m making up.

I’m curious as to why you seem to think a PhD would be worth more money than a MS, a BS, or someone with no degree at all. Also, what makes you think a PhD has more “future potential” compared to the others? How would you justify your response?

But I’d be interested to hear more insights on how you can accurately tell someone is brilliant within say a 20-30 min interview and able to decide their salary without seeing their actual performance. It would seem to me that you can get a general idea of whether someone is an idiot or not within that time, but to decide his/her salary, you’d still have to go back to their prior experience (on resume) or their education.

I mean the things we do require more than knowing how to implement a data structure or fancy bit operations. I was amused when my friends told me when they were interviewing, they were asked to implement a linked list on paper, or how to use bit operations to divide a number by 2, and my friends are CS PhDs. A more challenging question would be asking how to solve a hair simulation problem when there are 500 characters interacting with each other in the scene and you want it all done in real time with shadow. Would you ask this kind of questions in an interview?

I guess what I mean to say is a fresh PhD would lack industry experience and possibly some relevant knowledge (such as writing commercial grade software) required for a position comparing with someone who’s been in the industry for a while. But it doesn’t mean the new graduate doesn’t have the potential so do the job well. Their trainings in terms of problem solving and creating new technologies can be an asset to the company in the long term. So to me it’s a question of prior experience vs future potential and how they are valued in terms of $$$. Thanks.

That said, you clearly stand a much better chance of having the chops by having completed a BSCS, MSCS, or CS PhD, because you have been studying in the area relevant to what I’m looking for in candidates. Nevertheless, I’ve interviewed people from so called “top schools” (MIT, etc.) who have been truly abysmal and I’ve interviewed people without degrees who have been brilliant. (And vice versa.)

Basically, anyone who hires someone solely based on what school they went to, or what degree they have, is a moron. The only thing that can tell you whether someone is suited for the job is a thorough interview process, or references from people you trust. (A letter of recommendation from a professor is useless, btw.) The information on a resume is merely something that is used to sort the resumes in an estimated priority order as to who to call first.

So, to finally answer your question: advanced degrees have no direct relevance on salary negotiation as far as I’m concerned. They may have an indirect relevance in that they might have provided you with the knowledge and skills that do affect your salary negotiation.

Others may have a different view on this.

As for skills, I would expect them to know their computer science curriculum inside and out as they're likely to have just completed such a degree. And even if they didn't, I still expect them to have equivalent knowledge -- they will just have to learned it all on their own if they took EE, physics, or didn't go to university at all. It's a meritocracy: I'll hire you based on what you know, I don't care how you obtained the knowledge or what school you did or didn't go do; the only thing that matters is that you have the chops.

As for CS-degree equivalent skills, I will expect you know everything that was presented in classes on data structures and algorithms, computer architecture, and linear algebra. You need to be proficient in C/C++ and at least one other language. Bonus points for everything above that. Brains, enthusiasm, and drive are very important too, of course, and can make up for deficiencies in knowledge areas.

I’ve meant to write a post about what I think a programmer should know. If you stick around, I might actually even get around to it eventually!

What I’d like to know is: What is the ballpark salary range for a junior programmer? And what skills do you expect from a student/junior programmer coming in?

jordan

I cross referenced your data and they seem to match for the engineering part.

Enjoy :)

fatlimey: Keep in mind that this database lacks all the O1s, J1s, L1s which have been used more and more the last few years.