# CodePath Mock Interview Feedback Guide

As the student is going through the mock interview, keep in mind how you would evaluate the student as an interview candidate in the following categories:
- Problem Solving
- Communication
- Coding
- Evaluation
- Speed

### Core areas for assessment:
- Problem Solving
- Did the student ask clarifying questions to gather more information before trying to solve the problem?
- Was the student able to come up with multiple solutions and explain their trade-offs?
- Communication
- Was the student able to explain their approach in an understandable way?
- Was the student able to ask relevant questions to understand the problem?
- Did the student talk about their general approach before coding it up?
- If the student got stuck at any point, were they able to talk through why they got stuck?
- Coding Skills
- Was the student able to code up a working solution?
- Did the student write easy to understand code?
- Did the student consider possible edge cases and handle it in their code?
- Was the student able to verify their code works by tracing through the code by hand or by running tests?
- If there were bugs, was the student able to notice and fix the bugs themselves?
- Evalation Skills
- Was the student able to correctly state the run time and space time complexity of their solution?
- Speed
- Was the student able to complete the question within the time frame?
- Did the student spend too much or too little time asking questions before trying to code up a solution?

#### Other areas for assessment:
- Response to feedback
- If you gave the student any feedback or hints, was the student able to take the feedback and improve their solution?

### Final Evaluation:

Based on the student's mock interview, it would be good to give the student a 'interview score'. For example, you can use a rubric similar to this:

**Hire** - You would strongly advocate for hiring this student.

The student solved the problem without any hints, and had bug-free code. They were able to analyze their solution correctly and discuss potential tradeoffs.

**Maybe Hire** - The student did pretty well, and you would probably hire them, but you wouldn't strongly advocate for them.

The student was able to code a working solution without major hints. They may have missed a few edge cases and needed help with minor debugging. They were able to analyze their solution.

**Probably No Hire** - The student didn't do very well, and you wouldn't hire them, but you could be convinced otherwise if other interviewers saw a high potential in them.

The student needed multiple minor hints to get to a working solution. The student was also not able spot and and fix their own bugs.

**No Hire** - You would not hire the student based on this interview, and would advocate against hiring them.

The student need major hints to get to a working solution or the student was not able to code up a solution.