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 146 - 150 of 193 Interviews
Meta interviews FAQs
Software Engineer - Intern applicants have rated the interview process at Meta with 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 58.1% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 3 weeks. I interviewed at Meta in Aug 2013
Interview
I contacted my school recruiter and had a phone screening with her after a week. Then I was scheduled for a technical phone interview for the following week. The interview was easy involving basic data structures, but my interviewer seemed disinterested the whole time. I would ask questions, but there was just silence until I 2nd or 3rd time.
I was asked 3 coding question, I gave the most optimal solution to all. I copy-pasted my code after the interview, and everything compiled and ran perfectly.
I did not get an offer because apparently I was not "quick enough". Oh well.
Interview questions [1]
Question 1
- Convert sorted array to BST
- Print the above tree level by level
- I forgot the last question
The process started out with a pre-screening test which was coding based. There was one question to be done in 60 minutes. The question was fairly simple for me and I completed it quickly. Then, I was called for the onsite interviews a week later. The interview was supposed to last for 45 minutes. Now, in my interview, I was first asked about the best experience I have had in my last two years. Then, the interviewer quickly moved on to the coding questions. There were two questions for which I had to explain my solution and then code it on the whit board. I was able to both the questions, but I guess the interviewer might not have liked the way I had explained my approach as I was not called for the next interview. The interviewer was not very vocal and did not really participate in the discussion where you explain the approach. That is why it becomes difficult to detect if the interviewer is understanding your words or not. Anyways, it was a some experience.
Interview questions [1]
Question 1
Given a binary tree, which is not necessarily balanced, print the nodes in the tree in a level-wise manner. Also, nodes on the same level should be printed on a single line.
A modification of the question was added later in which I cannot really add a "level" variable in the structure of the node in the tree.
They usually have one interview and if you clear that you have another interview. Mine were on consecutive days. Each interview was 30 mins. They do not spend too much time chit chatting and usually get right to business. They focus on how you approach the question more than the if you actually got the question right or not
7
Top companies for "Compensation and Benefits" near you