# Meta Software Engineer Interview Experiences

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/guides/meta-software-engineer-interview/experiences
Source observed: 2026-11-04T22:02:45.785Z
Last checked: 2026-11-04T22:02:45.785+00:00
Indexed: 2026-11-05T06:38:42.356+00:00

---

# Meta Software Engineer Interview Experiences

We collect real interview experiences from candidates who have gone through Meta software-engineering interviews. This collection concerns Meta roles and is part of our Meta Software Engineer interview guide. It was updated 7 days ago by Meta candidates.

- [Expert guide](https://www.aced.io/guides/meta-software-engineer-interview)
- **Interview experiences: 56**
- [Questions: 216](https://www.aced.io/guides/meta-software-engineer-interview/questions)
- [Resumes: 154](https://www.aced.io/guides/meta-software-engineer-interview/resumes)

[Share your experience](https://www.aced.io/questions/contribute?src=guide)

## At a glance

- **Interview difficulty:** Most candidates rate the Meta interview as **moderate**. The displayed distribution is 0 very easy, 2 easy, 29 moderate, 11 difficult, and 0 very difficult.
- **Offers received:** The median Meta offer is about **$350k in total compensation**. The displayed range is **$120k low**, **$350k median**, and **$545k high**.
- **Questions asked:** The largest displayed categories are **Coding (37)** and **Data Structures & Algorithms (35)**, followed by **Behavioral (25)** and **Other (47)**.

## Featured experience: Senior Software Engineer, Infrastructure

[Read the full experience](https://www.aced.io/experiences/meta-facebook-senior-software-engineer-interview-dd0a91?returnPath=%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences)

- Company: Meta
- Level: Senior / L5
- Location: United States
- Submitted: Apr 13, 2026
- Verified: February 2026
- Difficulty: Difficult

The candidate describes a phone screen followed by a virtual loop with four rounds: two coding rounds, one system-design round, and one behavioral round. The phone screen involved a single tree-traversal coding problem. The experience also included a new AI coding section; the format felt flexible, but the candidate was expected to write the actual code and use AI only in a limited way. The candidate found the process challenging and would have spent more time preparing behavioral stories.

Questions included:

- [What is the project you are most proud of?](https://www.aced.io/questions/1031)
- [Design APIs for Facebook live commenting.](https://www.aced.io/questions/1747)
- [Construct a binary tree given its preorder and inorder traversals.](https://www.aced.io/questions/3417)
- [+9 more questions](https://www.aced.io/experiences/meta-facebook-senior-software-engineer-interview-dd0a91?returnPath=%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences)

## Additional candidate experiences

The collection includes experiences across senior, entry-level, product, frontend, computer-vision, staff, and general software-engineering roles. The following summaries preserve the substantive details visible in the collection:

### Software Engineer (L3)

A prior interview attempt reached the final round, so the online assessment was skipped. The process then included a recruiter call, phone screen, and final loop with three technical interviews and one behavioral interview. Coding rounds emphasized explaining brute force before optimizing, defending the selected approach, manually tracing code because it could not be run, and proving correctness. Team matching could take a long time when office and team preferences were specific. Questions included conflict resolution, difficult challenges, and finding the longest path in a graph.

### Software Engineer (E5)

The candidate reported a recruiter call, a coding screen with two common problems, and a full loop spread across multiple days, with several weeks to prepare. Behavioral preparation and system-design time management were cited as weaknesses. A system-design prompt concerned handling simultaneous high-traffic ticket purchases on a ticketing website.

### Software Engineer, Product

The process included a recruiter conversation, a pre-onsite package with CodeSignal, a live technical screen, an engineering-philosophy multiple-choice questionnaire, and an onsite with data structures and algorithms, system design, behavioral, and AI-enabled coding rounds. The candidate described preparation materials including a prep PDF, portal videos, mock system-design resources, and an AI-round practice environment. Reported questions included Design Chess.com, “Is this a valid palindrome?”, and “Vertical Traversal of a Binary Tree.”

### Computer Vision Engineer

The candidate described recruiter delays followed by an initial team-member conversation and two nontechnical screening interviews with Reality Labs members. Topics included past projects, team fit, and potential contributions. Questions included making a mistake, past projects, and implementing a computer-vision process.

### Other reported formats and topics

Candidates described combinations of recruiter or HR screens, online assessments, phone screens, technical screens, coding rounds, system design, behavioral or culture rounds, and team panels. Reported coding topics included binary trees, graph traversal, palindromes, LRU cache, circular buffers, `memcpy`, sliding windows, arrays, linked lists, calculators, islands, parentheses, anagrams, merge-k sorted lists, and water trapping. Reported design topics included Chess.com, Dropbox, Netflix, TikTok, Ticketmaster, TinyURL, a web crawler, a notification system, a cookbook app, a file system, an auction page, Facebook-style feeds, and a scalable image editor.

Some candidates described two medium LeetCode-style questions in a 45- or 60-minute session, with emphasis on correctness, time complexity, communication, and manually tracing solutions. Other accounts mentioned CodeSignal GCF assessments, Karat-style technical screens, AI-enabled coding, frontend coding and system design, and questions about product architecture, APIs, UX, geo-distance concepts, quad trees, and system interactions.

## Access

We invite candidates to [share an interview experience](https://www.aced.io/questions/contribute?src=guide). Trial access is available when a candidate shares an experience, and membership unlocks the complete collection through [Become a member](https://www.aced.io/upgrade?src=guide-experiences). The collection currently exposes one featured experience and summaries of additional experiences; some full entries and question lists require access.

![Meta logo](https://exponent-static.s3.amazonaws.com/company_logos/meta.png)

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences). Opening a form does not execute a tool.