PayPal Interview Questions — Page 8

PayPal·Software Engineer·Technical Phone Screen

Jun 2026

PayPal coding screen, one question, pretty standard binary search territory. Nothing wild but the O(log n) constraint makes it clear they want you to actually think about complexity and not just brute force it.

Given a sorted array of distinct integers and a target value, return the index of the target if found. If not found, return the index where it would be inserted to keep the array sorted. Your solution must run in O(log n) time.

“Classic binary search but with a small twist at the end.”

View Post

PayPal·Software Engineer·Technical Phone Screen

Jun 2026

Got a coding question from PayPal that looked clean on the surface but had enough edge cases to slow me down. Pretty standard technical screen format.

Given an encoded string in the format k[encoded_string] where the substring inside the brackets is repeated k times, write a function to decode it. Assume the input is always valid and digits only appear as repeat counts.

“I went straight for a stack-based approach and it mostly worked, but I fumbled on nested brackets for longer than I should have.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026

PayPal data scientist interview that leaned heavily into causal inference theory. One meaty question that covered a lot of ground, felt more like a stats exam than a typical DS screen.

Using Uber or Uber Eats data as context: define confounding in causal inference, give a concrete Uber-specific example with a clear treatment, outcome, and confounder, explain the direction of bias, and describe at least two methods to detect or mitigate confounding including what assumptions each requires.

“This question has three parts and I kind of fumbled the transition between them.”

View Post

PayPal·Data Scientist·Onsite - Cross-functional / Panel

Jun 2026

PayPal fraud team interview for a Decision Scientist role on the Chicago ATO side. The whole thing was a dense stakeholder/BI case that covered dashboards, exec comms, and tooling debates all at once. More to unpack than I expected going in.

Walk through a 30/60/90 day plan for your first quarter on a fraud team, with specific deliverables at each milestone.
Define five core dashboard tiles for an account takeover monitoring dashboard, including the exact metric formulas and the right denominators.
Write a short executive update (around 150 words) to cross-functional stakeholders explaining a proposed fraud rule change, its expected impact, and the assumptions behind it.
Someone pushes back saying SQL is all you need for analysis. How do you decide when to use Python instead, and what governance practices do you put around code-based work to keep it trustworthy?

“I've done 30/60/90 questions before but never with this level of specificity demanded.”

View Post

PayPal·Data Scientist·Technical Phone Screen

Jun 2026

PayPal data scientist interview with a meaty unsupervised learning scenario that made me realize how much I'd been leaning on labeled data my whole career. No softball warmups, just straight into a hard problem.

You have millions of historical transactions with no fraud labels. Which unsupervised methods would you use to surface suspicious activity, and how would you evaluate the model's performance without ground truth?

“This one hit different because evaluation without labels is genuinely hard and I spent too long on the modeling side before they nudged me toward the second half.”

View Post

PayPal·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

PayPal PM interview with a classic product sense question about unmet user needs. Not a lot of context to go on, but the question itself is a meaty one that can go sideways fast if you're not careful about scoping.

Identify a user need that the market currently isn't addressing. How would you go about validating a solution for it?

“Two-parter and the second half is where people fall apart.”

View Post

PayPal·Data Scientist·Hiring Manager Screen

Jun 2026

PayPal data scientist interview that leaned heavily on past experience in risk and fraud analytics. The main ask was basically a structured career walkthrough with a strategic twist at the end about why you'd want a role that's lighter on modeling.

Walk me through two or three past projects in risk or fraud analytics where you owned key decisions, moved measurable metrics, and had to navigate real trade-offs.
This role is less focused on modeling and more on analytics and strategy. Given your data science background, how does that shift align with what you're actually good at and what you want to be doing?

“This is the kind of question where you think you're ready and then halfway through the second project you realize you've been vague about what you actually decided versus what the team decided.”

View Post

PayPal·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Did a system design round at PayPal for a software engineer role. The interviewer was pretty helpful with hints throughout, so it didn't feel like I was drowning the whole time.

Design a fraud detection service for a payment system.

“The interviewer dropped hints along the way which made it more of a conversation than an interrogation.”

View Post

PayPal·Machine Learning Engineer·Technical Phone Screen

Jul 2026

PayPal ML engineer interview with a coding round that leaned heavier on algorithms than I expected. The question was classic sliding window territory but they pushed into streaming territory pretty fast, which is where things got interesting.

Given a binary array and an integer k, find the length of the longest contiguous subarray you can get by flipping at most k zeros to ones. Walk through an efficient algorithm, its time and space complexity, and how you'd adapt the approach for a streaming data source.

“The base sliding window solution came to me pretty quickly, two pointers, track zero count, shrink left when zeros exceed k.”

View Post

PayPal·Data Scientist·Take-home Assignment

Jul 2026

PayPal DS take-home before onsite: you get a dataset, analyze an A/B test, and present slides. The scope was wider than I expected and the noncompliance angle tripped me up a bit.

What primary metric and guardrail metrics would you use to decide whether to ship the experiment?
Walk through the statistical tests and confidence intervals you would run, and what sanity checks you would perform before trusting any results.
How would you handle the fact that some assigned users never actually saw the new experience, and which estimand would you report?
How would you investigate heterogeneous treatment effects across platform, country, and user type without running into p-hacking issues?
What would your slide deck look like, and how would you communicate uncertainty and next steps to a PM or engineering audience?

“I went with orders_7d as primary and flagged revenue_7d and support_tickets_7d as guardrails.”

View Post