Interview Them Back

Most interview advice treats the last ten minutes as a courtesy.

“Any questions for us?”

This is where you are supposed to ask about culture, professional development and what success looks like, then nod thoughtfully while they give you the answer they have given every other candidate.

It is also the only part of the interview where you are the one gathering information.

By that point, they have asked about your judgment, your mistakes, your leadership style, the hardest thing you have ever done and where you see yourself in five years. You are allowed to find out whether the job they are selling actually exists.

Most people waste the opportunity asking questions that invite rehearsed answers. “What is the culture like?” gets you collaborative. “What do you enjoy about working here?” gets you the people. “What does success look like?” gets you a slightly friendlier version of the job description.

The problem is not that these are unreasonable questions. They just tell you very little.

These are the questions I ask instead, what I listen for and the two I have stopped asking entirely.

The final ten minutes are the only part of the interview where the job has to explain itself.

The single best question

“Who had this role before me, and where are they now?”

If I could ask only one question, it would be this one.

Nothing else produces as much useful information with so little room for a rehearsed answer. There are a few ways it can go, and every one tells you something.

They were promoted and still work there.

Good sign. Follow it.

How long were they in the role? Where did they move? Was the promotion a natural next step, or did they spend six years doing two jobs before somebody finally changed the title?

A promotion tells you there may be somewhere to go. The details tell you how long the trip takes.

They left the company.

Ask why, evenly and without turning it into an interrogation.

A confident interviewer will usually give you a straightforward answer. They found a larger role. They relocated. The company changed direction. It was not the right fit.

A vague answer here is often more useful than a clear answer to anything else in the interview. If three people suddenly become fascinated by their notes, that is also an answer.

It is a new role.

Then ask who has been doing the work until now, because somebody has.

Was it spread across several people? Was one person quietly carrying it without the title? Did that person apply?

If an internal person has been doing the work, wanted the role and did not get it, you may be walking in as their new manager. That does not make the job impossible. It does make the first six months a very different job from the one in the posting.

There was somebody in the role and it did not work out.

That is a real answer, and they may not be able to share the details. What matters is whether they can tell you what will be different this time.

Did the scope change? Did the reporting line change? Are the expectations clearer? Is there now budget or authority that did not exist before?

If the previous person failed and nothing about the role has changed, they may be hiring a different person to run the same experiment.

The question that makes them stop performing

“What would make you say, six months from now, that hiring me was a mistake?”

Most people have never been asked this. You can usually see the moment they stop interviewing and start thinking.

That pause is useful.

A good answer is specific and slightly uncomfortable.

“If you cannot build trust with the platform team, this will not work.”

“If you need a lot of direction, you will struggle here.”

“If you avoid conflict, the problems will sit too long.”

Those answers tell you where the job actually gets hard. They also tell you what the manager is already worried about, which is often more important than anything written in the job description.

A bad answer is reassurance.

“I cannot imagine that happening.”

“You seem like a great fit.”

“We would support you.”

None of those answers the question. It means they have not defined failure, they do not want to tell you what the difficult part is or they are still trying to close you.

All three become expensive later.

Three questions that reveal the actual conditions

“What is the last decision this team made that you disagreed with, and what happened?”

This tells you whether disagreement is survivable and whether the team is allowed to make decisions the manager would not have made personally.

Listen for an actual event. What was the decision? Who made it? What did the manager do after disagreeing?

A leader who says, “I disagreed, they made the call and I supported it,” is telling you something useful about the team’s authority.

Someone who cannot remember ever disagreeing with the team is telling you something too. Either the team is not making meaningful decisions, the manager is revising history or everyone learned a long time ago not to bring forward ideas the manager will dislike.

A team that never disagrees may be unusually aligned. It may also have stopped telling the truth.

“Who else needs to say yes for me to get something done?”

The org chart tells you who you report to. It does not tell you who can stop you.

This question usually gets a more honest answer about authority than asking, “How much autonomy will I have?” Everybody says you will have autonomy. Then you arrive and discover that five people must approve a decision you are supposedly accountable for.

Listen to the length of the answer.

If the list is long, the job may be politics wearing a technical title. That is not automatically a reason to walk away. Plenty of important work requires influence across several groups.

You should know before accepting whether you are being hired to make decisions or spend most of your time collecting permission.

“What is the first thing you would want me to fix, and what has stopped it from being fixed already?”

The second half is the whole question.

Everybody can name the problem. The systems are fragmented. Delivery is too slow. Teams do not trust one another. Costs are too high. Nobody knows who owns what.

Very few people can explain why the problem is still there.

If the answer is that nobody has owned it, fine. That may be exactly why the role exists.

If the answer is that the team lacked a specific skill, budget or decision, that is useful too. You can ask whether that condition has changed.

If the answer becomes vague, pay attention. Something political may be standing in the way, and they either cannot or will not tell you what it is.

Everybody can tell you what is broken. Very few can tell you why it has been allowed to stay broken.

Questions for the manager

“Tell me about someone on your team who has grown significantly. What did you do?”

You are listening for a real person and a real action. They do not need to identify the employee, but they should be able to tell you what happened.

Did they give the person a larger problem before they were completely ready? Put them in a room they would not otherwise have entered? Give difficult feedback? Advocate for a promotion? Protect them while they learned something publicly?

Someone who has genuinely developed people can answer this quickly because they remember the work and are usually proud of the person.

Someone who has not will explain their philosophy.

“I believe strongly in empowering my team.”

Wonderful. What did you actually do?

“When someone on your team disagrees with you, what does that look like?”

Nearly everyone says they welcome disagreement. That is the expected answer and it means nothing on its own.

Ask for the last time it happened.

What did the person disagree about? How was the decision made? What happened to the relationship afterward?

If they cannot produce an example, disagreement may be welcome in the same way questions are welcome at an all-hands: technically available and rarely advisable.

Two questions I stopped asking

“What is the culture like?”

You will get the answer they prepared.

Collaborative. Fast-paced. Mission-driven. People care deeply. Everyone has a voice. You could assemble the answer yourself from any careers page on the internet.

Culture is not what they call it. It is what the other answers reveal.

Who can disagree? Who gets promoted? How are bad decisions handled? What happened to the last person? How many people need to approve something? That is the culture.

“What is the work-life balance like?”

I stopped asking this one reluctantly because it is a completely reasonable thing to want to know.

In my experience, it still costs something to ask, and it tends to cost women more. You may be heard as someone already looking for a reason not to work hard, which is ridiculous and also not imaginary.

The answer is usually useless anyway. Nobody says, “We are going to message you at ten o’clock every night and act surprised when you stop answering.”

I ask for the same information without using the phrase.

“What time are the team’s standing meetings?”

“How often does work come up on weekends?”

“When something happens after hours, what usually causes it?”

“Who is expected to respond?”

Same information. Less room for an interviewer to attach a story to why you asked.

I am aware that this is a workaround for an unfair thing rather than a solution to it.

What to watch when nobody is answering

Some of the best information in an interview is not spoken.

Who is in the room

If you are interviewing for a senior role and everybody you meet looks the same, that is some of the most reliable information you will collect all day.

Nobody had to prepare it. Nobody had to remember the company line. They simply showed you who gets to be there.

Whether they have read your resume

Someone who has not read it is telling you where the role sits in their priorities.

One person being unprepared happens. An entire interview panel asking questions answered in the first third of your resume is a pattern.

They expect you to arrive having researched the company. It is reasonable to notice whether they offered you the same courtesy.

Whether anyone is late, and what happens next

The lateness itself is not the point. Meetings run over. Calendars break. Human beings have lives.

Watch the handling.

Do they apologize? Acknowledge that you waited? Explain briefly and move on? Or do they arrive fifteen minutes late and behave as though your time began when they entered the room?

That is often how your time will be treated after you work there too.

Whether they ask you anything difficult

A good interview should make you think.

If nobody tests your judgment, challenges an assumption or asks about a real failure, the process may not be real. They may already know whom they want. They may be desperate to fill the seat. Or it may be a place where nobody examines decisions very closely.

I have been caught by more than one of those.

An easy interview feels wonderful. Unfortunately, that is not the same thing as a good one.

The list to keep open during the interview

1. Who had this role before me, and where are they now?
2. What would make you say, six months from now, that hiring me was a mistake?
3. What is the last decision this team made that you disagreed with, and what happened?
4. Who else needs to say yes for me to get something done?
5. What is the first thing you would want me to fix, and what has stopped it from being fixed already?
6. Tell me about someone on your team who has grown significantly. What did you do?
7. When someone on your team disagrees with you, what does that look like?

For working expectations:

- What time are the team’s standing meetings?
- How often does work come up on weekends?
- When something happens after hours, what usually causes it, and who responds?

You will rarely have time to ask everything. Pick the questions that address the thing most likely to make the role fail.

What to do afterward

Write down your read within an hour.

Not just what you liked. You will remember that. Write down what worried you.

What answer became vague? What did they avoid? What did you find yourself explaining away because you liked the manager, wanted the title or were relieved that the interview seemed to go well?

If something felt wrong and you cannot explain why, write that too. You do not need to convict anybody. You are preserving your own read before enthusiasm gets a chance to improve it.

Write down what worried you, not what impressed you.

I have gone back to those notes twice.

Both times, the problem was already in them.

I had not failed to see it. I had simply wanted the job badly enough to call it something else.