The interview process is pretty straightforward. 1) HR screen. 2) Hiring Manager. 3) Super Day (System Design and Coding on-site). The recruiter was super kind and enthusiastic, but it took her a while to schedule the 2nd round. The 2nd round was a disaster. It was an early call, and the Hiring Manager couldn't stop yawning and stretching. It felt like he'd just been woken up 5 minutes ago - super unprofessional. His rejection feedback was not in sync with what happened during the call; I would recommend him staying awake next time.

Well, this one was... interesting. I honestly don’t even remember when I applied, since there was no confirmation or acknowledgment at the time. By the time they reached out, weeks or months later. I had forgotten about it. Their first contact came completely out of the blue — a take-home assignment sent without any prior conversation or introduction. The odd part was that it was for a .NET Engineer role, despite the fact that I’ve never worked with .NET. They mentioned that was fine as long as I was open to learning it, which already set the tone. Fortunately, the task could be completed in Java. However, the project skeleton they provided was easily among the lowest-quality Java code I’ve ever encountered in an interview setting. I couldn’t resist cleaning it up a bit before proceeding — perhaps that was a mistake. The feedback I received for my clean, structured, and well-tested solution was that it was “hard to follow” and “not tested enough.” At that point, I realised we were simply operating at different levels of understanding. My impression was that the code I received reflected a lack of familiarity with standard Java practices — exactly the kind of outcome you might expect if I were to write .NET code from scratch.