Overall, a lengthy and difficult process.
Lots of Leadership Principles were involved, so practice them very, very well.
LeetCode Hard SQL questions will do the job.
The recruiters prepare as best they can, but Data Engineering interviews are still not explicitly out there in terms of prep materials.
Most of my interviews went absolutely technical, in-depth, with my experience and projects.
Got a phone call from the recruiter and was excited, only to know that they were not moving on.
The role was for L5.
Phone Screen:
Given the Orders and Catalog tables:
Q1: Get the top 10 best-selling items for each product group in the US in 2020. Q2: How much did each item contribute to the total sales of the product group?
On Site:
Round 1: Detailed discussion on Indexes and how I will use them for a given question. (Note: Study multiple indexes, partial indexes, and ordering.)
Round 2: (Probably Bar Raiser)
Round 3: Only LP
FACT_ORDER_ITEM: product_id, customer_id, view_day, item_price, quantity, page_view_id, is_ordered
Note: This table receives 100M records/day and has data for 5+ years.
DIM_CUSTOMER: customer_id, address, age, education
Note: This table has 1B records.
We need to create geographic and demographic dashboards based on these weekly, monthly, and yearly tables, keeping in mind the huge volume of data within them for any joins.
The following metrics were computed from 2 interview experiences for the Amazon Big Data Engineer role in Seattle, Washington.
Amazon's interview process for their Big Data Engineer roles in Seattle, Washington is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Amazon's Big Data Engineer interview process in Seattle, Washington.