Defending a Project You Built
Many developer processes include a round in which you walk an engineer through something you built. It looks like the easiest round of the day, and candidates often report it as one of the hardest. The interviewer does not stay with the summary. They pick one decision and ask why you made it, then ask why again, and keep going until they reach the edge of what you understand. For experienced candidates, a production system usually counts for more than an academic project.
What the round is testing
- Whether you did the work you describe. The depth of your answers shows whether you made the decisions or watched someone else make them.
- Whether you understand your trade-offs. That includes the ones you made without noticing.
- Whether you can explain a system clearly to someone who has never seen it.
- How you think about failure and measurement: what went wrong, how you knew, and what you would change.
The rest of this lesson is for subscribers
Unlock every lesson in Programming for Quantitative Developers, and every other premium course.
Subscribe to continueTest your knowledge
Questions are only available to subscribers.
Keep reading Programming for Quantitative Developers
33 lessons in this course, and every other premium course, on one subscription.
- Every lesson in every course, with the worked examples and interactive simulators
- Graded questions on every lesson, with explanations for the wrong answers as well as the right one
- The trainers, timed assessments and brainteaser library that go with them