# Meta Software Engineer (E5) Interview Experience 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/experiences/meta-facebook-senior-software-engineer-interview-99496e Source observed: 2026-11-04T22:42:59.927Z Last checked: 2026-11-04T22:42:59.927+00:00 Indexed: 2026-11-05T04:21:07.799+00:00 --- # Software Engineer (E5) Interview Experience We publish this **verified** interview experience for a Meta Senior / L5 software engineering role in the United States. It was submitted 7 months ago. The reported result is **Rejected**, the interview date was **10 months ago**, the timespan was **5 weeks**, and the difficulty was **Moderate**. ![Meta](https://exponent-static.s3.amazonaws.com/company_logos/meta.png) This experience appears within our [Meta Software Engineer (SWE) Interview Guide](https://www.aced.io/guides/meta-software-engineer-interview), which was updated 7 days ago by Meta candidates. The guide includes [56 interview experiences](https://www.aced.io/guides/meta-software-engineer-interview/experiences), [216 questions](https://www.aced.io/guides/meta-software-engineer-interview/questions), and [154 resumes](https://www.aced.io/guides/meta-software-engineer-interview/resumes). > I had done really poorly on the easy coding question, but I still got through to the next round, which was really surprising. Then in behavioral, the interviewer said, "that does not sound like a conflict," and I had to change my story on the spot. ## Interview process A recruiter cold-reached out for an E5 software engineer role. The contributor described a short recruiter call, followed by a coding screen with two common problems in one session. They performed poorly on the easy problem but barely advanced. The full loop was spread across multiple days, with a few weeks to prepare. The final coding rounds were mostly standard. The contributor felt weak in behavioral because they lacked suitable work stories, especially for conflict, and felt they mishandled system design by not controlling time or setting scale assumptions. The reported rejection came after the final round. The process consisted of: - Recruiter screen - Phone interview - Final round ## Interview rounds There were **6 questions across 3 rounds**. ### Recruiter screen — 1 question The screen lasted approximately **15–20 minutes** and mainly checked whether the candidate fit an E5 profile with sufficient experience, ownership, and mentoring scope. **Question types:** [Behavioral](https://www.aced.io/questions?type=behavioral), [Project Discussion](https://www.aced.io/questions?type=project-discussion) Specific questions: - [Can you walk me through your experience and the projects you've been working on?](https://www.aced.io/questions/4229?interview=meta-facebook-senior-software-engineer-interview-99496e) - How many years have you been working? - How many people are on your team? - What are your roles and responsibilities on your current project? - What languages and frameworks are you using? The contributor discussed approximately six years of experience, two current projects, team structure, day-to-day ownership, and leadership and mentoring responsibilities. ### Phone interview — 2 questions The remaining content is available to members. ### Final round — 3 questions The remaining content is available to members. ## Access and practice We offer access to the rest of this interview and new experiences added weekly through [Become a member](https://www.aced.io/upgrade?src=experience). You can alternatively [Share your experience](https://www.aced.io/questions/contribute?src=experience); a **24-hour trial starts once your submission is approved**. You can also [Practice this loop](https://www.aced.io/questions/4229/past-projects?interview=meta-facebook-senior-software-engineer-interview-99496e). ## More Meta interview experiences - [Senior Software Engineer, Infrastructure — Meta, Feb 2026](https://www.aced.io/experiences/meta-facebook-senior-software-engineer-interview-dd0a91?returnPath=%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences): “There’s a new AI coding section I haven’t seen before. They still want to test my coding skill, so I first implement by myself, then use AI as a code reviewer for readability and missing test cases.” **Verified; 2 rounds, 7 questions**. - [Software Engineer (L3) — Meta, Jan 2026](https://www.aced.io/experiences/meta-facebook-software-engineer-interview-f72c39?returnPath=%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences): “In the age of AI, I could feel the interviewer adding little follow-up questions just to make sure I actually understood the problem, because if you were using AI tools, there’d be a lag. Even clearing the onsite doesn’t mean you’ll find a team quickly.” **Verified; 3 rounds, 2 questions**. - [Software Engineer, Product — Meta, Nov 2025](https://www.aced.io/experiences/meta-facebook-software-engineer-interview-907e36?returnPath=%2Fguides%2Fmeta-software-engineer-interview%2Fexperiences): “I think I was one of the first people to take Meta’s AI round, and the models I had were really bad, like ChatGPT mini. I tried asking for test cases and it would just spit out something completely wrong.” **Verified; 4 rounds, 4 questions**. Browse [all 56 Meta Software Engineer interview experiences](https://www.aced.io/guides/meta-software-engineer-interview/experiences). --- [Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fmeta-facebook-senior-software-engineer-interview-99496e&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%2Fexperiences%2Fmeta-facebook-senior-software-engineer-interview-99496e). Opening a form does not execute a tool.