Quick Answer
Long polling, WebSockets, and SSE in English: define the user need first (chat, notifications, one-way stream), then compare connection cost, latency, and complexity out loud.
Diagrams and what to say while drawing
Draw as you speak: requirements → APIs → estimates → boxes → deep dive → bottlenecks. Western panels score the narration as much as the diagram.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Long polling | Client waits; server answers when ready | “Long polling holds the request until there’s data.” |
| WebSocket | Full-duplex persistent connection | “WebSockets allow bidirectional realtime messages.” |
| SSE | Server-sent events, one-way stream | “SSE is simpler when the server only pushes.” |
| Fan-out connections | Many open sockets | “Persistent connections change load-balancer design.” |
ESL English phrases and transitions
Open and clarify
- “It depends on whether we need bidirectional traffic.”
- “I’ll compare long polling, WebSockets, and SSE on latency and complexity.”
- “For chat I’d lean WebSockets; for notifications SSE can be enough.”
UK/US system design moves
- “The tradeoff is X versus Y.”
- “I’ll deep-dive this component next.”
- “A single point of failure here would be …”
Pair this chapter with Mockly’s related article: chat system interview phrases in english.
Key English language pitfalls
| Pitfall | Sounds like | Say instead |
|---|---|---|
| Always saying WebSockets | Overkill | Match transport to need. |
| Ignoring proxies/LBs | Prod surprise | Mention connection-friendly infra. |
| No reconnect story | Fragile clients | Say backoff + resume. |
| Summary | Clear tradeoffs are how Western panels hear senior engineers. | |
Common English mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Confusing SSE with WS | Fuzzy concepts | Directionality is the key difference. |
| Forgetting mobile radio cost | Battery drain | Note battery/network cost. |
| No fallback | Brittle | Start long poll, upgrade if needed. |
What the interviewer is testing
For realtime transport choices, UK/US interviewers test structured thinking, scale intuition, and calm spoken English — not accent perfection.
They listen for clarify → estimate → design → tradeoffs → bottlenecks. If those moves are audible, you sound hireable.
How to open in English
First 20 seconds
- “It depends on whether we need bidirectional traffic.”
- “I’ll compare long polling, WebSockets, and SSE on latency and complexity.”
- “For chat I’d lean WebSockets; for notifications SSE can be enough.”
long polling vs websockets vs sse
Use this sequence for long polling vs websockets vs sse. Say the step name before you do it.
| Step | What to say |
|---|---|
| Need | Chat? Live scores? Notifications? Who sends data? |
| Long polling | Works everywhere; more HTTP overhead; timeouts. |
| WebSockets | Best bidirectional; connection state; proxy support. |
| SSE | One-way server→client; simpler than WS for feeds. |
| Ops tradeoffs | LB sticky sessions, connection limits, reconnection. |
Weak vs strong answers
Weak
I’d just use WebSockets for everything realtime.
Strong
If the server only pushes notification events, I’d use SSE for simplicity; for chat typing and messages both ways, WebSockets; long polling as a fallback on restrictive networks — here are the tradeoffs…
How to say the key terms
| Term | Say it |
|---|---|
| RTT | “round-trip time” |
| concurrent connections | “concurrent open connections” |
Follow-up questions you will get
Expect these
- “How do you scale a million idle WebSocket connections?”
- “What happens when a load balancer drops the socket?”
Practice drill
Set a timer for twelve minutes. Design realtime transport choices out loud in English. Record yourself. Check: clarify, estimate, tradeoffs, bottlenecks.
Repeat tomorrow focusing only on the deep-dive section.
Answer frameworks you can reuse
Clarify → APIs → Estimates → Data model → High-level → Deep dive → Bottlenecks.
For every deep dive: options → tradeoffs → recommendation.
Frequently Asked Questions
Tap a question to expand the answer.