PayPal Software Engineer interview typically runs 4–5 rounds: online assessment, recruiter screen, Karat or HackerRank live coding, and a final loop with technical, system design, and behavioral interviews. The process takes roughly 2–5 weeks and is distinguished by follow-up-heavy coding questions and full-stack system design tied to payments and scalability.
$121K
Avg. Base Comp
$220K
Avg. Total Comp
4-5
Typical Rounds
2-5 weeks
Process Length
What strikes us most across these experiences is the gap between what candidates expect and what they actually encounter. Multiple candidates reported going in prepared for a heavy LeetCode grind, only to find that the process leaned heavily on communication and reasoning — explaining every step, handling follow-up constraints, and talking through design tradeoffs in real time. One candidate who received an offer specifically noted that the interviewers cared a lot about how they explained their thinking, and that getting to a working answer wasn't enough — interviewers pushed on edge cases and code modifications after the initial solution. That pattern shows up repeatedly across both offer and no-offer outcomes, and it connects directly to what PayPal actually builds: payment systems where correctness, consistency, and failure handling matter more than raw algorithmic speed.
The technical scope is broader than a typical SWE loop, and that breadth catches people off guard. We've seen questions span classic DSA (trees, heaps, BFS, two-pointers), Java and OOP fundamentals, multithreading and concurrency, web concepts like HTTP GET vs. POST, SQL and database design, and system design ranging from Dropbox-style storage to notification systems to full browser-to-backend architecture. The Karat rounds in particular add a format-specific layer of pressure — one candidate described the interviewer pushing them to keep narrating even during moments they needed to think, making an otherwise manageable problem feel intense. Candidates going through Karat should treat the talk-and-type-simultaneously format as its own preparation target, separate from the problem difficulty itself.
The process is also genuinely inconsistent across teams and levels. Some candidates saw a lightweight two-round loop; others went through a four-hour final day covering Problem Solving, Design Logic, System Design, and Work Practices back to back. Communication after interviews was a recurring frustration — several candidates reported multi-week delays or being ghosted entirely after completing technical rounds. Go in knowing the experience may vary by team, but the underlying bar stays consistent: solid fundamentals, clean verbal reasoning, comfort with at least a surface-level distributed systems or payment-adjacent design conversation, and a clear answer to why PayPal specifically.
Synthetized from 16 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.
The hardest part for me was realizing how lightweight the process actually was. I started with an online assessment on HackerRank, which was 90 minutes and had a Java/OOPs question plus two LeetCode-style problems, one easy and one medium. After that I got contacted by HR and had a recruiter call that was mostly standard HR questions. The technical part stayed pretty straightforward: in one round I was asked two DSA questions, one on trees and one on stacks, and the stack one was the classic next greater element type. In another round, the questions were medium LeetCode level again, including a two-pointer problem and a question around HTTP requests and API basics, so it felt like they wanted to see both coding fundamentals and a little practical backend awareness.
The most complete process I went through was OA -> 15 minute recruiter screen -> two 45 minute technical rounds on the same day. One tech round was on HackerRank with an engineer and was very algorithmic, including a heap/priority queue question involving stones. The other was more of a resume grill with an engineering manager, plus a simple verbal system design discussion and behavioral questions. Both interviewers were helpful and guided the conversation, and there was even a short one-minute introduction at the start. Overall it felt chill and not overly intense, but you still had to communicate clearly and get through the test cases cleanly. I ended up receiving an offer in my process, while another ended with no offer, so I’d say the bar was reasonable but they were looking for solid fundamentals and clear explanation more than anything flashy.
Prep tip from this candidate
Be ready for medium LeetCode problems in the usual patterns they used here: two pointers, trees, stacks/next greater element, and heap/priority queue. Also review Java OOP basics, HTTP/API fundamentals, and be prepared to talk through your resume bullets and projects in a behavioral-style round.
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 | |
| Over-Budget Projects | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| Paired Products | |
| P-value to a Layman | |
| Third Purchase | |
| Nearest Common Ancestor | |
| String Mapping | |
| Sort Strings | |
| Most Repetition | |
| Target Indices | |
| Finding The Mode | |
| Duplicate Rows | |
| Priority Queue Using Linked List | |
| Success Measurement | |
| Descending Alphanumeric Sorting | |
| Mouse Search | |
| Concurrent LLM Serving | |
| User Event Data Pipeline | |
| String Palindromes | |
| Foreign Key Constraints | |
| Shortest Path Algorithms | |
| Above Average Product Prices | |
| Acquisition Threshold | |
| Your Strengths and Weaknesses | |
| Pool Matching | |
| LRU Cache 1 |
Synthesized from candidate reports. Individual experiences may vary.
Candidates complete a HackerRank-based online assessment featuring Java/OOP questions and two LeetCode-style problems ranging from easy to medium difficulty. This step is common for campus recruiting and some general applications, and serves as the first technical filter before any human contact.
A standard HR call covering your background, resume, location, and motivation for joining PayPal. Expect questions like why you chose PayPal and basic fit questions, alongside a walkthrough of the upcoming interview stages.
Many candidates go through a Karat-conducted live coding interview that includes Java fundamentals, one or two DSA problems that often build on each other, and sometimes brief system design discussion questions. The format requires narrating your reasoning while coding simultaneously, so practicing out loud under time pressure is essential.
Typically two back-to-back technical rounds conducted via HackerRank or CoderPad, covering LeetCode-style DSA problems such as trees, stacks, heaps, binary search, BFS/DFS, and two pointers, alongside OOP concepts, web fundamentals like HTTP methods and API basics, and occasionally SQL and database fundamentals. One round is usually with a senior engineer focused on algorithmic coding, and another with an engineering manager who also covers resume deep-dives, project walkthroughs, and behavioral questions. Interviewers frequently add follow-up constraints or edge cases after an initial solution, reflecting PayPal's emphasis on transaction reliability and practical engineering judgment.
Candidates are asked to design systems such as a Dropbox-like application, a scalable notification system, a payment processing flow, or a chat application, with discussion around scaling, caching, data consistency, and security for user and payment data. Some roles extend this to full-stack architecture covering DNS, CDN, load balancers, WebSockets, long polling, and database schema design, reflecting PayPal's distributed systems and fraud/risk considerations.
A structured behavioral interview covering teamwork, communication, conflict resolution, and past project experience using STAR-style questions. Topics include strengths and weaknesses, difficult challenges, and how you collaborate with teams, and may include a hiring manager conversation about team fit and career goals.