My interview journey moved through several rounds and then stalled in a way that felt out of step with how the conversations had gone. Early on, I had an intro call with a director or hiring manager, followed by LeetCode-style coding medium questions and then a system design round, with a manager behavioral round and even an additional HR touchpoint. Across the technical discussions, the vibe was generally solid and the rounds felt fair enough while I was in them.
The problem showed up after the last interview. I was told the feedback was positive and that they needed more time to assess other candidates, and I was promised I’d hear back within a week. I waited, and nothing came. When I followed up, I got another delay explanation, then silence again. Even when I was told things were moving forward, the lack of a clear reason or any specific feedback made the rejection feel like it wasn’t properly closed out.
4 months ago
Average Positive New York, NY
After an initial recruiter screen, I ended up doing a coding-heavy process that leaned heavily on HackerRank and similar live coding setups. The first technical stage was framed like a real-world style prompt—something meant to mirror a day-to-day problem—but it still felt like trying to interpret requirements while using the platform itself. Even when I could see a path to the solution, the experience was often slower than expected because so much time went into figuring out exactly what the interviewer meant and how the environment expected the code to be structured.
Most of the rounds followed a familiar pattern: a coding challenge where I had to debug against test cases, then additional technical sessions that pushed me to reason about edge cases and complete as much of the solution as possible under time pressure. I remember one round where the interviewer focused on basic string manipulation and hash map logic, and I spent time explaining why the data representation felt unrealistic. I also had a session where I passed the tests but didn’t fully finish one required method, and for senior-level expectations they still wanted complete implementation.
6 months ago
Difficult Negative Edinburgh, Scotland
My process started normal enough: after an initial recruiter screen, I moved into technical testing and then a system-design-and-behavioral style set …
6 months ago
Average Positive Pune
I went through a two-round process that felt pretty focused and structured. Round one was technical and centered on taking a flat collection of object…
10 months ago
Average Positive United States
After a recruiter outreach, my process included an initial technical screen and then several more structured stages. Some of the rounds were coding ch…
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 screen, followed by multiple technical rounds that may include coding challenges, system design, and behavioral interviews. The overall timeline can vary, with some candidates experiencing delays and a lack of transparency in communication throughout the process.
Recruiter screenTechnical roundsTimeline
Coding Challenges
Candidates can expect coding challenges that often involve LeetCode-style questions, with a focus on debugging, edge cases, and real-world problem-solving. The coding environment may add pressure, as candidates are required to interpret prompts and complete solutions under time constraints.
LeetCodeDebuggingTime pressure
System Design & Behavioral Rounds
The interview process includes system design discussions where candidates are expected to articulate their thought process and reasoning. Behavioral interviews assess collaboration and communication skills, often focusing on past experiences and team dynamics.
System designBehavioralCollaboration
Communication & Feedback
Candidates frequently report a lack of clear communication and feedback throughout the interview process, leading to frustration and uncertainty about their standing. Many express a desire for more detailed feedback post-interview to understand areas for improvement.
FeedbackCommunicationTransparency
Interview Atmosphere & Pressure
The atmosphere during interviews can be high-pressure, with some candidates feeling rushed or interrupted, which may hinder their ability to fully express their knowledge and reasoning. This dynamic can affect overall performance and candidate experience.
High-pressureInterruptionsCandidate experience
Expectations vs. Reality
Candidates often find that the expectations set during the interview process do not align with the actual evaluation criteria, particularly regarding the depth and breadth of knowledge required. This mismatch can lead to feelings of disappointment and confusion about the outcome.