
Before the call: the README does the first interview
- How to run it, in one command if you can.
- What you built, in three sentences.
- The decisions you made and why.
- What you left out on purpose, and what you would do next.
- How long you spent. Be honest.
A five-minute tour
- The requirement, in your own words.
- How the code is laid out.
- The one decision you are proudest of.
- The tests: what they cover and what they do not.
- What you would change with another day.
Name the weak spots first
Every take-home has them, and the reviewer has already found them. "The error handling in the import is thin. With more time I would validate each row and report all the failures at once" turns a flaw into evidence of judgment. Waiting to be caught does the opposite.
Be ready to change it live
A common second half: "Now add a field" or "What if the file has a million rows?". Open the code, find the place, and talk through the change as you make it. This is where knowing your own code shows, so read it again the evening before.
Questions you should expect
- Why this structure and not a simpler one?
- What happens with bad input?
- How would this behave with a hundred times the data?
- What would you test next?
If you used AI tools to write it
Check the assignment's rules first. If tools were allowed, say that you used them and be able to explain every line, because the call exists to find out whether you can. If they were not allowed, do not use them.