If you work in I.T., and are technical be it network, security, programming or the multitude of specialties within the field, have you ever gone in for an interview and been given a test? I have. A month or so before accepting my current position, I came in for an interview at a certain consulting firm. They surprised me with a test. While I passed the test (I even pointed out how their test was flawed), the entire experience was disheartening and a waste of time, for me, the interviewer, and the consulting firm. First I’ll explain the test and what happened, then I’ll give my thoughts on why testing in general in these situations does not work.
I had two telephone interviews with a consulting firm over a hour each. During both interviews the general manager (we will call him Pete) made a statement that my resume did not seem technical enough for the position. That statement should have been a red flag for me that the company is not very good at reading and hiring people that are technical. Anyone that knows me, would never make that statement and if you actually read my resume you would easily see that. Nevertheless, I explained that I was in fact technical, and gave Pete a couple of examples of technical situations I had been involved with previously. I repeated this during the second interview when he again questioned my technical skill from my resume albeit the response was more curt than previous. At the end of the second interview, Pete decided that he wanted me to come to their head office to meet face to face with the staff, get a tour, and chat some more. I agreed.
The following week I drove two and half hours to the head office. I arrived 5 minutes before my scheduled meeting time. The receptionist said they were expecting me. After a quick phone call, she told me Pete would be out shortly. Pete was ten minutes late (red flag number 2). Finally Pete came to get me, we shook hands and he brought me into a board room. He never apologized for being late, didn’t even mention it (red flag number 3). We sat down and engaged in some small talk conversation. Then Pete mentioned that we were just waiting for another employee (we will call him Kingsley) to join us momentarily. There was something in his face when he said that that bothered me. He seemed guilty (red flag number 4), but I just assumed I mis-read him and we waited for the arrival of Kingsley.
Kingsley arrived with a laptop in hand. We shook hands and he sat down. I got the impression he was more nervous than I was. Pete said that Kingsley was going to ask me some questions and give me a test and he would be back afterwords so we could continue our conversation. A surprise test, wonderful (Red flag number 5)! Kingsley was a nice guy. He was uncomfortable, but that might just have been lack of experience in an interview situation. He put the laptop in front of me. On the screen he had three virtual routers and requested that I set up some dynamic routing using weighted variance. His specifications of what he expected were precise, right down to the protocol I was to use, EIGRP. Fortunately, I had done a lot of work with EIGRP in my past. Back then, a colleague of mine who was a Cisco employee had forwarded me papers on the inner workings of EIGRP as I had to set up a rather large network using EIGRP. I had read and made certain I understood all the details in those papers. Unfortunately, that was about six years ago.
I configured the routers and got them all talking and routing using EIGRP with Kingsley looking over my shoulder the entire time – that is very nerve racking even if you are comfortable and know what you are doing. While I managed to get it working for the most part, I was getting an error when I tried to configure one of the interfaces to accept routes from another router. It struck me as odd because although it was six years ago, I specifically remembered doing this part on live systems and was confident it was correct. I asked Kingsley and he said that I was missing something. When I asked him what I missed, he said he could not tell me. The thing was that his face told me he didn’t know and he was lying (red flag number 6). He also looked somewhat confused by the problem I was encountering.
Kingsley dropped me off in reception and went on his way. The receptionist then informed me that I was done and could leave as Pete left the office already (red flag number 7). I drove two and a half hours for a surprise test, didn’t meet the staff, did not speak to Pete or anyone else about the opportunity, and was not given a tour. I was not asked if I had any questions or concerns and Pete had already left for the day. I drove two and a half hours back home furious. At this point I knew I wouldn’t work for this company. I don’t work for anyone who treats people that way, period.
The test also bothered me. I was positive I was right with the interface configuration. That evening, I drove to a friends office who has some real routers and equipment available and set up a quick lab. The lab was exactly the same setup as I was presented in the surprise test I was given earlier that day. I had no errors, and the interface configuration that was not working on the virtual test worked in my real lab. I even found an online document from Cisco that supported my interface configuration.
Normally, I send a thank you email after I have had a face to face interview out of courtesy. I crafted a thank you to Pete and Kingsley. First I told Pete I was sorry we were not able to have a chance to talk and he was unable to provide me the tour of the facilities he promised. I thanked Kingsley for his time and I explained to him that the test he asked me to do bothered me so much that I tried his test with real routers and it worked. I sent him screen shots, step by step instructions and the configurations of each router so he could see that it worked and replicate it if he chose to do so. Finally, I suggested that he might want to check his virtual setup. If there were other candidates interviewing they may not be able to complete the testing due to a problem with the test setup. Kingsley responded and said that he was impressed I took it upon myself to figure it out after the fact and acknowledged their was a problem with the test and he would be fixing it.
This entire interview process was awful. I felt like I was dis-respected, my time was not worth anything. If companies want to retain dedicated employees that are good at what they do, this is not the way to go about it. What can I and others learn from this experience? Here are the key items that stick out in my mind.
Get assistance from someone that is technical if you are not. Many people feel they are ‘technical’ and have what it takes to determine technical skill, yet are not technical themselves. As such, they resort to looking for specific technical jargon on resumes, often comparing the format and words found on other resumes of employees that were considered good in the past. This makes no sense. It is not fair the company hiring, nor the candidates that are selected. I have a basic understanding of how the human heart works, but I am not a heart surgeon or a doctor. It is safe to say that having me review resumes of heart surgeons for their understanding of the human heart and how it relates to a position on a hospital surgery team would be silly. Following the same logic, it makes no sense having a non technically experienced individual attempt to question or assess someones technical skill. Let a technical person do that part.
Testing is degrading and insulting. Even though I have an excellent understanding of routing, specific large scale experience with EIGRP, and was able to show them their test was flawed, the experience was negative and I felt insulted. It was as if they were questioning my integrity. Acting as if I might have mis-represented myself on my resume. Regardless of the outcome of the test, the interview process was already over in my head. I can’t work for a company that works in that manner. I have consulted for companies that have that general outlook and it typically proliferates in their day to day processes and dealings with employees and often clients. If a lawyer with ten years experience was applying for a position in a law firm and they came highly recommended with an impressive resume, do you assume off the bat they are mis-representing themselves and test them? Getting an understanding of their experience and thoughts is one thing, testing is another. Most lawyers I know would walk out insulted. Yet in the technology industry this seems acceptable to some.
If you must test then be please smart about it. I would argue that testing during an interview process is absolutely not necessary if you know how to effectively interview and by testing you reveal your lack of expertise in how to interview. If you feel you absolutely must test then take the time to at least make the test relevant to the candidates as well as the company. In the testing experience I described, I assume their goal was to understand how good I was at designing and working with routing. EIGRP is not the routing protocol I know best. It would be the one I understand third best. BGP is by far the first. Next is OSPF, then EIGRP. It would have been better for myself and the company if they had not specified a protocol. Instead, allow me to choose what protocol would be suited best to solve the problem and solve it. If you are hiring for a consulting position, which they were, that is easily the more valuable skill. Testing me the way this company did highlighted their lack of experience consulting, interviewing and their lack of expertise as a company.
The interviewer and company are being evaluated as well during the interview. This is probably the most important point. You need to ask yourself what impression are you giving the potential candidate? Are you putting your best foot forward and showing them why they want to work for you and your company? Candidates can go elsewhere and good candidates will. I personally believe that one of the reasons (not the only one) why many tech companies and start-ups want young people is that the older ones have experience to know what type of company they want to work for, what characteristics and experience of management they will work under and what conditions they will not. I’ve consulted for many tech companies where their management is in-experienced compared with companies in other industries.
I can compare and contrast this experience to another interview I had for a small consulting firm in the same time frame. The owner was friendly, technical, treated me with complete respect. We had a great conversation. He was able to find out about me, my experiences and my technical abilities. I was able to learn about him and the company. Very positive experience for him and myself. No test, no surprises. They were an amazing small consulting firm.
If you are a person that interviews for your company or a recruiter representing a company, what impression do you leave with the candidate after an interview? Is it positive or negative? Do you care what impression you leave?
photo courtesy of …
Through school and reading I have a basic understanding of how the human heart works, but I am not a heart surgeon or a doctor. It is safe to say that having me review resumes of heart surgeons for their understanding of the human heart would be silly. Following the same logic, it makes no sense having a non technically experienced individual attempt to question or assess my technical skill. Let a technical person do that part.