Real, anonymous reports from people who interviewed for Software Engineer at Pinterest, newest first and distilled into what to expect across the loop.
Get your personalized Pinterest Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
The first thing that went wrong set the tone. The interviewer sent me the wrong link for the virtual meeting, and they were about five minutes late. During the warmup question—basically a variation of the Boyer-Moore Voting Algorithm—they kept interrupting while I tried to implement a brute-force approach to understand the problem, and they wouldn’t let me finish my thought.
They did the same pattern for a second question, a graph traversal problem. Throughout, the interviewer didn’t seem very engaged or interested, starting from the beginning rather than only after I struggled.
3 months ago
Difficult Neutral Seattle, WA
The technical screen felt difficult in a very specific way: it was essentially LeetCode medium-to-hard, and I had about an hour. I could get hints, but the expectation was still that I’d solve the problem myself rather than coasting through with help.
What stood out was how much the clock mattered even with collaboration allowed. I ended up not progressing to an offer, and the process left me with the usual sense that the bar was high enough that “almost” didn’t count.
4 months ago
Easy Negative United States
I walked into the process expecting Pinterest to feel intense, but the technical interview ended up surprisingly light. It was just two coding questio…
4 months ago
Average Negative United States
I moved through the process in a straightforward sequence: recruiter call, a tech round, then an onsite, followed by a rejection call. After the onsit…
4 months ago
Average Neutral United States
My first step was a technical phone screening with a hard time box of about an hour. I remember it as one coding problem where there was a follow-up q…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter Screen
The initial recruiter screen is typically focused on behavioral questions and logistics, allowing candidates to discuss their backgrounds and project experiences. This stage sets the tone for the process and is generally straightforward and relaxed.
BehavioralLogisticsBackground
Technical Screen
Candidates can expect a technical phone screen featuring 1-3 LeetCode-style coding questions, often with a mix of medium and hard difficulty. The emphasis is on solving problems under time pressure, and pacing is crucial to demonstrate coding proficiency.
LeetCodeCodingTime Pressure
Onsite Interviews
The onsite typically consists of multiple rounds, including coding, system design, and behavioral interviews. The structure is designed to evaluate both technical skills and soft skills, with a focus on clear communication and problem-solving abilities.
System DesignBehavioralMultiple Rounds
Interview Atmosphere
The interview experience can vary significantly, with some candidates reporting unengaged interviewers or a lack of clarity during technical evaluations. A positive atmosphere is noted by others, emphasizing professionalism and respect throughout the process.
EngagementProfessionalismAtmosphere
Feedback and Outcome
Candidates often express disappointment regarding the feedback process, with some feeling that their performance did not align with the final decision. The communication about outcomes can feel abrupt or unclear, leaving candidates uncertain about their standing.
FeedbackOutcomeCommunication
Preparation Insights
Candidates suggest preparing for a range of technical questions, particularly in data structures and algorithms, and practicing coding under time constraints. Utilizing platforms like PracHub for case studies can help structure thinking during coding interviews.