Tag Archives: jobs

Interviewing and Being Interviewed

For the past 2 months, I have been interviewing candidates for 3 different positions: Business Analyst, Test Engineer, and Software Developer. The candidates that I interview are first vetted by headhunters, then their resumes are reviewed by me for specific job skills. If they pass those two checks, I act as gatekeeper and perform an initial interview to determine whether they will be considered for the job. This process means I’m not interviewing the candidates who have no matching skills.  But there is still a great difference between the candidates.

My questions tend to focus on 3 areas for each interview: what experience can you show me that matches the qualifications I’m trying to meet, how do you handle difficult and/or complex situations on the job and what job specific knowledge do you possess.

Headhunters have seen the same job listing that I’m working from when I interview a candidate. So I’m always surprised when that candidate has no experience in one of those job areas. Mind you, I will hopefully catch that when I review the resume, if the headhunter hasn’t. But I will sometimes give the candidate the benefit of the doubt if I see similar items listed on their resume. But, if I then talk to the candidate and they have no experience in that area, I see this as a waste of time, both for me and for the candidate, since they are not someone I can consider hiring.

The knowledge I’m looking for is more the book learning – type of information; the type of things you learn in school and let you communicate with like-minded professionals. We all hate the tech-speak of others. But we have all learned that the tech-speak helps us communicate effectively with like-minded individuals. If you don’t know what a tool is that is common to your profession, or you don’t understand a term I use that is in wide application within your profession, I will not look favorably upon your candidacy.

I do have a pet peeve for this one. I am a technical person. I am frustrated when the person I’m interviewing talks to me as if I do not have that background, but rather as they would talk to an ‘outsider’, someone with no technical skills. Sometimes I thinks it’s because they don’t understand the concept well enough to explain it. Sometimes I think it’s because they’re not used to ‘talking tech’. Frankly, they need to get over that.

Lastly, I will as ‘what if’ type scenarios. If the person has experience with those, I want to hear how they were handled. If they don’t, I want to hear the logical thought process they would go through to come up with a solution.  If they have been through the given scenario before, I will often try to come up with others so I can see how they’ll handle a ‘new’ situation. If they have been through the situation before, I want details. This is their place to shine because they are showing how they overcame a difficult situation. I was using checkmarks for the job skills. I will be looking for how much you understand a situation and can relay the solution for this question.

Many times, an answer may be good for several questions. For example, a ‘what if’ may also help me see that the person has the technical vocabulary I’m looking for, or that they have had the experience that the job requirements asks for. Hopefully I won’t then ask a question that requires a person to repeat themselves.

It’s interesting that I have seen, after many, many interviews, that there are certain personality types that make a good interviewee for each position. For the analyst, I want a people person, for the tester, I want a very detailed person and for the developer, I want someone who can get ‘into the weeds’ when it comes to technical matters.

The analyst needs to have both technical knowledge and people skills. They are primarily involved in helping to articulate the requirements from the stakeholders and convert those into a technical solution. For this, they need to be able to talk to people. The candidate that I find that does best then is the one that I can hold a conversation with. They will easily elaborate on any answer. They will be perceptive enough to see the point of my question and be sure to hit that point with their answer. They will understand the ‘big picture’ and their questions to me at the end will show that.

The tester better be detail oriented. Their job is to find problems with a project before the stakeholder, or the end user, does. If something slips through, they are often the ones that are blamed. When I talk to this person, I expect steps 1 to 3 of their explanation will have several subparts. I will not need to ask them to elaborate because they have probably given me more information that I expected.

The developer may be the person with less people skills than the others. Often they are the person who I need to ask many follow up questions to get answers. But, when I ask those follow-up questions, it is often of a technical nature and I expect a technical response. I want you to explain to me how your thought processes worked. I want you to help me understand where the difficulty lay and how you resolved it. I want to know that you can do better than the monkey in front of the keyboard writing Shakespeare. I want you to show me you understand why a certain technology you use is the better choice for the problem given.

Many of the candidates I interview do not speak English as their first language. Practically speaking, that means I’m dealing with an accent. For this reason, I try to conduct video interviews whenever possible. That way, I can read lips to help me understand what they are saying. Video interviews also help me see the person’s body language as they speak. Are they confident? Are they struggling to answer my questions? Are they expressing a passion for their chosen profession?

The down side of any remote interview – video or voice only – is the person with the lousy connection or the poor equipment. Please people! This is a technical job that I’m interviewing you for. If you can’t figure out how to connect, or how to be heard, I will think less of your problem solving abilities. The current positions are remote, which means you’ll spend a lot of time in video or voice conferences. The others on the call with you will not put up with this nonsense!

The best interviews? When I interview someone with ‘that spark’. They are passionate about what they do. They are perceptive in their answers. They are engaging.

The frustrating interviews? When I interview a great person, who is not great for the position for which I’m seeking candidates. I wish I could put you in my pocket to pull out at a later date. But I know that you’re good enough that you’ll have had several great offers before I can talk with you again.