Mock Interview Kits
Full 45-minute interview scripts you can run with a friend, mentor, or by recording yourself.
What’s in This Folder
| File | Round Type | Best For |
|---|---|---|
| html-css-round.md | Frontend fundamentals | Campus rounds, internship screens |
| javascript-round.md | JS core + small live task | Almost every web dev interview |
| react-round.md | React concepts + component task | Product companies, startups |
| backend-round.md | Node/Express, APIs, auth | Backend-focused roles |
| fullstack-round.md | End-to-end stack | Full-stack intern/junior roles |
| system-design-round.md | Architecture at student level | Product companies, later rounds |
| evaluation-rubric.md | Scoring guide | Interviewer reference |
How to Run a Mock Interview
Setup (5 minutes before)
- Pick a role: Interviewer reads the script; candidate does not peek ahead.
- Set a timer: Use a phone timer for each section. Real interviews are timed.
- Choose environment: Video call (realistic) or in-person with a whiteboard/paper.
- Candidate brings: Resume, one project ready to discuss, IDE or paper for live tasks.
During the Interview
- Candidate answers out loud — no reading from notes.
- Interviewer asks at least 2 follow-ups per main question.
- If candidate is stuck for 30+ seconds, interviewer gives a small hint (note that you needed a hint).
- Live tasks: candidate explains approach before writing code.
After the Interview (Debrief — 10 min)
- Score using evaluation-rubric.md.
- Candidate asks: “Which answers were weak? Did I communicate tradeoffs?”
- Assign homework: redo weak topics from the relevant section in the playbook.
- Schedule a retry in 3–5 days.
Recommended Practice Schedule
| Week | Focus | Kit |
|---|---|---|
| 1 | Fundamentals | HTML/CSS + JavaScript |
| 2 | Framework | React + Backend |
| 3 | Integration | Full-stack |
| 4 | Polish | System design + Full-stack retry |
Run each kit twice — first attempt exposes gaps, second attempt shows improvement.
Tips for Interviewers (Friends/Mentors)
- Don’t be too nice. Ask follow-ups even when the answer sounds right.
- Say “Can you go deeper?” or “What would break if…?” often.
- For live tasks, watch process more than perfect syntax.
- Use the rubric honestly. A score of 2/5 on communication is useful feedback.
Tips for Candidates
- Treat every mock like the real thing: dress decently, camera on, no phone.
- Record yourself at least once — you’ll notice filler words and rambling.
- Connect answers to your project whenever possible.
- It’s okay to say “I don’t know, but here’s how I’d figure it out.”
Pair With Other Sections
- Weak on concepts? → Go to the topic folder (
01-html-css,02-javascript-core, etc.) - Weak on “why” questions? → 11-interview-patterns
- Weak on project defense? → 08-project-interview-bible (when available)
- Want real company patterns? → 12-interview-experiences
One mock interview per week is worth more than 50 hours of silent reading.