History and Brains
I won't pretend this is a new issue, or something that 'our generation' started, but I suspect it has gotten worse over time. First of all, economics and social history is a part of this. Speaking specifically of the United States, after the 1950s, most of Europe was in a economic ditch due to the destruction from World War 2. People could easily get jobs and brought up the 'baby boomer' generation. The US invested a lot into tech, and made a large number of advances. Without digging deep into the history, the boomer generation slowly amassed wealth and was able to assist their children to go to college and unlike any other time in history, the US population mostly has college education. Unlike many areas in the world, in the United States it is often the case that you take out what is effectively a long-term loan for education. While this is overly broad, many people excepted quick success or ignore the bill until after they graduated. The US slowly moved away from manufacturing jobs, leaving us with many 'service' jobs, like changing oil and child care. One of the few other sectors with significant growth was tech. Also part of the cultural zeitgeist was that the boomer generation encouraged a belief in their children of being special. With large debts from school, few places to work (that pay well) and unreasonably high expectations in life, much of the younger generation has been forced to compete in an environment they were not prepared for. Add in pressure from social networks where your successful friends are highly visible, and lying to get a job might seem like a way out and up.
There is another real set of reasons involving the brain. The first one is, many of those who lie on their resume are young. They have little life experience and don't have a sense of the possible consequences. They also don't have the brain to handle the risks. Literally, those who are young enough don't have as many connections to the executive part of the brain and make dumber choices. It is also why crime trends towards youth as well. Notice how the drop off age is about 25. About the same time the brain develops.
Another factor involves the Dunning-Kruger effect, people don't know when they aren't very good and when they are very good they think less of themselves. Those who don't know there lack of skill think they are amazing, so they tend to inflate their resume with less truthful statements. Worse yet, since they are lying to themselves, they are in some ways more capable of lying to others. Those who are more knowledgeable tend to know how little they really know. They therefore seem less capable, which helps bolster the case of the less skilled.
Employers Worst Enemy: Themselves
The final factor is the automated checking of resumes that looks for keywords in a resume. Sometimes playing alphabet soup can help you get a job. If you have little to no experience, alphabet soup is about the best bet you can make. If you can back up the claims even a little it might make sense to do so. Sometimes this is referred to as 'Embellishment'. However, that can become a slippery slope. In what might have been the worst interview I ever observed, in looking to find an upside, my coworker choose a technology the candidate had listed and asked him to talk about it. The resume had categories, like 'familiar' and 'expert', with this technology being marked as expert. I believe it was Tomcat servers, something I think most of us were not expert in and was not used in that company, so we were not evaluating his actual knowledge. His first comment was that he only used it in a testing context, and that was how he was an expert. So we asked how he'd find a bug in said system, or how he'd get updates deployed. The best answer we eventually got after digging into his background was other people did everything for him.
But what did we do? If he was smart, we taught him perhaps how to answer that form of question better without ever learning any of the tech he claimed. In essence, even though we didn't hire him, he could learn the wrong things from that interview. Worse yet, while he didn't get our job, we had no way of notifying other employers of his behavior. We couldn't say how we caught him in several lies because his former employers included employers we had, so we knew some of the work was not his.
From an employers point of view, when they are first hiring, it is not unlikely they don't know what a good tester looks like. They do some web research and come up with a list of properties that sound reasonable to them and come up with a job description. If you follow the CDT view where things depend on context, it will be hard for an employer to ask smart questions. Worse yet, ISTQB is about the only thing an employer might be able to use to filter with. Ignoring my personal opinion on the value of such a cert, since an employer probably doesn't know much about testing or ISTQB, they are not likely to go doing the validation of such a certificate. If someone feels ISTQB is of little value, they might justify in their head, "My employer won't know the difference."
The employer is more likely to offer on the low end of the pay scale, even if they want experienced people. Sometimes this is because they can't afford anyone more advanced, else they would already have a test team. Other times it is because they are small and thus don't have enough cash to afford senior people. Even if they have a test team, not everyone treats this as more than a job, and might not take their interviewing seriously. This allows beginners in, as well as those whom lie on their resume. In my experience, often these sorts of companies also have death-march-like development processes because the company has not matured. This makes it so that many newer recruits end up leaving. Another area where this happens is in contracting. When you need 30 testers in seats and you are contracted to have them, or your pay is tied to the number of people, you have a conflict of interest between hiring just anyone and keeping the customer happy. You might hire a few 'iffy' people because you can hide them in the middle of some better employees.
What Do We Do?
The truth of the matter is I don't know that we can as a society eliminate this sort of low-level corruption. I worry as automation gets better and less high paying jobs come available what sort of world we will live in. One likely result is with increased competition we will see an upswing in this sort of falsification.In trying to evaluate my own predictions, I tried to find any data around trending, to see if this problem is in fact getting worse. I couldn't find anything substantial, but a variety of different percentages were thrown around and nothing that felt authoritative. The one thing I did notice was the numbers were typically large, like 40% of resumes have some form of fraud in them. Okay, you caught me, it was 39% with other numbers on that page lower. Oh, and that was percentage of organizations, not resumes. Darn, you're reading up on my data now? I just wanted to make the number seem more round and dramatic. What's wrong with that? The point is, we all have to be careful with our language and clear on what we expect. I imagine you expect that I try to get my facts straight and while some rounding might be implied, that the unit of measure would remain consistent. For example, culturally, Latin Americas commonly include pictures with their resumes, while in the United States, that is unusual. So if you send a resume to Latin America, you better include a picture, as that is the norm. I know no one of us can set such expectations, but you can set them for yourself and ask about unclear parts of resumes that don't seem to follow your standard. We have to make honesty the norm by being honest ourselves.
Obviously if you are having people ask you about advice regarding lying on your resume, the answer should be no. I have given recommendations for people, and I have had one friend list work he did for me in his resume when I was about 16-18 years old. He actually did do some testing, but it was not for a formal company. I said he could because he did the work, formal organization or not. Some people might see that sort of buddy system as flawed because you can use contacts to get jobs, but those without contacts are disadvantaged. I have even heard claims that this can be accidentally racist/sexist, based upon who you know and trust. The fact of the matter is, that hiring people you know and trust has always been a thing. The reality is that hiring based upon personal knowledge of someone else's previous work is one of the best filtering mechanisms. Hiring based in part upon the recommendation of someone you know is probably helpful. Dr. Kaner suggested a entire packet of stuff be used to track someone's career, but that doesn't help much for those starting off. Perhaps a broader network, like that of Dr. Kaner or LinkedIn is also of value, but that only helps vet people you know. I recognize that some people may disagree with the idea of hiring people you have formerly worked with, and I welcome discussion around that. I think it is better to have an open discussion than for me to stand on my soap box and expect you to just accept what I say.
There are two things we can do today for every candidate. The one easy thing we can do is be careful with our hiring. Get to know the candidate, ask lots of questions, and in the end, if you aren't sure, don't hire them. I know that can hurt candidates, but I think it is important to choose the right person rather than getting the wrong person but moving faster. The second piece is to investigate the claims of a candidate. While I think it is better to do so in an interview, even after an interview, if a candidate makes a claim, it isn't too late to go look into it. Better to spend ten minutes now than waste 6 months with them and another 3 months trying to get rid of them. If that means calling the candidate to ask them a question, get on the phone and call.
While most of this has been about the interviewer insuring they are not being lied to, the candidate too should be concerned about the company. From a candidate side, ask detailed questions, and dig into the details. What is your bug count? How much does it vary? What flaws are there at the company? What strengths? And again, don't assume the interviewer isn't embellishing in their answers. I don't think any interviewer would say "It's hell here. Go somewhere else." So investigate the company and the workplace environment.
Ultimately, you have to work with either the candidate or the people interviewing you for 8 hours a day, for a long time, so choose wisely.
No comments:
Post a Comment