And I prefer your responses when they consider the whole response, not dismiss by selective reading.

I wasn't putting "words in your mouth", nor suggesting that you would base your judgement soley upon the statistic--but it does happen.

I remember a situation a few years ago where I had submitted my CV for a post that was almost the exact twin of the role I was just finishing. I never heard anything. Then a month after I had taken another position, the company rang me asking about my availability. It turned out that the pre-vetting of CVs had been done by the human resources department--counting keyword matches. There were two of the 12 acronyms on the job description that failed to appear on my CV, and it was rejected at that stage.

When the interviews had been conducted and no suitable candidates found, the department manager had asked to see any rejected CVs and was astounded to find mine had been rejected. (His words.) The two missing acronyms were internal-use-only systems that no one from outside the company could ever have had experience of. Essentially boiler plate requirements added to all job descriptions by the HR bods. Most of the accepted CVs had been submitted through agencies aware of this, and they had added them to their submitted CVs. Mine was sent direct. The department manager was very angry, as I was already committed to my new post.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^8: Some reflections on the Brainbench Perl Test by BrowserUk
in thread Some reflections on the Brainbench Perl Test by metaperl

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.