What we're saying is that for potential employers who don't just take the short cut of "oooh, certification = good", which we believe is bad practice, and we're arguing that a certification, to us, is a potential red flag; and before an interview you should find the people needed to probe into whether they actually have the technical chops to back that certification; but you should already have those people in the interview whether or not the applicant has a certification.
If they have the cert, and the tech chops, great, most people will add merit points to the person with the cert over the one without the cert.
I think it can be boiled down to this: as an employer you should be at least as suspicious of those bearing certifications as anyone else you interview; it should not be an "E-Z pass" into the company.
-Scott
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.