Your home node doesn't show your location, so it's hard to comment on the job situation - it is quite industry and location specific. If you find some financial institutions or publishing companies there are bound to be perl positions going. Take a look at the jobs.perl.org and whatever general job site serves your location.
Certifications? If any applicants I review have certifications my tendancy is to be more sceptical of the rest of their CV. If you're a Cisco engineer, sure, certification is important, but not programming. I'd be more impressed that you had, say, read the back catalog of the perl journal, or perhaps built a website using a web framework of your choice. The second bonus of doing the latter is that you have some sample code to give recruiters - some employers ask to see that.
Note that I'm not saying you can't test basic coding skills. I personally give all candidates who make it to first interview through a set of written tests and on-whiteboard interactive problems. If you've read the Camel book cover to cover and put some of it into practise in code you're in good shape.
-
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.
|