2 Apr
2006
2 Apr
'06
8:57 p.m.
Richard wrote:
In article <44307ACB.1090607 at pacbell.net>,
Jim Battle <frustum at pacbell.net> writes:
I suspect it is a cheap way of splitting people into two groups...
when you have enough applicants, you look for quick ways to
differentiate among them. <shrug> And, I suppose this is better
than sorting by HEIGHT... :>
I've heard of people asking these types of
questions during job
interviews -- and I think it is an asinine way of judging someone's
abilities.
Microsoft, and companies that aspire to be Microsoft by imitating
everything they do, has a tendency to ask "brain teaser" questions on
job interviews. Personally I always thought this was a stupid way to
evaluate an employee. I've yet to see any explanation of why this is
something that Microsoft does, but I'm sure they have one. I've been asked those questions and I always
thought to myself "uh...
yeah, this doesn't reflect anything I do as a software engineer, it
just reflects whether or not I "get" this little mind teaser trick".
I think a better way is to have someone pseudo-code a well-known
algorithm. You can then note *how* they approach it (top down,
bottom up, linearly, etc.). Then, engage them in a discussion of
the merits of their implementation as well as where it falls down.
Finally (most importantly) ask them how they would test/qualify it
(since it seems so few people approach testing with any vigor)
Once it was Microsoft, so I expected this. The other
time it was a
game company. Although I don't know why they bothered with the mind
teaser since it seems all they cared about were cheap bodies who spent
their free time playing video games anyway.
Yeah, when they give you your paycheck in QUARTERS... :>
--don