Interview Experiences

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

Share yours, earn XP

5 stories

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

FacebookSoftware Engineer
Reported Jul 2026

Facebook Software Engineer interview: BFS matrix task and unfinished technical loop

After the recruiter step, I had a coding-centered technical round with two questions in about 45 minutes. One required a normal solution followed by an optimization follow-up, which made the round more demanding than I expected. In the next video-conference interview, the interviewer was very communicative and answered questions as they came up. The coding challenge used BFS: I was given a matrix…

Technical Screen0
FacebookSoftware Engineer
Reported Jul 2026

Facebook Software Engineer interview: coding loop, system design, and offer

A recruiter phone screen led into a classic technical sequence. After the call, I did two back-to-back LeetCode medium coding interviews with engineers. The tone was collaborative and friendly, with emphasis on explaining my thinking, writing good code, and improving my solution in follow-ups rather than being caught out. Later, the onsite had a full-loop structure: two coding sessions with two L…

OfferOnsite0
FacebookSoftware Engineer
Reported Jul 2026

Facebook Software Engineer interview: recruiter screen, LeetCode loop, and no offer

After a recruiter contacted me on LinkedIn, I had a scheduled screen about my background and what I wanted from a new role. It was clearly a gate: if the alignment looked right, I would move forward. The technical sequence followed a familiar pattern, starting with a phone screen and then an onsite that mixed coding, behavioral questions, and system design. The coding questions were LeetCode-styl…

RejectedTechnical Screen0
FacebookData Engineer
Reported Jul 2026

Data Engineer interview at Facebook: unclear bookstore scenario

After a recruiter screen, I went into a technical conversation that felt tougher than the preparation materials. The difficulty was not only coding or SQL. A scenario resembling a bookstore checkout system was described too vaguely for me to know the intended behavior, and the interviewer did not help clarify it. Once I understood what to build, I worked through it, but the experience still felt…

0
FacebookSoftware Engineer
Reported Jul 2026

Facebook Software Engineer interview: two coding questions and onsite loop

After a recruiter call, I had a technical screen that began immediately with coding. I answered two LeetCode-style questions and had to communicate clearly as I worked. The questions were heavily Meta-tagged, so targeted preparation mattered more than generic DSA practice. The onsite loop added behavioral, two more coding questions, and system design. The recruiter was accommodating and the proce…

Technical Screen0

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