Meta Machine Learning Engineer interview questions
based on 159 ratings - Updated May 31, 2026
Averageinterview difficulty
Mostly positiveinterview experience
How others got an interview
62%
Recruiter
Recruiter
22%
Applied online
Applied online
14%
Employee Referral
Employee Referral
1%
Campus Recruiting
Campus Recruiting
1%
In Person
In Person
Interview search
159 interviews
Viewing 11 - 15 of 159 Interviews
Meta interviews FAQs
Machine Learning Engineer 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 44% positive. This is according to Glassdoor user ratings.
Candidates applying for Machine Learning Engineer roles take an average of 21 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 36 days.
Common stages of the interview process at Meta as a Machine Learning Engineer according to 1 Glassdoor interviews include:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Meta (New York, NY) in Jul 2025
Interview
It was five rounds interview, one screening round + full loop (four rounds)
All in all: six leet code style questions, behavioral interview, system desgin interview
Everything was online and everyone were friendly
I applied through a recruiter. The process took 2 months. I interviewed at Meta in Sep 2025
Interview
The whole process is very streamlined and automated as much as possible. Good:
- Recruiter was very nice and generally helpful.
Bad:
- All interviews are fully remote. That's not a problem except the design interview. Its very difficult to discuss design remotely, especially given hard constraints.
- No ML questions, even for an ML engineer role. All technical interviews are only coding.
Final design interview was very PM-style, with a strong focus on business metrics. Every time I wanted to discuss ML-related technicality (i.e. network architecture, loss function, source of training data, ..) I was harshly interrupted by an interviewer.
- zero diversity. All interviewers are young Eastern Asians in their 20s.
Interview questions [1]
Question 1
Screen:
- one round of 90-minute coding; 4 related problems of increasing complexity
- Leetcode-style interview with a person. 2 questions - palindrome, trees
Full loop (each interview is ~45 mins):
- AI-assisted coding. You need to understand a codebase, fix bugs, implement new functionality. You can use Claude
- 2 medium Leetcode problems
- behavioral. Focus on past projects, conflict resolution etc.
- ML design.
Just an intro screening call with recruiter who contacted me on linkedin without follow-up. i think because they were looking for more years of experience for a senior role. Asked how I worked with rag