Behavioral · Extra High-Value

When you don't know the answer

Easyhonestyproblem solvinginterview skills

Interview question

What do you do in an interview or on the job when you don't know the answer?

How to answer

The short answer

Honesty + structured thinking beats bluffing.

On the job

  1. 1Say what you *do* know
  2. 2State assumptions
  3. 3Search docs / logs / code
  4. 4Ask a targeted question to the right owner
  5. 5Time-box investigation and update stakeholders

In the interview

  1. 1Clarify the question
  2. 2Think aloud with a framework
  3. 3Admit gaps explicitly: "I haven't used Flink in production; here's how I'd approach it from streaming fundamentals…"
  4. 4Ask a clarifying question if stuck

Example outline

> If I don't know a Spark config, I won't invent one. I'll reason about vs compute, propose how I'd measure, and say what I'd look up. Then I'll connect it to something I *have* done, like fixing a skewed join in a project.

Fresher tip

Interviewers expect gaps. Coachability is the signal.

Interview tip: Never fabricate experience with a tool.