
Plaid Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 75 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Plaid.
Software Engineer Intern
The interview process was quick and professional. It had 3 stages: an online assessment, an HR chat, and a final interview. The online assessment had two parts to a large, medium-leetcode-difficulty question. The final interview was 3 hours long, split into 1.5 hours of technical questions and 1.5 hours of a manager discussion. The technical part involved three questions, each building on the previous one.
- Can you share about your previous internship experience?
Software Engineer
The technical interview process is notably behind industry standards - instead of using standard coding platforms like CoderPad or HackerRank, they gave prompts/ starter code in Zoom, asked candidates write code in their own environment and send it via email, creating an inefficient back-and-forth. The process itself is draining: 7 rounds of interviews, including repetitive technical assessments where alternative approaches aren't well-received. Recruiter consistently showed up 30+ minutes late to scheduled meetings. Most concerning: After completing the entire process, I was informed that even passing all rounds doesn't guarantee placement due to headcount/reorganization issues. Subsequently, received a rejection with zero feedback and no further communication. The experience suggests serious organizational issues. I wouldn't recommend this process even for interview practice, given the excessive time investment required and the quality of technical discussions. Other companies offer much more respectful, efficient, and professional interview experiences. Save yourself time and energy by looking elsewhere.
- Coding question involving hashmap and math
- System design question about scraping events, ingesting, and notifications
Software Engineer
I rarely write reviews but this one annoyed me the most. Round 1 was a HM call. Round 2 was a 1hr System Design interview combined with a 1hr Coding interview. The System Design interviewer was obnoxious and seemed not senior enough to understand my points. He was also distracted on his phone twice, and I had to get his attention back. The third time, I stopped talking and he didn't notice for a minute, then claimed he lost connection, which I didn't believe. The Coding round was good, but it was annoying that Plaid made us set up IDEs. We were given boilerplate code over Google Meet chat and then asked to email the completed code.
- NDA
Plaid Software Engineer Interview Questions
Quoted word for word from Plaid interview reports.
“Can you use a web scraping library to scrape a site and put the data into a file?”
Read reports →“Can you derive PI using monte carlo simulations?”
Read reports →“How would you design an API rate limiter?”
Read reports →“What's your approach to calculating the total cost of a grocery cart when coupons are involved?”
Read reports →“Describe a question related to parsing strings and rendering DOM elements.”
Read report →“How would you create interactive UI components using CSS, HTML, and vanilla JS?”
Read report →“What are the potential edge cases for the solution you provided?”
Read report →“Tell me about a time you couldn't keep a promise.”
Read report →“Were the technical questions more practical and less algorithm-based?”
Read report →Formats, difficulty and experience
Across all 75 Plaid interview reports.