← Back to Directory

PayPal interview notes, page 5 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·Data Scientist·Hiring Manager Screen

May 2026
PayPal data scientist interview that went deep on past work, less a conversation and more an interrogation of every decision I'd made on a project.
  • Walk me through the hardest project on your resume. Why was it difficult, what other approaches did you consider, and why did you go with the solution you chose?

“This is where I got into trouble.”

View Post

PayPal·Data Scientist·Technical Phone Screen

May 2026
PayPal DS interview centered on a crypto feature launch scenario. The whole session was basically one big case study broken into three parts: metrics, diagnosis, and product ideas. Pretty product-heavy for a data science role, which surprised me a bit.
  • PayPal just launched a crypto trading feature. What success metrics would you track after launch?
  • Transaction volume drops shortly after the crypto feature releases. Walk me through how you'd figure out what's causing it.
  • Propose two data-driven improvements to the crypto feature.

“I started with acquisition stuff (new users, activation rate) then moved to engagement and monetization.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

May 2026
PayPal PM interview with a competitive strategy question framed around Amazon. Pretty classic case but the Walmart angle made it feel fresh, or at least fresher than the usual 'how would you improve our product' stuff.
  • You're a PM at Amazon and Walmart is entering your market. How do you respond?

“I started by trying to figure out what 'entering your country' even meant specifically, like which product line, which geography.”

View Post

PayPal·Machine Learning Engineer·Technical Phone Screen

May 2026
PayPal ML Engineer interview that leaned heavier on algorithms than I expected. The coding portion was basically a classic grid search problem dressed up with some extra complexity discussion, which felt a bit out of place for an ML role but whatever.
  • Given a 2D grid of characters and a target word, determine whether the word can be traced through adjacent cells (up, down, left, right) without reusing any cell. Describe your algorithm, walk through the complexity, and talk about any pruning strategies or iterative improvements you'd make.

“I went straight to backtracking and it was fine, but the follow-up about pruning is where I got a little fuzzy.”

View Post

PayPal·Software Engineer·Technical Phone Screen

May 2026
PayPal SWE interview with a graph/traversal problem dressed up in a fun theme. The core challenge was solid even if the wrapping was a bit whimsical.
  • You're given a castle where rooms are named after flowers. Each room contains an instruction pointing to the next room. Write an algorithm to find all rooms that contain treasure.

“The flower-naming thing threw me for a second, felt like a trick.”

View Post

PayPal·Software Engineer·Technical Phone Screen

May 2026
PayPal technical phone screen for a software engineer role, pretty much one long algorithm deep-dive. They wanted more than just working code, they wanted you to justify every design decision and compare approaches out loud.
  • Given an integer array and an integer k, return any k most frequently occurring values. Implement an average-case O(n) time and O(n) space solution using a frequency map and bucket-based grouping, and explain why the approach is linear.
  • Compare the bucket-based O(n) solution with a heap-based O(n log k) approach. When would you prefer one over the other, and what are the memory trade-offs?
  • How would you handle ties when multiple values share the same frequency and you need to decide which ones to include in the top k results?
  • Does your solution correctly handle negative numbers and very large value ranges in the input array?

“The bucket sort angle is the key insight here.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed at PayPal, got asked a business model question that felt more like a case warm-up than a real product question.
  • How does PayPal make money?

“Went through transaction fees, merchant services, interest on balances, that kind of thing.”

View Post

PayPal·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at PayPal for a software engineer role. The whole session was basically one giant question about building a cross-border remittance product, and they wanted you to go deep on pretty much every layer of the stack.
  • Design a cross-border money transfer service where users can send money internationally, with real-time exchange rate quotes, fee calculation, compliance checks, multiple funding and payout methods, transfer tracking, failure handling, and user notifications.
  • How would you handle exchange rate quotes in a way that's consistent for the user but doesn't expose the system to excessive currency risk?
  • Walk through how you'd ensure idempotency across the transfer workflow, especially around retries and third-party payout partner calls.
  • How would you model the data to support transfer status tracking, including intermediate states, failures, and refunds?
  • How would you enforce country-specific transfer restrictions and per-user limits at scale without making every transaction slow?

“This question ate the entire session.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at PayPal with a metrics investigation question framed around Instagram. Pretty standard product analytics territory but the cross-company framing threw me a bit.
  • You're a PM for Instagram and you notice month-over-month retention has dropped 20%. What could be causing this?

“The Instagram framing in a PayPal interview is a little weird and I spent the first 30 seconds just mentally adjusting.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026
PayPal data science interview with a SQL-heavy focus, at least for this round. Two questions, both centered on the same pair of tables about contact syncing. Nothing wild, but the denominator logic on the second one is the kind of thing that trips you up if you're not careful.
  • Given a table of synced contacts and a table of user info, write SQL to calculate the average number of contacts synced per user.
  • Using the same tables, write SQL to find what percentage of all PayPal users have synced at least one contact.

“Straightforward aggregation question.”

View Post