Meta

Meta Software Engineer Onsite Coding Questions

875+ questions from real Meta Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.

875
Questions
8
Topic Areas
10+
Sources

What does the Meta Onsite Coding round test?

The Meta onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.

Top Topics in This Round

Meta Software Engineer Onsite Coding Questions

August 1st: Headhunter invitation August 12th: Store interview (one easy, one medium-high frequency question) August 13th: Arranged in Anse September 12th: Anse (four medium-high frequency questions,

Given three sorted arrays in ascending order, merge them into a single sorted array. Aim to maximize efficiency. ### Example: Input: ``` [1, 4, 7] [2, 5, 8] [3, 6, 9] ``` Output: ``` [1, 2, 3, 4,

Facebook onsite

Coding 2022

138 1249 791 79 for anyone who recently will be onsite fb good luck I have been interviewing with other companies as well and here are my other posts about Google onsite, Amazon onsite and Apple...

Given a string s and an integer n, find the shortest substring that contains exactly n unique letters.\n\n### Input\n- A string s with a length between 1 and 10^5.\n- An integer n, which ranges from 1

Given a binary tree and a target sum, determine if the tree has a root-to-leaf path such that adding up all the values along the path equals the given sum. The structure of a tree node is as follows:

Given an integer array `nums` and an integer `k`, return the `k`th largest element in the array. You may assume that `k` is always valid, 1 ≤ k ≤ array's length. **Example:** ``` Input: [3,2,1,5,6,4

Given the root of a binary search tree and two integers low and high, return the sum of values of all nodes with a value in the inclusive range [low, high]. ### Input: - `root`: The root node of the

Given an array of points points on a 2D plane and an integer k, return the k closest points to the origin (0, 0). ### Example: Input: `points = [[1, 3], [-2, 2]]`, `k = 1` Output: `[[-2, 2]]` ###

Meta E5 Software Engineer Coding Interview Sliding Window Substring

Coding,Strings,Sliding Window,Hash Table,Two Pointers 2026

👋Hi everyone, just sharing since this community helped me a lot Meta has always been my dream company. I felt so stressed and couldn't sleep the night before. During the interview, I was running on 4

I have a Meta onsite in a few days, but a family emergency just derailed my prep and mental headspace. Does rescheduling hurt my chances or risk the headcount being filled before I can interview? I’d

Will background check flag this

Career,Background Check 2026

I was let go at meta and my last actual day on contract was Feb 24. I applied to a different company on March 8th but had meta as current job on resume. I finally got accepted at a new job but still w

Meta SWE Infrastructure Full Loop Interview 5 YOE

System Design,Interview Structure 2026

I recently cleared phone screen and have been asked to schedule full loop. I can see 2 system design rounds, 1 coding, 1 AI coding and 1 Behavioural round. In my experience E4/E5 has 4 rounds in full

2026 New Grad Recap

Career,New Grad,Job Search,Interview Process 2026

How was new grad 26 recruiting for everyone? Was fortunate enough to have a return offer, but none of my new grad interviews/onsites converted to an offer, which I thought was shocking since I probabl

Just got an email to schedule my onsite after completing tech screening rounds **5 days ago** (Meta E4 Production Engineer, USA). Should I book it **as soon as possible** (next week) or is **2-3 weeks

Meta Software Development Engineer Onsite Interview Experience and Team Match Inquiry

Onsite,Coding,System Design,Behavioral,Binary Tree,Arrays,Two Pointers 2025

This was my first interview at Amazon, a company whose name literally means "squid factory" (meaning small, unreliable, and often unreliable). However, the experience was surprisingly good. The engine

Sharing the coding round challenges: I was worried this would be a hard challenge, but surprisingly, they were all very simple, high-frequency medium challenges. I worked through the top 100 most freq

Meta Frontend Engineer E4 Onsite Interview Experience

Onsite,Frontend,System Design,Rejection 2025

All questions from leetcode past 30 days. Surprised that they're so lazy. Product Architecture Design - Very frontend focused, blackbox all of backend. Thought I did pretty well but got rejected, oh w

Sharing a recent virtual interview session, hoping to accumulate good karma. Good luck everyone in your interviews! Following the process: 1. Coding - Bait Lingqi + Bait Xianlu 2. System Design - Drop

Meta E5 Product Onsite Interview Experience (U.S.)

Phone Screen,Onsite,Coding,System Design,Behavioral,Binary Tree,Strings,Math 2025

**Phone Screen** * **[Binary Tree Vertical Order Traversal](https://leetcode.com/problems/binary-tree-vertical-order-traversal):** Return the vertical order traversal of a binary tree's nodes. * **[Mi

Meta Full Loop Software Engineer Interview Experience September–October 2025

Dsa,Ai Coding,System Design,Behavioral,Onsite,Full Loop,Strings,Stack,Lru Cache 2025

**Candidate Profile** **Education:** IIT Kanpur **Experience:** 2.5+ years full-time at a product-based startup **Internships:** 8 months total **Phase 1: Elimination Stage** * **Problem:** The screen

What to Expect in the Meta Onsite Coding Round

The Meta Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 875+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.

Reports tagged with the Onsite Coding round at Meta show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.

How To Prepare for This Specific Round

Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.

Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.

Onsite Coding Round Timing and Format

The Onsite Coding round at Meta typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.

Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.

Common Failure Modes in This Round

Reports tagged "no hire" at Meta Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.

The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.

See All 875 Questions from This Round

Full question text, answer context, and frequency data for subscribers.

Get Access