The interview has two main parts: a phone screen and a longer, in-person interview section full of longer questions.

The phone interview is a standard 1 hour, half SQL questions and half generic programming questions. Follow the advice of the recruiter to prepare for these. The name of the game is being quick; the more questions you see, the better off you will be.

The in-person interview will consist of 3 problem-solving interviews. In my experience, you will be given a scenario of a data engineering problem (i.e., how to identify the metrics for performance for this specific feature) and you will be expected to write SQL and actual code for the context of the problem itself.

There will also be a more standard behavioral interview portion, asking you about your work experience, how you deal with interpersonal problems, and that sort of thing.

Finally, there will be a casual lunch conversation where you can ask about the work culture and other day-to-day questions.

The interview was long, but the questions were not unfair, I think, and weren't your generic data structures and algorithm questions.

The interviewers themselves were very respectful, helpful, and nice. I was sick the day of the interview, and they allowed me to take quick breaks when needed.

Overall, it was a pleasant process. There are no tricks to the interview; you just have to prepare!

Given this data, calculate this KPI.

How would you design the data model for this scenario?