There aren't really, and it's a perpetual topic of discussion. Mostly someone says, "Hey, it'd be nice if . . ." and most everyone else says, "No that's inane." And nothing's done, until n months later when the next poor soul comes out of left field and brings it up again. Lather. Rinse. Repeat.

(That being said, using "PERL" would most certainly fail you were there any worthwhile ones . . . :)

Update: Judicious googling brings up Perl Certification revisited as probably the most recent thread here.

I managed to pass both with flying colors despite the test being just awful. The questions were worded confusingly. Some of the answers on the "best answer" questions were subjectively chosen, and with Perl 4 idioms in mind (this was after 2000). The certification test tend to be no better than the "What do you know about Perl?" articles online (and not as good as the ones from O'Reilly or from The Perl Journal).

So, I'm a certified Perl programmer twice over, at the request of two different companies that had no faith in the certifications. I'm pretty sure Larry Wall, Randal Schwartz, Allison Randal, and Damian Conway haven't bothered. I'm not saying I'm a terrible Perl programmer, but really... wouldn't you rather have one of the other people mentioned writing your code?

Entry Level Perl Certified....... $25

Guru Level Perl Certified...... $75.... free business cards included.

See Perl Certification revisited

As others here have said, most Perl certifications - or, for that matter, most employer tests for programming ability - are inane. At one point, when $COMPANY wanted to hire me (I wasn't all that interested, but figured I'd see what they had to offer), they asked one of their people to vet my Perl knowledge. The questions he asked me mainly demonstrated his ignorance of Perl as well as his ignorance of the interviewing process. One sequence that I really treasure was when he asked me what the variable types in Perl were. When I read off the mantra of $, @, and %, and possibly & (and even cited the relevant part of "perldoc perldata" from memory), he hemmed and hawed and insisted that I missed one - then insisted that filehandles (not even globs, but specifically filehandles) were a "variable type that was introduced in Perl 4" (!!!) The interview went nowhere after that point, of course - their "programmer" decided that I didn't know Perl based on this "evidence".

It's worth noting that $COMPANY is one of the largest, richest companies in the world; I'm certain that they have plenty of Perl and interviewing expertise on tap - but their clueless behavior arbitrarily reduced their pool of available talent. Dumb.

-- 
Human history becomes more and more a race between education and catastrophe. -- HG Wells

I like it that way.

You could get a couple of other certificates, and say that you still prefer to program in Perl.

I like to show off my certificate from http://expertrating.com/. IMHO certificates are just a shiny button saying "You know $something!". Especially that one, anything over 50% and you're "certified."

I very much agree.
I've got a certification there also and I can say there's
not much to it and it's not worth much,also I wouldn't know
if that(expertrating) or any other perl CERT is recognized anywhere.
At least Larry Wall says: If they want to get certified and somebody wants to certify them, that's fine. I just don't want to do that myself.

My wife thinks I'm certified in Perl - well, certifiable anyway.