Envié una solicitud electrónica. Acudí a una entrevista en HungerStation en nov 2025
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Complete the code exercise (Design Patterns/OOPS)
Explain ACID, SOLID etc.
Solicité el puesto a través de la recomendación de un empleado. Acudí a una entrevista en HungerStation (Riad) en jun 2025
Entrevista
Summary : After passing 4 rounds of technical interview, CTO said to me on call "We don't hire people from one of your past companies". Lol. Rejected.
Read in detail below:
1 - Initial HR call
2 - First technical round it included:
a - SOLID and Design Patterns
b - Screen sharing coding session, no language no compile, just process and clean code. And a DB query and logs to look and discuss possible issue.
c - Microservices and when to chose & some more questions
3 - Second Technical interview, System design on draw.io how uber/careem finds car close to you. Then a separate detailed discussion on planning a monolithic to microservice. What can happen wrong. How to tackle it. Migrating related questions.
4 - Another technical round with principle engineer, again discussed microservices. How you measure performance. What techniques to do monitoring. Code quality questions. How handle transactions in microservices. How will you scale an app and why choose the stack?
5 - CTO interview, again asked technical questions about microservices, when to choose monolithic, how you measure performance. If there is crash how will you respond? How will you observe and monitor your code? Asked about my past experiences and why did i choose specific tech stack for one of the case?
On call with CTO, he said you come from a specific company and we usually dont hire people from that company:)
I said, I have already cleared all 4 rounds of interviews, so i think I have what it takes to be here.
So, after CTO interview, i got rejection.
What a waste of time. I can not believe a CTO asking technical questions that have already been asked multiple times during previous rounds. And then finally rejecting and saying to me on call that i don't hire people from this company. I find this a very low evaluation point.
Preguntas de entrevista [1]
Pregunta 1
SOLID, Design Principles, Microservices, Transactions, Threads, System Design, Code Performance