Meta Software Engineer (internship) interview questions
based on 718 ratings - Updated May 13, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
33%
Applied online
Applied online
31%
Employee Referral
Employee Referral
22%
Campus Recruiting
Campus Recruiting
13%
Recruiter
Recruiter
0%
Other
Other
0%
In Person
In Person
Interview search
718 interviews
Viewing 646 - 650 of 718 Interviews
Meta interviews FAQs
Software Engineer (internship) applicants have rated the interview process at Meta with 3.3 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 74.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer (internship) roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 43 days.
Common stages of the interview process at Meta as a Software Engineer (internship) according to 3 Glassdoor interviews include:
Phone interview: 67%
Presentation: 33%
Here are the most commonly searched roles for interview reports -
I applied through college or university. I interviewed at Meta
Interview
I had an on campus interview and it was fairly smooth. The interviewer was polite and helped me whenever I got stuck on a problem. The interviewer was also very informative whenever I asked questions regarding the company.
I applied online. The process took 2 weeks. I interviewed at Meta (Atlanta, GA) in Jan 2017
Interview
Two standard phone interviews (similar to how Google, Amazon or pretty much any other company does their phone screens). Got an email later with their offer. It was really fast, HR was very pleasant to work with compared to other experiences.
I applied through college or university. The process took 3 weeks. I interviewed at Meta (Stanford, CA) in Oct 2017
Interview
On-campus interview. The interviewer was friendly and introduced himself. A few minutes of resume discussion and then the technical question on the whiteboard. I worked the problem out in pseudocode and then in code, making sure to think out loud. A few days later I was invited to the on-site, which hasn't yet happened.