Company
PayPal interview questions
53 practice questions in the style of PayPal's interviews, covering Analytics & Experimentation, Coding & Algorithms, Machine Learning, Statistics & Math, Data Manipulation (SQL/Python), Behavioral & Leadership, System Design, ML System Design, Software Engineering Fundamentals.
12 easy33 medium8 hard
PayPal interview questions by the numbers
Last updated
Katkat has 53 PayPal interview questions. The largest topics are Coding & Algorithms (30%), Analytics & Experimentation (19%) and Data Manipulation (SQL/Python) (17%). By difficulty: 23% easy, 62% medium and 15% hard. The most common round is Onsite (62%). Frequent concepts include Fraud Detection, Aggregations, Arrays and Binary Search.
Topics
- Coding & Algorithms30% · 16
- Analytics & Experimentation19% · 10
- Statistics & Math11% · 6
- Behavioral & Leadership8% · 4
- Machine Learning6% · 3
- System Design6% · 3
- ML System Design2% · 1
Difficulty
- Easy23% · 12
- Medium62% · 33
- Hard15% · 8
Interview rounds
- Onsite62% · 33
- Technical Screen38% · 20
Roles
- Data Scientist72% · 38
- Software Engineer23% · 12
- Machine Learning Engineer6% · 3
Frequent concepts
- Fraud Detection6% · 3
- Aggregations2% · 1
- Arrays2% · 1
- Binary Search2% · 1
- Business Logic2% · 1
- Calibration2% · 1
Most mentioned in interview experiences
- 1.Assess card transactions and plan risk strategy1 report
- 2.Compare WHERE vs HAVING with aggregates1 report
- 3.Decide if a dice-betting game is favorable1 report
- 4.Design elevator scheduling for small building1 report
- 5.Explain differences between Python list and tuple1 report
- 6.Explain past experience and role fit1 report
- 7.Explain unsupervised fraud and evaluation1 report
- 8.Interpret p-values and common pitfalls1 report
- 9.Reduce airport ride cancellations under causal constraints1 report
- 10.Should you play a dice payout game?1 report
Counted from 4 candidate interview experiences on Katkat. How we collect and count
Showing 1–30 of 53 results
Analyze Transactions for Risk and Implement Mitigation Strategies evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Assess HashMap vs ConcurrentHashMap states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenAssess card transactions and plan risk strategy evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Boost User Login Rate: Key Metrics to Monitor states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistAnalytics & ExperimentationOnsiteThis question assesses the ability to design an end-to-end, low-latency machine learning pipeline for detecting account takeover (ATO) in payment transactions, focusing on label noise, feature engineering, and system deployment constraints.
PayPalData ScientistMachine LearningTechnical ScreenThis interview question evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer for Calculate Probability of Heads in Coin Flip Experiment states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistStatistics & MathOnsiteThis question evaluates proficiency in data cleaning, aggregation, and time-series manipulation within the Data Manipulation (SQL/Python) domain, focusing on filtering by group counts and calculating inter-event timing metrics.
PayPalData ScientistData Manipulation (SQL/Python)OnsiteCompare WHERE vs HAVING with aggregates evaluates SQL or pandas logic, joins, grouping, window functions, null handling, edge cases, and validation in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistData Manipulation (SQL/Python)OnsiteThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Compare final, finally, finalize states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates understanding of caching policies and memory/storage hierarchy trade-offs, focusing on how write-back and write-through handle writes, coherence, durability, latency, bandwidth, dirty bits, write amplification, and power-loss risks.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates understanding of basic statistical concepts and numerical computation—specifically population versus sample variance—and tests algorithmic implementation skills, edge-case handling, and complexity reasoning within the Coding & Algorithms domain.
PayPalData ScientistCoding & AlgorithmsTechnical ScreenThis question evaluates understanding of statistical measures and numeric computation, focusing on implementing variance calculations (population vs sample) and considerations for numerical stability.
PayPalData ScientistCoding & AlgorithmsTechnical ScreenThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Contrast TCP vs UDP; detect loss states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates proficiency in basic Python programming, string/text processing, frequency counting and sorting algorithms, reflecting core competencies for data manipulation tasks.
PayPalData ScientistCoding & AlgorithmsOnsiteThis question evaluates understanding of probability theory, expected value computation, risk-neutral decision criteria, and basic Monte Carlo simulation concepts within the Statistics & Math domain, testing both conceptual understanding of discrete probabilistic outcomes and practical application of simulation-based verification.
PayPalData ScientistStatistics & MathOnsiteThis Behavioral & Leadership interview prompt for a Senior Data Scientist evaluates leadership, cross-functional influence, strategic communication, career planning, and team-operating competencies by requesting a data-driven project example, a 3–5 year career outlook, and definitions of effective managers and teams.
PayPalData ScientistBehavioral & LeadershipOnsiteThis question evaluates proficiency in designing distributed, fault-tolerant payment systems with competencies in payments flows, exchange-rate management, compliance and regulatory constraints, transactional integrity, idempotency, scalability, reliability, and observability.
PayPalSoftware EngineerSystem DesignOnsiteThis system design question tests the ability to architect a real-time, low-latency fraud decisioning service that combines deterministic rule engines with machine learning model scores. It evaluates practical understanding of distributed systems trade-offs, feature store design, and safe model/rule deployment on a high-availability critical path.
PayPalSoftware EngineerSystem DesignOnsiteThis question evaluates a Machine Learning Engineer's competency in end-to-end ML system design for real-time payments fraud detection, including labeling under delayed confirmations, handling extreme class imbalance and sampling, feature engineering across behavioral, graph, device and merchant signals, model selection for latency and scale, and production scoring and monitoring architecture. It is commonly asked in the ML System Design category to assess how an engineer balances low-latency decision-making with delayed sparse labels, calibration and threshold trade-offs, operational scalability and resiliency, and drift/adversarial detection, testing both conceptual understanding and practical application.
PayPalMachine Learning EngineerML System DesignOnsiteThis question evaluates a data scientist's experiment-design and statistical-analysis competencies, including cluster-aware randomization, power/sample-size calculation, sequential monitoring, and translating detectable effects into net business impact for a real-time account-takeover prevention rule on a payment platform.
PayPalData ScientistAnalytics & ExperimentationTechnical ScreenThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design and Analyze A/B Test for Cashback Program states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistAnalytics & ExperimentationOnsiteThis problem tests your ability to design a holistic fraud detection strategy by balancing technical model metrics with business-critical operational trade-offs.
PayPalData ScientistAnalytics & ExperimentationTechnical ScreenDesign elevator scheduling for small building evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalData ScientistSystem DesignOnsiteA PayPal data science onsite case asking you to design metrics and a randomized experiment for an optional checkout donation feature on a food-ordering platform. Covers goal and hypothesis framing, a primary/diagnostic/guardrail metric hierarchy with precise definitions, user-level experiment design with power and variance-reduction, confounder/marketplace-bias handling, and a launch decision framework.
PayPalData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates engineering fundamentals, trade-offs, examples, pitfalls, and operational implications in a realistic interview setting. A strong answer for Detect memory leaks in C++ states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerSoftware Engineering FundamentalsTechnical ScreenThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Explain HashMap internals and collisions states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Explain Java volatile semantics states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
PayPalSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates proficiency in SQL and Python data manipulation, covering window functions, join semantics (INNER, LEFT, RIGHT, FULL, CROSS), ranking functions, group and string aggregation, type casting, and building row-wise accumulations in Python, and it falls under the Data Manipulation (SQL/Python) category.
PayPalData ScientistData Manipulation (SQL/Python)OnsiteThis Statistics & Math interview question for a Data Scientist tests understanding of confounding and causal inference in observational data. Candidates must define a confounder, give a concrete non-demographic Uber example identifying the exposure, outcome, and confounder with the direction of bias, and describe at least two mitigation methods along with the assumptions each requires.
PayPalData ScientistStatistics & MathOnsiteEvaluates understanding of Python data structures—specifically lists versus tuples—by probing concepts such as mutability and its implications, high-level performance and memory trade-offs, typical use cases, and hashability for use as dictionary keys.
PayPalData ScientistCoding & AlgorithmsTechnical Screen
PayPal interview experiences
All 3 →- Passed Two Fraud Rounds Despite a Rocky PerformancePayPal · Data Scientist · Onsite · Jan 2026In progress
I applied to a few PayPal positions before Christmas, and two of my applications got recruiter calls. One of them was for a Fraud DS role and moved to interviews fast. The interviewer was someone from the same team based in India, and the interview was at 10:30pm Eastern. They asked about fraud, statistics, SQL, and Python. The second round was with the hiring manager, also based in India, at aro…
- Two Brutal Phone Rounds on SQL, Python, and Airport Causal InferencePayPal · Data Scientist · Technical Screen · Dec 2025
Overall impression: it was really hard. First there was a 15-minute recruiter call. They asked briefly about my current job, why I was looking, and my visa/status situation, then said they'd send an email with the interview process. The phone interviews were two rounds total, each 1 hour. Round 1: coding (including SQL and Python), plus a case study. The SQL question was built around drivers and…
- Three Back-to-Back Onsite Rounds and a SQL StandoffPayPal · Data Scientist · Onsite · Jul 2025
Past experience, resume, explaining the role. Then they asked two case questions. Case 1: 3-level apartment plus 1 basement — find the best way to operate the elevator. Case 2: card risk — what will fraudsters do. Onsite: 3 rounds back-to-back. Risk/fraud scenario. Started off talking about my past experience, then the interviewer explained that this DS role isn't mainly about modeling. He gave m…
More companies
- Meta666
- Amazon653
- Google486
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- xAI53
- Lyft52
- Tesla52
- Other51
