地点在三番
电面
SQL : Given schema about products, categories, customers, orders etc. Questions were like
- Query to get customers that dont have any orders
- Get top 3 customers for each product
- Get most ordered products for each category
Coding:
- Buy Sell problem-1
- Get words in a sentence
Onsite
Behaviorial
- Whats your 90 day plan
- How do you prioritize
- What can you talk about in detail (I was not able to understand what was questioned, later it hit me that they want to know what are you passionate about)
- Why FB
- Why DE
- What is the goal of DE
- Diff between Data Engineer & Data Scientist
Tech1
- Was given a line graph with a spike in month time line? What do you think happened? I gave 8 different reasons. The interviewer was looking for specific reason “new users”
- Given an table structure of identifying users as new/returned/churn/active. Create a table that would be cumulative. Again, the question was ambigous, the answer was FULL OUTER join.
Tech2
- Coding:Write a service to implement scalable logging
Tech 3
- Design Uber DW schema
- Metrics to identify, why those, why not others
- Factors to consider if you want to launch in new market
- Vague sql question: Query to get trips for airport, how to get exclusive trips for/to airport.
I felt no question was asked directly. Perhaps they want to know how you approach given ambiguous or missing info.
It was very time consuming to understand what they want to solve.
The coding and sql complexity was easy-medium. The challenge was nothing was specific, depending on your answer the followup question would be asked.
I had a good discussion with the lunch buddy. She was very open about culture, working style, expectations, career growth
She confirmed that SWE folks rule and are respected more than DE/DS. Promotions, career velocity and compensation is not that great for a DE as SWE.
Interview Feedback
They said they didnt find enough “Product Sense” in my answers.
SQL & Coding was okay.
Onsite Experience was good. Since I flew from Seattle to SFO, there was lot of time lost. They should have Onsite in Seattle that would be really helpful.
Advice to other candidates
- Read Ralph Kimball DW book, solve all LC sql questions, solve easy n med in LC for programming
- Think like a PM specifically for FB (metrics, prioritization, how to infer data)
Good Luck !