How to Handle a Rude CS Interviewer

How do you handle a rude CS interviewer?

Stay verbal — keep narrating your thinking even when they push back. Don't match their energy; stay polite and measured. If they cut you off, ask one clarifying question and continue. Don't call out the rudeness directly during the interview; if it crossed a real line, give that feedback to the recruiter after. Most rudeness is a test of composure; the candidates who pass it stay professional regardless of why.

Why interviewers act this way

Three common reasons you can't verify from the candidate seat:

1. Deliberate stress test. Some companies train interviewers to apply pressure as a calibrated check on whether you crumble.
2. Time pressure or fatigue. Sixth interview of the day, lunch skipped — the terseness has nothing to do with you.
3. Bad people skills. Some excellent engineers are simply not warm; their default style just lands that way.

Your tactics don't change across the three cases. The right response is the same regardless of cause.

Tactic 1: Stay verbal, keep narrating

The single most common candidate mistake under hostility is going quiet. Silence makes the room worse — the interviewer has nothing to respond to and your evaluation drops because they can't see your thinking.

Keep talking. Narrate out loud:

Okay, I'm going to re-read the problem to make sure I have it right... so the input is X and the constraint is Y. Let me think about edge cases first — what if the array is empty? Got it. So my first approach is...

This signals composure, keeps your own brain organized, and gives the interviewer something to react to. Per The Pragmatic Engineer's writing on senior interview signals, "communicates clearly under uncertainty" is one of the most consistently-rated positive signals across interview rubrics.

Tactic 2: Treat pushback as data, not attack

When an interviewer says "that's wrong" — even sharp-toned — treat it as technical feedback, not personal hostility. Two phrases that land:

"Could you say more about what's not working — is it the time complexity, or am I missing an edge case?"

"I think I see what you're pushing on. Let me revise — instead of [X], what if I [Y]?"

These reframe the interaction from "interviewer attacking, candidate defending" to "interviewer reviewing, candidate iterating." The shift changes what the interviewer writes in their post-loop notes — from "candidate got defensive" to "candidate took feedback well."

Tactic 3: Don't match their energy

The instinct under stress is to match. Terse for terse, sarcastic for sarcastic. This always damages the loop.

The asymmetry: the interviewer writes a one-paragraph summary that calibration reads in 90 seconds. "Candidate stayed professional despite [hostility]" tilts the decision in your favor; "candidate became combative" tilts it against you — even when their provocation was first.

Keep your tone neutral-to-warm. You're demonstrating that you don't melt under pressure.

When the interviewer cuts you off

Common pattern: you're mid-sentence on your solution, and they interrupt with "just give me the answer."

The move:

1. Stop immediately.
2. Acknowledge: "Got it — let me cut to the answer."
3. Give the shortest correct answer you have.
4. Ask: "Should I walk through the reasoning or move on?"

Don't argue. Don't sigh. The professionalism in this moment is the entire signal.

When the rudeness crosses a line

A small fraction of rude-interviewer moments are behavior that violates professional norms — personal insults, discriminatory remarks, inappropriate questions. Don't call it out in the interview; the loop is the wrong forum. Finish professionally.

After the loop, send the recruiter a short note:

Hi [Recruiter] — in the [round] interview, [specific behavior]. Flagging in case it's useful feedback. Either way, I appreciated the rest of the loop.

Per the Harvard Business Review's research on workplace incivility, companies that take this kind of feedback seriously are better employers regardless of the eventual decision. Companies that don't are surfacing data you'd want before accepting an offer.

The next interview is the only thing in your control. Book it, prep for it, run the same playbook.

About the author: Alex Chen is the founder of InterviewChamp.AI and writes about the modern tech interview from the inside — what changed, what works for new grads, and where the old playbook fails.