Taro Logo

Data Engineer Interview Experience - United States

September 1, 2021
Negative ExperienceNo Offer

Process

The recruiter called first and I provided details about my current role. After deciding I was a good fit, they forwarded me for a Codility test.

Virtual Codility:

  • 1 Hour: The interviewer was friendly. For 30 minutes, they asked about my experience and questions about MPP, Big Data, and pipelines. For 25 minutes, I was given 3 SQL and 3 Python questions. I completed 2 questions completely in both SQL and Python. For the third question in each, I only had time to explain my logic.

Feedback: Was good.

The recruiter called again to set up a 4-hour virtual loop interview. Here is where the frustrating part begins.

I received zero emails or details about the interview format. The invite had one interview with a Senior Manager to go over a homework assignment. I emailed twice to understand what the homework was, but received no comment or reply.

On the day of the interview, they realized they hadn't sent me the homework assignment. So, that 1-hour interview, which was part of the 4-hour loop, was cancelled.

The other 3 interviews were ETL Design, Behavioral, and Data Modeling, each. I had a fairly good experience with these interviews. I have no complaints.

In the evening, after the loop interview, I was given a document containing details explaining the format of the 4-hour interview (after I had already completed 3 of them) and the homework assignment.

I emailed the recruiter that it was disappointing because it was unfair of them not to provide me with the interview details beforehand. He commented that I did well and requested 1 hour of my time for the homework assignment.

I spent some time over the weekend to finish the homework and its evaluation. Even this was a good experience, and I liked the homework assignment.

Then, a few days later, the recruiter told me he expected to hear about my feedback soon.

It has been more than 2 weeks since my loop interview, and I still haven't heard from the recruiter. He is now ghosting me on LinkedIn.

It's such a disappointing experience because I feel they haven't given me a fair opportunity as others. The entire ghosting episode is even more sad.

Questions

Phone Interview - Round 1

30 mins design questions Mostly about Streaming architecture and GCP analytics stack.

30 mins Python and SQL

SQL: Based on GROUP BY and JOIN. Medium level. 3 questions.

Python: 3 questions, LeetCode medium-easy level.

  1. Given a string, break it into segments of length k. Make sure you don't cut words, and your sentence should not end with a space.

Virtual Onsite - 1

Interview - 1

  1. What is an MPP database and why is it faster?
  2. What kinds of queries are slower on MPP?
  3. Explain Hive.
  4. You have log records with 3 fields: id, timestamp, status. Lots of records, 1000 per second. How will you store and model the data? Explain the full architecture and choice of ETL.
  5. What kind of data quality checks would you perform for the above?
  6. Explain a good design that you worked on recently and why you are proud of it.
  7. Draw on the board and explain in detail.

Interview - 2

Behavioral:

  1. Why Wayfair?
  2. Explain a scenario where you had to convince someone to make a decision.
  3. How do you keep yourself updated?
  4. Explain your most satisfying project.

Interview - 3

  1. Tell us about your most challenging project/problem you solved and are proud of in the last 6 months.
  2. When I mentioned GCP - POC, tell us why you chose BQ.
  3. What challenges did you guys face?

OLTP data model Wayflix (Similar to Netflix).

Write some SQL:

  • All movies acted and directed by a given actor.
  • A few more SQLs involving JOIN, set operations.

At the end, convince me why I should say yes to your selection.

Interview - 4

Homework:

  1. Design choices and questions about the homework.
  2. How would you handle batch and streaming data coming in at once?
  3. How would you merge streaming data in near real-time?
  4. Some more questions about the homework and the data model chosen.

Was this helpful?

Interview Statistics

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

Success Rate

17%
Pass Rate

Wayfair's interview process for their Data Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive67%
Neutral0%
Negative33%

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

Wayfair Work Experiences