Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

11 stories

Likes earn the author +10 XP for the first 3 likes each day

MetaData Engineer
Nov 2026

TaskManager Sorting Problem Extended to Multi-Level Parent/Child Tasks

A very "engineering-style" interview question: implement a TaskManager class that filters, de-duplicates, sorts and prints tasks according to rules, and once the basic version is done, extend it to multi-level parent/child tasks. The question doesn't test long, fancy algorithms. It tests requirement clarification, choice of data structures, multi-key sorting and tree traversal. Problem overview I…

Technical Screen0
MetaData EngineerSenior+
Sep 2026

Leadership and Fullstack Phone Screen, Rejected Over 'Not Enough Impact'

From the recruiter to the interviewers, the whole thing gave off an absurd vibe. I was applying for a senior position, and the job description didn't even list a level at the time. After I applied, the recruiter had me submit my availability directly — no call at all. Once it was scheduled, I was told it would be one Leadership round and one Fullstack round. I thought that was a little strange at…

RejectedTechnical Screen0
MetaData Engineer
Reported Jul 2026

Meta Data Engineer interview with timed SQL, Python, modeling, and product scenarios

After recruiter outreach, I went through a structured set of rounds built around speed and clear problem solving. The recruiter call covered role fit and process details. Then came a technical screen with several SQL and Python tasks under tight time limits. I had to keep working until each task was fully resolved with the expected results, while the interviewers kept returning to my thought proc…

Technical Screen0
MetaData Engineer
Mar 2026

Tech Screen Into a Four-Round Full Loop

Locked — open it to unlock the full story with XP.

OnsiteXP0
MetaData Engineer
Dec 2025

Missed the 3-for-3 SQL/Python Bar in a 25+25 Screen

I've actually been pretty happy at my current job and wasn't planning to switch. A Meta recruiter reached out to me a few times, so I figured I'd interview just to see how it would go. Technical round (25 minutes of SQL + 25 minutes of Python) I hadn't grinded LeetCode in a long time. The questions weren't too hard, but they were tricky. The interviewer spoke excellent English and gave me a lot o…

RejectedTechnical Screen0
MetaData Engineer
Dec 2025

25 Min SQL, 25 Min Python, and I Only Passed One of Each

I've been pretty happy at my current company and honestly wasn't planning to switch jobs. A recruiter from Meta reached out to me a few times, though, so I went into the interview with a just-try-it-and-see attitude. Technical round (25 min SQL + 25 min Python) I hadn't touched LeetCode in a long time. The questions weren't super hard, but they were tricky. The interviewer spoke excellent English…

Technical Screen0
MetaData Engineer
Dec 2025

Three VO Rounds (Reel, Car Rental, Carpool) End in an Add-On Interview

I prepared for the VO for a long time, and I still ended up getting an add-on interview — I can accept that outcome. I'm hoping someone kind who's been through an add-on interview can share the question bank!! Will they pull from question types that come up a lot but I wasn't asked, or will they pull from really old questions? I've read a lot of other add-on interview posts and haven't gotten any…

In progressOnsite0
MetaData Engineer
Sep 2025

A Confusing Building-Capacity Coding Problem Plus SQL on the Library Schema

Python Questions 1 and 2 are basically the same as the ones posted yesterday. For question 1, I got a follow-up: how do you write it without heapq. For question 2, the log list's true/false values need to alternate, and you also have to consider that a book needs to be checked out before it can be returned — otherwise that's wrong too. Question 3 is a new one I'd never seen before and it's a bit…

Technical Screen0
MetaData Engineer
Sep 2025

Onsite Loop: Product Sense, Data Modeling, Python, SQL

Product Sense (10 minutes) Try to keep your answers fairly brief. Prepare 4-6 main metrics and you don't need to explain in much detail why you picked each one, unless you feel the interviewer wants to hear more or they ask directly. Every interviewer's expectations are a little different, but overall I felt they don't dig in that deep, so don't spend too much time preparing for this part. The qu…

Onsite0
MetaData Engineer
Aug 2025

Three Onsite Case Studies on Private Accounts, Carpooling, and Netflix

The overall experience was okay — at least all the interviewers were superficially friendly. But two of them were more than 5 minutes late. For every product sense question, they'd first ask you how you understood the product, then ask what dimensions there were (at this stage they just wanted a high-level list of entities), and finally what metrics you'd use. The first question was a new one, ab…

Onsite0
MetaData Engineer
Jul 2025

Four Onsite Rounds in One Day

Four rounds total, all held on the same day, with a lunch break in between: Round 1: ETL technical Round 2: Data modeling Round 3: ETL technical (leaning more toward real-time processing) Round 4: Behavioral + ownership-related HR calls ahead of time to explain what each round covers, so the overall schedule is pretty clear. The first two rounds lean toward data modeling and traditional batch pro…

Onsite0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP