HungerStation interview questions

The initial recruiter call was professional and well organized. The recruiter provided clear information about the role, expectations, and the overall interview process. The technical interview included a live coding session of approximately 45 minutes. The questions were relevant and required a solid understanding of object-oriented programming and design patterns. The remaining 30 mins of the interview focused on standard theoretical topics such as ACID properties and other backend fundamentals. Overall, the discussion felt constructive and aligned with the responsibilities of the role. However, after the interview there was no communication or follow-up from HungerStation regarding the outcome. Even a brief update indicating whether the process would continue or not would have been appreciated. Providing candidates with a simple response or short feedback demonstrates professionalism and respect for their time and effort. Unfortunately, the lack of any response left a disappointing impression of the overall experience.

I cleared the first round, which was a live coding session. The interviewer was very supportive, and I was able to solve the problems successfully. In the second round with a Ukrainian interviewer, out of 90 minutes, around 60 minutes were spent on theoretical questions. I used the remaining 30 minutes to explain my system design thoroughly. Despite this, the HR feedback was disheartening. The reason mentioned for rejection was that I had “zero production experience in GoLang.” I had actually shared my 6 months of GoLang experience during the interview, and I successfully explained a saga design pattern. In my system design, I chose a graph database for storing user data, but I forgot the exact name (Neo4j) when asked. It felt frustrating that after 1.5 hours of discussion, the focus seemed to be only on a few minor points rather than the overall performance and understanding demonstrated throughout the interview.