Meta Data Engineer I interview questions

Recruiter reached out through LinkedIn. I was excited about the opportunity though never thought Facebook for employment. Explained me about the interview process, saying first round of programming interview 30 mins Python & 30 mins SQL and then the onsite. Gave documents on what to prepare for the interview and asked me go through glassdoor for people's experience. The call itself was kinda of motivating for me to perform well. I was totally motivated and my interview was scheduled after two weeks. I flunked in First round. Prepared very hard (daily 2-4 hrs) but still some how managed to screw up in the interview. Still wondering what I was thinking when I gave the interview because in different setting I would answered it easily. I desperately wanted to clear first round and get to 2nd my bad did not do well. The interviewer was cool he was helping but you stay in control by taking time understand the question and answer. I am 11yrs exp, not sure if want to try again. My suggestion: Just prepare only what has been shared with you by the HR that's good enough Try giving mock test with time, I think this is VERY important (which I did not) questions are only from what you see here (at least for me) use monitor if you can when you give exam, since coderpad uses only half of your screen as editor I felt it's difficult with it (at hindsight). I was rushing to answer and chose wrong solution for first question and screwed it up from then on Now I realize it was simple question I over complicated STAY COOL

Recruiter Phone Screen - You should be answer to basic questions about joins, loops. Coderpad tech interview - Fairly easy questions involving SQL joins, aggregates, python loops, and string manipulations. If you can solve most of the medium and hard SQL and Python questions on leetcode without looking up anything, this part should be easy. But do verbalize your thoughts so as to leave a good impression on the interviewer. In Person Interview - 3 whiteboard interviews. The most important thing to practice is to rapidly solve common logic / programming problems on a white board. You will not be asked obscure functions or modules, the relative efficiencies of sorting algorithms, and they are not "trick" questions. They are practical problems, not theoretical or academic problems. Don't waste time memorizing every sorting algorithm. You have to quickly identify the problem and write the optimal (or extremely efficient) answer. I say rapidly because in an hour interview, you may only have 20 minutes per problem between introductions, talking, and explaining. It also may be difficult to understand your interview's accent or handwriting. One interviewer I found particularly bad about interrupting, explaining boundaries, and constantly had me change my variable names, losing lots of time and understanding. Although they say they insist on perfect SQL, one interviewer told me I could not use a multi-part join condition and insisted I use two different joins. Hmm... Also it's a whiteboard, so syntax and and setup matter far, far less than your logic. The interview cares way more that you grasp the essential problem and solution than if you remembered a colon or to import the right module at the beginning. "Product Sense" - I got feedback that my product sense was not strong enough. Not sure, perhaps study problems faced by huge companies such as facebook such as very large scale data processing, or brainstorm all of the edge cases faced by a user before designing your solution, rather than letting the interviewer hint the edge cases.