I think part of the problem is this description from a recent posting of yours for "Senior PERL Developer & Conusmer Services Lead":

We are seeking an experienced Internet developer to lead the developme
+nt 
of our high-traffic Web properties including WhitePages.com, 
WhitePages.ca, and PhoneNumber.com, as well as hundreds of affiliate s
+ites.
You must be passionate about web applications, scalability, and the 
end-user experience. You will write technical specifications based 
on product requirements documents, and both oversee and participate 
in the implementation of those products. You will work closely with 
Product Management, Quality Assurance, and Operations, as well as 
the rest of the Product Development team, to ensure that your 
sties are available, responsive, scalable, secure, up-to-date, 
and feature-rich.
[download]

From this I gather that you want a web programmer who has some experience with scalable apps. But the rest sounds like generic boilerplate for a programming job with a traditional software development process. It is nice that there is a software development process, but it doesn't really describe what the job will be like. Will the programmer be more of an architect, or a code monkey? Are the projects to be executed by individuals or a large team? Will the apps be built around a predetermined MVC framework, or is this an ab initio project? What is amazing about the work you are all doing? I realize that companies don't want to show their hands to their competitiors, but the more concrete of a picture you can build for prospective employees, the more excited they will get about your job.

Personally, I always look to jobs.perl.org first, because if folks advertise there, they probably are clued into Perl and its community.

---

---

• 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.