I advise people not to waste their time. I wish I had read others' reviews before bothering.

The interview process had 5 stages:

• The initial screen with the internal recruiter was fine.
• The coding challenge was a nice challenge. I would say I completed it almost perfectly with TDD, explaining my thoughts, and fulfilling all their requirements. It was just core Java, which I have 15+ years of experience in. I've interviewed many people and know exactly what is being looked for.
• The interviewer seemed unengaged for some reason.

I just received an email stating they had thought about it and decided against hiring me. They suggested I learn their tech stack and reapply. I was only tested on Java, despite having architected and written full products, including pipelines and all the cloud infrastructure as code. I have plenty of experience in many tech stacks.

As for the role itself, they seem to focus solely on Java development and are quite old-school, where engineers don't touch any of the DevOps side. They have a very basic career path, but I would like to think that would change as they mature as a company.

The main problem with the interview, however, is that neither the recruiter I dealt with nor the initial recruiter who reached out to me responded when I asked for feedback. Neither demonstrated a level of professionalism to respond.

Perhaps it's worth considering them again in a few years when they have matured a little as a company.

Initial questions were basic, like: What is ACID? What is CQRS? What are equals and hashcode?

Write a load balancer that can only take 10 service registries, with no duplicates, and ensure it can handle concurrency. Then, add strategies for Round Robin and Random when fetching. They apparently want a Test-Driven Development (TDD) approach, so implement it that way.