Xolo (Estonia) interview questions

The entire recruitment process was very easy and convenient for the job seeker. HR did their job very well, I was informed about the next steps and deadlines. I received detailed feedback.

I was interviewed for the role of Product Engineer, which is a Software Engineering position. I went through a total of four interviews, including the initial recruiter screening. Screening Interview: This was a 45-minute conversation that covered some basic questions and an introduction to the company and the role. The recruiter was very kind and made the discussion comfortable and engaging. Product Interview with the COO: This was a one-hour session where we discussed my previous experience, my motivation for joining the company, and my interest in contributing to the product side rather than just focusing on code. Technical Interview: This was another one-hour interview focused on technical topics, but the questions were more conceptual than technology specific. I was asked about clean code, how to handle production issues, and given a small design scenario. The interviewer was really nice and asked questions that were very relevant for a Mid/Senior level engineer not the kind of low-level or core Java questions that are typically asked of fresh graduates. I really appreciated the focus on practical thinking and problem solving over rote technical trivia. Interview with the CTO: This interview wasn’t originally scheduled, but since the CTO had recently joined the company, he wanted to speak with me directly. It was planned for 30 minutes but ended up lasting an hour. We had a deep discussion about my past experience, especially around microservices. It felt more like a technical conversation than a formal interview — we were so engaged that neither of us noticed the time. The CTO was also very approachable and open-minded. Overall, the interview process was smooth and enjoyable. There were no coding assignments or live coding rounds. The main focus was on whether the candidate is genuinely interested in working on the product side, not just writing code. For me, the process felt natural because I’ve always been involved in product thinking throughout my career.