I had a short phone interview that lasted about ten minutes. The questions felt fairly straightforward and centered on fundamentals: version control basics, HTTP-related topics, and object-oriented programming principles.
After that, the interviewer shifted into scenario-style questions. I had to think through different problem situations and explain how I’d approach solving them step by step. It didn’t feel like a trick interview, more like a quick check of how I reasoned when the problem details changed.
4 months ago
Average Negative Singapore
I went through multiple rounds and the process felt like it was moving normally at first. After the interviews, though, I didn’t hear anything back for about a month.
When I followed up with HR, I was told the whole team had frozen until the new financial year. After that, there was still no clear next step or timeline—just silence. The experience left me feeling stalled more than rejected, because nothing was actually communicated beyond the pause.
5 months ago
I interviewed for a backend role and the discussion was clearly anchored in a modern Java stack. The technical part revolved around Java and Spring Bo…
6 months ago
Average Neutral Bucharest, Bucuresti
The process I experienced felt pretty calm and well-run. Difficulty-wise, it landed around average for me, and the coding portion was a focused live c…
7 months ago
Average Neutral United States
My process started with an HR screening and then moved into a technical interview that leaned heavily on SAP ABAP fundamentals. The conversation wasn’…
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 consists of multiple rounds, starting with a brief HR screening, followed by technical interviews that may include coding and behavioral assessments. Candidates have noted delays in communication and feedback, with some experiencing lengthy waits for updates after their interviews.
HR screeningmultiple roundscommunication delays
Technical Assessments
Technical interviews focus on programming fundamentals, with questions often centered around specific technologies relevant to the role, such as Java, Spring Boot, or Python. Candidates reported a mix of live coding sessions and theoretical questions, with an emphasis on problem-solving and reasoning during coding tasks.
live codingJavaPython
Behavioral Questions
Behavioral interviews assess candidates' motivations, experiences, and problem-solving approaches, often using scenario-based questions to evaluate how candidates handle real-world situations. The tone during these discussions is generally friendly and conversational.
behavioralmotivationsscenario-based
Difficulty Level
Candidates have reported a range of difficulty levels during interviews, with some finding the technical questions to be challenging and others describing the experience as average. The overall tone of the interviews is often supportive, but some candidates felt overwhelmed by the complexity of certain questions.
average difficultysupportivechallenging questions
Feedback & Follow-Up
Many candidates expressed frustration over the lack of timely feedback and closure after interviews, with some receiving generic rejection messages without detailed explanations. This lack of communication has left candidates feeling uncertain about their performance and the decision-making process.
lack of feedbackgeneric rejectioncommunication issues
Cultural Fit & Team Dynamics
Interviews often include discussions about team dynamics and cultural fit, with interviewers assessing how well candidates align with the company's values and working style. Candidates noted that these conversations were less confrontational and aimed at understanding day-to-day operations.