Part 4 of 7 · 1 min read
What gets scored
Six things, and code is only one of them.
Interviewers vary, but the same six points appear in most scorecards (common practice):
- Requirements. Did the candidate ask before building, and fix the scope?
- Modelling. Are the classes the right nouns, each with one clear job?
- Rules in the right place. Does each rule live with the data it needs?
- Extensibility. Can a new vehicle type or payment method be added without editing many files?
- Correctness. Does the main flow work, including bad input and edge cases?
- Communication. Does the candidate explain each choice and its cost?
A made-up scorecard for a good answer: asked 6 questions, named 7 classes, put pricing behind an interface, coded park and unpark, found 3 edge cases, answered the change request in 5 minutes.
Extensibility
Extensibility is how easily a design takes a new feature without rewriting what already works.
Example: adding a "motorbike" vehicle by writing one new class, and changing nothing in the ticket or pricing code.
Check yourself: 1. Which two scorecard points involve code directly? 2. What does "rules in the right place" mean? 3. Why is communication scored?