Started with a standard call with the HR/recruiter. After clearing that, an open-ended coding task was given. They wanted the task to be available on Github but not deployed with setup instructions. The task was to build a small web application that consumes an external services API. Their expectation was that it wouldn't take more than 4 hours but had a deadline of 1 week. I completed it over a weekend and provided the code. What followed was probably the most bizarre review process I have encountered in interviews ever. One feedback I got was that there were thousands of files after setup - because they decided to count all the files in the node_modules folder, which obviously would not be present in a production deployment. Another feedback was that no linters were installed - even though linters would not have raised any issues in code quality since my editor is configured to do it automatically and there was no requirement to setup CI for the repo. The review process seemed like a very dogmatic cargo-cult approach to code quality and system design. If you are a pragmatic programmer who understands the reasons behind programming and OO design principles and why they should be applied, don't bother applying. The team either don't understand all these principles or don't care about why they are following these principles