Why Full Stack Developers Who Ask Questions Back Impress Me Most

WEAK ANSWER:

Interviewer: "How would you design a URL shortener?"

YOU:
"I'd use Node.js and MongoDB. I'd create a
collection for URLs and a collection for stats."

Why it fails:
❌ Jumps straight to code
❌ No clarifying questions
❌ Doesn't consider scale (what if it handles 10K req/sec?)
❌ Misses the business context

STRONG ANSWER:

Interviewer: "How would you design a URL shortener?"

YOU:
"Before I jump in, can I ask a few questions?

First, what's the expected traffic? 10 requests
per second or 10,000? That changes whether I use
a simple SQL database or a NoSQL store with Redis.

Second, do we need analytics on the clicks?
If so, I'd architect it so the redirect doesn't
wait for the analytics write — maybe using a
message queue like Kafka.

Once I know that, here's how I'd architect the
system..."

Why it works:
✅ Asks clarifying questions
✅ Shows architectural trade-offs
✅ Proves business awareness

THE 3-STEP FRAMEWORK:

1. Clarify
   "Can you tell me more about the scale and the
   users?"

2. Architecture
   "Assuming X scale, I'd use Y because of Z."

3. Trade-offs
   "The downside is [A], but I'd mitigate it with [B]."

This turns a test into a conversation.

THE QUESTIONS TO ASK:

✅ Scale:
   "How many requests per second?"
   "How many users?"

✅ Constraints:
   "Is this greenfield or legacy?"
   "Are there any tech stack mandates?"

✅ Business:
   "What's the main goal? Speed or quality?"
   "Who is the user?"

✅ Team:
   "What does the current team look like?"
   "What are the biggest pain points?"