After an online assessment, the timeline got fuzzy. I completed the assessment around mid-February, but there weren’t any official emails afterward with a confirmed interview date. I only saw tentative scheduling details from the company, and even after that step was marked complete, nothing moved forward.
Because the process essentially stalled immediately after the assessment, I didn’t reach any actual interview rounds where I could demonstrate skills or have a technical discussion. What stood out most was the lack of official communication: the absence of a clear interview date and the uncertainty about next steps. I didn’t end up receiving an offer, and the experience left me with more questions than answers about whether the process was still active.
6 months ago
Average Positive New York, NY
After a recruiter call, my process moved pretty fast into two back-to-back coding interviews. The first coding round focused on DSA in Python/PySpark, and the second one was DSA-style work in SQL. I remember both feeling fairly demanding, but still aligned with core data-engineering fundamentals rather than trick puzzles.
Once the two coding rounds were done, I had the hiring-manager stage that blended technical and managerial discussion. That round felt more like unpacking how I think through problems—my prior work, how I’d approach work end-to-end, and the reasoning behind my decisions. The last step was a system design interview with a two-person panel. Overall it felt like a structured climb from fundamentals to how I’d design solutions at a higher level, and I walked away feeling like the bar was consistent across stages even though there wasn’t an offer.
11 months ago
Average Neutral India
My first interaction was pretty grounded in the role I’d listed on my profile. They asked me about the projects I’d mentioned, and because I had writt…
> 1 year
Average Positive India
My interview journey started with a technical round that was scheduled in a longer block, about an hour and fifteen minutes. It covered a lot of SQL a…
> 1 year
Difficult Neutral India
My interview ended up being around three rounds total, split between technical and managerial. Two of the rounds were technical, and one was manageria…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Assessment & Communication
Candidates often begin with an online assessment, but experiences with communication afterward vary significantly, with some reporting delays or lack of clarity on next steps, which can lead to frustration and uncertainty about the process.
AssessmentCommunicationTimeline
Technical Rounds Structure
The interview process typically includes multiple technical rounds focusing on core data engineering skills, including coding in Python, SQL, and big data technologies like Spark and Azure, with a mix of practical and theoretical questions.
Technical RoundsPythonSQL
Behavioral & Managerial Interviews
Candidates experience a blend of behavioral and managerial discussions, often aimed at understanding their problem-solving approaches and team dynamics, which follow the technical evaluations to assess fit and collaboration skills.
BehavioralManagerialTeam Dynamics
Difficulty Level & Expectations
The overall difficulty of the interviews is generally perceived as intermediate to difficult, with a strong emphasis on practical competency and real-world application of data engineering concepts rather than theoretical knowledge.
While many candidates appreciate the organized structure of the interview process, some report inconsistencies in scheduling and communication, which can impact the overall candidate experience and lead to feelings of disconnection.
OrganizationSchedulingCandidate Experience
Outcome & Feedback
Despite many candidates feeling they performed well technically, a significant number did not receive offers, often citing issues related to compensation discussions or lack of timely feedback as contributing factors to their overall experience.