Re: [GD-General] what you look for in a coder...

[Javier A. <ja...@py...>]

Jamie Fowlston wrote:

> The most reliable bad sign i know is just a 'bad feeling'. If someone
> manages to give you a bad feeling over the course of an interview,
> that tends to mean something isn't going to work. I don't think i've
> ever come across a case where someone was hired despite a bad
> feeling, and turned out good.
>
> These aren't terribly scientific or easy to measure, but that's
> people for you :)

This is spot on - it's hard to reject somebody without being able to explain
it in formal terms, but previous history shows that it in fact works. After
a couple years recruiting, you eventually get the confidence to go ahead
with that kind of gut feeling.

Specific skills and knowledge are good things.

I also try to find out how "honest" they are, heh not in terms of being
liars or criminals, but how willing they are to have opinions, propose their
own choices, and debate them; some people go too far (opinionated, stubborn,
not willing to compromise), and some people don't go far enough (waiting for
you to express a view before they go and nod in agreement).

Dealing with a candidate that is nervous in the interview is hard, because,
even if the information you need will still show up, there will be a lot of
noise. :)

Finally, it's very interesting to dig up as much information about their
previous (or current) jobs, and why they decided to move out. Dragons be
there so handle the issue with a lot of care because it can be a touchy
subject, but you can find out a lot about his attitude in a team / company
environment.

You will get as much information from what they say as from how they say it,
what issues they avoid, and how they react.

-- 
  Javier Arevalo
  Pyro Studios