My round felt very tense and difficult right from the start. The conversation came across as abrasive and one-sided, with the interviewer explaining their own points without really listening to what I was saying. Even though I was able to get through it, the client-style call itself was challenging to navigate.
By the end, I didn’t feel like the process was “on me” in a normal way—it felt more like the communication style made the interaction harder than it needed to be. I didn’t receive an offer, and honestly it wasn’t the kind of environment I enjoyed or felt aligned with.
4 months ago
Average Neutral Poland
I went through a sequence that started with a relatively straightforward coding check, followed quickly by a heavy theoretical round. The first part was easy enough to settle me down, but then the interview shifted into broader questions about programming language fundamentals and how those concepts translate into real systems.
Across the technical conversation I got pushed on frameworks and architecture ideas like microservices, plus general programming and database concepts. I also had to talk through OOP topics in depth—things like encapsulation and abstraction—then connect them to real-world examples. Later in the same technical flow, the questions turned more intense on C++ and core software engineering concepts: OOP from basics up through stronger understanding, and even topics tied to unit testing and agile were brought up.
4 months ago
Average Neutral Turin
After a recruiter outreach, I went through a short, friendly sequence: first a call with HR, then a technical interview, and finally a manager round. …
4 months ago
Average Positive Spain
My process started with a recruiter reach-out, and a few days later I was pulled into a technical conversation that mixed live coding with role-focuse…
4 months ago
Average Positive Poland
My experience started with a straightforward technical interview centered on C++. The coding portion felt manageable—an easy LeetCode question—followe…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with a recruiter outreach, followed by a technical interview and a managerial round, with timelines varying from a few days to several weeks. Candidates noted that communication about scheduling and feedback can be inconsistent, leading to uncertainty about their status.
Technical interviews often emphasize a mix of live coding and theoretical questions, primarily centered around programming fundamentals, C++, Java, and software architecture. Candidates should prepare for a range of topics, including OOP principles, frameworks, and practical coding tasks, rather than just algorithmic challenges.
Live codingC++Java
Communication Style & Environment
Candidates reported varying experiences with interviewers, ranging from supportive and engaging to abrasive and unprofessional. The communication style can significantly impact the interview atmosphere, with some candidates feeling rushed or dismissed during technical discussions.
Communication styleInterview atmosphereProfessionalism
Behavioral & Managerial Discussions
Managerial rounds often focus on fit and past experiences, with discussions about teamwork, project management, and handling customer interactions. Candidates should be prepared to articulate their work history and how it aligns with the company's needs.
Managerial roundBehavioral questionsTeamwork
Feedback & Follow-Up
Many candidates expressed frustration with the lack of feedback and closure after interviews, with some experiencing ghosting or delayed responses. It's advisable for candidates to proactively seek feedback and clarity on next steps after their interviews.
FeedbackFollow-upCommunication
Overall Difficulty & Candidate Experience
The overall difficulty of the interviews is perceived as average to tough, with varying levels of pressure and expectations. Candidates should be ready for a demanding process that tests both their technical skills and their ability to communicate effectively under pressure.