← Back to Directory

PayPal interview notes, page 2 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

Apr 2026
Interviewed for a data science role at PayPal, got a product analytics question about Venmo that seemed straightforward but had more layers than I expected.
  • What could explain a decline in the number of Venmo users linking their bank accounts?

“I jumped straight to trust and security concerns, which felt obvious in retrospect.”

View Post

PayPal·Data Scientist·Onsite - Behavioral / Leadership

Apr 2026
Behavioral loop for a Data Scientist role at PayPal. Four questions, all the classic ones you'd expect, but the follow-ups had some teeth. Nothing shocking, but I left feeling like I could've been sharper on a couple of them.
  • Walk me through a project you owned end-to-end. What was your role and what did you actually move?
  • Where do you want your career to go over the next few years?
  • What does a good manager look like to you, and can you give an example of a time you dealt with misalignment or friction with someone above you?
  • What makes a team work well, and how do you personally contribute to that kind of culture?

“This is the one I over-prepared for and somehow still fumbled the impact part.”

View Post

PayPal·Product Manager·Recruiter / HR Screen

Apr 2026
Applied for a PM role at PayPal and got asked the classic motivation question. Not much else to report here.
  • Why do you want to work at PayPal?

View Post

PayPal·Software Engineer·Onsite - System Design / Architecture

Apr 2026
PayPal system design round, one meaty question about caching policies that ended up going deeper than I expected. Not a bad experience but I definitely left some points on the table.
  • Compare write-back and write-through caching policies. How does each handle writes, cache coherence, durability, latency, and bandwidth? Where would you use each, and what are the trade-offs around dirty bits, write amplification, and power loss risk?

“I started with the basics fine: write-through flushes to storage on every write so you never lose data but you pay the latency cost every time, write-back only writes to the backing store when the cache line is evicted so it's faster but you're sitting on dirty data that disappears if power goes out.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Apr 2026
PayPal data scientist interview focused heavily on A/B testing fundamentals and causal inference. Felt like a gauntlet of stats knowledge compressed into one session. Solid prep on experimentation workflows is non-negotiable for this role.
  • What does a p-value actually represent, and how would you explain it to someone without a stats background?
  • Define Type I and Type II errors and explain the practical consequences of each in a product experimentation context.
  • Walk me through the full end-to-end workflow for running an experiment at a product company, from hypothesis to decision.
  • What is Simpson's paradox and how would you go about detecting it in practice?
  • How would you choose primary and secondary metrics for an A/B test on a payments feature?
  • Name two causal inference approaches you'd use when you can't run a randomized experiment, and explain when each is appropriate.

“I gave a technically correct answer but immediately second-guessed my wording mid-sentence.”

View Post

PayPal·Software Engineer·Recruiter / HR Screen

Apr 2026
Pretty standard HR screen for a software engineer role at PayPal. Mostly behavioral and motivational stuff, nothing technical. Felt more like a vibe check than a real interview.
  • Walk me through your previous project experience.
  • Why are you interested in working for a foreign company?
  • Give a brief self-introduction in English.
  • How do you think about your career development going forward?
  • What draws you to PayPal specifically?
  • Do you have any questions for us?

“I rambled a bit trying to cover too many projects at once.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Apr 2026
Interviewed for a Data Scientist role at PayPal and got a pure coding question about implementing variance from scratch in Python. No libraries allowed, which was a bit of a curveball for a DS interview rather than a pure SWE one.
  • Write a Python function to compute the variance of a list of numbers without using any external libraries like NumPy or pandas. Discuss your assumptions around population vs. sample variance, edge cases like empty or single-element lists, and the time and space complexity of your solution.

“Spent the first minute just asking clarifying questions, which I think saved me.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Apr 2026
Interviewed for a Fraud Data Scientist role at PayPal. The questions were heavily domain-focused, covering fraud taxonomy, model evaluation, and end-to-end system design. More technical depth required than I expected for a DS role.
  • What are the common fraud types in payments? Define each and give an example.
  • Walk through how an account takeover works end-to-end, from credential acquisition to monetization. What signals would you use to detect it?
  • What's the difference between first-party and third-party fraud? Why does ground truth quality differ between them, and how can mislabeling bias your model?
  • How do you measure whether a fraud model is actually working in production? Give at least five metrics, explain the precision-recall tradeoff, and describe how you'd pick a decision threshold.
  • Design a fraud strategy from scratch with a target of having something useful deployed within six to eight weeks. Cover data, modeling, decisioning, monitoring, and iteration.

“Seemed like a warmup but they wanted crisp definitions, not a brain dump.”

View Post

PayPal·Data Scientist·Onsite - Behavioral / Leadership

Apr 2026
PayPal senior DS onsite, behavioral and leadership focus. Four questions across influence, career direction, manager expectations, and team dynamics. Nothing too surprising but the questions had more depth than I expected from a behavioral round.
  • Tell me about a project where your analysis actually changed a product or engineering decision. What was unclear at the start, what did you do, and what shifted as a result?
  • Where do you see your career going over the next few years in terms of scope, skills, and the kind of impact you want to have? How does this role fit into that?
  • What does a good manager look like to you in a data science or analytics org? What do you need from them, and what do you bring to that relationship?
  • Describe what a strong team looks like to you. Think about how the team makes decisions, sets technical standards, and handles relationships with stakeholders.

“This is the one I fumbled a bit.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Apr 2026
PayPal data scientist interview with a product scenario focused on login rate optimization. The question was open-ended and metric-heavy, which I didn't fully anticipate going in.
  • You're the product data scientist responsible for improving daily login rate. What metrics would you define, monitor, and prioritize, and how would you build a dashboard or report around them?

“I started with the obvious stuff like DAU and login frequency but then kind of stumbled when they pushed on leading vs lagging indicators.”

View Post