Candidatei-me online. Fiz uma entrevista na empresa Exabyting.
Entrevista
Exabyting’s interview process can be lengthy and demanding, with multiple technical and psychological rounds that may feel excessive. In my case, most of the 4–5 interviews were scheduled during regular office hours, often in the middle of the workday, making it difficult to manage alongside my existing job. This may be challenging for other working candidates as well.
After completing all stages and aligning on general terms, one would normally expect the process to move smoothly toward closure. During the final phase, I raised a small and respectful query about scheduling logistics, after which the direction of the process changed unexpectedly and did not progress further. The explanation focused largely on behavioral interpretations and placed responsibility on the candidate side rather than addressing the broader context, which was discouraging given the time and effort invested.
From my perspective, hiring decisions appeared highly centralized, and the final interactions sometimes felt subjective rather than purely based on technical evaluation or fit. The “interview board review,” intended to track candidate progress, can feel as though it supports the rejection decision and frames concerns around the candidate, especially since the documentation is prepared internally. Although the company collects feedback from rejected candidates to improve the process, similar concerns seem to recur without clear visible changes.
At the same time, their HR and marketing teams present a polished image on LinkedIn and Facebook, frequently highlighting culture and work environment. Based on my experience, this public image does not fully reflect the candidate experience. However, I have heard positive reviews from individuals who have already joined and witnessed a good work culture.
Perguntas de entrevista [1]
Pergunta 1
Data Structures, Algorithm Complexity, Spring Boot, Thread, Database Isolation, Sorting Algorithms,System Design, OOP Principles, Database Design, SOLID, Recursion, Edge Case Handling, Mathematical Logic in Code, some hands-on coding problems were also given to test logical implementation and efficiency etc
i interviewed for python but the guy who took my interview was from java. though he asked me questions from python but as he lacked info about python, the questions were vague
Candidatei-me online. O processo levou 2 meses. Fui entrevistado pela Exabyting (Daca) em set. de 2025
Entrevista
The interviewer was similarly experienced as me (around 5 years) leading a small team of maybe two people. He started casually speaking and in not so serious topics, like where he is from, what he loves to do and asked similar things about me. Then he proceeded with short technical questions one by one. He didn't have AWS experience and thus couldn't relate to my career experience fully and mostly stuck to generic questions in software engineering. It was friendly interview but a bit disappointing as I felt not being on the same page with him about a few matters.
Perguntas de entrevista [1]
Pergunta 1
Hiking stage: (30 mins interview):
- indexing and does db auto index something (yes, when unique)
- is redis single or multi-threaded
- binary tree vs binary search tree vs balanced tree
- any algo that fascinates you
- how to detect cycle in graph
- graph vs tree
- event loop (the context switching, time slice, round robbin etc, he didnt ask about threading, rather how one thread do tasks simultaneously)
- do you use oop? since not, how do you reuse stuff?
- open to switching stack?