Tag Archives: interview questions

Before we can interview for interest and passion, we have to define the work. It’s always about the work.

Most S-III roles are system roles, building systems that don’t solve problems, but prevent them. The tools at S-III are work flow diagrams, time and motion studies, schematics, sequencing and planning. The role is typically the manager of a functional team (marketing, sales, business development, estimating, operations, QA/QC, warranty, research and development, HR, legal). Longest time span goals and objectives would be 12 months – 16 months – 20 months – 24 months. Learning would include analytic. Highest level problem solving would include root cause and comparative analysis. Value-add to the organization is consistency and predictability. It is the role at S-III to create the system, monitor the system, constantly improve the system. One of the most important systems at S-III is the people system inside the function.

Managerial roles at S-III are accountable for the output of the team at S-II.

Given a large customer problem, the central question for the S-III manager is, why didn’t our system prevent that problem, or at least, mitigate the damage from that problem.

Interview questions –

The purpose of these next questions is to look at some of the systems you built and how you built them. Tell me about a project you were accountable for, containing several steps, that was similar to other projects you completed in the past?

What was the project?

What was your role on the project?

How long was the project?

Using this project as an example, tell me about a system you created to solve its problems and make its decisions?

What were the circumstances in the project that lead you to create a system?

Step me through the system that you created?

How did you communicate the steps in the system to the team?

How did you test the steps in the system to make sure they were in the best sequence?

During the project, did any of the steps in the system change?

When steps in the system changed, how did you track the changes and modify the system?

When the project was totally complete, what parts of the system could be applied to other projects?

Think about the next project where that system was useful?

What was the project, why was that project a candidate to use the same system?

What modifications did you have to make to the system, so it had a positive impact of this next project?

How did you document the modification to the system?

How was this system important to the effectiveness of your functional team?

Tell me about another system you created related to a project in your company?

Each of these questions asks for a specific piece of data about the candidate. And though we are trying to find out about an attitude or feeling, the questions are still laser focused on the work.

“The new guy just doesn’t seem to fit,” Cynthia said. “Our company is built on a culture of teamwork. He doesn’t seem to be a team player.”

“You hired him. What questions did you ask about teamwork?” I wanted to know.

“Well, I asked him if he thought teamwork was important?” she replied.

“And?”

“And, he said yes. He said teamwork was very important at his last job.”

“What did you expect him to say?” I pressed.

“Well, I wanted him to say teamwork was important, because, to be successful at this company, we have to work as a team,” Cynthia insisted.

“So, the candidate gave you the response you wanted to hear?”

Cynthia was silent.

“Look, teamwork is a state of mind,” I nodded. “It’s like an attitude. You cannot interview for an attitude. You cannot interview for a state of mind. You can only interview for behaviors connected to that attitude. Ask yourself, how does a person, with an attitude of teamwork, behave? Once you identify connected behaviors, you can ask a better set of questions. So, what are some behaviors connected to teamwork?”

Question:
All of our projects are different. We never know what our customers will want, in advance. It’s almost always a custom solution. So, when we are hiring a project manager, it’s difficult to determine what skills the candidate will need to be successful. That’s why, most of the time, we wing it, when it comes to interview questions. How can we do a better job in the interview, instead of just working off of the resume?

Response:
We may not know anything about the project, but we can still work on preparedness. So, think about behaviors connected to being prepared.

Diagnostic questions

Project planning

Short interval planning

Project adjustments

Discipline

The only way to work through an ill-defined or unknown project specification, is to define the project. You are accurate, that many customers don’t really know what they want. Sometimes your best contribution, in managing the project, is helping the customer to define the project. What are the problems to be solved and the decisions to be made as the project meanders its way to completion?

Question:
You told us not to hope. You told us not to look in the eyes of the candidate. You told us not to make the decision in the first three minutes of the interview. All you told us was what NOT to look for. But, you didn’t tell us WHAT to look For!!

Response:
Look for something that sits in front of our eyes. And yet, we cannot see it.

It is easy to observe behavior AFTER the candidate shows up for work, we can see the evidence of the work product, and we are often disappointed. We made the hire based on hope, based on what we thought we saw in the eyes of the candidate, and made that decision in the first three minutes. We made our decision BEFORE we had any data.

The question is, how do we get that data, how do we get that evidence in the interview? It is, as easy to see in the interview, as it is to see in the work. No, we cannot directly observe, but we can certainly ask questions that allow us to observe through description.

The problem is that we don’t ask questions related to behaviors in the role. We rely on stupid stuff that we, as interviewers, interpret about the candidate. We use trick questions. We try to climb inside the head of the candidate. STOP. Don’t play amateur psychologist.

But, we are experts about the work. We can spot positive behavior on the plant floor or in the field. We can spot negative behavior, and it takes only a nanosecond for us to tell the difference. Why? Because we are competent managers.

Don’t play amateur psychologist, play to your strength as a manager. It’s all about the work. We don’t see the evidence in the interview because we don’t prepare to ask the right questions, because we don’t prepare to ask enough questions. So, we rely on faulty assumptions, like hope. And because we don’t have the right questions, or enough questions, we make the decision in the first three minutes.

What to look for in the interview is EVIDENCE. And most interviewers don’t ask enough questions to gather that evidence. -Tom

Hiring Talent Summer Camp is launched. Today is the last day for open registration. For more information and registration, follow this link – Hiring Talent Summer Camp.
______

On Wednesday, we talked about the Spirit Animal interview question. Sparked a bit of response.

I do see the humor in this question, and on the surface, it does seem silly. However, there may be more to the question than you think. I had a manager tell me they ask silly questions like this, not to judge the surface response, but to evaluate how the candidate reacts to such a silly question. Do they roll their eyes disrespectfully? Does it take an exorbitant amount of time to come up with an answer? Are they creative with their answer? Do they panic and start sweating? Are they a quick wit and come up with a novel response?

Interviewers misinterpret candidate responses because they ask questions which require interpretation. The Spirit Animal question will get a response, like rolling eyes, a long pause, panic sweats, snappy answer. But what does that response mean related to the work in the role. We don’t know what it means and any attempt to interpret the response places us in the position of playing amateur psychologist.

Most managers don’t have a degree in psychology, certainly not a Masters or PhD in psychology. None are certified by their respective state to practice psychotherapy. Most managers stink at it.

But managers are expert at spotting positive work behaviors, expert at spotting negative work behaviors. Don’t play amateur psychologist, play to your strengths as a manager. Ask questions about the work. It’s all about the work. And never ask about a person’s Spirit Animal.

Mine is a python that starts with a wrapped embrace, then squeezes the life out of its unsuspecting prey. -Tom

Hiring Talent Summer Camp is launched. And there is still time to climb aboard. Registration ends on Friday. For more information and registration, follow this link – Hiring Talent Summer Camp.
______

Rifling through my archives –

I was shocked this morning to read an article posted on LinkIn. The Strange and Difficult Questions CEOs Ask in Job Interviews. At first, I thought it was going to be a spoof article, given the questions that were listed. But, as a I read on, I found that the author was serious about sharing these questions, with attribution to a stoic CEO.

What’s your superpower… or spirit animal?
“During her interview I asked my current executive assistant what was her favorite animal. She told me it was a duck, because ducks are calm on the surface and hustling like crazy getting things done under the surface. I think this was an amazing response and a perfect description for the role of an EA.” — Ryan Holmes, HootSuite CEO

This has to be one of the most idiotic interview questions invented. It’s cute but has nothing to do with the work. Perhaps Mr. Holmes believes he has some divine (psychological or psychopathic) ability to accurately interpret a candidate’s response to such an inane question.

My mother thinks I am amazing, but that doesn’t qualify me for the role.

“So, how can I find out if a candidate will follow our standard operating procedures or if they will experiment using their own methods, wasting our time and resources to find out we were right in the first place?” Melinda asked. “What questions do you ask?”

“What are my two favorite questions?” I asked.

Melinda didn’t have to think on that one. “Tell me about a time when? And, step me through?”

“Okay, so using those two questions, create a series that helps me understand how the candidate will respond when they disagree with work instructions,” I prompted.

Melinda took a deep breath, slowly exhaled, thinking.

Tell me about a time when you disagreed with the way you were supposed to complete a task assignment?

What was the project, or what was the task?

Step me through the specific method you were told to follow?

In that method, what did you disagree with?

What did you do?

Step me through your alternate method?

Why did you think it was better?

Who did you talk to about it?

What questions did you have?

What was the outcome?

“Good questions,” I nodded. “And in their responses, what would you be listening for?”

“First, I would want to find out if they had a real awareness of their work instructions,” Melinda started. “Did the candidate listen to the work instructions they were given? Next, I want to find out the line of thinking about the work instructions. I want to see how respectful they were of their manager or if they simply flew off the handle and did things their way. I want to see how they responded, if it was helpful or if it was counterproductive.”

“I don’t understand,” Ben defended. “For the entire time that I have been responsible for hiring people, I have always used the resume to ask my questions.”

“That’s because you didn’t have any other questions to ask,” I replied. “Here is the biggest problem in most interviews. Without an extensive bank of prepared questions, the judgment about the candidate defaults to how good the resume looks, first impressions and gut reactions.”

“Okay, okay. How many questions are we talking about?” Ben relented.

“You divided the tasks into different Key Result Areas (KRAs). How many KRAs do you have?”

“Let’s say six,” Ben bit his lip.

“Ten questions for each KRA, six KRAs, that means sixty written prepared questions.”

“Sixty questions, are you out of your mind. Who has that kind of time?” Ben said, pushing back.

“You can spend the time, creating questions on the front end, or you can spend the time managing behavior on the back end. The choice is up to you.”