Write some application with messy code and file structures. This messy app
is:
- Inconsistent in naming convention
- Baking business logic into one big function
- Using quite a number of Imperative Programming styles
- ...
handle:
- Side effects (hitting API, sending email after registering, etc)
- Business logic (i.e calculating discount like in order app)
- Saving to database
- (TODO challenging feature, like displaying search result but show an "interlude component" every 5 items for 3 times)
And the candidate is required to review the code and make improvements however he wants.
Metrics:
- SRP
- Folder/file structure
- Abstraction?
- Consistent code style
Points to take:
- It's fun. Good developers are always hungry for improvements
- See how well he does the code review: does he give contructive feedbacks? It's about Team Player, Coach, and Communication attitude
- Asking "why do you recommend that change?" can tell us how reasonable his approach is (Strong background)
- At the same time, from the changes he commits, we can know how Structured/Organized and Clean he is