Behavioral vs. Technical
Interviews evaluate two dimensions. Understanding both — and why behavioral matters more than most think — is fundamental to finding signal.
The two dimensions
Every interview evaluates some combination of:
| Dimension | What it measures | Example questions |
|---|---|---|
| Technical | Can they do the job? Skills, knowledge, problem-solving. | "Design a system that handles 1M requests/sec" |
| Behavioral | How do they do the job? Judgment, collaboration, leadership. | "Tell me about a time you disagreed with your manager" |
Why behavioral is undervalued
Most companies over-index on technical skills and under-index on behavioral signals. Here's why that's a mistake:
Technical skills are:
- Learnable and trainable
- Easy to assess (right or wrong answers)
- Domain-specific (change with technology)
Behavioral traits are:
- Deep-seated and slow to change
- Hard to assess without structure
- Universal (apply across every role, every company)
A brilliant engineer who can't collaborate, take feedback, or own their mistakes will hurt your team more than a good-but-not-brilliant engineer who does all three.
The signal hierarchy
In a strong interview process, behavioral signal is weighted equally or higher than technical signal. Here's how to think about it:
Strong Technical + Strong Behavioral → Hire (clear bar raiser)
Strong Technical + Weak Behavioral → Usually No Hire (risk)
Weak Technical + Strong Behavioral → Depends on level & learnability
Weak Technical + Weak Behavioral → No Hire (clear)
The riskiest quadrant is strong technical + weak behavioral. These candidates look great on paper and in coding rounds but create team dysfunction, resist feedback, or make poor judgments under pressure.
Behavioral interviewing basics
A behavioral question asks about something that actually happened, not a hypothetical:
| ✅ Behavioral | ❌ Hypothetical |
|---|---|
| "Tell me about a time you had to make a decision with incomplete data" | "What would you do if you had to make a decision with incomplete data?" |
| "Describe a project that failed. What was your role?" | "How do you handle failure?" |
| "Give me an example of when you influenced a team without authority" | "Are you good at influencing people?" |
Why does this matter? Past behavior is the best predictor of future behavior. Hypotheticals tell you what someone thinks they'd do. Behavioral questions reveal what they actually did.
Exercise: Convert to behavioral
Take each hypothetical question and rewrite it as a behavioral question.
1. "How do you handle conflict on a team?"
→ "Tell me about a specific time you had a conflict with a teammate. What happened, and how did you resolve it?"
2. "Are you comfortable making decisions under pressure?"
→ "Describe a situation where you had to make an important decision with a tight deadline and limited information. Walk me through your thought process."
3. "What's your management style?"
→ "Tell me about a time you had to manage someone who was underperforming. What did you do, and what was the outcome?"
4. "Do you take ownership of problems?"
→ "Give me an example of a time you identified a problem that wasn't your responsibility and chose to own it anyway. What happened?"
Why is 'strong technical + weak behavioral' often a No Hire?
What makes behavioral questions more effective than hypotheticals?
Which of these is a properly formed behavioral question?