Top Tech Transition Enroll now

Real Interview Experiences

Learn what to expect, straight from candidates who've been through it at top tech companies.

908 interviews243 companies286 offers
Loading experiences…

Browse by company

Browse by role

← Back to all experiences

Meta Software Engineer Interview Experience

Meta · Intern

ResultGot the offer ✓
Timespan2 months
DifficultyMedium
Rounds2

Interview process

My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation speed and correctness, while the later sections required more problem-solving depth and handling more complex constraints under time pressure.

After that, I had a technical interview consisting of two LeetCode-style medium questions in a 45-minute session. The focus was on both arriving at efficient solutions and clearly communicating my thought process while working through each problem.

What went well was my ability to understand the problems quickly and stay consistent across different difficulty levels. What didn’t go as well was pacing, especially in balancing correctness and optimization within the time limits.

Interview rounds · 2

  1. 1

    Online assessment

    Coding

    Codsignal GCA

    1. Q1. Codesignal GCF
  2. 2

    Technical round

    Data Structures & AlgorithmsCoding

    DSA questions

    1. Q1. Leetcode
    2. Q2. Tree Node

Tips from the candidate

I would tell a friend to focus heavily on medium-level LeetCode problems with strong emphasis on speed and clean implementation. The CodeSignal assessment ramps up in difficulty across multiple sections, so being comfortable transitioning from easy warm-up problems to more challenging ones under time pressure is important.

For the later technical round with two questions in 45 minutes, I would recommend practicing solving mediums in 15 to 20 minutes each while clearly explaining thought process out loud. Being able to quickly identify patterns and move from brute force to optimized solutions is key. I would also suggest doing mock interviews to get used to pacing and communication under constraints.

Company culture

I think it was the encouragement from the interviewer which felt rare. Even during a timed and fairly high-pressure technical interview, the interviewer was patient, gave space to think, and provided subtle reassurance when I was on the right track. It made the process feel more like a collaborative problem-solving exercise rather than an interrogation.

It also stood out that the expectations were very structured and consistent. There was great focus on how clearly I communicated my reasoning and broke down problems.

Details

CompanyMeta
RoleSoftware Engineer
LevelIntern
LocationUnited States
InterviewedOct 2024
Questions asked3