Plaid Software Engineer Phone Screen Questions
5+ questions from real Plaid Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Plaid Phone Screen round test?
The Plaid phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Plaid Software Engineer Phone Screen Questions
## Problem A bank has undergone several mergers. Each merger maps old account IDs to new ones. Given a list of mergers `[(old_id, new_id)]` applied in sequence and a query account ID, return the final canonical ID it resolves to. Mergers may chain: if A -> B and B -> C, then A ultimately resolves to C. ```python def resolve_bank_id( mergers: List[Tuple[str, str]], query_id: str ) -> str: ... def resolve_all( mergers: List[Tuple[str, str]], queries: List[str] ) -> List[str]: ... ``` **Example:** ``` mergers = [("ACC001", "ACC002"), ("ACC002", "ACC999"), ("ACC050", "ACC999")] resolve_bank_id(mergers, "ACC001") -> "ACC999" resolve_bank_id(mergers, "ACC050") -> "ACC999" resolve_bank_id(mergers, "ACC999") -> "ACC999" # no further mapping ``` ## Approach Model as a Union-Find (Disjoint Set Union) structure. Each `merge(old, new)` is a union operation with path compression. ## Follow-ups 1. How does path compression in Union-Find achieve near-O(1) amortized `find`? 2. What if a merger maps one new ID to multiple old IDs simultaneously? 3. How would you detect and handle circular mergers (A -> B -> A)? 4. How would you audit which original IDs all map to the same canonical ID?
## Problem Design a coupon application system for an e-commerce checkout. Coupons have types: `percent_off`, `fixed_off`, `buy_x_get_y_free`, and `category_discount`. Rules: - At most 2 coupons can be applied per order. - Coupons cannot reduce the price below $0. - Some coupons are exclusive (cannot stack with others). Implement: - `apply_coupons(order, coupon_codes) -> CheckoutResult` ```python class CouponSystem: def apply_coupons( self, order: dict, # {"items": [{"id", "category", "price", "qty"}]} coupon_codes: List[str] ) -> dict: # {"original": float, "discount": float, "final": float, "applied": List[str]} ... ``` **Example:** ``` order = {"items": [{"id":"i1","category":"electronics","price":200,"qty":1}]} coupons = ["SAVE10PCT", "TECH20"] # SAVE10PCT: 10% off entire order # TECH20: $20 off electronics category apply_coupons(order, coupons) -> {"original": 200, "discount": 40.0, "final": 160.0, "applied": ["SAVE10PCT","TECH20"]} ``` ## Follow-ups 1. How do you determine the optimal order to apply coupons to maximize the discount? 2. How do you enforce the exclusivity constraint when 3+ coupons are submitted? 3. How would you validate coupon expiry and single-use restrictions? 4. How do you handle a `buy_x_get_y_free` coupon across multiple cart items?
Plaid SWE Phone - Group Transactions
## Problem Group financial transactions by merchant, category, or date and compute aggregates for each group. ## Likely LeetCode equivalent No direct unambiguous LC equivalent. ## Tags hash_table, arrays, design
## Problem Given a loan principal `P`, annual interest rate `r` (as a decimal), and term in months `n`, compute the full amortization schedule - the breakdown of each monthly payment into principal and interest portions. ```python def amortization_schedule( principal: float, annual_rate: float, months: int ) -> List[dict]: # Returns list of {month, payment, principal_paid, interest_paid, remaining_balance} ... ``` **Example:** ``` P=10000, annual_rate=0.06, months=12 Monthly rate = 0.06/12 = 0.005 Monthly payment = P * r / (1 - (1+r)^-n) = 10000 * 0.005 / (1 - 1.005^-12) = 860.66 Month 1: interest = 10000 * 0.005 = 50.00 principal = 860.66 - 50.00 = 810.66 balance = 10000 - 810.66 = 9189.34 ... Month 12: balance rounds to 0.00 ``` ## Follow-ups 1. How do you handle rounding errors so the final balance is exactly $0.00? 2. Extend to support extra monthly payments that reduce the remaining principal. 3. How would you compute the total interest paid and the effective APR if fees are included? 4. Model a variable-rate loan where the interest rate changes every 12 months.
## Problem Settle debts or transactions among a group with minimum number of transfers, a classic graph debt-reduction problem. ## Likely LeetCode equivalent LC 465 - Optimal Account Balancing (>80% confident) ## Tags graph, backtracking, greedy
What to Expect in the Plaid Phone Screen Round
The Plaid Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 5+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Plaid show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Plaid typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Plaid Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 5 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access