Skip to contentSkip to footer

Software Engineer Data Interview Questions

Salaries
Interviews

438 software engineer data interview questions shared by candidates

Interview questions were relatively too simple to understand what they want. I am definitely sure that it was waste of time to spend on their interview process as they wasted 4 hours of mine and then said no, they need someone with more exposure to Scala. In fact, they rarely asked Scala questions, so feedback was really useless. In fact, Scala was not asked in the last interview at all. So, literally I could have saved at least 1 hour. Questions were very simple: What are RDD, DF and DS.? What are types of transformations? Difference between map and flatMap? How do you tune your spark application? Tell me about your project? One coding challenge that was very complicated to think about. Of course interviewer knows because they have gone through it online. It was going into Bitwise multiplication to find answer. Team Lead interview was very much like a chitchat and I was hoping like they liked my profile so there is no difficult question here. However, after a week when they didn't follow up. I sent two emails to recruiter and she called me saying that they need someone with more Scala exposure. I was furious to have wasted my 4 hours. They should learn to have proper sequence of interviews. If candidate didn't pass second round then why did you waste 2 extra hours. I will make sure I don't apply to any of their positions in future.
avatar

Senior Software Engineer (Data Pipelines)

Interviewed at SecurityScorecard

3.5★
Mar 19, 2021

Interview questions were relatively too simple to understand what they want. I am definitely sure that it was waste of time to spend on their interview process as they wasted 4 hours of mine and then said no, they need someone with more exposure to Scala. In fact, they rarely asked Scala questions, so feedback was really useless. In fact, Scala was not asked in the last interview at all. So, literally I could have saved at least 1 hour. Questions were very simple: What are RDD, DF and DS.? What are types of transformations? Difference between map and flatMap? How do you tune your spark application? Tell me about your project? One coding challenge that was very complicated to think about. Of course interviewer knows because they have gone through it online. It was going into Bitwise multiplication to find answer. Team Lead interview was very much like a chitchat and I was hoping like they liked my profile so there is no difficult question here. However, after a week when they didn't follow up. I sent two emails to recruiter and she called me saying that they need someone with more Scala exposure. I was furious to have wasted my 4 hours. They should learn to have proper sequence of interviews. If candidate didn't pass second round then why did you waste 2 extra hours. I will make sure I don't apply to any of their positions in future.

Basics of relational databases, OLAP vs OLTP, and the difference between a database and a data warehouse. They also asked to explain the need for stored procedures when the underlying SQL query can be executed on its own. Practical scenario-based questions like an e-commerce workflow (AWS login, orders, products, delivery, payments) and how all these systems are connected. Python-related questions, especially if it’s mentioned on your resume — they focus more on your project workflows and logic, not actual coding. Detailed discussion about the projects you’ve worked on — architecture, approach, challenges, and decisions. Questions about pipeline failure handling, such as how you would detect, troubleshoot, and recover using scripts or automation.
avatar

Software Data Engineer

Interviewed at GoDaddy

3.9★
Nov 19, 2025

Basics of relational databases, OLAP vs OLTP, and the difference between a database and a data warehouse. They also asked to explain the need for stored procedures when the underlying SQL query can be executed on its own. Practical scenario-based questions like an e-commerce workflow (AWS login, orders, products, delivery, payments) and how all these systems are connected. Python-related questions, especially if it’s mentioned on your resume — they focus more on your project workflows and logic, not actual coding. Detailed discussion about the projects you’ve worked on — architecture, approach, challenges, and decisions. Questions about pipeline failure handling, such as how you would detect, troubleshoot, and recover using scripts or automation.

Viewing 191 - 200 interview questions

Glassdoor has 438 interview questions and reports from Software engineer data interviews. Prepare for your interview. Get hired. Love your job.