CQ> This is why I hate trivia questions as a gauge of skill.
Yeah. I'm also much more interested in communication skills and comfort
with things like revision control, configuration management, ticket
tracking, change control, and other principles like that, than about any
particular technical skill. You can learn technical skills, but if you
don't like using tickets to track your work, can't express yourself
clearly in writing, and don't get why configuration management is a good
idea, that's going to be hard to overcome. (Unless you're an eager-to-
learn novice, in which case you are fun to teach. :^) But if you're a
senior sysadmin and are lacking those things, I don't care so much how
well you understand TCP and kernel modules and whatnot.
(That said, I do really like Tom's question, or really more like
"approach" than "question". It seems like a good way to find out pretty
much whatever you want to find out in any given situation: Don't just run
down a checklist of questions with one right answer, follow up and swim
around and see what you bump into. The real problem with interviewing is
that most jobs are not very much like interviews...)
-Josh ([email protected])
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
