Entrata interview questions

The process consisted of an initial screening round (10–15 minutes) followed by a technical round. In the technical interview, I was asked about OOP concepts, SOLID principles, design patterns, Java, and SQL queries. I answered the Java-related questions confidently and explained the concepts clearly with relevant examples. However, after the interview, HR informed me that I was rejected. When I asked for feedback, I was told that I was not able to explain OOP, SOLID, and design patterns properly — which contradicts my actual interview performance. The feedback felt generic and inaccurate, and seemed more like a standard rejection reason rather than something based on a fair evaluation. Overall, the process lacked transparency, and the feedback was not useful for improvement.

The process stretched over 2+ months and 7+ rounds, which is impressive if the goal was endurance testing rather than hiring. There were 4+ technical rounds, and somewhere along the way it became clear that the interviewers themselves were still figuring out what role they were hiring for. Scheduling had its own unique charm - candidates were expected to prepare for the next round at lightning speed, but when it came to feedback or clarity, things moved at a more… philosophical pace (think 1–2 weeks of silence after each round). By the end, it felt less like an interview process and more like a long-term commitment - with no closure. Despite going through 7–8 rounds, there was no feedback on where things didn’t work out, which really adds to the mystery. On a positive note, everyone involved was polite and soft-spoken unfortunately, that didn’t translate into a particularly helpful or transparent experience.