My interviews followed a multi-round path and felt clearly engineering-focused, with a strong emphasis on live coding under time pressure. I went through several rounds that included a hiring manager conversation and at least one presentation moment tied to the technical work. The technical side included a hard LeetCode-style problem with extensions, and another live coding challenge where I had to build a project from scratch quickly.
One part that really stands out was how compressed the work was: I had only 45 minutes to produce something substantial, and the prompt wasn’t just about writing an algorithm—it also required understanding how to work within the platform they were using. Difficulty-wise, it felt like intermediate-to-hard consistently, and the hiring bar seemed unforgiving.
9 months ago
Average Neutral London, England
Right after my CV got through, I got sent a Codesignal test. The question was basically about labeling Tetris-like blocks by mapping each block type to a different value, with the goal of making the code general rather than hardcoded to a single layout.
There were 10 tests overall, so I was constantly checking whether my approach would hold up beyond the first scenario. The round felt like it was testing the shape of my thinking as much as the final logic, since if I tried to shortcut the generality, I could tell quickly from how the tests behaved.
> 1 year
Difficult Positive London, England
After an initial HR conversation, I moved into a more hands-on technical track that felt intense and fairly algorithm-driven. I went into a live codin…
> 1 year
Average Neutral India
My process started with a recruiter phone screen, and then the technical part moved quickly: two separate coding rounds followed by a system design in…
> 1 year
Average Neutral United Kingdom
My timeline stretched out to more than a month, and the coordination issues started to shape my experience almost as much as the interviews themselves…
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
Coding Assessments
Candidates typically start with a coding assessment that can include multiple questions, often under time constraints, focusing on data structures and algorithms. These assessments are generally challenging, with many candidates reporting a mix of medium to hard problems.
LeetCode-styleHackerRankTimed assessments
Technical Interview Rounds
The interview process includes several technical rounds, often featuring live coding sessions where candidates must solve problems in real-time while discussing their thought process. Interviewers expect clear reasoning about time and space complexity, and the difficulty level is usually intermediate to hard.
Live codingAlgorithmsComplexity analysis
System Design and Behavioral Interviews
Candidates also face system design interviews where they must discuss architectural decisions and trade-offs, along with behavioral interviews that often utilize STAR methodology to evaluate past experiences and cultural fit. These rounds are structured and distinct from technical assessments.
System designBehavioralSTAR
Communication and Coordination Issues
Many candidates experienced significant delays and poor communication throughout the interview process, including scheduling issues and lack of follow-up after interviews. This can create frustration and uncertainty about their application status.
Coordination issuesCommunicationFollow-up
Interview Environment and Interpersonal Dynamics
The atmosphere during interviews can vary, with some candidates reporting a supportive environment while others faced dismissive or unengaged interviewers. This interpersonal dynamic can significantly impact the overall experience and candidate performance.
Candidates noted that while the interview process was often well-structured, the feedback received post-interview was sometimes vague or lacking, leaving them uncertain about their performance and areas for improvement.