The purpose is not to perform a familiar set of questions. It is to determine what this candidate could solve, and whether the opportunity makes sense for both sides.
A candidate joins a video interview. On the interviewer’s screen are an applicant-tracking profile, the submitted résumé, recruiter notes, LinkedIn history, and perhaps an automated summary of the candidate’s background.
The organization has access to more information than hiring teams could have imagined a generation ago. And yet the conversation begins: “Tell me a little about yourself.”
The problem is not that this is always a bad opening question. It is that the interviewer frequently has no plan for what should follow. They move through standardized prompts, record fragments of the answers in the hiring platform, and complete an evaluation form after the call. The process is structured, documented, and technologically supported, but may still reveal little that was not available before the interview began.
A strong interview is not defined by the platform hosting it, the scorecard attached to it, or whether every required question was asked. It is a prepared, responsive inquiry designed to determine whether this candidate can succeed in this role, within this organization, under the conditions that actually exist.
More importantly, it should determine what this particular person may be able to solve.
Every position exists because an organization has work that needs to be done, problems that need to be addressed, or opportunities it is not yet equipped to pursue. The job description may define the general territory, but the interview should explore the potential match between the organization’s needs and the candidate’s particular capabilities.
What has this person encountered before that resembles the conditions here? What do they understand that the organization currently lacks? Which problems could they approach differently? Where might they strengthen the role rather than merely occupy it?
That makes the interview a process of mutual discovery. The organization is learning what the candidate could contribute, while the candidate is deciding whether the role, leadership, resources, and business conditions would allow that contribution to matter. Both parties arrived because there was enough interest to begin a conversation. The interview should determine whether that interest can become a credible working proposition.
Ten goals for a useful interview
1. Define what the organization needs someone to solve
Before evaluating a candidate, the interviewer must understand why the role exists now. What is not working? What needs to change? Which opportunities are being missed? What must the person accomplish that the organization cannot accomplish (or is not accomplishing) without them?
Without that clarity, the interview collapses into qualification matching. The hiring team asks whether the candidate has held similar titles, used familiar systems, or completed comparable tasks without determining whether that experience equips them to address the organization’s actual needs. The job description provides boundaries. The business problem provides the reason for the conversation.
2. Enter with a roadmap, not a script
The resume, job description, recruiter notes, work samples, and earlier conversations should shape a preliminary view of the candidate before the interview begins. What appears especially relevant? What remains unclear? Where does the candidate’s experience align, and where does that alignment need to be tested?
Preparation does not mean deciding in advance. It means entering the conversation knowing what evidence is still needed.
3. Use the resume to find the story behind the record
A resume documents roles, dates, responsibilities, and selected accomplishments. The interview should uncover the context those facts cannot provide. What was happening inside the organization? What problem was the candidate brought in to solve? What authority and resources did they actually have? Which outcomes belonged to them, and which were the result of a larger team?
The objective is not to repeat the resume aloud. It is to understand what the resume means.
4. Follow the answer, not merely the question list
A prepared interviewer should have a roadmap, but a productive conversation will not always follow it in order. An unexpected comment may reveal more than the next scheduled question.
Good interviewers listen for what deserves another question. They ask for clarification, test inconsistencies, and pursue details that change their understanding of the candidate. A rigid script can create consistency, but it can also cause the interviewer to miss the most valuable evidence offered during the conversation.
5. Replace polished claims with specific evidence
Candidates know they are expected to describe themselves as strategic, collaborative, adaptable, and results-oriented. Asking whether they possess those qualities rarely produces useful information.
Ask where those qualities became necessary. What decision did they make? What alternatives did they consider? Who disagreed? What changed because of their involvement? The goal is not to collect the correct vocabulary. It is to understand how the candidate operates when the quality being discussed is actually required.
6. Separate interview fluency from job capability
Some candidates are exceptionally skilled at interviewing. Others are more compelling when discussing real work than when delivering polished answers to anticipated questions.
Unless presentation under interview-like conditions is central to the role, conversational polish should not become a substitute for capability. The interviewer must distinguish between someone who presents a persuasive account of competence and someone whose experience demonstrates it.
7. Examine judgment, not just outcomes
A successful result does not automatically prove that the decisions behind it were sound. Nor does an unsuccessful result necessarily indicate poor judgment.
A useful interview explores what the candidate knew at the time, which constraints shaped the decision, what risks they recognized, and what they would do differently now. This shows how the person thinks, adapts, and learns when circumstances are imperfect.
8. Explore what this particular candidate could make possible
Candidates who satisfy the same basic requirements are not interchangeable. Each brings a different combination of experience, judgment, relationships, ideas, and ways of approaching the work.
A strong interview considers more than whether the candidate can perform the role as currently defined. It asks which problems this person may be especially equipped to solve, where they could improve the role, and what capabilities they might introduce that the organization had not originally considered. Sometimes the strongest candidate is not the person who most precisely resembles the previous employee. It is the person who offers the most credible response to what the organization needs next.
9. Make the operating reality part of the conversation
Every role operates within conditions that may not appear in the job description: unclear authority, competing stakeholders, limited resources, organizational resistance, inherited problems, or a manager with a particular working style.
Those conditions should be discussed directly. The candidate’s questions, interpretations, and challenges are evidence too. What do they notice? Which assumptions do they test? What risks do they identify? The organization is not simply deciding whether it wants the candidate; the candidate is deciding whether the organization offers a credible opportunity to do the work.
10. Leave with evidence that can support a decision
“Strong candidate,” “good energy,” and “not sure about fit” are reactions, not findings. By the end of the interview, the interviewer should be able to identify what was learned, which examples support the assessment, what remains unresolved, and whether another conversation would produce genuinely new information.
If several people are involved, each should have a defined area to evaluate and a reason for being there. More interviewers do not automatically produce more knowledge. The process becomes useful only when each conversation contributes distinct evidence to the decision.
The interview should change what the organization knows
A good interview does not need to eliminate every uncertainty. It should replace broad assumptions with better evidence, reveal what the candidate could solve, and clarify whether the organization can offer the conditions that person would need to succeed.
If the hiring team leaves knowing nothing that could not have been learned from the application, the interview did not accomplish its purpose. It was performed, recorded, and completed, but it did not meaningfully advance the decision.
The measure of a strong interview is not how many questions were asked. It is whether both sides now understand the possibility in front of them more clearly.
By Melissa Brandt | Melissa Brandt & Associates