Arrayhopper question over HackerRank before an interview with anyone. I was told that some of "their" test cases didn't pass my code and I was rejected. After a long time I was given their test cases and what I found was that their interpretation of the problem is different from mine. Remember, you can only print out indices that you can actually go to, not ones you consider going to. So, if the test case is [2 0], you output "0, out" and NOT "0, 2, out" even though you considered the value 2. You can ONLY output indices which is not very clear based on the problem statement. In that case, you can't go to 2, but you do consider it, so it's only "0, out." You can go "beyond the array" with only considering 2. Most of the misinterpretations stem from " Once you can legally hop beyond the last array element, you have successfully traversed the array." What does beyond the last array element mean? It doesn't mean simply the last array element like a real ArrayHopper question, but actually arraysize+1. Also what brings up confusion is "If there is no solution, the program should write the string “failure” to the standard output stream, followed by a newline character." Well, what exactly is no solution? If it gets stuck? If you can't reach arraysize+1? The company is setting up software engineers for failure by not providing all of the test cases on HackerRank at compilation time. There are too many possibilities and it is difficult when only one example in the problem statement and two example test cases are actually given. Also keep note that if you click "run code" twice, you get all 15 test cases and not just the two sample ones. I failed too many test cases because I didn't understand the index issue and was rejected. "Performance is paramount for our company" and so on. Well, if you made the problem more clear I would have passed.