RoundHound
Get accessSign in
Prepare
HomeHomeJobsJobsPractice historyHistoryProgressProgress
Get full access?Sign in
Jobs/Meta

Software Engineer, New Grad

Meta · Entry-level (E3)

Research from Oct 93 rounds, none tried

This is how Meta interviews for Software Engineer, New Grad, from our research: 3 rounds, what each one looks for, and how to prepare. Pick any round and an AI interviewer runs it with you out loud, by voice or by typing. Afterwards you’ll see what went well and what to work on next.

Your first 60 minutes of practice are free. No card needed.

Next: your first full round

Do the Coding Interview One round.

One full round, as long as theirs, shows where you stand before you work on anything specific.

Set up this round →Practice the full interview day
Length45 min · Entry-level (E3) level

The rounds

3 rounds · 2 h 10 min

Pick a round to see what it asks of you and where you stand on it.

Coding Interview One

Tests algorithm selection, correct implementation, complexity awareness, and edge-case handling in a short coding session.

Coding · 45 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Confirms inputs, outputs, constraints, and examples before selecting an approach.
  • Chooses a fitting data structure or algorithm and explains why it meets the constraints.
  • Writes logically correct code with clear names, simple control flow, and no avoidable redundancy.
  • States time and space complexity accurately and connects both costs to the approach.
  • Identifies relevant empty, boundary, duplicate, or invalid cases and addresses them in the written code.

Expect to be pushed on

Probe alternate constraints and require a better complexity when needed.
Ask for edge cases and a manual trace through the written code.

Shapes of problem you may get

  • Standard array, string, tree, or graph problem
  • Pattern-recognition problem with a complexity follow-up

What they look for

Researched today

Recent exact-level Meta reports commonly show two coding interviews and one behavioral interview. Coding rounds use LeetCode-style data structure and algorithm problems, often with complexity and edge-case follow-ups; one report gives 45 minutes and two questions. Behavioral discussions cover project impact, conflict, and reflection. A current technical screen, online assessment, design round, or extra follow-up is not confirmed.

They reward

  • Fast, direct problem solving with clear explanations.
  • Careful attention to complexity, edge cases, and code quality.
  • Specific ownership, collaboration, and learning from project decisions.

What to avoid

  • Do not code before confirming the input model and required output.
  • Do not accept a brute-force approach without stating its complexity and limits.
  • Do not hide uncertainty about complexity or skip a requested optimization.
  • Do not let a follow-up erase correctness and explanation on the first approach.
  • Do not describe team success without separating your own actions.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Attempts

Every round you’ve done for this job, newest first.

All attempts in History →

Coding Interview One, Coding Interview Two, and Behavioral Interview have no attempts yet.

  • Two-part data-structure problem with edge cases

    • How to prepare

    1. Rehearse constraint-first problem setup

      Select six varied algorithm problems. For each, write the input model, output, constraints, examples, likely data structure, and target complexity before coding.

      Recent exact-level reports describe LeetCode-style coding rounds and attention to complexity and edge cases. This makes the opening explanation worth preparing first.

      Company researchMeta SWE New Grad Interview Experience - Menlo Park, CaliforniaMeta Software Engineer New Grad Interview Experience - Menlo Park, CaliforniaInterview Experience - 115 - Meta | Software Development Engineer | New Grad

    2. Prepare clear invariant explanations

      Choose three problems involving arrays, trees, or graphs. Rehearse stating the invariant, naming the main variables, and explaining why each update preserves correctness.

      This round tests implementation and explanation in 45 minutes. A short invariant explanation helps keep code and reasoning aligned without relying on memorized solutions.

      Suggested approach

    3. Build an edge-case trace habit

      For each selected problem, list empty, single-item, duplicate, boundary, and invalid cases when relevant. Trace one normal case and one boundary case on paper.

      Candidate reports mention edge cases, code quality, and manual testing. A prepared trace gives you a concrete check after implementation.

      Company researchInterview Experience - 115 - Meta | Software Development Engineer | New GradMeta Intevriew experience - Interview Experience - FrontendLead Discuss

    Then try the round

    You have six selected problems, written setup notes, three invariant explanations, and edge-case traces for each problem.

    Resources to focus on
    • Preparing for your software engineering interview at Meta

      Focus on “Full interview: coding—what to expect” and “How to prepare for the coding interview.” The guide may not match every current E3 cycle.

      Use its guidance on explaining approaches, complexity, testing edge cases, and managing time for this round.

    • DSA - Prepare For Coding Interview

      Focus on “5. Complexity Analysis: The Foundation” and “9. How to Solve a Problem You’ve Never Seen.”

      Use the sections to practice constraint reading, approach selection, trade-offs, and boundary-case testing.

    Do

    • Clarify inputs, outputs, constraints, and examples before choosing an approach.
    • State the invariant, write readable code, then manually trace normal and boundary cases.

    Avoid

    • Do not code before confirming the input model and required output.
    • Do not accept a brute-force approach without stating its complexity and limits.

    Your first try takes the full 45 minutes, like the real one.

    Confirmed · 7
    • Recent exact-level candidate reports describe a final loop with two technical or coding interviews and one behavioral interview.
    • Recent exact-level candidates report LeetCode-style coding questions for Meta new-grad interviews.
    • One June 2025 exact-level report says each coding interview lasted about 45 minutes and contained two coding questions.
    • Exact-level reports describe coding difficulty from basic or medium to medium-hard or hard.
    Likely · 2
    • The university-grad role likely expects code quality and test coverage in addition to algorithmic problem solving, because a university-grad posting lists high-quality code with good test coverage and increasing project complexity.
    • The E3 behavioral discussion likely tests collaboration and technical choices because Meta describes software engineering as cross-team work, and direct reports include project deep dives and conflict questions.

    Worth asking them

    Questions that fill in what the research couldn’t tell us.

    Are current E3 University Grad interviews still two coding rounds and one behavioral round?
    Does this E3 loop include a technical screen, online assessment, or design discussion?
    What language, editor, execution policy, and coding-round duration should I use?

    Research status

    Collected Oct 9. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

    Correct this brief