← Back to Directory

PayPal

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·Data Scientist·Technical Phone Screen

Jul 2026
PayPal data scientist round focused entirely on a streaming anomaly detection problem. Pretty deep systems-thinking question for a DS role, felt more like a software engineering interview at points.
  • Design and implement a streaming login event processor that fires an alert whenever a user logs in from 4 or more distinct devices within any 10-minute sliding window. The function consumes a time-ordered stream of (user_id, timestamp, device_id, success) events. Walk through your data structures, eviction strategy, how you handle late-arriving events (up to 30 seconds), and the exact alerting semantics at window boundaries. Provide pseudocode.

“This was the whole interview basically.”

View Post

PayPal·Software Engineer·Technical Phone Screen

Jul 2026
PayPal software engineer interview with a deep dive into Java internals. The question felt more like a grad-school exam than a typical coding screen, which I wasn't fully prepared for.
  • Walk me through how HashMap works internally in Java, including the underlying data structures and how the implementation changed across different Java versions.
  • Beyond separate chaining, what other collision resolution strategies exist for hash maps, and what are the real trade-offs between them in terms of time complexity, memory usage, and cache performance?

“I knew the basics: array of buckets, linked list chaining, load factor.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jul 2026
Got a take-home style SQL case for a Data Scientist role on PayPal's fraud side. The problem was dense, like genuinely one of the harder SQL prompts I've seen in an interview context, and it tested whether you actually understand window functions and time-based filtering or just know how to write basic joins.
  • You're on a fraud detection team. Write a single SQL query that identifies candidate account takeover events in the last 7 days. A candidate event requires: the user's first successful login from a new device or new IP in the prior 30 days, followed within 2 hours by a transfer over $500 to a first-time recipient. Exclude users whose accounts are less than 7 days old at login time. If multiple transfers match the same login, keep only the earliest. Return specific output columns including a reason code, and at the end recommend indexes to support the query on a PostgreSQL-like warehouse.

“This one took me a while to decompose.”

View Post

PayPal·Machine Learning Engineer·Onsite - System Design / Architecture

Jul 2026
PayPal ML Engineer interview that went deep on fraud detection architecture. One big open-ended question that basically asked me to defend an entire research agenda in real time. Not a vibe check, more like a technical thesis defense.
  • How do you see large language models fitting into fraud detection, both near-term and long-term? Walk through the tradeoffs versus traditional supervised models across dimensions like data modalities, feature engineering, latency, interpretability, adversarial robustness, privacy, and compliance. Then propose a hybrid architecture and an evaluation plan to justify actually adopting it.

“This question is basically a full system design plus a research proposal crammed into one.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jul 2026
PayPal fraud data science interview that was basically a deep dive on p-values and experimentation. More rigorous than I expected for what was framed as a stats refresher.
  • Give a precise definition of a p-value. What does it actually mean, and what are common misconceptions about what it does NOT mean?
  • You run an A/B test on a new friction step like an extra OTP verification and get p=0.03. What can you actually conclude, and what else do you need before making a decision?
  • What are at least four common pitfalls when using p-values in practice? Think about things like multiple testing, peeking at results early, p-hacking, and so on.
  • How would you adjust your analysis when testing across many regions or segments, when outcomes are rare and delayed like chargebacks that arrive weeks later, or when randomization isn't clean due to spillover effects?

“I started with the textbook definition and then fumbled a bit trying to articulate the 'does not mean' part without sounding like I was reciting a Wikipedia warning label.”

View Post

PayPal·Software Engineer·Technical Phone Screen

Jul 2026
PayPal technical phone screen for a software engineer role, pretty deep on C++ internals. One question, but they really wanted you to know the details, not just the surface answer.
  • In C++, if you write `std::string a = "123"; std::string b = a;`, what operations are invoked under the hood? Walk through copy construction vs move semantics, how memory allocation typically works, Small String Optimization, and why the standard doesn't mandate copy-on-write.

“I knew the basics but stumbled a bit on SSO.”

View Post

PayPal·Software Engineer·Technical Phone Screen

Jul 2026
Technical phone screen for a software engineer role at PayPal, focused pretty heavily on Java concurrency internals. One question, but it went deep fast.
  • What does the volatile keyword actually guarantee in Java's memory model? Walk through visibility, happens-before ordering, instruction reordering restrictions, and where volatile falls short compared to synchronized or locks.

“I started okay on visibility, said something about flushing to main memory and every thread reading fresh values.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

Jul 2026
PayPal PM interview, one strategy question about the Honey acquisition. Short and to the point, not much else to say about the format.
  • Why did PayPal acquire Honey?

“I fumbled the opening a bit.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jul 2026
PayPal data scientist interview that leaned pretty hard into SQL fundamentals, specifically around aggregation and filtering. The question felt deceptively simple at first but there were a few layers they wanted you to work through.
  • Write a query to find merchants with a chargeback rate above 0.5% over the last 30 days using HAVING, and explain why you can't use WHERE for this.

“I knew the answer but fumbled explaining the WHERE vs HAVING distinction out loud.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jul 2026
PayPal data scientist experimentation round had a stats check that felt more like a quiz than a conversation. Quick binomial probability stuff, nothing that required much back-and-forth.
  • A fair coin is flipped 10 times. Calculate the total number of possible outcome sequences, the probability of exactly 3 heads, and the probability of at most 3 heads.

“Multi-part but not actually hard once you remember it's just binomial.”

View Post

PayPal interview FAQ

What rounds are in the PayPal interview?

Candidates most often report a technical phone screen (60 write-ups), a system design round (11), a product sense round (9) and a hiring manager screen (3).

What does the PayPal technical phone screen cover?

Across 60 technical phone screen write-ups, the most tagged question topics are Product Analytics & Metrics (67 questions), A/B Testing & Experimentation (46) and Technical Trade-offs (46).

What is asked in the PayPal system design round?

Across 11 system design write-ups, the most tagged question topics are System Design (15 questions), Technical Trade-offs (13) and Data Modeling (4).