I ended up in a process that felt like it needed to be fast, almost abruptly. After a wait while they reviewed my CV, I got an invitation that I expected to be an introduction interview, but it turned into a technical interview right away. The developer explained they had too many applicants and that the process had to move quickly, and I was asked to solve tasks without any real framing.
The technical portion leaned on real problem-solving rather than a leisurely conversation. I had more than one coding-focused interaction, and while the questions weren’t described as deeply technical in a research sense, there were still a lot of calls that asked coding questions and tested how I thought. I also got the sense from later rounds that interviewer engagement varied—some conversations felt like people were busy or not fully invested, which made it harder to read what they were actually optimizing for.
> 1 year
Average Negative Spain
I started with a phone interview where we talked about my past experience and how it connected to areas like microservices—especially the tradeoffs of approaches like Spring Boot and why I’d used Docker before. It moved quickly and felt productive.
Then it switched into a coding round. The question itself was easy enough for me to discuss multiple solution ideas, and it turned out to be a medium-level leetcode-style problem. I ran into time pressure and didn’t get to cover complexity the way I wanted to, but I did walk through different approaches while I still had room to think.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
