Ultimate Dilemma in Interviews: When to be Specific, When to Stay High-level?
- Tianyu Koenig
- 2 days ago
- 3 min read
Many of my clients ask me the same question:
When do you get into the weeds, and when do you stay vague?
It sounds simple. But it's one of the hardest things to get right in interview storytelling, because the mistake goes both ways - Some people drown the interviewer in details when a high-level answer was all that was needed. Others stay so generic when specifics were called for that they sound like every other candidate.
The fix is one principle:
Detail is evidence. Use it only when you need to prove something.
When to zoom in
1. "How" behavioral questions
When an interviewer asks how you got stakeholder buy-in, how you achieved alignment, or how you collaborated across functions, a summary answer doesn't cut it.
"I communicated with stakeholders" and "I had meetings with my PM" are invisible. They don't differentiate you from every other candidate who also had meetings.
What the interviewer wants is your actual approach: your talking points, how you anticipated pushback, how you handled disagreement, what specifically you owned versus handed off.
The same applies to XFN collaboration questions — "I worked cross-functionally" signals participation, not leadership. The detail is what proves the claim and moves you from team member to key driver in the interviewer's mental model.
2. Process and craft questions
"What's your design process?" "How do you make design decisions?" "How do you incorporate AI into your work?"
A high-level answer to these sounds memorized. A specific one sounds real. Use a concrete project to anchor your methodology, not just what you do, but why, and what tradeoffs you navigated along the way.
3. Technical and tradeoff questions
"Who did you recruit for your research?" isn't satisfied by a demographic summary. The interviewer wants your recruiting criteria and the reasoning behind them — what you included, what you excluded, and why those boundaries made sense for the problem.
"Why did you go with option A over B?" is asking for your tradeoff analysis, not your conclusion. Walk through what A gave you, what you'd lose with B, and what constraints shaped the decision. This is where your judgment becomes visible.
When to stay high-level
1. Project walkthroughs
When walking through a project, your job is to establish the logic line, not tell the whole story.
A clean structure works: problem, why it was worth solving, what you did, what resulted. Everything else is a detail the interviewer can pull out with follow-up questions.
The two most common traps: spending too long on business context before getting to your contribution, and going deep on solution details that weren't asked about. Neither adds signal. A focused high-level answer invites sharper follow-up — that's where you get to zoom in.
2. Business context
Every project has a larger business backdrop, but not all of it belongs in your answer.
Only include context that directly explains why the problem existed or why your scope was defined the way it was.
Here an example - If your project was introducing a chatbot to improve engagement, you don't need to walk through every other engagement initiative the team was running. That context doesn't help the interviewer understand your problem or your decisions; it just adds length and confusion.
3. Solution details
When you've established what you built, resist the urge to walk through every design decision, iteration, and edge case you considered. The interviewer doesn't need the full feature spec, they need just enough to understand the shape of your solution.
Save the details for follow-up. If they want to go deeper on a specific decision, they'll ask. Volunteering everything upfront buries the signal in noise and makes it harder for the interviewer to steer the conversation toward what they actually care about.
A useful technique:
If you had only 20 seconds to summarize this story, what would you say? Start there, then only expand on the key information that appears in that 20-second version.
Anything that didn't make the cut is simply noise.
A question to keep with you
Before every answer, ask:
"Am I saying this to prove something, or just because I remember it?"
If it's the former, say it. If it's the latter, cut it.
The goal isn't brevity. It's precision — making sure every word is doing work.
Are you struggling to balance specificity and high-level thinking
for specific interview questions?
An outsider perspective always gives more clarity:
Comments