Page 1 of 3

Interviewing Programmers

Posted: Fri Apr 15, 2011 4:52 pm
by norb
Small rant.

I'm on a two year contract that is almost up, so I've been doing some interviewing. I was on one yesterday and sometimes I just don't understand people.

I listened to what this company needs and felt confident that I could fill those needs. It was not my area of expertise, but many times (almost every job) I have entered the position not being an expert at the area of work. What I present instead is a body of work and excellent references. Those companies that have giving me programming tests have never been disappointed. But the one area I really fail at is the trivia quiz. Unless it's something that I am currently working on, I don't remember exact concepts or exact terms. I do remember where I've done it, or where to find it. I guess my brain does not consider it important to store information found in a two second internet search or an error in the compiler.

So if I was some memory whiz, but only an average programmer, I would have been extended an offer. IMO it's like hiring a painter to do a portrait. They show you a body of work, tons of beautiful portraits, excellent references, but you do not include them because they don't know the technical names for combining colors or lighting. Rather than hire the carpenter that shows you a host of satisfied customers and many examples of his work, you hire the one that can describe in detail every tool and it's textbook use.

Some things weren't meant to be, but the fact that a company can ignore a body of work and excellent references in exchange for someone with a great memory and answers easily found in today's internet age is beyond my comprehension. I always find a job, there are enough companies out there that understand what it takes to be a great programmer. Things that just can't be faked. It just befuddles the mind that there are still companies out there that wonder why they are behind schedule and why they can't squash bugs, and they turn up a chance at someone that has a proven history over many years of doing just that.

Rant Over :)

Re: Interviewing Programmers

Posted: Tue Apr 19, 2011 9:15 pm
by Little Powell
Been there done that many times. I've never understood the memory quiz games... It's similar working in IT. All of the interviews I've been through where they quizzed me or even gave me a written test, I have not received offers... The jobs where I basically sat down and had a friendly conversation with the interviewer, talked about the job, talked about my background, that's when I ended up getting the job. The interview I had that lead to my current position actually took place in a restaurant over a couple of beers. :)

Re: Interviewing Programmers

Posted: Tue Apr 19, 2011 9:44 pm
by X Navy Seal
I agree with LP. Informal interviews are the best. Just try to remember that the way companies/people interview says a lot about what it might be like to work there - and how enjoyable it might or might not be. For example, if someone is a complete hard-ass at the interview just imagine them as your boss.

Re: Interviewing Programmers

Posted: Tue Apr 19, 2011 10:30 pm
by SouthernSteel
Seal, how many interviews have you even had? :lol: Not a bad point, but still.

At least take some heart, Norb, in the fact that you got an interview (and I easily assume more than one). Lots of folks don't even get that these days. Apologies for being an insufferable optimist, it's really quite difficult and against my nature.

It took me almost 1 full year and a move across the country to find a job after I got my Master's, ie, no interviews, no nothing.

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 5:32 pm
by norb
I had two face 2 face within a few days. The one I mentioned above just upset me that people are still that foolish. It was frustrating, trying to promote myself and also trying to explain as nicely as possible that their interview methods were not going to land them the right candidate. They were already over a year behind schedule and they didn't need a theoretical programmer, they needed a workhorse! They just didn't get it.

The other interview went well and I got the offer, I start in two weeks. The CEO is a programmer, so we got along great. Now I have more work than I have time for. My current company wants me to continue contracting into the future. My last company reached out and wants me available if they land an impending deal, and I have a new full time job. My full time job, or mortgage payer, always gets top priority. My last company will have to do without me, as I just don't have the time. My current company will eat into some of my game dev time for a little while, probably over the summer. When it rains it poors. But it's a great feeling knowing that people that you've worked with, want you back.

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 5:37 pm
by SouthernSteel
Congrats - all worked out pretty darn well, I'd say. I'm still waiting for the time when I feel in demand :laugh:

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 7:16 pm
by X Navy Seal
Yep - I am sure glad I did not go to grad school for history then I might be on here boring everyone with my lack of job prospects.

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 8:12 pm
by Amish John
My current company will eat into some of my game dev time for a little while, probably over the summer.

But it's a great feeling knowing that people that you've worked with, want you back.
Hate to see the game development temporarily put on the back burner, but "real" work must come first.

You got that right about being asked to come back to a company which you voluntarily left. Happened to me and I did go back to my old company. Got a raise to go to the new company and another raise when I went back to the old company so that worked out well.

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 8:25 pm
by norb
Sometimes it's the only way to get a decent raise, leave and then come back. I've seen many instances of this. Giving raises their hands are tied and your grouped in with everyone else. But if you come back, they have a lot more room for negotiation. Especially since you don't require relocation nor do they have to pay a recruiter a finder's fee. It's risky, but it works out well many times.

Re: Interviewing Programmers

Posted: Wed Apr 20, 2011 9:25 pm
by Garnier
Happy for you, but it will probably mean map-making waits longer so not happy for me. :)