← Back to Directory

PayPal interview notes, page 6 of 10

Large Enterprises

Most of these PayPal write-ups come from Data Scientists (53), then Software Engineers (22) and Product Managers (10). The most reported rounds are the technical phone screen (60), the system design round (11), the product sense round (9) and the hiring manager screen (3).

91 interview notes · updated Jul 2026

PayPal·Software Engineer·Technical Phone Screen

Jun 2026
PayPal software engineer interview with a graph/union-find problem that looks deceptively simple until you realize brute-force swapping won't cut it at scale.
  • Given a string and a list of index pairs where you can swap characters any number of times, return the lexicographically smallest string possible.

“My first instinct was to just simulate the swaps greedily and I wasted probably five minutes going down that path before realizing it doesn't work.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026
Did a technical screen for a Data Scientist role at PayPal and got a coding question on computing variance from scratch in Python. Pretty focused session, no fluff.
  • Given a Python list of numbers, implement a function to compute its variance without using numpy or pandas. Be prepared to discuss population vs sample variance, edge cases, and complexity.

“I jumped straight into the sample variance formula without asking which type they wanted, and the interviewer had to stop me to clarify.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026
A product analytics case for a data scientist role at PayPal, structured around diagnosing a sudden drop in shopper order acceptances on a grocery delivery marketplace. The question was thorough and multi-part, covering funnel decomposition, root cause trees, metric slicing, artifact detection, and mitigation proposals. Pretty intense for a single question.
  • A grocery delivery marketplace sees order acceptances by shoppers drop by roughly two-thirds on a Sunday afternoon compared to baseline. Walk through how you'd diagnose this: define the metric precisely, build a root-cause tree across shopper supply, customer demand, and platform/merchant systems, list the metrics and slices you'd check first, distinguish a real drop from a logging artifact, and propose mitigations and an experiment to validate your leading hypothesis.

“This was a beast of a question.”

View Post

PayPal·Data Scientist·Executive / Final Round

Jun 2026
Final round behavioral interview for a Data Scientist role at PayPal. Two-part question that blended a classic stakeholder communication ask with a live mini-case. Felt like a reasonable interview but the time pressure on the mini-case was real.
  • Walk me through a time you had to convince stakeholders using data. And as a follow-up mini-case: a critical KPI dropped 20% overnight. What do you do in the first hour?

“The stakeholder part I handled fine, structured it as situation-action-result and talked about a time I pushed back on a product decision using funnel data.”

View Post

PayPal·Software Engineer·Onsite - System Design / Architecture

Jun 2026
PayPal system design round for a software engineer role. One meaty question about cross-border payments that had a lot more moving parts than I expected going in.
  • Design a cross-border money transfer service like Remitly, accounting for country-specific transfer restrictions and real-time exchange rate lookups.

“I started with the happy path and got pretty far before they pushed on the compliance angle.”

View Post

PayPal·Software Engineer·Technical Phone Screen

Jun 2026
PayPal software engineering interview that went pretty deep into networking fundamentals. The TCP/UDP question felt like it had multiple layers and I wasn't sure how far they wanted me to go.
  • Compare TCP and UDP across reliability, ordering, congestion control, connection setup, and overhead. Then explain how TCP detects packet loss and triggers retransmission, covering timeouts, duplicate ACKs, fast retransmit, and selective acknowledgments.

“Started strong on the basic TCP vs UDP stuff, reliability and ordering are easy, but then they pushed into congestion control and I got a bit fuzzy.”

View Post

PayPal·Data Scientist·Onsite - System Design / Architecture

Jun 2026
System design round at PayPal for a Data Scientist role. The question was about elevator control policy, which I was not expecting at all for a DS position. Felt more like a software engineering interview honestly.
  • Design a control policy for a single elevator serving four stops (basement, floors 1 through 3). Walk through what you're optimizing for, the physical constraints, what state the controller tracks, how it decides the next stop, the data structures involved, and how you'd simulate and compare different scheduling strategies.

“This was a lot to unpack.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at PayPal with a product analytics case set in the Uber Eats context. One question, pretty focused on diagnosing a metric drop.
  • You're a PM for Uber Eats. Cart conversion has dropped by 10% over the last 3 months. How would you go about finding the root cause?

“I started with segmentation which felt right but I jumped to hypotheses way too fast without really confirming the metric definition first.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026
PayPal data scientist interview, technical phone screen focused on SQL. One meaty question about tracking navigation sequences, which honestly took me longer to work through than I expected.
  • Given a table of page visit events with user, page, and timestamp columns, write SQL to find users who visited page A and then page B (in that order) within the same calendar day, never visited page C that day, and completed the A then B sequence more than once.

“The 'more than once' part is what got me.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026
PayPal data scientist interview focused entirely on A/B testing theory and causal inference. The questions were layered and assumed you already know the basics, so if you're rusty on anything beyond p-values, it gets uncomfortable fast.
  • What does a p-value actually represent in the context of a running experiment?
  • Define Type-I and Type-II errors and give a business example for each.
  • What is Simpson's Paradox and why is it dangerous when reading experiment results?
  • How would you go about selecting primary, secondary, and guardrail metrics for an experiment?
  • If you can't randomize users into treatment and control groups, what causal inference approaches would you use?

“I gave the textbook answer about probability under the null hypothesis and they pushed back asking what that means practically for a product decision.”

View Post