The process starts with a relaxed call with the company's recruiter. She was really friendly and asked simple screening questions. Then, it was followed by a technical test where you have to build a simple application that consumes an API and renders that using React. They ask you not to spend more than 4 hours working on it. Afterward, they sent me a rejection with a feedback that is extremely nitpicky and based on personal taste and opinions. It doesn't align with the fact that this test should be done in less than 4 hours. To give some examples, it was criticizing committing a lot, and not having a lot of commit descriptions. Not clearly describing the test coverage (even though the code was 100% tested), implementing things in a specific way that the reviewer didn't like, not having a style checker installed (even though it's globally installed as a dependency and the code has no style offences). They gave zero feedback about the frontend part which had a lot of neat optimizations, code separation, and good test coverage. Overall, it was focusing on tiny details that weren't right from their point of view and ignoring everything that is done right. My advise to the review team at Marley Spoon is to be pragmatic and objective while reviewing technical tests.

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