phData Data Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at phData.
phData
Data Engineer
Entry Easy Positive experience Accept offer 3 rounds
Interview process
Technical screen Onsite Panel
Interview formats
Technical Coding System Design Behavioral
The first part was a pen-and-paper test with SQL questions and a basic coding problem you could do in Python or Java. There were also some computer fundamentals MCQs on a Google form. The second round was a face-to-face interview mostly about my resume. They asked me a data structure question about deleting a node from a linked list, and about Kafka and Spark architecture. We also covered the basic OOPs concepts and real-life uses of stacks and queues. I was also asked to design the backend for Zomato. The last round was more like a manager talking about my skills, some general management stuff, and how I'd fit into the company.
Confirmed questions2 questions
- Basic pillars of OOP.
- Given the value of a node in the linked list, delete it.
phData
Senior Data Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Coding Technical
The interview had 2 rounds. The first round was a coding round where you could use your chosen language. The second round was technical, and the job description specified it was for Java, Scala, or Python.
Confirmed questions1 question
- Tell me about your projects, and your experience with Python, SQL, cloud technologies, and ETL processes.
phData
Data Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Coding Technical
It was a total mess. The whole process dragged on for months, and in the end, I didn't get the job. The coding test itself was pretty basic, though their test cases were a bit tricky. You could pass the test in the app, but then they'd hit your code with scenarios beyond the provided cases, and if you missed any, you'd fail. I was told another team might be a better fit and that they'd reach out, but I never heard back. I was upfront about my skills and career goals. They mentioned the Java test wouldn't be heavily weighted given my background in ETL, reporting, and SQL. Honestly, it felt like the worst interview process I've ever gone through.
Confirmed questions1 question
- Can you write code to determine if all occurrences of the letter 'A' in a given string appear before all occurrences of the letter 'B'?
phData Data Engineer Interview Questions
Quoted word for word from phData interview reports.
“Given the value of a node in the linked list, delete it.”
Read reports →“Given the hour and minute, can you calculate the angle between the clock's hour and minute hands?”
Read reports →“What's the SQL query to find the average score for each question?”
Read reports →“Can you write a function that checks if all 'A's appear before all 'B's in a given string?”
Read reports →“Can you write a program to count word occurrences in a file?”
Read report →“Can you write code to determine if all occurrences of the letter 'A' in a given string appear before all occurrences of the letter 'B'?”
Read report →“Can you explain what Joins are in SQL?”
Read report →“Can you explain the Hadoop architecture and provide an example of MapReduce?”
Read report →“Could you tell me about the basics of Operating Systems?”
Read report →Formats, difficulty and experience
Across all 18 phData interview reports.