Interview Process (3 Rounds Total) Round 1 & 2 – Technical and Coding Rounds These two rounds were focused and technically strong. Topics included: Data Structures and Algorithms Distributed Data Processing (Kafka, Spark, etc.) System Design and Architecture Python and PySpark programming Advanced SQL and Dimensional Modeling Cloud and Data Platform design I was able to solve all coding questions with correct output. The interviewers confirmed during the call that I had provided correct answers and executed the code successfully. Overall, both rounds were conducted professionally and technically satisfying. Round 3 – Managerial and Behavioral Round This round covered: Project leadership and ownership Cross-functional collaboration Communication and stakeholder management Behavioral and scenario-based questions At the end of the discussion, the manager gave positive verbal feedback and mentioned, “We are good with the interview. The recruiting team will get back to you with a positive response. When would you be able to join?” This strongly indicated a successful outcome. Post-Interview Communication This was the disappointing part of the experience. No response for 15 days after the final round. Upon following up, HR said the managerial round did not go well—completely contradicting the live feedback from the manager. After another 10 days, I received an email stating: "After internal review, the business has decided to pause the recruitment process for this role." This back-and-forth communication was unclear and inconsistent. It raised concerns about transparency and coordination between the interview panel and HR. Summary What Went Well: Technically challenging and relevant interview rounds. Interviewers were skilled and respectful. Covered all critical aspects expected from a Staff Data Engineer. What Did Not Go Well: Unclear and conflicting post-interview communication. HR responses lacked consistency and transparency. Final outcome seemed misaligned with actual feedback from interviews. Advice to Future Candidates Prepare thoroughly on Spark, Python, system design, and cloud data architectures. Don’t assume verbal confirmation equals selection—wait for formal communication. Be ready for a long feedback cycle and follow up proactively.

Coding and Video Interview. Multiple choice questions on Machine learning,Python,SQL. One game test also conducted. waiting time is too much. They are not confirming about result on time. Overall process was comfortable.