Meta Rejected Me After the Onsite. It Was the Ranking Question, Not the Coding Round.
I designed News Feed ranking well. I designed it for a world with no bad actors.
Jul 10, 2026 · 1 min read · backend,database,devops
Meta Rejected Me After the Onsite. It Was the Ranking Question, Not the Coding Round.
Six days after my Meta onsite, the recruiter opened with “so, we got the debrief back” and I knew before her next sentence exactly which forty-five minutes had done it.
Not the coding rounds. I’d trained for those like an athlete.
The ranking question.The Round I Wasn’t Worried About
If you’re prepping for a Meta interview in 2026, you know the loop: two coding rounds, a behavioral, and the system design round the one candidates and recruiters famously nickname “Pirate.”
I’d spent six weeks on the coding rounds. The system design interview, I’d skimmed. I had shipped ranking-adjacent systems before, and I told myself that round was already mine.
The role was E5 senior engineer. I’d taken the day off and told exactly one person.
The two coding rounds that morning went the way six weeks of practice makes them go clean, boring, finished with minutes to spare. I walked into the design round loose. Relaxed, even.