We have great expertise in supporting companies and candidates in their social recruiting and talent hunting journey, alleviating the “skill gap” issue. Our capabilities and our problem-solving approach are proven by the appreciation of so many customers. Let’s have a talk!
On this subject, here is an article about the hiring for skills vs. hiring for potential: Those working in the tech industry say the perennial skills shortage stems as much from firms’ sky-high expectations as it does from a dearth of manpower. 
If you were hiring electricians, would you expect them to be a dab hand at plastering, proficient at carpentry and a competent carpet fitter? Probably not, so why do recruiters expect developers, sysadmins and other IT workers to have such a ludicrously wide range of skills?That was the question asked by TechRepublic readers following a recent article on IT skills shortages.
Those working in the IT industry say job ads frequently demand a skillset so large or so specific that very few applicants can ever match up.
“Recruiters look for unicorns who match their 27-point wish list and don’t read in depth or talk to anyone to find out what they’re about,” said one reader.
“And heaven forbid you don’t have the latest framework that got hot a year ago, even if you have decades of experience and have learned a dozen languages.”
Readers listed examples of non-sensical or impossible expectations, including a post for a Linux Sys Admin role demanding someone with skills related to Windows sysadmin, systems engineering, devops, sales, level 1-2-3 support, C++ and Java programming, network engineering and network operations.
In general, firms have a tendency to want to hire fully-formed employees from day one, rather than someone they train up on the job, according James Milligan, director of IT recruitment for the UK and Ireland at Hays.
“Organizations tend to want to hire the final product, rather hiring people with the competencies to do the job,” he said.
“So you end up with these job descriptions which are long shopping list of skills, which, if you look at the open market, are not readily available.”
Even if someone were available with 100 percent of the skills needed to do a job, they’d be unlikely to apply for it, he said, because there’d be no personal development.
“What they [businesses] should do is employ somebody with 50 or 60 percent of the skillset, where there’s a lot of scope of personal development for that individual,” he said.
“They need to be a lot more open minded in terms of the type of person they’re looking for and the amount of investment they are prepared to put into them.”
Compounding firms’ unrealistic expectations of applicants, according to IT workers, are HR employees who are often engaged in little more than a box-ticking exercise when it comes to assessing an applicant’s skills, without understanding how those skills relate to the role on offer.
“This situation is magnified drastically by the non-technical gate keepers (recruiters) that have no clue how to evaluate someone technical, other than compare the brand names of each software tool to a list that has been given to them,” said another TR commenter.
“For example, someone that may have a PhD and have done a dissertation on inversion of control (IoC) cannot get a job because the company uses Spring and the student has not used that particular IoC container.”
Another tech industry worker and TR commenter reported that HR at his firm tweaked a posting for a technical role to add requirements that “we didn’t need, never mentioned and didn’t go along with the position”.
“It took some convincing by our boss to get HR to change some of their wording. And this isn’t a new phenomenon.”
Others blamed HR for misunderstanding the scope of the IT role being advertised, for example, asking for every skill on a list given to them by a technical manager, when the manager is seeking someone proficient in just one of those skills.
Hays’ Milligan described the problem of non-technical gatekeepers blocking good candidates as “a fundamental issue in large organizations where technology is not their core function”.
“Look at more traditional organizations, say a bank, where recruiting technology people might only be 10 to 30 percent of the job. They firmly have issues with understanding that whilst a CV says ‘X, Y and Z’, it also means that person can do ‘A, B and C’. They don’t understand the context of technology.
[to continue, click HERE]
