I was at a meeting of the EE Program Advisory Committee at Conestoga College Friday morning, and talk turned to certifications.
I voiced the (possibly radical) idea that certifications are almost useless unless it's to appease an HR person ("Each candidate must have A, C, B, D, E, F and G.") I was pleasantly surprised to find that everyone at the meeting agreed with me -- certifications generally mean that you're book smart and that you passed an exam. They don't provide much support for how smart you are or what cool problems you've solved recently.
For me, the best interview process is one that's part closed questions, perhaps to expand more on their resume .. and part open-ended questions, where you ask them to go up to the white board and do a presentation on some problems they've solved lately. If they've got what it takes, that presentation should be a pleasure to listen to -- if not, then they're not cooked yet. Thanks, and we'll be in touch.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
-
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.
|
