My interview felt pretty manageable overall. I had a first round where the focus was on fundamentals—ETL concepts and how I approach SQL-based queries. The questions weren’t trying to trick me; they were more about whether I understood the core workflow and the right SQL building blocks.
Later I went through another round that stayed in the same lane: explain my background, then talk through roles and responsibilities, and show that I had a solid grasp of SQL alongside Python and Spark basics. It was more of a steady evaluation of whether I could handle the day-to-day concepts than an intense technical grilling.
1 month ago
Difficult Neutral London, England
My process started with a phone conversation, and then I joined a quick video call with someone from the team where the questions were simpler and more about direction than depth. After that, I had a more technical interview with two technical members. The overall structure felt like a ramp-up: first get my background, then move into the real technical evaluation.
What stood out was how much the technical portion leaned on direct questioning rather than live coding. I wasn’t doing algorithm-style exercises; it was mostly question-and-answer, and the interviewers pressed on the logic behind what I said. Even though the format felt straightforward, the difficulty landed as harder because it was fast-paced and tied closely to my stated experience.
2 months ago
Difficult Positive Noida
After a recruiter-style first step, I had a 1-hour technical interview where we basically dug into what data engineering meant in practice, then moved…
3 months ago
Average Positive Brazil
My process didn’t fail on technical ability—it fell apart because of logistics. I had an initial HR interaction that felt friendly, and then I was inv…
3 months ago
Positive
I went through a fairly long, multi-step pipeline that included an assessment and then multiple interviews. It started with HackerRank OA, followed by…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically follows a structured flow, starting with an HR conversation, followed by technical interviews, and often concluding with an HR discussion. Candidates noted that a clear progression through rounds helped maintain focus and build on previous discussions.
StructuredHRTechnical
Technical Interview Focus
Technical interviews primarily assess SQL, Python, and data engineering concepts, with a strong emphasis on practical application and scenario-based questions. Candidates should prepare for in-depth discussions on ETL processes, data quality, and specific technologies like Spark and Databricks.
SQLPythonETL
Assessment & Coding Challenges
Many candidates experienced initial assessments that included coding challenges or online tests, often focusing on SQL and Python skills. These assessments set the tone for the technical interviews and were critical in determining progression through the hiring process.
CodingAssessmentSQL
Behavioral & Fit Questions
The HR rounds often included behavioral questions aimed at assessing cultural fit and communication skills, with a focus on teamwork and collaboration. Candidates should be prepared to discuss their past experiences and how they align with the company's values.
BehavioralCultural FitTeamwork
Interview Difficulty & Expectations
The overall difficulty of interviews varies, but many candidates noted that while some rounds felt manageable, others were intense and required deep technical knowledge. It's important to be well-prepared for both straightforward and challenging questions.
DifficultyPreparationTechnical Knowledge
Logistics & Communication
Candidates reported mixed experiences with logistics, including scheduling issues and communication delays. A smooth process with timely feedback can enhance the overall experience, so candidates should be proactive in following up if needed.