How Interviews Actually Work (From Both Sides of the Table)

If you're getting interviews but not offers, the problem is rarely your resume or your skills.

It's that you don't fully understand how interview decisions are actually made.

Most candidates walk in thinking they're there to prove competence. In reality, by the time you're interviewing, competence is mostly assumed. They've read your resume. The interview exists to answer a different question:

"Is this the person we want to work with, and will they make our lives easier or harder?"

That changes everything about how you prepare.

And here's the part most early-career people miss: you'll be on the other side of this table sooner than you think. A peer interview, a panel, a "can you grab coffee with this candidate?" Understanding both sides makes you better at each.

This module covers what interviewers are really weighing, how to read and adapt to the person across from you, and how to prepare, show up and follow up.

The short version

• Interviews are less about finding the best candidate and more about avoiding the wrong one. Your job is to reduce perceived risk.
• Interviewers are silently asking three things: Will I enjoy working with you? Are you still hungry? Will you make my life easier?
• Skills rarely win late-stage interviews. Trust, judgment and preparation do.
• Adapt to the interviewer's style. Match their pace, level of detail and how they frame success.
• Treat it as a working session, not a performance. Then follow up like you listened.

What's really happening on the other side

Interviewers are overloaded. They may be reviewing hundreds of applications, running several interviews in a day, and sitting on a panel of three to eight people, all while doing their actual job.

Even early-career roles now often involve a recruiter screen, a hiring manager interview, a panel, and some version of a culture or values conversation. Not because companies love complexity. Because hiring is high-risk, and every step is an attempt not to make a mistake.

Which leads to the most important insight in this module:

Key idea: Interviews are less about finding the best candidate, and more about avoiding the wrong one.

The three silent questions

Regardless of role or company size, most interviewers are asking themselves the same three things.

1. Will I enjoy working with this person? Not just "are they nice," but do they communicate clearly, think before they speak, and make collaboration easier? A test many interviewers use, whether they admit it or not: would I want to be stuck on a five-day work trip with this person?
2. Are they still hungry? Especially for career switchers, or anyone who looks overqualified. Will you do the actual day-to-day work, or are you already thinking about the next job? Nothing raises risk faster than a candidate who says the right things but signals they don't want to do the work.
3. Will this person make my life easier? Managers don't need heroes. They need reliable execution, sound judgment, and someone who doesn't need constant oversight. "Easy to work with" is not a soft compliment. It's a hard differentiator.

Why skills rarely win

Unless you're in a genuinely scarce field, you're not unique on skill alone. By the later rounds, most candidates are close enough technically, qualified on paper, and capable of learning what they don't know.

So the decision shifts from capability to confidence. Who feels prepared? Who understands the business? Who sounds like they've done this before, or is clearly ready to?

Interviews aren't performances. They're trust-building sessions.

Read the person across the table

Most candidates prepare answers. Very few prepare to adapt.

Most people communicate the way they like to be communicated with. The best candidates communicate the way the interviewer needs. That isn't being fake. It's strategic empathy: reducing friction so your substance actually lands.

You can place most interviewers using two quick reads:

• Assertive or responsive? Do they move fast, push for conclusions and interrupt? Or are they deliberate, structured and patient?
• Task-focused or people-focused? Do they care most about facts, logic and results? Or about trust, relationships and how things feel?

• Analyst (task, responsive). Values accuracy and structure. Distrusts hype. Give clean, specific answers and offer to follow up in writing.
• Collaborator (people, responsive). Values trust and harmony. Slow down, listen fully, talk about how you work with others.
• Driver (task, assertive). Values speed and results. Lead with the outcome, keep it short, skip the backstory.
• Expressive (people, assertive). Values energy and vision. Match their enthusiasm, use stories, connect to the bigger picture.

Diagnose in the first few minutes. Are they structured or conversational? Results-focused or relationship-focused? Fast or reflective? Do they interrupt or listen? Then adjust one thing: pace, level of detail, or how you frame success. Don't label people permanently. Just adapt faster than the person across the table expects.

The question that does the diagnosing for you

If you get a chance to ask a question early, ask this:

"Before we get started, can you describe what your ideal candidate looks like in this role: how they operate, how they communicate, and what success looks like in the first 6 to 12 months?"

If they answer, they've just told you what they value, what they're worried about, and how to tailor every answer that follows. Most candidates never ask it. The ones who do stand out immediately.

Prepare, show up, follow up

Before: be able to answer these cold

• Why this company?
• Why this role, right now?
• What problems does this team actually need solved?
• How would I add value in the first 90 days?
• What does success look like in year one?

Go beyond the website. Read interview reviews on Glassdoor or Indeed. Learn the interview structure. Talk to a customer, salesperson or support rep. Use your network for context. Preparation is how you reduce perceived risk.

Prepare three to five stories you can adapt to most questions. Structure them with STAR:

During: make them feel confident

• Be respectful, energetic and engaged.
• Answer the question that was asked, clearly and directly. Rambling signals poor judgment.
• Show judgment in what you emphasize and what you leave out.
• Show you can work independently and collaborate.
• Be confident, not loud. Confidence feels calm. Ego feels loud.

Remember that interviewers assume this is your best version. If this is 100 percent, they're mentally discounting what they'll get on an ordinary Tuesday.

Your goal isn't to impress. It's to make the interviewer feel confident.

After: prove you listened

Send a short follow-up the same day. Reinforce what they said they needed and how you fit it. Show enthusiasm without desperation. A good follow-up says: I listened, I understood, and I'm intentional.

When you're the interviewer

You'll be asked to interview someone sooner than you expect. Do it well:

• Use a consistent structure. Same core questions for every candidate, so you're comparing fairly.
• Make them comfortable. Explain the format up front. Nervous people give worse signal, not more honest signal.
• Listen more than you talk. Take notes. Let them finish before you follow up.
• Look for the three silent questions, but write down evidence, not vibes.
• Be clear about next steps and timing, and make sure someone actually closes the loop.

Being a good interviewer is also the fastest way to become a better candidate. You'll see from the inside what builds trust and what kills it.

What it looks like in practice

A hypothetical example.

Say you're interviewing for an operations coordinator role. You prepared four strong STAR stories, each about two minutes.

Ninety seconds in, you notice the hiring manager checking the time, cutting your intro short and asking, "So what's the biggest thing you fixed in your last job?" Classic Driver.

You adjust. You lead with the result: "I cut our weekly inventory errors by more than half." Then two lines of how. Then you stop. When she wants more, she asks.

Later, a panel member speaks slowly, asks how you handled a disagreement with a coworker, and nods through your answer. More Collaborator. You slow down and talk about how you brought the other person along.

That evening, your follow-up references the specific problem the manager named: late vendor deliveries. You add one idea for how you'd approach it in your first month.

Same stories. Different delivery. Much less friction.

Common traps

• Rambling. Long answers signal poor judgment. Fix: STAR in under two minutes, then stop.
• Overselling. Ego feels loud. Fix: calm, specific evidence.
• Generic answers. They tell the interviewer you didn't do the work. Fix: tie every story to their business.
• Ambition without respect for the role. Fatal for career switchers and step-back moves. Fix: show you want this job, day to day.
• Treating it like a stage. Fix: treat it as a working conversation about their problems.
• One delivery for every interviewer. Fix: read the style early and adjust pace, detail or framing.

Do this this week

Prepare for your next interview, even if it isn't booked yet.

1. Write answers to the five "before" questions for one real target role.
2. Draft three STAR stories, each with a number in the result. Time yourself saying them out loud. Cut anything over two minutes.
3. In your next three conversations at work, guess the other person's style and adjust one thing. Notice what changes.

Your tool

CopyINTERVIEW ONE-PAGER

ROLE / COMPANY: ___________________   INTERVIEWER(S): ______________

THE FIVE ANSWERS (say each in under 60 seconds)
  Why this company?         _____________________________________
  Why this role, now?       _____________________________________
  Problems they need solved _____________________________________
  My first 90 days          _____________________________________
  Success in year one       _____________________________________

MY STORIES (STAR + Link, under 2 minutes each)
  #  Theme (e.g. fixed a problem, conflict, learned fast, led)
  1. ______  S:____ T:____ A:____ R (number):____ Link:____
  2. ______  S:____ T:____ A:____ R (number):____ Link:____
  3. ______  S:____ T:____ A:____ R (number):____ Link:____

THE THREE SILENT QUESTIONS (one proof point each)
  Easy to work with:  ___________________________________________
  Still hungry:       ___________________________________________
  Makes life easier:  ___________________________________________

OPENING QUESTION
  "Before we start, can you describe what your ideal candidate looks
   like in this role: how they operate, how they communicate, and
   what success looks like in the first 6-12 months?"

READ THE ROOM (first few minutes)
  Fast or reflective?          Facts or relationships?
  -> Driver: result first, short.   -> Analyst: precise, structured.
  -> Expressive: energy, story.     -> Collaborator: slow, listen.
  Adjust ONE: pace / detail / framing

MY QUESTIONS FOR THEM (pick 2-3)
  - What would make someone great in this role vs. just good?
  - What's the biggest problem this team needs solved this year?
  - What did the last person in this role do really well?
  - What does the next step in the process look like?

SAME-DAY FOLLOW-UP
  Subject: Thank you - [Role] conversation
  Hi [Name], thanks for the time today. What stuck with me was
  [specific problem they mentioned]. Based on [my relevant result],
  I'd start by [one concrete idea]. I'm genuinely excited about
  this role and the team. Looking forward to next steps.
  [Name]

IF I'M THE INTERVIEWER
  [ ] Same core questions for every candidate
  [ ] Explain the format at the start
  [ ] Listen, take notes, let them finish
  [ ] Write evidence, not vibes
  [ ] Tell them next steps and timing, then close the loop

Talk about it

1. Which of the three silent questions do you think you answer weakest in interviews, and what proof could you bring next time?
2. What's your own default style, and which interviewer style do you find hardest to connect with?
3. Think about a time you were on the hiring side, even informally. What made you trust one person over another?

— Evan