Taro Logo

Data Engineer Interview Experience

May 1, 2018
Neutral ExperienceNo Offer

Process

I was approached by a recruiter on LinkedIn. The next day, we had a 30-minute call, and they asked me five basic questions each from SQL and Python. The recruiter mentioned that if I was very good with SQL, I would have a great chance of clearing the phone screen.

Soon after, my first telephonic screening was scheduled. This was similar to what most people have already described: 30 minutes of SQL and 30 minutes of Python.

The interviewer called and went straight to the questions. They asked basics of SQL, although I got confused and a little nervous since this was my first coding interview. Having said that, with a little hint from the interviewer, I could answer 4 out of 5 SQL questions and 2 out of 3 Python questions.

Yet, I received a rejection email the next day. I have read many Glassdoor reviews, and with my scores, people usually get called for an onsite interview. I'm not sure what the reason for rejection was.

If I were to attend the interview again? Yes, definitely.

Questions

sql:

  • inner join
  • cases
  • order by
  • limit

python:

  • avg length of sentence
  • valid IP address

Was this helpful?

Interview Statistics

The following metrics were computed from 347 interview experiences for the Meta Data Engineer role in United States.

Success Rate

15%
Pass Rate

Meta's interview process for their Data Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive63%
Neutral24%
Negative13%

Candidates reported having very good feelings for Meta's Data Engineer interview process in United States.

Meta Work Experiences