
PayPal ML Engineer interview typically runs 4-5 rounds: HR screen, coding, manager behavioral, system design, final behavioral/technical. It usually takes about 3 weeks and can include extra HR or follow-up rounds.
$142K
Avg. Base Comp
$219K
Avg. Total Comp
4-5
Typical Rounds
3-8 weeks
Process Length
We've seen a clear pattern in PayPal's ML Engineer interviews: they care far more about whether you can build and defend real machine learning systems than whether you can recite theory. Multiple candidates reported that the most important conversations centered on production pipelines, real-time predictions, data drift, and model decay — the kinds of issues that only come up when you've actually shipped ML into a live environment. Even when the coding portion was present, it read as a filter rather than the main event. The deeper signal was whether your past work sounded hands-on, specific, and relevant to fintech-scale problems.
A recurring theme is that PayPal seems to probe breadth first, then quickly pushes into depth. Candidates described ML questions that started general and then moved into loss functions, models, algorithms, and neural networks, alongside applied business cases tied to PayPal's own domain. That mix tells us they want engineers who can connect technical choices to customer-facing outcomes, not just optimize metrics in isolation. Another non-obvious factor is seniority: one candidate received positive feedback yet was still told they wanted someone with more experience, which suggests the bar is heavily weighted toward prior production ownership. Our candidates also consistently mention slow or uneven follow-up, so the process can feel more demanding than polished.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Paypal process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Paypal
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| String Shift | |
| Find the Missing Number | |
| P-value to a Layman | |
| Nearest Common Ancestor | |
| Bank Fraud Model | |
| Precision and Recall | |
| Duplicate Rows | |
| Assumptions of Linear Regression | |
| Priority Queue Using Linked List | |
| Variable Error | |
| String Mapping | |
| Sort Strings | |
| Bias vs. Variance Tradeoff | |
| Most Repetition | |
| Unsafe Content ML Design | |
| Data Preparation for Imbalanced Data | |
| Finding The Mode | |
| Poker Pair | |
| Overfit Avoidance | |
| User Event Data Pipeline | |
| String Palindromes | |
| Descending Alphanumeric Sorting | |
| Mouse Search | |
| Shortest Path Algorithms | |
| Acquisition Threshold | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Pool Matching | |
| Generative AI Privacy |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with an initial HR/recruiter screen to discuss your background, role fit, and overall experience. In one experience, there was even a second HR conversation later in the process before the technical rounds resumed.
This round focuses on data structures and algorithms, with some interviews also including intermediate SQL and basic Python. Candidates reported questions like LeetCode #4 (median of two sorted arrays), and the interview may include a resume walkthrough and brief self-introduction in multiple languages.
A manager-led discussion digs into your past machine learning work, production experience, and depth of understanding. Interviewers ask detailed questions about your resume projects and expect concrete examples of real-world ML systems you've built or supported.
This round centers on designing scalable machine learning systems, especially for real-time predictions. Topics include building ML pipelines in production and handling issues like data drift and model decay.
The last round is a combined discussion with the manager and team that blends behavioral and technical evaluation. Candidates may be asked broader ML questions or a business-case style problem tied to PayPal's data science use cases.