My interview started off feeling like it would test real engineering thinking, but the early technical rounds quickly became a mismatch. In the pair programming round, I was given object-oriented skeleton code with placeholders to fill in, and I worked on something circuit-breaker adjacent. The evaluation criteria were mainly about whether I knew the concept, whether I could propose multiple approaches, and how well I could collaborate with the interviewer. I didn’t need to be perfect on syntax, but the logic still had to be structured and efficient enough.
After the coding part, system design was on a business scenario, and the round asked me to reflect on past projects. I talked about things like latency and consistency trade-offs, plus query patterns. But what stood out most was how inconsistent the feedback and expectations were across interviewers—one pushed me toward an unnecessarily complex design, while another wanted something straightforward that satisfied the requirements.
4 months ago
Average Positive Tallinn
My process started with a recruiter screen where we covered my background and fit for the role. After that, I moved into pair programming with two engineers to implement a product feature. The session felt fairly relaxed overall and focused more on how I worked with someone than on doing any clever algorithm gymnastics.
Next came system design. I remember being asked to design a scalable platform that could handle payments, and the conversations were grounded in practical constraints rather than purely academic diagrams. I then had a product interview where the emphasis shifted toward product understanding and how I fit the team culturally. I had to talk through how I’d think about the work and how I would define success for the team, and it leaned heavily on soft skills.
4 months ago
Average Neutral London, England
The journey I went through had a clear five-stage structure, starting with a recruiter call that was basically a Q&A. That first step took about half …
5 months ago
Average Positive Tallinn
Recruiter communication set the tone for me in a good way, and the early stages felt supportive. I did a pair programming round with an engineering le…
5 months ago
My process stretched out to about a month and followed a very structured path. It started with a recruiter call, then moved quickly into a coding step…
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
Recruiter & Initial Screening
The interview process typically begins with a recruiter call that covers background and fit for the role, setting a generally supportive tone. However, experiences vary, with some candidates noting rushed or superficial interactions that left them feeling uncertain about expectations.
RecruiterInitial ScreeningCandidate Experience
Technical Assessments & Pair Programming
Candidates undergo a pair programming round that often emphasizes collaboration and practical problem-solving over pure algorithmic challenges. The format can vary significantly, with some candidates experiencing supportive interactions, while others report confusion due to differing expectations among interviewers.
Pair ProgrammingTechnical AssessmentCollaboration
System Design Interviews
System design rounds focus on real-world applications and practical constraints, but candidates often report inconsistent expectations from interviewers, leading to confusion about what constitutes a successful design. The emphasis is on applying engineering judgment rather than rote memorization of patterns.
System DesignPractical ConstraintsEngineering Judgment
Product & Cultural Fit Discussions
Interviews include discussions around product understanding and cultural fit, where candidates are evaluated on their past experiences and how they would define success within the team. These rounds often lean heavily on soft skills and can be pivotal in the overall assessment.
Product DiscussionCultural FitSoft Skills
Feedback & Communication
Feedback during the process can be inconsistent, with some candidates receiving timely and constructive insights, while others report vague or delayed responses that leave them feeling uncertain about their performance. This variability can significantly impact the overall candidate experience.
FeedbackCommunicationCandidate Experience
Overall Process Length & Structure
The interview process is generally structured and can take several weeks to complete, with multiple stages including assessments and interviews. Candidates often express frustration with the length and pacing, especially when key expectations are not communicated until later stages.