[danwee]

Not sure if it would be any better, and I say this as someone who hates leetcode-related interviews.

Code reviews are way more subjective than writing a piece code (at the end of the interview session, if the code works, then that's a huge thing already).

If I highlight something like "Perhaps we could inject that dependency, instead of harcoding it": sure, that seems probably the most correct assesment, but again, what if we are dealing with a really small project and hardcoding the dependency is the best way? Same goes for variable names ("i" is too short? Depends on the scope, right? Well, probably it depends on the interviewer's mind), what about composition vs inheritance? Again, subjective as hell. And don't let me get started with anything related to microservices vs monolith...

[endemic]

I've come to the conclusion that any sort of job interview has a high level of subjectivity. Basically as an applicant, you roll the dice and hope that you have a good day and "click" with the interviewer.

[francisofascii]

I think job interviews are subjective and not a bad thing. Some objectively good candidates are not good for certain roles and vice versa. To me, your answer would be the best and would allow you to fit into more roles. You give options for a situation, rather than dogmatic statements like, you must inject that dependency, or the variable names should be done this way. But that is my subjective assessment.