I think instead of not doing interviews, if you were encountering the problems you mention, would be to get better at interviewing. Interviewing is not about asking "How good are you at X? How good are you at Y?" You are trying to gather a lot of different information:
- Is this person's long term goals consistent with my goals for the position?
- How well does the candidate communicate?
- Personally, I like to ask what the person has been doing to improve their skills, on their own. Reading books? Working on an open source or their own project?
- Will this person fit in with my team, and the company at large?
Amongst other things unrelated to "How well you know X."
The best tip though, is to hire physicists. They're cheaper, sexier, smarter,...
Sexier and smarter, certainly, but I don't know about cheaper. Maybe better to say "a better value"? :)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|