After an initial recruiter touchpoint, I later got pulled into a task-based stage. The assignment involved navigation route calculation, and I completed it and submitted it over email. The task was reviewed and approved, and after a few weeks I was invited to another interview on Teams.
That Teams meeting came after the project work step, so it felt like they had already aligned on what I could produce from the task. The overall pace stretched out a bit, mostly because of the time between task submission and the next scheduling.
> 1 year
Average Positive Belgrade, Central Serbia
My first steps were pretty structured. I was introduced to a project manager and developers who worked on the same project, and the PM showed me what they were building. Early on, they asked me to introduce myself, which set the tone for how they wanted to think about my background.
Then the interview shifted into the technical part. Most of the questions were C++ related, and they kept coming one after another for about the first thirty minutes. After that, they gave me three separate coding questions to work through.
> 1 year
Average Negative Houston, TX
I joined a short call that barely lasted about five minutes, and it started off wrong. I said hello, but the interviewer immediately got into the ques…
> 1 year
Difficult Neutral Belgrade, Central Serbia
My interview process started with a CV screening step and then moved straight into a technical interview with a lot of different topics packed into ab…
> 1 year
Average Negative Finland
I was given a coding challenge to complete, and I worked through it until I’d solved most of the problems. After that, I followed up asking for feedba…
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
Initial Screening & Task-Based Stage
The interview process typically begins with a recruiter touchpoint followed by a task-based stage where candidates complete a coding assignment that is reviewed before moving to the next interview stage. Candidates should be prepared for a waiting period after task submission, which can affect the overall momentum of the process.
Recruiter touchpointTask-based assignmentWaiting period
Technical Interview Structure
Candidates can expect a structured technical interview focusing on C++ fundamentals, data structures, algorithms, and other relevant topics, often featuring multiple coding questions. It's important to be ready for a fast-paced environment where clarity of communication is crucial.
C++Data StructuresAlgorithms
Behavioral & Communication Assessment
Interviews often include a focus on behavioral aspects, assessing candidates' backgrounds and communication skills, which are considered important for team fit. Candidates should be prepared to discuss their experiences in a way that highlights their ability to communicate effectively.
Behavioral questionsCommunication skillsTeam fit
Interview Tone & Environment
The tone of interviews can vary significantly, with some candidates reporting negative experiences due to perceived rudeness or lack of respect from interviewers. It's advisable to remain adaptable and professional, regardless of the interview atmosphere.
Interview toneRespectProfessionalism
Feedback & Communication Post-Interview
Candidates often express frustration over a lack of feedback or communication after interviews, which can leave them feeling uncertain about their performance. Following up for feedback is encouraged, but candidates should be prepared for potential delays in responses.
FeedbackCommunicationFollow-up
Decision Timeline & Outcome
The decision-making process can vary, with some candidates receiving quick offers after a single interview while others experience longer waits. Understanding that outcomes can differ widely based on individual experiences is essential.