Mock Interview Kits ⚡ Recently updatedUpdated on Jun 30, 2026 — this content may still be evolving.

Mock Interview Evaluation Rubric

Use this rubric after every mock interview. Score each dimension 1–5. Be honest — inflated scores don’t help.

Total score: Sum of all dimensions (max 50 for standard round, max 60 if using optional dimensions).

Core Dimensions (Score All Rounds)

1. Technical Accuracy

Are the facts correct? Do follow-ups hold up?

Examples:

• Score 2: Says “React virtual DOM is always faster than real DOM”
• Score 4: Explains virtual DOM tradeoff including overhead for simple pages

2. Problem-Solving & Live Tasks

Approach before code? Handles edge cases? Recovers from mistakes?

Live task modifiers:

• Needed a hint within 30 sec: cap at 3
• Needed a hint after 2+ min: cap at 2
• Finished early with follow-ups: +0.5 (round up at end)

3. Communication & Clarity

Could you follow their explanation? Appropriate pacing?

Reference: answer-frameworks.md — Framework 1

4. Tradeoff & Depth Awareness

Do they know when NOT to use something? Real-world judgment?

Examples:

• Score 2: “Always use Redux for state”
• Score 4: “Context for theme/auth, local state for forms — I used Context in my project because…“

5. Project Connection

Can they defend their own work? Specific, not generic?

Round-Specific Dimensions (Score 1 Additional)

Pick the dimension matching the kit you ran.

HTML/CSS Round — Layout & Accessibility

JavaScript Round — Async & Runtime

React Round — Component & State Design

Backend Round — API & Security Design

Full-Stack Round — Integration Thinking

System Design Round — Architecture & Requirements

Behavioral Signals (Checkbox — Not Scored)

Mark ✓ or ✗ for interview presence:

Score Interpretation

*Core = 5 dimensions × score 1–5 = max 25, plus round-specific (max 5) = 30 total for standard scoring.

Dimension priority for improvement

Fix the lowest score first, not the easiest topic:

If Technical Accuracy = 2 but Communication = 4
→ Study concepts, not presentation

If Technical Accuracy = 4 but Project Connection = 2
→ Rewrite project explanation; practice 2-min pitch daily

Written Feedback Template

Copy this after each mock:

## Mock Interview Feedback

**Date:**
**Kit used:**
**Interviewer:**

### Scores
| Dimension | Score (1-5) |
|-----------|-------------|
| Technical Accuracy | |
| Problem-Solving | |
| Communication | |
| Tradeoff Awareness | |
| Project Connection | |
| Round-Specific | |
| **Total** | /30 |

### Top 3 strengths
1.
2.
3.

### Top 3 areas to improve
1.
2.
3.

### Questions that stumped the candidate
-

### Follow-ups that went well
-

### Homework (specific)
- [ ]
- [ ]
- [ ]

### Retry date:

Interviewer Calibration

Avoid score inflation

• 3 is good. Most practice mocks should land 15–22 total.
• Don’t give 5 for “I’ve heard of it.”
• Live task with bugs but good process = 3, not 1.

Avoid score deflation

• Nervousness ≠ wrong. Re-prompt once before scoring down.
• Student level ≠ senior level. Don’t penalize for not knowing Kubernetes.

Consistency across mocks

Use the same rubric when re-running a kit. Compare delta, not just absolute score:

Pass / No-Pass Guide (For Realistic Simulation)

At intern/campus level, a mock “pass” typically means:

• Total score ≥ 20
• No dimension at 1
• Problem-Solving ≥ 3
• Project Connection ≥ 3
• Completed live task with working logic (syntax errors okay)

A “no-pass” doesn’t mean quit — it means 2 weeks focused prep before the real interview.

Related Resources

• Answer structure: answer-frameworks.md
• Pattern drills: 11-interview-patterns
• Topic deep dives: folders 01 through 07 in this playbook