PayPal Data Scientist candidates report practical SQL and Python work, statistics and experimentation discussions, modeling or ML design, and close questioning about projects and assumptions.
$227K
Avg. Base Comp
$334K
Avg. Total Comp
3-4 rounds
Typical Rounds
3-5 weeks
Process Length
PayPal Data Scientist interviews reported here combine applied technical work with discussions of how candidates reason through product and business decisions. SQL is the most consistently concrete technical theme. Candidates describe live or HackerRank-style exercises involving joins, aggregations, subqueries, window functions, percentile bucketing, and messy data such as null IDs, string dates, or leading spaces. Python also appears in coding screens, including pandas/numpy data-cleaning and aggregation tasks.
Statistics and experimentation are another recurring area. Reported prompts include confidence intervals and p-values, A/B-test design, switchback testing for a payment-method change, and other statistical scenarios. Prepare to state assumptions, explain tradeoffs, and connect an experiment or metric choice to the business question rather than only naming a technique.
Later conversations may shift toward project depth and practical modeling. Candidates report being asked to defend modeling and feature decisions, handle a classification setting with missing labels, discuss a business problem, or walk through an ML system from data preparation through deployment. Hiring-manager and behavioral discussions have covered favorite projects and working with non-technical stakeholders. Individual sequences vary, but these reports support preparing for both hands-on analysis and clear communication about judgment.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Paypal process.
Overall, the conversations were more collaborative than I expected. I felt most confident during the technical and case study rounds because they closely matched the kind of credit risk analytics and client-facing work I do every day. The biggest surprise was how much the interviewers cared about my thought process rather than arriving at the "perfect" answer—they often dug into why I made certain assumptions or how I would handle ambiguity. The behavioral interview was where I started sweating a bit. Instead of standard questions, they challenged me with situations around influencing stakeholders without authority, handling disagreements, and learning from mistakes. It felt less like reciting prepared stories and more like having an honest conversation, which forced me to think on my feet. Looking back, that was probably the most valuable part of the entire process.
Questions asked: build a model for detecting credit risk
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Paypal
Write a query to get the total three-day rolling average for deposits by day
| Question | |
|---|---|
| Merge Sorted Lists | |
| String Shift | |
| Paired Products | |
| Over-Budget Projects | |
| Swipe Precision | |
| Find the Missing Number | |
| Third Purchase | |
| Bank Fraud Model | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Variable Error | |
| Nearest Common Ancestor | |
| Sort Strings | |
| String Mapping | |
| Precision and Recall | |
| Finding The Mode | |
| Target Indices | |
| Poker Pair | |
| Priority Queue Using Linked List | |
| Success Measurement | |
| Assumptions of Linear Regression | |
| Duplicate Rows | |
| Testing Price Increase | |
| Nightly Job | |
| Descending Alphanumeric Sorting | |
| Most Repetition | |
| Unsafe Content ML Design | |
| Mouse Search |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter or phone conversations about background, interest in PayPal, prior machine-learning work, and sometimes an overview of the process. A hiring-manager discussion may also focus on the team, the role, projects, and behavioral examples.
Candidates report live or HackerRank-style coding that can include SQL joins, aggregations, subqueries, window functions, percentile tasks, and data cleaning. Python, pandas/numpy, or an algorithmic problem may also appear, with reasoning and communication assessed alongside the solution.
Candidates report statistics, A/B testing, experiment-design, and product-analytics discussions. Examples include confidence intervals, p-values, switchback testing, and explaining assumptions or potential bias in an ambiguous business scenario.
Candidates report modeling or business-case conversations, a take-home follow-up, ML system design, and deep dives into past projects. Be prepared to explain the rationale for technical decisions, feature choices, stakeholder framing, and what you would change.
