Pinterest Machine Learning Engineer Tech Phone Interview Experience
Interview Experience
A bizarre experience: I applied to this company quite late; several onsite interviews were already completed, while this one had just started its phone interview. I'm currently an AS at a major compan
Full Details
A bizarre experience: I applied to this company quite late; several onsite interviews were already completed, while this one had just started its phone interview. I'm currently an AS at a major company. 7.5 years of yearly experience, with about 5-6 years of LLM experience from the BERT era to now. My interviewer was an SDE from a South Asian country. He seemed a bit distracted throughout, constantly replying to messages, and we didn't seem to be on the same technical wavelength. The questions were generally quite simple: a brief chat about my experience, and quick answers to some very basic ML questions, such as what overfitting is, what a decision tree is, and whether it's linear or nonlinear. The coding wasn't a LeetCode problem; it asked me to implement a system to determine if an IP address is on a blocked list, and then discuss the complexity, improvements, etc. I felt I answered very well; the implementation, optimization, and code cleanliness were all fine. The next morning, I received an email saying, "Emal decided not to move forward." I've now become the first person I failed out of nearly thirty interviews in this job-hopping wave. I had to come here and vent.
About This Question
This is a candidate experience report from a pinterest interview for a mle role during the phone screen round reported in 2025.
It covers the following topics: Tree .
Difficulty rating: Easy
Topics
More Pinterest Interview Questions
About Pinterest Interview Reports
This question was reported by a candidate who interviewed at Pinterest. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Pinterest are the higher-signal extractions to take from this report.
For broader preparation context, the Pinterest interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Pinterest reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Pinterest Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Pinterest reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.