Skip to main content
Meta
Meta Machine Learning Engineer (MLE) Interview Guide

Updated by Meta candidates

Back to all
VerifiedUnited States2 days ago
Meta

Computer Vision Engineer (L5) Interview Experience

Meta·Senior / L5
What caught me off guard was that one of the coding rounds was not generic LeetCode at all. It was AI coding, with things like sparse matrix times vector multiplication and k-nearest neighbor search, and they still wanted multiple questions under pressure.
Result
Got offer
Interview date
2 months ago
Timespan
1 month
Difficulty
Difficult

Interview process

What surprised me most was how much the process emphasized solving several coding questions under pressure. I had an initial recruiter screen, then a 45-minute pre-screen with a senior manager about my past work and impact, and after that a full loop of five interviews. The loop was two coding rounds, one of them classic LeetCode-style and one of them AI coding with data-processing and math-heavy prompts like sparse matrix times vector multiplication and k-nearest neighbor search, plus two design rounds and one behavioral. The design interviews were split between an ML modeling discussion for a computer vision problem and a system design round on something like Google Street View, which I found pretty challenging. I passed the loop, got notified that I made it through, and then moved into offer negotiation.

  • Recruiter screen
  • Phone interview
  • Technical interview
  • Other

Interview tips

Generic LeetCode will NOT cut it. I would practice doing two or three coding problems back-to-back under time pressure, and I would make sure some of that prep is AI-flavored coding around data processing and math, not just classic algorithms. I would also be ready for two very different kinds of design interviews: one that is really ML modeling for computer vision, and one that is true end-to-end system design. For behavioral, I would have clean stories ready on delivery pressure, conflict, and responding to tough feedback.

Company culture

The process felt pretty standard for a big tech company, but with a heavier emphasis on fast live coding than I expected. The interviewers were also pretty deliberate about pacing and scope, so it did not feel like casual conversation rounds. It felt structured, high-bar, and very intentional about covering both modeling depth and production thinking.

Questions asked

Overview

I started with a recruiter screen that was basically a fit check for whether my background matched the role.

Question types asked

Unlock more real interview experiences

Get full access with a membership, or share your experience to try it free.

formerly Exponent

Get updates in your inbox with the latest tips, job listings, and more.

Follow Us

Products
Courses
Interview Questions
Interview Experiences
Popular articles
Guides
Coaching
For Partners
Company
Exponent Labs, LLC © 2026
Terms of Service | Privacy