Plaid Interview Questions — Page 1

Plaid·Software Engineer·Technical Phone Screen

Apr 2026

Plaid SWE interview with a communication-heavy technical question that required walking through a project for someone who might not share your background. More nuanced than it sounds.

Walk me through a past project in detail, specifically one where your interviewer probably doesn't share your technical background. Cover the problem, your design choices, trade-offs, and results, and explain how you'd adapt the explanation so a non-expert can follow and ask real follow-up questions.

“This tripped me up more than I expected.”

View Post

Plaid·Software Engineer·Onsite - System Design / Architecture

Apr 2026

Plaid system design round focused on distributed rate limiting, which sounds straightforward until you start thinking about cross-region consistency. There was also a follow-up scheduling problem that I didn't see coming and probably didn't handle as cleanly as the first part.

Design a globally distributed rate limiting system that enforces per-API-key limits (e.g. 100 req/sec) across multiple geographic regions, where requests can hit any region but the limit must be respected globally, not per-region.
You're scheduling tasks in a worker system under rate limiting. Compare two strategies: prioritizing the highest-cost tasks first versus maximizing the number of tasks completed. What are the trade-offs and when would you pick each?

“This is the kind of question where you can talk for 40 minutes and still feel like you left half of it on the table.”

View Post

Plaid·Software Engineer·Recruiter / HR Screen

Apr 2026

Short screen at Plaid, basically just the one motivational question about why I wanted to work there.

Why do you want to work at Plaid?

“Rambled about fintech infrastructure and open banking for a bit.”

View Post

Plaid·Software Engineer·Onsite - System Design / Architecture

May 2026

Plaid software engineer round where you prep a slide deck on a past project and present it live. The format is pretty specific and the stoic interviewer vibe can mess with your pacing if you're not ready for it.

Walk through a substantial past project end to end using a slide deck: cover the problem, your role, system architecture with a diagram, key technical decisions and alternatives, concrete results, and lessons learned.
For each architectural decision you presented, why did you choose that approach over the alternatives?

“The silence mid-presentation is what gets people.”

View Post

Plaid·Software Engineer·Technical Phone Screen

May 2026

Plaid data engineering screen, one coding/data problem that looked easy on the surface but had a follow-up that would've wrecked me. The first part was clean enough, the second part (many-to-many mapping) is a whole different beast they save for later.

You're given a dataset that maps bank names and identifiers to two ID systems: an internal bank ID and an external bank ID. Write a function that takes this dataset as input and returns a clean mapping from every internal bank ID to its corresponding external bank ID.

“The join logic itself wasn't bad once I clarified the schema upfront, which I actually remembered to do this time.”

View Post

Plaid·Product Manager·Onsite - Product Sense / Strategy

May 2026

Interviewed at Plaid for a product role, got asked the classic 'how would you improve our product' question. Short and focused.

How would you improve the Plaid product?

“Knew this type of question was coming but still fumbled the setup a bit.”

View Post

Plaid·Software Engineer·Technical Phone Screen

May 2026

Plaid SWE interview with a meaty algorithmic problem that had more moving parts than I expected. The core idea isn't too bad but they wanted the full package: proof of correctness, complexity analysis, working code, and tests, all in one shot.

Given an array of item prices in a checkout line, apply a discount rule where each item's discount equals the price of the first subsequent item that costs less than or equal to it. Return the array of final prices and the total savings. Solve in O(n) time, prove correctness, analyze complexity, and write code with tests.

“I recognized the monotonic stack pattern pretty fast, which was a relief.”

View Post

Plaid·Machine Learning Engineer·Technical Phone Screen

May 2026

Interviewed for an MLE role at Plaid and got a data structure question that looked deceptively simple on the surface. Two mappings, one lookup function, and a bunch of edge cases to reason through.

You have two mappings: one from bank codes to canonical institution IDs, and another from institution IDs to one or more bank records. Preprocess these mappings and implement a lookup function that, given a bank code, returns all associated banks. Walk through your data structure choices, time complexities, and how you handle missing codes or duplicate entries.

“My first instinct was to just chain the two lookups at query time and call it done.”

View Post

Plaid·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026

Plaid ML engineer interview focused entirely on designing an evaluation and debugging framework for a production RAG semantic search system in fintech. Five-part deep dive, very systems-thinking heavy, less about coding and more about whether you can reason about quality measurement end to end.

You own a production RAG-based semantic search feature for a fintech product. Design a lightweight but production-ready evaluation and debugging framework covering retrieval quality, answer quality, faithfulness, latency, and cost as offline metrics. What do you measure at each stage and what thresholds would you hold?
What online signals would you track for this system, and how would you run a controlled experiment for a retriever or prompt change without contaminating results?
Where does your benchmark data come from, how do you create labels, and how do you keep the eval dataset fresh without breaking historical comparisons?
How do you integrate evaluation into CI/CD, what are your model-release gates, and what would you alert on in production dashboards?
Search relevance suddenly drops in production. Walk through exactly how you'd localize the failure to a specific pipeline stage, confirm the root cause, apply a fix, and prove the fix actually worked.
Your LLM-as-judge for faithfulness is itself a model. How do you evaluate and trust the judge, and what do you do when the judge disagrees with human labels?
A new retriever improves your offline ranking metric but loses the online A/B test on answer-acceptance. How do you reconcile that, and which signal do you believe?
A regulator asks you to prove that a specific user could not have retrieved a document they weren't entitled to. What in your logging and eval system lets you answer that, and how do you proactively test for permission leaks?
The corpus churns 10% daily but is 90% stable week over week. How do you keep retrieval quality stable across re-indexing, and how would you detect a silent indexing failure on the churning slice?

“This was the core of the whole interview and I spent probably too long on the retrieval side before getting to faithfulness.”

View Post

Plaid·Frontend Engineer·Technical Phone Screen

May 2026

Plaid frontend interview that had me building a small React app with filtering and color-highlighting features. More involved than I expected for a single round, and the follow-up discussion about render performance caught me a bit flat-footed.

Build a small React app that displays a list of items with a real-time filter control and a coloring feature that highlights items based on user input or item attributes. Walk through your component decomposition and state management approach.
What's the difference between controlled and uncontrolled inputs in React, and when would you choose one over the other?
As the item list grows larger, how would you keep rendering performance reasonable in this kind of component?

“I started with a single component and had to refactor mid-session once it got messy, which was not a great look.”

View Post