Tell me about a time you disagreed with a technical decision — how did you handle it?

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

1. Didn't argue in the meeting — said "I have some thoughts, can we discuss offline?"
2. Prepared a comparison doc with a simple table:

AspectWebSocketSSE

DirectionBidirectionalServer → Client only
ComplexityHigher (reconnection, state)Simpler (auto-reconnect)
Browser supportAll modernAll modern
Our needServer → ClientServer → Client ✅

3. Had a 1:1 conversation with the tech lead, shared my analysis
4. 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

PrincipleWhy

Don't argue in publicAvoids defensiveness
Data over opinionsComparison table > "I think"
Listen firstThey may have context you don't
Find compromiseSSE now + WebSocket-ready architecture
Follow throughBuild the abstraction layer yourself