Meta Software Engineer, Intern interview questions
based on 193 ratings - Updated Jun 8, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
35%
Campus Recruiting
Campus Recruiting
32%
Applied online
Applied online
16%
Recruiter
Recruiter
16%
Employee Referral
Employee Referral
2%
Other
Other
Interview search
193 interviews
Viewing 16 - 20 of 193 Interviews
Meta interviews FAQs
Software Engineer, Intern applicants have rated the interview process at Meta with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 59% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer, Intern roles take an average of 90 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 32 days.
Common stages of the interview process at Meta as a Software Engineer, Intern according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
It was really straightforward. Recruiter reached out and sent coding screen. A few days after completing it, I scheduled an interview. It was only one round. The questions were both leetcode easy
The interview starts with self-introdction, then two medium level leetcode with dry run and complexity analysis. Then I asked several questions and the interviewer answered. No behavior questions and stuff.
I applied online. The process took 3 weeks. I interviewed at Meta (Londres, Angleterre)
Interview
Very technical interview, the interviewer didn’t even go through the “introduce yourself” formalities, opened straight with the Leetcode question. Overall, didn’t enjoy the interview, felt very impersonal. There were two leetcode-style questions to solve within 40 minutes on whiteboard. Company is very focused on reducing latency, so if that’s not something you particularly enjoy as a technical challenge,
might not be the best fit (as was in my case)