Plaid Software Engineer interview questions

6 Software Engineers have shared notes from their Plaid interviews, with the questions they were asked in each round. That is 75% of the 8 Plaid interview notes on Screna AI.

6 Software Engineer interview notes

Plaid·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Plaid coding round centered on a single problem: a coupon discount system built out in two phases, with a lot of edge case pressure. Clean code and test coverage mattered as much as getting the logic right.
  • You have a shopping cart where each item has a category and a price, plus a list of coupons. First, implement applying a single coupon (fixed discount or percentage off a category) and compute the final total. Then extend it to handle multiple coupons with stacking rules you define. Handle edge cases: discount exceeding item price (clamp to zero), same category targeted by multiple coupons (define your rule), and percentage discounts above 100% (cap at free). Write clean code, test cases, and analyze time complexity.

“This felt manageable at first and then the edge cases kept stacking up.”

View Post

Plaid·Software Engineer·Technical Phone Screen

Jun 2026
Plaid data engineer interview that threw a deliberately messy real-world data problem at me. Two coding tasks, both around bank name normalization and fuzzy ID mapping. The problem was intentionally underspecified, which I was not prepared for.
  • Write a function that normalizes raw bank name strings into a canonical form, handling things like inconsistent casing, punctuation, abbreviations, and corporate suffixes like 'N.A.', 'Inc.', or 'Corp.'.
  • Given cleaned bank data with an internal ID system and an external ID system that don't map 1:1, write a fuzzy matching function that returns for each internal bank ID the set of plausible external bank IDs it could correspond to.

“I jumped straight into lowercasing and stripping punctuation and felt pretty good about it, but then I got tripped up on the suffix-stripping part.”

View Post

Plaid·Software Engineer·Technical Phone Screen

May 2026
Plaid data engineering interview with a data cleaning and ID mapping problem. Pretty focused on schema design and how you handle messy real-world data, which felt very on-brand for Plaid.
  • You have a dataset that maps bank names and identifiers to two ID systems (internal and external). Write a function that produces a clean mapping of every internal bank ID to its corresponding external bank ID.

“The base case is a 1:1 join once you line up bank name and identifier correctly, which sounds easy but the first thing I fumbled was not asking about nullability up front.”

View Post

Plaid·Software Engineer·Onsite - System Design / Architecture

May 2026
Plaid data engineering interview built around a take-home assignment. You show up with SQL already written, then spend the session defending every decision while the interviewer throws increasingly annoying edge cases at you. Less about writing code on the spot, more about whether you actually understand why you made the choices you did.
  • Walk me through how your pipeline moves data from raw source through to the final analytical layer. Why did you structure it that way?
  • How would you handle incremental loads here? Walk me through the tradeoffs between a full reload, CDC, and a high-watermark approach on an updated_at column.
  • Your model assumes events arrive in order. What breaks if they don't, and how does your design handle that?
  • How do you handle duplicate rows coming from the source system? Where in the pipeline do you deal with them and why there specifically?
  • What happens to your model when the source schema changes? Say a column gets added, or worse, a column gets renamed.
  • Your pipeline has a partial-day partition at the end of a run. How do you make sure downstream consumers don't query incomplete data?
  • How do you handle deletes in the source system? Does your model support hard deletes, and if not, why not?
  • You have NULLs appearing in a join key. What do you do, and what does it mean for the rows that can't join?
  • Timestamps in your source data are inconsistent across time zones. How does that affect your model and where do you normalize it?

“This was the opening and I thought I had it locked.”

View Post

Plaid·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Plaid SWE interview with a project presentation round where you walk through a past project end to end using a short slide deck, live, in front of the interviewer. The format is more structured than a typical system design chat and the stoic-interviewer thing is real, don't expect much feedback mid-presentation.
  • Walk us through a substantial past project end to end, covering the problem, your role, system architecture, key technical decisions, results, and lessons learned.
  • Why did you make this architectural choice instead of the alternative you mentioned?

“This is the whole round basically.”

View Post

Plaid·Software Engineer·Technical Phone Screen

Apr 2026
Plaid software engineer interview with a communication-heavy prompt that asked you to walk through a past project for someone outside your domain. Not what I expected going in.
  • Walk me through a past project in detail, specifically one where the interviewer might not share your technical background. Cover the problem, your design choices, trade-offs, results, and how you'd explain it so someone unfamiliar can still ask meaningful follow-up questions.

“This one tripped me up more than I expected.”

View Post