I think that the most important hing is your knowledge and skills.
Once I've been working as an advisor - the company wanted to know who (i think) would fit the best. We had a guy with a certificate that 'confirmed' his skills; skills he learned at the course and used as a template - and he had nothing to show (except his certificate). Immediatelly after he left the room, we have wasted his application. Why? The certificate is only a piece of paper - the real value is knowledge and skill! If company likes you 'offer' then you get the job :-)

Update: Sorry for duplicate entry - my browser had critical error and by mistake I've wrote my reply second time.

Good luck!
Greetz, Tom.

In reply to Re: Suggested skill set for aspiring perl programmer? by tmiklas
in thread Suggested skill set for aspiring perl programmer? by DigitalKitty

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.