Interview Patterns
Recurring question shapes that appear across companies — not random trivia. Master the pattern once, adapt to any wording.
What’s in This Folder
| File | Pattern Type | Count |
|---|---|---|
| top-why-questions.md | ”Why did you choose X?“ | 30 |
| comparison-questions.md | ”X vs Y — when to use which?“ | 25 |
| debugging-questions.md | ”Something is broken — how do you debug?“ | 15 |
| architecture-questions.md | ”How would you structure/design…?“ | 15 |
| project-defense-questions.md | ”Defend your project” probes | 20 |
Why Patterns Matter
Interviewers rarely ask truly novel questions. They ask the same shapes in different words:
| You hear | It’s really this pattern |
|---|---|
| ”Why React and not Vue?” | Why-question |
| ”REST vs GraphQL?” | Comparison |
| ”Login works locally but not in prod” | Debugging |
| ”How would you scale this?” | Architecture |
| ”Is that the best database for this?” | Project defense |
If you prepare by pattern, one good answer framework covers dozens of phrasings.
How to Study These
Step 1: Read the answer out loud (don’t skim)
Silent reading feels productive. It’s not interview practice.
Step 2: Replace the example with YOUR project
Every answer has a project connection section. Fill it in:
“Why MongoDB?” → “In my expense tracker, I chose MongoDB because…”
Step 3: Practice the follow-ups
The main answer gets you 60 seconds. Follow-ups are where interviews are won or lost.
Step 4: Use answer frameworks
Pair with answer-frameworks.md:
| Pattern | Framework |
|---|---|
| Why-questions | Framework 1 (Technical Concept) + your real reason |
| Comparisons | Framework 6 (X vs Y) |
| Debugging | Framework 7 |
| Architecture | Framework 8 |
| Project defense | Framework 3 (Project Explanation) |
Weekly Drill Plan
| Day | Focus | Count |
|---|---|---|
| Mon | 5 why-questions | Out loud, timed 90 sec each |
| Tue | 5 comparison questions | Include “what I used in my project” |
| Wed | 3 debugging scenarios | Walk through all 6 debugging steps |
| Thu | 3 architecture questions | Draw a diagram for each |
| Fri | 5 project defense patterns | Use your actual project |
| Sat | Mock interview kit | 10-mock-interview-kits |
| Sun | Review weakest answers | Rewrite in your own words |
Common Mistakes Across All Patterns
- No tradeoff — “X is the best” sounds junior. “X fits because…, but Y is better when…” sounds thoughtful.
- Tutorial answer — “I used it because the tutorial used it” is honest but weak. Add one technical reason.
- No project link — Always bridge back: “In my project, this mattered because…”
- Memorized essay — Keep answers under 90 seconds unless they ask for more.
- Fake experience — If you haven’t used X, say so and explain how you’d evaluate it.
Pair With Mock Interviews
After studying patterns, run a mock where your partner only asks why/comparison/debugging questions for 20 minutes. It’s harder than it sounds.
Interviewers don’t ask “do you know React?” — they ask “why React for THIS problem?” Prepare for that.