Candidates describe Pinterest's software engineer interview as coding-heavy: a recruiter screen and technical phone screen, then a four-to-five interview loop with algorithms, system design, and a manager conversation.
$179K
Avg. Base Comp
$314K
Avg. Total Comp
6-7 rounds
Typical Rounds
2-3 months
Process Length
Candidates who interviewed for Pinterest software engineer roles describe a process built around coding. Reports typically start with a recruiter conversation and a live technical phone screen. A virtual onsite of four or five interviews follows: two or three coding rounds, one system design round, and a hiring manager conversation.
Data structures and algorithms carry the most weight in these reports. Problems are described as LeetCode-style, from medium to hard, sometimes with modifications from familiar versions. Reported examples include a medium phone-screen problem with a hard follow-up, a three-part coding question, a JSON validator, and a matrix pathfinding problem. Others include binary search combined with dynamic programming, and combinations of dictionary items across multiple lists. One candidate who solved every onsite problem optimally still did not get an offer. Treat clear communication and composure as part of the bar, not just correct code.
System design shows up in most loops. A senior candidate was asked to design a distributed key-value store and also had a Linux operations round. Another senior candidate was told the onsite would include a 60-minute architecture round alongside rounds on technical depth, competencies, and leadership.
Interviewer quality is described as uneven. Reports include a late interviewer who said nothing during coding and one who left the call midway. Rejections often came without feedback, and most reports in this set ended without an offer. One candidate says team matching is required before an offer and can stretch the process to two to three months. Ask your recruiter early about timing and team placement.
Synthesized from 32 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Pinterest process.
The question I kept thinking about after my loop was the system design round, because the interviewer wanted numbers before any boxes went on the whiteboard. The prompt was to design Pinterest's notification system. I was expected to work out the scale first: estimate QPS, consider busy times versus quiet periods, and reason about the size of the user base. Only after that did we move to technology choices and how to meet response time and availability targets. The SLAs were something I had to agree on with the interviewer during the discussion, so I couldn't just assume them.
The process began with a technical screen, a single 60-minute session of medium-to-hard LeetCode-style problems. The final round was three interviews back to back. One was the system design discussion, one was a medium-to-hard LeetCode-style coding problem, and the last was a behavioral interview in the hiring manager style. The recruiter was attentive throughout and kept me informed at each stage.
I did not receive an offer. Looking back, I would spend less time polishing the coding warm-ups and more time practicing estimation-first system design, since the scale numbers came before any architecture and clearly shaped the rest of the conversation.
Prep tip from this candidate
Practice back-of-envelope estimation for a notification-style system (QPS, peak hours, user base) before sketching components, since the interviewer expected the numbers to drive the design. Also agree on SLA targets explicitly with the interviewer rather than assuming them.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Pinterest
Write a query to return whether each user's subscription date range overlaps with any other completed subscription
| Question | |
|---|---|
| Size of Joins | |
| P-value to a Layman | |
| Most Repetition | |
| Priority Queue Using Linked List | |
| Ad Comments | |
| Feed Impression | |
| Max Width | |
| A/B Testing a Checkout Button Change | |
| Greater Release Dates | |
| Ranking Metrics | |
| Maximal Substring | |
| Maximum Common Substring | |
| Singly Linked List | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Comments Histogram | |
| Job Recommendation | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically describe a recruiter conversation covering their background and fit for the role. Accounts describe it as straightforward. It is a good moment to state any timeline constraints. One candidate says the process stalled after the final round despite flagging that they were in offer stages elsewhere.
Candidates report a live coding interview, typically a LeetCode-style problem in a shared environment. One faced a medium problem with a hard follow-up, and another a three-part question in a one-hour session. A third candidate's first coding round was a JSON validator.
Candidates report a loop of roughly four or five interviews, often in one day. Typical mixes are two or three coding rounds at medium to hard difficulty, one system design round, and a hiring manager conversation. At senior level, one candidate describes a Linux operations round. Another was told of technical depth, competency and leadership rounds plus a 60-minute architecture round. Interviewer consistency varies.
Timelines after the loop vary. One candidate received an automated rejection after eight days with no feedback, while another waited weeks to hear back. One candidate says team matching is required before an official offer and can stretch the process to two to three months. Follow up with your recruiter if you hear nothing.
