Payroc interview questions

Very one sided interview process. First interview a bunch of OOP related questions, but they didn't leave any time for me to ask questions. Not much effort spent by them to get to know me as a person and they did not at any point explain to me anything about the company or the role. The whole interview process was very impersonal and they only communicated to me through generic email addresses, there was no person involved. After first interview they gave me a take home test to do a L4 Load Balancer. The brief was like 3 sentences and extremely vague, and only a 72hr deadline. No acceptance criteria, specification or anything. After spending much time developing my first ever Layer 4 Load Balancer, second interview they asked me to spend 70 minutes explaining my solution; didn't seem they even bothered to read my code at all. The interviewers didn't even seem that they knew the language that the role was for (C#) and I had to explain certain language features I'd used in my solution to them, which I shouldn't have had to do. And after such audacity of not even reading my code and only relying on my 70min explanation (every other take home test I've done they had the sense of mind to actually read my code beforehand): still next to no time allotted for my own questions, no explanation of the company or the role, and they were bold enough to reject me afterwards without feedback. When I chased up for feedback I was told my solution lacked unit tests, even though I was never asked to add any and I was only given 72hrs to do it, so why the heck would I add unit tests??? Absolutely ridiculous. No concern for my time at all. And yet I still see them hiring for roles in many places. Please do not waste your time with this company: they are looking for unicorns.

Remote interview via Teams. General Q & A around experience to date. When have you went 'above and beyond' (that usual question). Technical questions and exploring approaches to projects. Touched on monitoring and resilience. Scenarios around database design.