Started with a standard HR interview followed by a code test. The test was to create library that met the stated business rules. The HR told me that that the next round would be to discuss the code I submitted. But that never happed. Was rejected based on the code test for minor reasons such as logging not being adequate and variable naming! Do note that there is no way to ask clarifying questions. The instructions say to make assumptions and document them. What irks me the most is that they didn't move me to the next round based on what I think is the fact that I didn't guess all the untold things that were expected by the interviewer. It is like asking people to guess the number someone is thinking of from 1- 100000! There is another review for the same role from a person with the EXACT same experience. So I am going to take comfort in the fact that I am not alone in this. Even in the test feedback, the positives outweighed the negatives by a significant margin. The decent thing to do would have been to invite the candidate to the next round to discuss their thought process on the design and implementation. Question for Octopus management: Is this how lead engineers work at Octopus? Where PMs give them a requirement and they work in vacuum and then hope for the best? Because that is what is expected from the candidate as part of the code test.