I went through a multi-round structure where the first technical hurdle was an asynchronous OA-style set of problems: a DSA question, an SQL scenario question, and a regex task implemented in Python. It was the kind of mix that forced me to switch modes quickly—algorithms, then data querying, then pattern matching.
After that, the later technical part felt much more “engineering” than the straightforward coding formats. I ended up with a system-design style problem focused on calculating a running median over stock prices within a sliding window, and then I was asked to build a thread-safe LRU cache. Those were tough questions, but there was one moment of relief when the LRU portion clicked because it resembled something I’d already practiced.
1 month ago
Average Neutral New York, NY
My process started with a recruiter screen that felt pretty casual at first. They covered my background and did the usual fit-style questions, and at some point they even asked for my opinion on AI and related topics—more of a perspective check than a deep technical probe.
Not every part of the recruiter interaction matched that tone. In one conversation, the recruiter got visibly defensive when I was transparent about my leveling expectations, and it turned into frustration instead of a clean alignment discussion. Separately, I also hit a different recruiter-driven rejection experience where the interviewer seemed disinterested, and when I asked for feedback about not moving forward, it felt like the call lacked basic care for clear communication.
3 months ago
Difficult Neutral United States
I went through a fairly standard, structured pipeline that was explicitly outsourced to Uptime Crew. The stages were consistent in my mind: an online …
3 months ago
Average Neutral Mountain View, CA
My journey felt long and structured around a big set of steps rather than just quick screens. The early pieces leaned on an OA and take-home style wor…
3 months ago
Easy Negative United States
My experience started with a recruiter-oriented flow, and it moved quickly compared to what I expected. I got a coding round through to completion, bu…
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
Online Assessment Structure
Candidates can expect a challenging online assessment consisting of three parts: a DSA problem, an SQL question, and a Bash scripting task, all within a strict time limit of 90 to 120 minutes. The assessment requires quick switching between different problem-solving modes, which can be a significant stressor.
DSASQLBash
Recruiter Interaction
The recruiter stage varies in tone, with some candidates reporting casual conversations while others experienced defensiveness or disinterest. AI-related questions frequently arise, focusing on candidates' usage of AI tools in their projects.
Recruiter screenAI usageBehavioral
Technical Rounds and Build Challenges
Following the initial assessment, candidates typically face a technical screen focused on their build challenge submissions, where they must explain their code and design choices. The questions often delve into system design and concurrency, requiring a solid understanding of core concepts.
Technical screenBuild challengeSystem design
Behavioral Evaluation
Candidates should prepare for behavioral interviews that emphasize teamwork, collaboration under pressure, and the application of AI in their work. These discussions often tie back to candidates' past experiences and project history.
BehavioralTeamworkAI application
Communication and Feedback
Many candidates noted a lack of timely communication and feedback throughout the process, leading to frustration, especially after interviews. This can create uncertainty about their standing in the hiring process.
CommunicationFeedbackFrustration
Overall Difficulty and Experience
The interview process is perceived as structured but can be lengthy and stressful, with candidates often feeling that the assessment's difficulty exceeds expectations for the role. The experience can vary significantly based on the interviewers' engagement levels.