Katkat

Company

Plaid interview questions

16 practice questions in the style of Plaid's interviews, covering Coding & Algorithms, ML System Design, System Design, Behavioral & Leadership, Software Engineering Fundamentals.

Questions16

3 easy13 medium0 hard

Your progress0/16

Plaid interview questions by the numbers

Last updated

Katkat has 16 Plaid interview questions. The largest topics are Coding & Algorithms (50%), System Design (19%) and Behavioral & Leadership (13%). By difficulty: 19% easy and 81% medium. The most common round is Technical Screen (75%). Frequent concepts include Greedy, Simulation, Cycle Detection and DFS.

Difficulty

  • Easy19% · 3
  • Medium81% · 13

Interview rounds

  • Technical Screen75% · 12
  • Onsite25% · 4

Roles

  • Software Engineer88% · 14
  • Machine Learning Engineer13% · 2

Frequent concepts

  • Greedy19% · 3
  • Simulation19% · 3
  • Cycle Detection13% · 2
  • DFS13% · 2
  • Graph13% · 2
  • Memoization13% · 2

Showing 1–16 of 16 results

  • Calculate the total makespan required to process a queue of ordered jobs across a fixed pool of identical parallel workers.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates proficiency in array processing, algorithm design, use of auxiliary data structures such as monotonic stacks, and formal complexity and correctness reasoning.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Calculate the total number of jobs completed by a given deadline across a multi-stage pipelined system with worker pools. The solution requires simulating stage-by-stage batch execution, tracking wave durations, and enforcing barrier synchronization between stages.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Determine the total number of jobs completed by a single worker executing a sequence of stage-gated tasks before a time limit expires. Tests linear simulation, division/modulo arithmetic, handling of zero-duration and zero-count edge cases, and 64-bit integer safety.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Design a comprehensive evaluation, monitoring, and debugging framework for a production Retrieval-Augmented Generation (RAG) system operating in a high-stakes financial data domain. The candidate must address multi-stage metrics, CI/CD regression testing, and root-cause localization for retrieval vs. generation failures.

    PlaidMachine Learning EngineerML System DesignOnsite
  • This question evaluates a candidate's ability to design large-scale conversational AI systems, covering competencies in distributed system architecture, real-time streaming, stateful multi-turn session management, safety controls, and integration with external tools.

    PlaidSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates competency in ML system design for fraud detection within fintech data-connectivity platforms, testing real-time scoring, feature engineering (including relational/graph signals), label strategy, model training and serving, and operational concerns such as latency, privacy, monitoring, and robustness.

    PlaidMachine Learning EngineerML System DesignTechnical Screen
  • This question evaluates proficiency in data structures and algorithms for building an in-memory service, including efficient lookup/update strategies, expiration handling, limit enforcement, idempotency, concurrency considerations, and time/space complexity reasoning.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's competency in designing geo-distributed, globally consistent rate limiting systems that enforce per-API-key and additional constraints while balancing low-latency request paths and regional failure tolerance.

    PlaidSoftware EngineerSystem DesignTechnical Screen
  • Design a secure, embeddable Pay by Bank frontend widget and supporting backend infrastructure that enables direct bank checkout via an isolated iframe and asynchronous payment processing.

    PlaidSoftware EngineerSystem DesignOnsite
  • Tests candidate self-awareness, career motivation, and adaptability when technical initiatives diverge from expectations due to real-world constraints.

    PlaidSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates project management, technical ownership, estimation, risk management, delegation, and cross-team communication competencies within the Behavioral & Leadership domain for software engineers.

    PlaidSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Tests the candidate's ability to design a high-throughput, memory-bounded rate limiter using bucketed counters instead of unbounded timestamp queues, balancing concurrency, memory overhead, and precision.

    PlaidSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates a candidate's skills in data normalization, deduplication, aggregation, and conflict resolution across multiple JSON data sources, with emphasis on canonicalization of aliases and handling inconsistent mappings.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement a graph traversal to resolve Boolean evaluation chains with negation, detecting cycles, paths leading to cycles, and undefined references in linear time.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Determine if all rules in a chained decision rule set resolve to a terminal 'pass' outcome without cycles or missing references.

    PlaidSoftware EngineerCoding & AlgorithmsTechnical Screen

Plaid interview experiences

All 13 →
  • Two-Hour Screen Ends on a Syntax ErrorPlaid · Software Engineer · Technical Screen · Sep 2026
    Rejected

    I saw online that the first round is usually one hour, but I applied for a backend role and they required two hours back to back, with a 15-30 minute break in the middle. The first hour's question was a common pipeline question from the forum, and it went smoothly. After I finished, the interviewer was very insistent about how to test it, including wanting asserts in Python rather than print stat…

  • A New Rule-Chain Validation Question in the ScreenPlaid · Software Engineer · Technical Screen · Aug 2026

    Unfortunately I ran into a question that wasn't posted here before. This was a few weeks ago, and the interviewer was a woman. Question: Chain Validation The system has a set of validation rules. Each rule has two fields: [rule name, result] The result can be one of three things: "pass" — the rule passes "fail" — the rule fails the name of another rule — meaning the final result of the current ru…

  • Coding Round with a 3-Milestone Pipeline ProblemPlaid · Software Engineer · Technical Screen · Jul 2026

    There were two rounds total: the first was coding, and the second was a project deep-dive where I had to put together my own PPT slides presenting a project. Plaid coding interview experience. The question was about an automation pipeline, with 3 milestones that added conditions progressively. Milestone 1: single worker — calculate how many jobs get completed within the time limit. The pipeline i…

  • Rejected

    My process started with a behavioral interview over the phone, followed by a formal Zoom meeting. The sequence felt structured from the beginning. I didn't run into any major problems during the conversations, but I didn't make it to the final round. The experience ended sooner than I had hoped, and I was disappointed that the last stage never happened for me. I didn't get an offer, though I appr…

  • Plaid Account Executive interview ending with a panel interviewPlaid · Account Executive · Other · May 2026
    Rejected

    The early steps were remote, and the process eventually became a mix of Zoom and in-person conversations. It moved through multiple stages, ending with a panel interview. The atmosphere was smooth across the rounds. Everyone I met was polite and professional, and the staff communicated clearly about what came next. I never felt blindsided by the logistics or the structure, which made it easier to…

More companies