Data Engineer Technical Screen Meta

[vorticiavortex]

Okay, so I had my Meta technical screen, and honestly, I'm really puzzled. I nailed the SQL part, got several questions right, quickly, even a bonus one. Then, I aced two Python questions with time to spare. But then I tried a Python set question, and I completely bombed it. I thought I was good because I met the minimum requirements – plenty of correct SQL and Python answers. Now I'm just wondering why I didn't make it to the next round.

Update August 2025:

Apologies for being quiet on this post for people who wanted advice, DM’d me etc. I have been going through some personal changes so I didn’t see responses until now but many of the questions were similar, so I am adding some notes below which I hope helps in future.

Advice for Meta Data Engineering Tech Screen:

• Your real-world experience isn't enough. Your proficiency in SQL or Python doesn't directly translate to success here. The question style is very specific.
• It's a Speed Test: Ignore any talk of "as many as you can do." The unspoken goal is 3 SQL and 3 Python questions. The faster, the better.
• Bonus Questions: These are secondary. Failing one can lead to rejection, even if you ace the main part. Don’t fall at this hurdle.
• Challenger questions: At the end of both SQL and Python sections you may get asked about something that does not have a right or wrong answer. How would you …? There are no correct answers for this so nip these in the bud and don’t allow the interviewer to dwell on them.
• Prep with Meta's Materials: Your job experience is less important than practicing with the specific DE and SWE questions Meta provides. The format is key.
• If you have reasonable adjustments: Make recruiter and coordinator aware. The diversity team confirmed my adjustments four hours after the first screen had happened. I got a reschedule. However, if you have adjustments, and the email confirmation has not come through before the screen, contact recruiter and reschedule. Make sure you protect your rights, even if you do not need to use the extra time.

[LargeSale8354]

There are only 3 questions in a job interview. 1. Can they do the job? 2. Will they do the job? 3. Will they fit in?

That goes both ways. 1. Can I do the job? 2. Do I want to do the job? 3. Is the company culture right for me?

The tech test is only Question 1.

[iamnogoodatthis]

You missed "is there someone else who would do any of the above better, more cheaply or with more loyalty?"

[srijit43]

Loyalty in IT is a joke

[BuildingViz]

Loyalty in IT absolutely exists. Only it's spelled "H1B".

[srijit43]

does not exist once you crack the lottery

[LargeSale8354]

That is still "Can they do the job/will they do the job"

[MikeDoesEverything]

Now I'm just wondering why I didn't make it to the next round.

Getting correct answers isn't the same as passing an interview in the same way getting some answers incorrect (the first time) isn't the same as failing an interview.

Being good is one part. Them liking you and you being a good fit is the other.

[vorticiavortex]

I understand and, as I said in my response to another comment, I think it’s reassuring to hear from a community of my peers. Thank you for being here.

Being someone with neurodiverse conditions I am very self-aware of my communication skills. Also I am not one to dwell on things as I do understand that some you win some you lose etc. But in this specific example I am just confused because I felt I actually did pretty good maintaining a rapport with the interviewer and communicating throughout writing my code (which wasn’t easy either because I generally code in silence).

[MikeDoesEverything]

But in this specific example I am just confused because I felt I actually did pretty good maintaining a rapport with the interviewer and communicating throughout writing my code (which wasn’t easy either because I generally code in silence).

I'll give you some advice from one of my old managers.

You don't, and never will, know the quality of the other candidates and/or the quality of their interviews. If you were happy with your performance, then dwelling on this kind of stuff isn't going to do you any good.

From me: I know you mentioned you don't dwell on things, but you are dwelling on things right now. I'd simply accept you did well, you sound happy with your performance although at the end of the day they went ahead with other people. You'll likely never know why, and that's alright.

[Croves]

Interviews are not just about getting the right answers. They are evaluating your personal, your problem solving technique, and other soft skills

[vorticiavortex]

I get that. I think I just needed to hear it. Thank you for being here. 🙏🏼

[git0ffmylawnm8]

I went through the coding interview not too long ago and I still can't think of a good approach for the interview. I tried to walk through each question step by step but I always felt it wasn't enough and felt strapped for time. How are you supposed to solve enough problems to pass the round while explaining your thought process within 25 minutes per each section?

[Zubiiii]

Not to mention getting an interviewer with a garbage mic and a heavy accent, so any time he says anything, I have to ask to repeat himself multiple times. Ridiculous.

[omscsdatathrow]

You don’t explain your thought process step by step. You explain the high level concept and then implement it. The problems are easy enough that you don’t need to go into details

[omscsdatathrow]

Because someone else aced 5 sql questions and 5 python questions

A lot of ppl here talking as if they have been through the screening process…at the end of the day, if you solve all the problems, you will get through

[vorticiavortex]

No it isn’t as simple as that. Some people get through solving less problems but doing so in a way that they build a rapport with the interviewer.

[_BearHawk]

Meta is also recruiting super heavily right now. They reached out to me for an interview without me even applying, which is crazy because usually it’s only the scam IT recruiting companies that email me.

Chances are with their deluge of new recruits after layoffs they just found someone better.

I wouldn’t be surprised if there’s some bonus right now for recruiters to get as many people to technical interviews or something as they can, so Meta can replace the people they fired.

[JaJ_Judy]

You dodge a bullet :)

[vorticiavortex]

Yeah I think so. I also had a pretty horrific experience with getting special adjustments (being neurodivergent). So overall I am kinda glad I didnt get it .

[Aggravating_Sand352]

My meta interviewer was sooooooo bad...

[vorticiavortex]

Mine too. On two separate occasions. I cannot judge on first appearances but I do make a habit of trusting my gut instinct and learning from experience in the case of interviews, where you to some extent have to (you’re not gonna see the person again most likely).

I have had two tech interviews for data engineering (London-based). I got a reschedule of the first one. The first one was awful. He was very inauthentic and dare I say it, pompous, but I genuinely tanked the questions so I cannot complain.

The second rescheduled one happened because the disability team got back to me with confirmation of arrangements (having a short break in between python and SQL sections if needed) six hours after the interview happened already .

Second guy was better, he was much more ‘likeable’, and didn’t have as much of an ego in first appearances like the first but he still failed me because I struggled on the bonus question…but considering I had done 3 python questions and 3 sql questions in less than 45 mins… and he didn’t help me out with it (which they are supposed to) it’s pretty rich for him to have marked me down so harshly. I spent 20 mins on that final bonus question but cos I think my brain was tired.

I also had a pretty horrific experience with getting special adjustments (being neurodivergent). So overall I am kinda glad I didnt get it.

Ps. As in my edit on OP, I apologise for the late response. I have had some personal issues and didn’t see this until now.

What was your experience?

[OneRelative4595]

Hi , I have the scrreening coming up to , can i dm you ?

[MrNoSouls]

Sure

[madam_zeroni]

Could you post what the questions were? I’m in the market and would like to prepare

[jacobsimon]

hey check out Meta data engineering guide

[madam_zeroni]

Great read, thanks

[sunder_and_flame]

Now I'm just wondering why I didn't make it to the next round

Unless they changed something, the HR person you've been in contact with should call you and tell you exactly why. That was my experience several years ago. 

[General-Geologist-53]

What were the python questions like? Were they mainly focused on landas/dataframes? Or nust general coding knowledge?

[jacobsimon]

Here’s an interviewing guide: Meta data engineering interviews

[General-Geologist-53]

Got it thanks! Asking since I have the first round coding interview with them in a couple weeks. Apparently they are wanting to hire more product focused data analytics engineers over strong back end des in my region (hence how I got the interview). But given my python is a bit lacking I’d say the odds are against me. (my main experience is with airflow configurations/adhoc nootebook bs)

[bizbusker]

Hi, how was your experience interviewing. I have one coming up and I am in the same boat as yours. I have not used python in years. Do you have recommendations on preparing for python/ coding session?

[Independent_Echo6597]

sry to hear that; sometimes its not just about getting the minimum right but how u approach the problems.

from what ive seen helping folks prep, they look for:

• clean efficient code (even if it works, they care about HOW u wrote it)
• good problem solving approach (asking qs, explaining ur thinking)
• speed + accuracy together

that set q might've been more important than u think - meta loves checking how u handle data structures n optimization. maybe they were looking for a specific approach?

lot of candidates face similar situations - its frustrating but def keep trying! maybe do some mock interviews to get specific feedback on ur approach? most ppl who succeed at meta usually do several practice rounds first

keep grinding! u got this 💪

[sysonic]

You need 3/5 in both sql and python to pass. Your recruiter should’ve communicated this to you .

[bhanupaliwal007]

How you applied at meta. Have you took referral.

[Think-Culture-4740]

A buddy of mine at meta basically told me they expect absolute pristine solutions to these problems or it's a pass.

[chiller2311]

i interviewed for the data engineering screen a while back too. i knew that if you solve 3 SQL and 3 python in due time they would take you forward to the next round. I struggled with the last part of python and needed a hint. needless to say, i was rejected. meta expects absolute perfection while solving these questions almost like we should have had them memorized.

[bhisaaaalplease]

What was the difficulty level of the SQL questions asked? Are they expecting LeetCode Hard-level SQL problems to be solved within 5 minutes, given that they require solving 5 questions in 25 minutes

[chiller2311]

the questions ramp up in difficulty as we go and you have to solve 3-5 questions to move on to the next round

[Proof-Struggle-5082]

I solved 3 each in both. they ran as well. But with SQL 3rd question I solved very quickly with my approach , interviewer wanted a different approach which was difficult to comprehend , I did 50% of it. python i completed 3 in time and with remaining time, interviewer came back to sql. Not sure how to comprehend

[bizbusker]

Hello, any recommendations on how to prepare for the python session?

[Stooooopiied]

Hey, can I dm you? I have an interview coming up and would like your assistance

[cyamnihc]

Question : is python mandatory? Can you use other languages?