After I applied, the process moved through multiple layers of testing that felt deliberately technical. I had a HackerRank assessment early on, then several follow-on rounds that included live/problem-solving interviews and additional case-style work. The coding and data engineering expectations were a bit broader than I first assumed, with interviewers focused heavily on critical thinking, logical reasoning, and the ability to communicate clearly while working through problems.
Across the technical rounds, the mix kept pulling me between Python and the data engineering stack rather than staying narrowly on SQL. There were Python questions that looked like DS&A practice, plus data engineering theory and concepts being asked directly (including fundamentals like relational database ideas and CAP theorem-style thinking). One later stage also involved analyzing data from multiple datasets using a Jupyter-style workflow with pandas, with the tasks centered on joins and basic CRUD-style operations, but still framed as “live data processing” rather than a quick quiz.
7 months ago
Average Neutral New York, NY
My process started with a phone screen, and that quickly led into a structured technical test that felt very exam-like. I was given pandas/dataframe questions based on an exam-style PDF, and the whole round tested whether I could reason about tabular manipulation rather than just write code from memory.
After that, there was a relatively straightforward algorithm problem. What surprised me was the pivot into a case-style conversation with a business person, where the discussion tied back to big data topics rather than staying purely in coding. Overall the difficulty sat in the average range for me, and the flow was consistent: quick recruiter alignment, then hands-on data work, then a light algorithm step, and finally a business-context case discussion. I didn’t receive an offer, but the experience felt organized and approachable compared to the heavier journeys I’d heard about.
> 1 year
Average Positive Montreal, QC
My interview journey felt pretty long and spread across a lot of checkpoints, but the structure was recognizable. It began with an initial application…
> 1 year
Average Negative London, England
My process started with a recruiter screen that went well, and then it moved quickly into HackerRank-based testing. I cleared the initial HackerRank m…
> 1 year
Average Positive London, England
I went through a process that felt closer to consulting than purely engineering. After an initial HR conversation, I was pushed into an online test th…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Assessments
Candidates can expect multiple technical assessments, including an initial HackerRank test focused on Python and SQL, followed by live coding and data manipulation tasks using tools like pandas and Spark. The assessments are designed to evaluate practical engineering skills and critical thinking rather than just theoretical knowledge.
HackerRankPythonSQL
Interview Structure
The interview process is generally structured, starting with a recruiter screen followed by technical tests and case-style discussions that blend coding with business context. Candidates should be prepared for a series of interviews that may include both technical and behavioral evaluations.
StructuredCase StudyBehavioral
Focus on Communication and Business Acumen
Interviews often emphasize the ability to communicate clearly and demonstrate business thinking, with questions probing past project impacts and team contributions. Candidates should be ready to articulate their thought processes and how they approach problem-solving in a business context.
CommunicationBusiness ThinkingProject Impact
Live Coding and Pair Programming
Candidates may encounter live coding sessions and pair programming, which require them to demonstrate their coding skills in real-time. This aspect can be challenging, as it tests both technical ability and the capacity to collaborate under pressure.
Live CodingPair ProgrammingCollaboration
Overall Difficulty and Length of Process
The interview process is described as lengthy and challenging, with multiple rounds that can feel repetitive. Candidates should be prepared for a rigorous evaluation that tests their technical skills across various sessions.
Lengthy ProcessChallengingRepetitive
Candidate Experience and Communication
Some candidates reported issues with scheduling, communication, and overall organization, which affected their experience. It's advisable for candidates to remain proactive in seeking updates and clarifications throughout the process.