Hey Anna,
while I haven't had a situation where I had to review side-project code during an interview, I had some interviews where I had to present and review pseudo-code and sketches for problems that were given during the interview. From that, I can advise the following:
Give a short description of the problem you're solving
Give your interviewers a quick run down of your perspective and the problems you wanted to solve with your solution. This makes it more likely that you all start with the same mental model.
Guide the interviewers through your code
Have a good mental model of the different parts of your application and how they work together. Identify important paths through your application that you can talk about (almost like user stories). For example, you probably don't want to spend a lot of time in your utils package, talking about string helpers and so on.
Have justifications for technical decisions
"Why did you use that library/data structure/database/...?"
Even if the answer is just: "lot's of people use it so there's a large community to ask questions to.", as long as it doesn't look like it's the first time you're thinking about that question, you'll probably be good.
In general, I like to think of an application as a complex topic that I've written an essay about. Now the challenge is to present that essay concisely and to the point in 10-15 minutes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Anna,
while I haven't had a situation where I had to review side-project code during an interview, I had some interviews where I had to present and review pseudo-code and sketches for problems that were given during the interview. From that, I can advise the following:
Give a short description of the problem you're solving
Give your interviewers a quick run down of your perspective and the problems you wanted to solve with your solution. This makes it more likely that you all start with the same mental model.
Guide the interviewers through your code
Have a good mental model of the different parts of your application and how they work together. Identify important paths through your application that you can talk about (almost like user stories). For example, you probably don't want to spend a lot of time in your utils package, talking about string helpers and so on.
Have justifications for technical decisions
"Why did you use that library/data structure/database/...?"
Even if the answer is just: "lot's of people use it so there's a large community to ask questions to.", as long as it doesn't look like it's the first time you're thinking about that question, you'll probably be good.
In general, I like to think of an application as a complex topic that I've written an essay about. Now the challenge is to present that essay concisely and to the point in 10-15 minutes.