My journey started with an interview setup that quickly moved into a heavy technical day. I ended up with five interviews total. After an initial phone screen, I had three separate programming interviews, each about an hour. Those were the more standard coding-style sessions, and then I hit a much longer challenge that lasted four hours where the interviewer checked in periodically to see how things were going.
After that programming stretch, there was still one more interview with a hiring manager. What I remember most was how seriously the technical questions were taken—they felt like they were probing my real expertise rather than just testing whether I could get through a single problem. Even in the hiring-manager deep dive, the conversation tied back to my project experience, not generic talk.
11 months ago
Average Negative United States
My first interaction started with the recruiter screen, and that’s where the vibe soured for me. During the conversation, the recruiter asked questions about whether I was familiar with data structures and algorithms—even though I had a CS background and experience at a top-tier company. It came across as condescending, and the questions felt more like checking boxes than trying to understand my actual background.
As the conversation continued, I answered honestly, but I felt like my responses weren’t being treated fairly. There was a sense that my clarification didn’t land, and the recruiter’s recap stayed wrong even after I tried to correct it. The process then moved toward a quick rejection decision without meaningful follow-up.
> 1 year
Average Positive United States
My process kicked off with a quick recruiter call where the recruiter set expectations and walked me through the timeline. That call was pretty straig…
> 1 year
Average Positive Hong Kong
I went through a pretty fluent, step-by-step process that started with a recruiter call. They explained what Liftoff was, asked questions about my bac…
> 1 year
Average Neutral United States
My process felt pretty clearly staged, but the goalposts didn’t come through cleanly to me. I started with a one-hour technical screening using an onl…
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 begins with a recruiter call to set expectations, followed by a technical screening and then multiple back-to-back interviews, often culminating in a longer coding challenge. Candidates can expect a well-organized flow with timely communication throughout the process.
Recruiter callTechnical screeningInterview flow
Technical / Coding Screens
Candidates will face several technical interviews focusing on coding challenges, often in a format that allows them to use their own development environment, which simulates real work conditions. Expect a mix of algorithmic questions and practical coding tasks, with a significant emphasis on problem-solving skills.
Coding challengesLeetCode-stylePractical tasks
Extended Coding Challenge
A notable aspect of the interviews is the longer coding challenge, which can last up to four hours and is designed to assess candidates' coding abilities in a more hands-on manner. This challenge is less about rapid problem-solving and more about demonstrating coding proficiency and thought processes.
Long coding challengeHands-on assessmentProject-based
Behavioral & Hiring Manager Interview
The final stages often include a conversation with a hiring manager that focuses on the candidate's past experiences and fit within the team, rather than just technical skills. This part of the interview aims to evaluate candidates holistically and gauge their interpersonal skills.
Overall, candidates report a friendly and professional atmosphere during interviews, with responsive recruiters who provide clear feedback and maintain open lines of communication. However, some candidates noted discrepancies between their performance and the final evaluations, leading to confusion.
Candidate experienceCommunicationFeedback
Difficulty & Expectations
While the technical questions can be challenging, candidates generally find the interviews engaging and well-structured. However, some have expressed that the evaluation criteria were not always clear, leading to unexpected outcomes despite feeling confident in their performance.