Meta Interview Experiences

Overview

How Meta’s SWE interviews actually run, based on candidate reports (Blind, Glassdoor, Reddit) and public interview-prep guides - including the new CodeSignal OA and AI-enabled coding round rolled out during 2025.

Meta's India funnel is narrower than the brand suggests

Entry-level hiring at Meta’s Bengaluru office runs through University Grad / early-career postings, a summer internship track, and referrals or off-campus applications - not a college-wide placement cell. No fixed CGPA cutoff is published, and there’s no evidence of a TCS/Infosys-style multi-college drive. Treat a forwarded “Meta is coming to our campus” message as unverified until you check Meta’s careers page directly.

How to use this page

Read the round table first, then the experiences. Practise DSA patterns with a focus on trade-offs, prepare a design answer scaled to your target level, and keep one clear story ready for each of Meta’s five behavioral signals.

Round-wise process

Round	Duration	What it tests
Recruiter screen	20-30 min	Background, motivation, logistics
Online Assessment (CodeSignal, some candidates)	70-90 min	Progressive multi-stage coding problem, video/mic monitored
Technical phone screen	45 min	1 live coding problem
Onsite - Coding (traditional)	45 min	DSA - arrays/strings, graphs, trees, intervals
Onsite - Coding (AI-enabled, since late 2025)	~60 min	Coding with a built-in AI assistant; your judgment and prompting, not the assistant’s output
Onsite - System design / architecture	45-60 min	Scaled to level - lighter architecture chat for E3, full distributed design for E4+
Onsite - Behavioral	45 min	5 signal areas: driving results, ambiguity, communication, growth, conflict resolution
Team matching	Varies	Team/org placement after the offer

Real interview experiences

Experience 1: Software Engineer E4 (referral, 2025)

Profile: ~4 years experience in backend/infra roles, applied through an employee referral, interviewed for a Bengaluru-based team

Recruiter screen

• 25-minute call: current role, target team preferences, comp expectations, and notice period. Referral meant the CodeSignal OA was skipped entirely and the process went straight to a phone screen.

Technical phone screen

• Longest Substring Without Repeating Characters (sliding window + hashmap), with a follow-up on handling Unicode edge cases.

Onsite

• Coding (traditional): Merge Intervals, then a follow-up on handling a live/streaming stream of intervals.
• Coding (AI-enabled): a rate-limiter implementation with an AI assistant available. The interviewer cared more about why the candidate accepted or rejected each suggestion than whether the assistant was used at all.
• System design: design the ranking layer behind a News Feed - caching, fan-out strategies, and consistency-vs-availability trade-offs at read time.
• Behavioral: a project with measurable impact, a time a decision had to be made with incomplete information, and a disagreement with a manager.

Result: Offer at E4. Takeaway: The AI-enabled round rewarded narrating the reasoning behind each prompt, not the code the assistant produced. The design and behavioral rounds carried noticeably more of the leveling conversation than either coding round.

Experience 2: Software Engineer E3, University Grad program (2025)

Profile: Final-year CS student, applied off-campus through Meta’s University Grad posting (not a campus placement drive), one relevant internship

Recruiter screen

• 20-minute call covering eligibility, graduation timeline, and location preference.

Online Assessment (CodeSignal)

• A single problem in 4 progressive stages: basic get/set on an in-memory store, then TTL expiry, then point-in-time reads, then deletion - about 80 minutes total, video and mic on throughout.

Technical phone screen

• Two Sum, then Valid Parentheses as a quick follow-up; interviewer probed time/space complexity on both.

Onsite

• Coding: Binary Tree Vertical Order Traversal (BFS with column tracking), then Group Anagrams.
• Architecture discussion (lighter than a full E4+ design round): a simplified notification-delivery flow, mostly API shape and data model rather than distributed-systems depth.
• Behavioral: why Meta, a time a project failed and what changed afterward, and a teamwork/disagreement story.

Result: Offer at E3. Takeaway: The behavioral round felt conversational, almost informal, but a friend in the same hiring cycle with stronger coding scores was rejected after a flat, generic behavioral round - treat it as a real evaluation, not a formality, even at entry level.

Questions that come up often

Coding / technical

1. Merge Intervals - sorting + interval merging
2. Longest Substring Without Repeating Characters - sliding window + hashmap
3. Binary Tree Vertical Order Traversal - BFS with column tracking
4. Number of Islands - grid BFS/DFS
5. Group Anagrams - hashmap of sorted keys
6. Product of Array Except Self
7. Minimum Remove to Make Valid Parentheses
8. Diameter of a Binary Tree

System design

1. Design Facebook/Instagram News Feed (ranking, caching, real-time updates)
2. Design Messenger or a chat/notification system at scale
3. Design a search or content-ranking service
4. Design a rate limiter or distributed cache

Behavioral

1. Highest-impact project you’ve shipped - how did you measure it?
2. A decision made with incomplete information, or something that broke after moving fast
3. Direct/difficult feedback given or received
4. A time you failed and what you changed
5. A disagreement with a manager or teammate and how it resolved

Practical tips for Meta

• The CodeSignal OA is a real gate for many candidates now (added in 2025) - practice under a monitored, timed setting, not just untimed LeetCode.
• If you draw the AI-enabled coding round, write a first pass yourself before leaning on the assistant, and be ready to explain why you accepted or rejected its suggestions.
• Scale your system-design answer to your target level - E3 loops often get a lighter architecture chat, not a full distributed-systems design.
• Don’t treat the behavioral round as a formality because it feels conversational - public reports say it (along with system design) decides your final level, sometimes independent of how well coding went.
• Prepare a distinct story for each of Meta’s five signals (driving results, ambiguity, communication, growth, conflict resolution) rather than reusing one story for all of them.

HR interview

Meta’s behavioral round doubles as its closing HR-style conversation: motivation, career direction, and a couple of the five signal-area stories described above. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common Meta HR/behavioral questions, sample answer frames, and STAR tips.

Similar companies

Google · Amazon · Microsoft · Apple · Netflix · TCS