My first step was a quick interview that felt almost like a timed Q&A. The format was straightforward: there were 4–5 questions, I was on a “no person” stage (so it didn’t feel like a traditional conversation), and I had about 60 seconds to plan an answer before being asked to deliver it for roughly two minutes.
What stood out was how much pacing mattered. The questions weren’t presented in a way that let me meander, so I had to structure my thoughts fast. Even though the timing created pressure, the questions themselves felt manageable, and I walked away feeling like it went fine.
4 months ago
Average Positive Hyderābād
The timeline was the first thing I noticed. It took about 2–3 weeks from when I started to when I reached the interview stages. The first round was described as a basic filter and included an online Codility-style test.
After that, I had a second round that was in person in the office. That part was a face-to-face interview, and it was held for a senior Software Engineer role.
4 months ago
Average Neutral Bulgaria
I went through a pretty standard multi-stage path, but the experience felt messy. It started with a recruiter phone call where the interviewer spoke e…
5 months ago
Average Negative Heredia
My process was short and tightly structured: I had two interviews. One was with the manager of the team, and the other was a technical conversation wi…
5 months ago
Average Positive Nottingham, England
My interview centered on a technical chat with the manager or lead developer. The conversation was broad but still technical, touching on general soft…
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 spans 2-3 weeks and includes multiple stages such as an initial coding screen, followed by technical and managerial interviews. Candidates should expect a steady pace but may experience delays due to scheduling or communication issues.
TimelineMulti-stageSteady pace
Technical Assessments
Candidates will encounter various technical assessments, including online coding tests (often Codility-style), live coding sessions, and discussions on software engineering principles. Expect a mix of algorithmic problems and language-specific questions, with a focus on clarity and correctness.
Coding testsLive codingTechnical principles
Behavioral & Managerial Interviews
Behavioral interviews are integrated into the process, often focusing on past experiences and problem-solving approaches. Candidates should prepare for discussions that gauge both technical knowledge and cultural fit within the team.
BehavioralCultural fitExperience-based
Communication & Feedback
The quality of communication throughout the process varies; some candidates report clear updates while others experience ghosting or lack of feedback. Candidates should be prepared for potential delays and follow-ups to ensure clarity on their status.
CommunicationFeedbackFollow-up
Difficulty Level
The overall difficulty of the interviews is generally described as average, with some candidates finding specific technical questions challenging. Preparation should include a mix of coding practice and understanding of software engineering concepts.
Average difficultyTechnical questionsPreparation
Group Assessments
Some candidates may participate in group assessments that include collaborative tasks alongside individual interviews. These sessions are designed to evaluate teamwork and interpersonal skills in addition to technical abilities.