Tell me about a time you disagreed with a technical decision — how did you handle it?
Question Details
This is a common behavioral interview question asked at nearly every tech company. The interviewer wants to see your communication style, ability to navigate conflict, and prioritization skills.
Suggested Solution
STAR Framework Answer
Situation
During a sprint planning meeting, the tech lead proposed using WebSockets for real-time notifications in our Next.js app. I believed Server-Sent Events (SSE) was more appropriate since we only needed server-to-client communication.
Task
I needed to either convince the team to use SSE or understand why WebSockets was the better choice — without creating conflict.
Action
- Didn't argue in the meeting — said "I have some thoughts, can we discuss offline?"
- Prepared a comparison doc with a simple table:
| Aspect | WebSocket | SSE |
|---|---|---|
| Direction | Bidirectional | Server → Client only |
| Complexity | Higher (reconnection, state) | Simpler (auto-reconnect) |
| Browser support | All modern | All modern |
| Our need | Server → Client | Server → Client ✅ |
- Had a 1:1 conversation with the tech lead, shared my analysis
- Listened to their reasoning — they planned bidirectional chat in Q3
Result
We agreed: use SSE now for notifications (simpler, faster to implement), but architect the abstraction layer so we can swap to WebSocket when chat is needed. The tech lead appreciated the research, and I learned about the Q3 roadmap.
Key Takeaways
| Principle | Why |
|---|---|
| Don't argue in public | Avoids defensiveness |
| Data over opinions | Comparison table > "I think" |
| Listen first | They may have context you don't |
| Find compromise | SSE now + WebSocket-ready architecture |
| Follow through | Build the abstraction layer yourself |