Xebia Data Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Xebia.
Xebia
Data Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical
The technical interview itself was actually pretty good. The person interviewing me knew their stuff and was respectful, and we had a really good technical discussion. But then it all went south because of the recruiter. After the interview, the HR recruiter just went completely silent. No feedback, no updates at all. It's a shame, seems like this is pretty common with HR these days, and this just proved it again. To make things even worse, the salary they offered was less than what's normal for this kind of job. It wasn't just a little disappointing, it was like they weren't even aware of market rates. So yeah, it was a pretty frustrating and totally unnecessary waste of my time. The technical part had promise, but the recruiting side was unprofessional and really discouraging.
Confirmed questions5 questions
- Can you discuss your experience with Apache Spark?
- Tell me about your proficiency in Python.
- Let's talk about Data Structures and Algorithms.
Xebia
Data Engineer
Mid Average Neutral experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Presentation Background check
Interview formats
Technical Behavioral Presentation Case
The hiring process was super long with weeks between stages because of people's schedules. The first call had some tech questions mixed with the usual 'tell me about yourself' and career goals stuff. The second call was all behavioral questions. The third call was with a sales person who was really focused on whether I'd help share knowledge and do things outside work hours, like attend meetups to boost their company brand. I was supposed to have a 2-hour technical interview next, but the recruiter called me the same day and canceled it because of the sales person's feedback and my 'lack of experience.' Even though I wasn't asked any technical questions except on the first call. After that, there would have been a one-week case study, a presentation, and I think another step. They talked a lot about how talented and amazing their people are. If you're okay with putting in extra hours outside of your normal workday at an IT 'elitist' consulting firm, this might be your place.
Confirmed questions3 questions
- Can you explain how to build a docker container?
- Would you classify Python as a dynamic or statically typed language?
- What is a parquet file?
Xebia
Data Engineer
Mid Difficult Positive experience Accept offer 6 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Recruiter call Technical screen
Interview formats
Technical Coding Behavioral
It was a 6 round process, and I got terminated at every round. First round was Level 1 Technical Discussion, then another Level 1 Technical Discussion. After that, it was Level 2 Technical Discussion, followed by another Level 2 Technical Discussion. Then came the Cultural Fit Round, and finally, the Client Discussion.
Confirmed questions8 questions
- Can you answer some high-level SQL queries?
- Do you know theoretical SQL questions?
- Tell me about PySpark.
Xebia Data Engineer Interview Questions
Quoted word for word from Xebia interview reports.
“How would you write Python code to determine if a given number is a perfect square or not?”
Read reports →“What is a parquet file?”
Read reports →“Would you classify Python as a dynamic or statically typed language?”
Read reports →“What about fact tables?”
Read reports →“Can you explain how to build a docker container?”
Read report →“Could you fetch all invalid December month transaction IDs (coming in ooo hours) from a dataset, applying conditions such as working hours from Monday to Friday (9 AM to 4 PM), excluding weekends and specific holidays (24th and 25th December)?”
Read report →“Tell me about PySpark.”
Read report →“Were there any questions about PySpark?”
Read report →“I was given a Python IDE to write code. While I was developing my logic, I failed to write the code. I explained my approach to you, and you responded by saying, 'This is the approach we'll/you'll be able to solve it, so there's no need to raise your voice and ask who's going to solve it? Me or you?'”
Read report →Formats, difficulty and experience
Across all 11 Xebia interview reports.