I had an online interview with a startup. They used a website where I could submit my programs to a set of programming questions. there was this question, whic

I had an online interview with a startup. They used a website where I could submit my programs to a set of programming questions. there was this question, which I don't remember now. the question had example inputs and outputs. the examples had a few sorted arrays as inputs. but the question didn't say that the answer should only accept sorted array. when the array is sorted, the solution is easier. but even it is not sorted, sorting the array first won't result in extra big O time. And sorting is trivial, so I commented in the code that I only implemented a solution where I expect a sorted array as the input. The question isn't clear regarding if the input is sorted or not. In case, the input is not sorted, sorting is trivial. I could use whatever to sort it .... I was proud of my answers, not on this question, but questions before this one. As some questions asked for bit manipulation. and I used inline assembly for a very speedy implementation. After I submitted my answers, the CTO of that startup ran my code against their unit tests, and minutes later I received rejection. I asked them, why? he gave me a case where the input is not sorted. clearly he didn't even look at my code. Using ambiguous questions to reject people doesn't make sense to me. Plus, the online coding platform isn't interactive at all. there was no chance for me to clarify the question. I guess they made this question unclear on purpose, but I don't know what they are testing? interview skills I guess? Or maybe they wanted to test if I'm a rigorous person. of that I didn't fail, as I had pointed out the input requirement was unclear. They didn't even't look at the code, not too many lines, which I feel disrespectful.