Meta's software engineer interview process has four main stages: a recruiter call, a 45-minute technical screen with two coding problems, a full loop of 4 to 6 interviews of 45 minutes each covering coding, design and behavioral, and then team matching and an offer. Some candidates also take a proctored CodeSignal online assessment before the screen, and prep sites report that since October 2025 Meta has been piloting an AI-enabled coding round that replaces one standard coding round. Reported timelines run from about three weeks to two months, longer when team matching is slow.
This guide walks through each stage using Meta's own candidate prep guides for the technical screen and the full loop, plus recent candidate reports. Practice varies by level and team, so your recruiter's instructions always win.
The process at a glance
| Stage | Length | What happens |
|---|---|---|
| Recruiter call | About 30 min (reported) | Background, target level, design track, language, schedule |
| Online assessment (some candidates) | About 90 min (reported) | Proctored CodeSignal test; format varies |
| Technical screen | 45 min | Intro, two coding problems in about 35 minutes, your questions |
| Full loop | 4 to 6 interviews, 45 min each | Coding, design (system design or product architecture), behavioral; one coding round may be AI-enabled |
| Team matching | Varies | Conversations with hiring managers until you match with a team |
| Offer | Varies | Level, compensation and start date with your recruiter |
The screen is a gate. The full loop decides two things at once: whether you are hired, and at what level.
Stage 1: The recruiter call
The first conversation is with a recruiter and, by most candidate accounts, lasts about 30 minutes. It is not technical, but it sets your target level, your design interview and the schedule.
Have these ready:
- A one-minute summary of your work. Team, scope, stack and one or two results with numbers.
- Your target level and the evidence for it. If you are aiming for senior (E5), be ready to name the multi-quarter projects you led.
- Your coding language. Meta's guide asks you to confirm it with your recruiter. Pick the one you are fastest in.
- Product or infrastructure. Meta says the design interview is either system design or product architecture depending on the position, and to ask your recruiter if you are unsure which one you will get.
- Any accommodation you need. Meta has a formal accommodations request process for candidates. Raise it early.
Ask back: Will I take an online assessment? How many rounds are in my loop, and will one be AI-enabled? Which design interview should I prepare for? Meta's guides also point candidates to a Preparation Hub in their Career Profile with coding puzzles and practice interviews.
Stage 2: The online assessment (some candidates)
Meta's official prep guides describe only the live technical screen, but since 2025 many candidates report a proctored online assessment first: 90 minutes on CodeSignal with camera and microphone monitoring, one problem split into four levels that unlock in order, which most candidates reportedly do not finish. Hello Interview notes some 2026 candidates instead report four separate easy-to-medium problems in 70 minutes. Not everyone gets one, and it must be done entirely on your own under Meta's and CodeSignal's rules. Our Meta online assessment guide covers the format and a prep plan.
Stage 3: The technical screen
Meta's Initial Interview Guide lays out the technical screen as a single 45-minute interview with an engineer:
| Segment | Time | What happens |
|---|---|---|
| Introductions | 5 min | Who you are, where you have worked, your areas of expertise |
| Coding | 35 min | Two problems on CS fundamentals such as algorithms, data structures, recursion and binary trees |
| Your questions | 5 min | Ask about the work from an engineer's point of view |
Remote screens use a collaborative editor such as CoderPad; in-person screens use a whiteboard. Candidates report that code execution is off, so trace your code by hand.
Meta grades the screen, and the coding rounds in the loop, on four focus areas:
- Communication. Asking clarifying questions instead of diving straight into code.
- Problem solving. Comparing approaches, choosing data structures, and stating time and space complexity.
- Coding. Turning the idea into organized, working code.
- Verification. Testing with sensible cases and finding your own bugs.
Three specifics from Meta's guide are worth acting on: practice medium and hard problems until each takes under 15 minutes, tell the interviewer if you have seen a problem before, and expect a follow-up that changes the constraints. Meta says it avoids puzzle questions, but problems can feel contrived because they must fit into 10 to 20 minutes.
Stage 4: The full loop
Meta's Full Loop Interview Guide says the loop is 4 to 6 interviews of 45 minutes each, with a few minutes at the end of each for your questions, covering coding, design and behavioral. For video interviews, you may be asked to share your screen over Zoom, Meta asks you to turn off video filters (including virtual and blurred backgrounds), and it asks that you use no unauthorized outside help, including AI tools like ChatGPT. For how loops work across companies, see our full loop interview guide.
Coding rounds
Expect about two problems in roughly 40 minutes per round. The interviewer will not compile your code, so structure, correctness and explanation matter more than a small syntax slip. Meta's guide calls catching your own bug a positive sign.
- No dynamic programming. Meta's full loop guide says it does not ask dynamic programming questions.
- Know the core structures cold: arrays, stacks and queues, hash tables, trees (including binary trees and binary search trees), graphs and heaps.
- Breadth beats depth. The guide recommends solving fewer problems across many types over drilling one type.
- Practice without tools. Write code in a plain text editor with no autocomplete or compiler, and talk through it as you go.
Our Meta coding interview questions guide has worked examples.
The AI-enabled coding round
In July 2025, 404 Media reported that Meta would let some coding candidates use an AI assistant in interviews. Hello Interview and interviewing.io report a pilot, starting October 2025, that replaces one standard coding round with a roughly 60-minute AI-enabled round:
- A CoderPad environment with multiple files, a terminal, a way to run tests, and an AI assistant that Meta builds into the environment.
- One extended problem in phases: fix a bug in existing code, implement the core feature, then optimize as larger test inputs expose weaknesses.
- Hello Interview reports grading on the same four competencies as standard rounds, including whether you verify the assistant's output instead of accepting it blindly.
Meta's published prep guides do not describe this round yet, so ask your recruiter whether your loop includes it. Outside the Meta-provided assistant in that one round, the no-outside-help rule applies to every interview.
Design: system design or product architecture
The design interview is 45 minutes, and Meta's guide says it is either systems focused or product focused depending on the position:
| System design | Product architecture | |
|---|---|---|
| Focus | Distributed systems, scalability, performance and efficiency | API design, usability and utility for a product used by end users |
| Meta's example prompts | Design a URL shortener; build Facebook chat; architect a worldwide video distribution system | Design a service or product API; design a chat service or a feed API; design an email server |
| Go deep on | Availability, scalability, security, testability, operations | Data models, client-server design, protocols, data formats, data ownership, handling product changes |
Either way, Meta scores four areas: problem navigation (asking questions that cut ambiguity and defining requirements), solution design (a working solution to the whole problem or its key pieces), technical excellence (dependencies, tradeoffs and failure points) and technical communication. The guide's advice: start from requirements, focus on tradeoffs instead of only the optimal answer, practice prompts on paper in roughly 30 minutes each, and get familiar with Excalidraw, the diagramming tool candidates report using. New grad (E3) loops typically have no design round.
Behavioral
One 45-minute session about your background, what you care about in tech and the impact you want to make. Meta lists five focus areas:
- Resolving conflict. Disagreements with colleagues or managers and how you settled them.
- Growing continuously. How you seek out feedback and improve your skills.
- Embracing ambiguity. Deciding and staying productive when information is missing or priorities shift.
- Driving results. Delivering against goals despite roadblocks.
- Communicating effectively. With your own team and with cross-functional partners.
The guide recommends outlining two or three major projects ahead of time, structuring answers with STAR (situation, task, actions, results), and being honest about projects that went badly. Our Meta behavioral interview guide has sample questions for each area.
How leveling works
Meta's software engineer levels start at E3 (entry level), and levels.fyi lists them up to E9. Prep sites commonly describe E4 as mid-level, E5 as senior and E6 as staff, and the level you interview for changes the loop:
| Level | Typical loop, as reported |
|---|---|
| E3 (entry) | Two coding rounds and a behavioral round; no design round |
| E4 (mid-level) | Coding (one round may be AI-enabled), one design round, behavioral |
| E5 (senior) | Same shape as E4; reports differ on whether there are one or two design rounds, and the bar on scope is higher |
| E6 (staff) | Can include a leadership assessment before the loop, then coding (including AI-enabled), an architecture round, a design round and behavioral |
Level is driven largely by the design and behavioral rounds. Hello Interview reports that a weak design or behavioral round can mean an offer one level below your target even when coding goes well, and interviewing.io reports that design interviewers are asked directly whether you fit another level. So tell stories at the scope of the level you want; for senior and above, that means projects that ran longer than a quarter, involved other teams and have measurable results.
Team matching, the offer and the timeline
If you pass the loop, the next step is team matching. Hello Interview and interviewing.io both report that since 2023 Meta matches candidates to a team before the offer, replacing the older approach of making the offer first and matching new hires after a bootcamp. Interviewing.io reports candidates may talk with anywhere from a handful to more than ten hiring managers, and the offer depends on a match. Treat these calls as two-way interviews: ask about the roadmap, on-call load and how impact is measured.
How long it takes. Hello Interview's guides put E5 at roughly 3 to 4 weeks, E4 at 4 to 8 weeks and new grad loops at up to 12 weeks, with team matching the biggest variable. Meta's guide suggests following up with your recruiter if you have not heard back within a week of your interviews. If the answer is no, interviewing.io reports candidates can usually try again after about 3 to 6 months.
Plan around the variable. Team matching can stretch a fast loop into a slow offer. If you have other processes running, tell your recruiter your timeline early.
A four-week prep plan
With about a month before the loop, this order follows Meta's own guidance:
- Week 1: coding fundamentals. Arrays, strings, hash maps, stacks and queues, trees, graphs and heaps. Do two mediums back to back in 35 to 40 minutes, in a plain editor, out loud. Skip dynamic programming.
- Week 2: speed and verification. Push toward Meta's target of under 15 minutes per problem. After every solution, trace two or three test cases by hand, then predict the follow-up.
- Week 3: design. Work Meta's own example prompts for your track on paper in about 30 minutes each, starting with requirements and ending with tradeoffs. If your loop includes the AI-enabled round, practice in an unfamiliar multi-file repository.
- Week 4: behavioral and full rehearsal. Outline two or three major projects, then map stories to the five focus areas. Finish with at least one full mock loop: coding, design and behavioral back to back.
The hardest part to practice alone is the talking. A free AI mock interview in CoPilot Interview lets you paste the Meta job description and your résumé, pick the level and question mix (including system design and coding), and answer out loud; each answer gets a score with what worked and what to improve.
Rehearse your Meta loop out loud
CoPilot Interview's free AI mock interview builds questions from a Meta job description and your résumé, scores each spoken answer, and ends with a report of likely next-round questions and practice drills. Free plan: 15 minutes a day, no credit card.
Try a free AI mock interviewFAQ
How many rounds are in the Meta software engineer interview?
Meta's full loop guide says the loop is 4 to 6 interviews of 45 minutes each, covering coding, design and behavioral. Before the loop come a recruiter call and a 45-minute technical screen, and some candidates take a CodeSignal online assessment first.
How long does the Meta interview process take?
Prep sites that track Meta loops report anywhere from about 3 weeks for some senior candidates to 2 or 3 months for new grads, with team matching the biggest variable. Meta's guide suggests following up with your recruiter if you have not heard back within a week of your interviews.
Does Meta ask dynamic programming questions?
Meta's own full loop guide says it does not ask dynamic programming questions and suggests focusing your prep elsewhere. Spend that time on arrays, strings, hash tables, trees, graphs, heaps, and stacks and queues.
Can I run my code in the Meta coding interview?
Not in the standard coding rounds. Meta's guide says the interviewer will not compile your code, so practice in a plain editor and trace test cases by hand. The AI-enabled round Meta began piloting in late 2025 is reported to be different, with a terminal and a way to run tests.
Does Meta do team matching before the offer?
Yes, according to prep sites and candidate reports: since 2023, candidates who pass the loop talk with hiring managers and need a mutual match before the offer is finalized. Previously, Meta made the offer first and matched new hires to teams after a bootcamp.