My interview path centered around an AI coding round that lasted about an hour. The problem itself felt fairly abstract, but what stood out was the emphasis on requirements comprehension before writing any code. I spent close to 25 minutes clarifying what was expected and making sure I understood the goal and constraints.
From there, the rest of the time went toward coding, with the round designed around using that earlier understanding to drive implementation. The overall loop I experienced was basically the AI coding round plus a system design round.
5 months ago
Average Positive Bengaluru
After a recruiter reached out, I went straight into a hiring manager conversation where we mostly discussed my resume and the systems I’d worked on. The coding round didn’t include DSA-style problems, and the main prompt was to build a service along with a database schema. It felt more practical than algorithm-heavy.
Next came the system design round, and it stayed fairly general—more about infra and how the product pieces fit together, plus database considerations. There wasn’t a huge amount of trickiness in the framing, but I had to be clear about tradeoffs and implementation details. Overall, it felt like a fairly straightforward loop with three meetings total.
6 months ago
Easy Negative London, England
A recruiter emailed to schedule a call, but the message had two different scheduling links. I went through the motions to interview, but after that po…
6 months ago
Average Positive India
My loop was three rounds and moved quickly enough that it felt pretty focused. First was a hiring manager round where we talked through my resume in d…
6 months ago
Difficult Positive United States
The most intense part of my round was a take-home programming assignment, followed by a code review call on Zoom. After submitting, I went into review…
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 consists of a recruiter call, a hiring manager discussion, followed by coding and system design rounds. The overall timeline is generally quick, with some candidates experiencing a smooth flow and others facing delays or ghosting after interviews.
Recruiter callHiring managerQuick process
Coding & Technical Rounds
Candidates can expect a mix of coding challenges that focus on practical applications rather than traditional algorithm questions, with prompts often requiring end-to-end solutions or service implementations. The coding rounds may include live coding or take-home assignments, with an emphasis on clarity and requirements comprehension.
Practical codingEnd-to-end solutionsLive coding
System Design Interviews
System design rounds are a significant part of the process, where candidates are asked to discuss high-level architecture and design considerations for various systems. Candidates should be prepared to explain trade-offs and implementation details clearly.
System designArchitectureTrade-offs
Behavioral & Values Fit
Behavioral interviews focus on understanding candidates' past experiences, decision-making processes, and how they approach challenges. Interviewers often seek clarity on candidates' thought processes and values alignment with the company culture.
Candidates have reported mixed experiences with recruiter communication, ranging from supportive and organized to unresponsive and frustrating. Clear communication throughout the process is essential for a positive experience.
Recruiter communicationCoordinationFeedback
Overall Difficulty & Outcomes
The overall difficulty of the interviews is generally perceived as average, with candidates receiving offers after demonstrating a solid understanding of technical and behavioral aspects. However, some candidates experienced ghosting or lack of follow-up, impacting their overall impression.