After a first step where I was put through LeetCode-style problems, I ended up doing medium-difficulty coding tasks under a tight time constraint. They gave me four problems to solve in 90 minutes, but the pacing ended up being such that I could realistically only finish about three.
Overall it felt more like a time-management test than a “solve everything perfectly” challenge. The questions themselves were in the middle range, but what mattered most was how quickly I could move from understanding to implementing, and how much I could complete before the clock forced me to stop. I didn’t get an offer, and I walked away feeling like I could tell what the remaining gaps were—but the deadline limited how much I could fix before the session ended.
9 months ago
Average Positive Ciudad de Mexico
My screening focused on topics that matched the role, with emphasis on data structures and algorithms. The difficulty landed in the middle to hard range, but it didn’t feel out of place for the company’s expectations.
Overall, the questions were relevant enough that it felt intentional rather than generic. I didn’t receive an offer, and the main thing I took from it was that the bar wasn’t just theoretical—they were looking for solid fundamentals and the ability to work through problems that could get challenging.
11 months ago
Average Positive San Francisco, CA
My process started with a recruiter call, and then about a technical screen where I was asked general LeetCode-style coding. After that, the onsite en…
12 months ago
Average Positive United States
The interview felt fairly standard from the start. It opened with the usual set of questions about why I wanted to work there, plus something about th…
> 1 year
Average Positive Ciudad de Mexico
My Pinterest interview experience ended up feeling challenging but accessible. I found that the interviewers were genuinely warm and showed real inter…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically begins with a recruiter call followed by a technical screening, leading into multiple rounds that include coding challenges, system design, and behavioral interviews. Candidates can expect a mix of individual problem-solving and collaborative discussions throughout the stages.
Interview roundsRecruiter callBehavioral
Coding Challenges
Candidates face a series of coding challenges that often include medium to hard difficulty problems, primarily focusing on data structures and algorithms. The time constraints can make it feel like a test of time management as well as coding ability.
Coding challengesLeetCodeTime management
System Design Focus
There is a significant emphasis on system design, particularly for iOS and Android applications, where candidates are required to build solutions based on verbal descriptions without written specifications. This round is noted as particularly challenging and important for evaluation.
System designiOSAndroid
Behavioral & Soft Skills
Behavioral interviews are included to assess candidates' past experiences and soft skills, with questions often centered around motivation and problem-solving challenges. This part of the interview helps to gauge cultural fit and interpersonal skills.
BehavioralSoft skillsCultural fit
Supportive Interview Environment
Candidates generally report a positive and supportive atmosphere during interviews, with interviewers providing hints and fostering a collaborative environment. This approach helps to alleviate pressure and encourages open communication.
SupportiveCollaborativePositive atmosphere
Language Requirements
Candidates should be aware that despite initial training allowing for language choice, they may be required to use a specific programming language during the coding assessments. This can add pressure if candidates are not as comfortable with the required language.