PayPal Software Engineer interview typically runs 3–5 rounds: online assessment, recruiter screen, and 2–3 technical interviews covering DSA, system design, and behavioral questions. The process takes roughly 2–4 weeks and is notable for its mix of Karat-style live coding and discussion-heavy system design rounds.
$145K
Avg. Base Comp
$210K
Avg. Total Comp
4-5
Typical Rounds
2-5 weeks
Process Length
What strikes us most across these 15 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. One candidate who received an offer specifically noted that the interviewers "cared a lot about how I explained my thinking" and that getting to a working answer wasn't enough — they pushed on edge cases and code modifications after the initial solution. That pattern shows up repeatedly across both offer and no-offer outcomes.
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, two-pointers, BFS), Java/OOP fundamentals, multithreading, web concepts like HTTP GET vs. POST, system design ranging from Dropbox to notification systems to full browser-to-backend architecture, and even SQL. The Karat rounds in particular add a layer of pressure that's less about problem difficulty and more about the talk-and-type-simultaneously format — one candidate described the interviewer pushing them to keep narrating even when they needed a moment to think, which made an otherwise manageable problem feel intense. If you're going through Karat, that format is its own skill.
The process is also genuinely inconsistent across teams. Some candidates saw a lightweight two-round loop; others went through a four-hour final day with Problem Solving, Design Logic, System Design, and Work Practices back to back. Communication after interviews was a recurring frustration — several candidates reported delays of weeks or being ghosted entirely. Go in with clear expectations that the experience may vary, but the underlying bar — solid fundamentals, clean verbal reasoning, and comfort with at least a surface-level system design conversation — stays consistent.
Synthetized from 15 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 | |
| Paired Products | |
| P-value to a Layman | |
| Over-Budget Projects | |
| Third Purchase | |
| Nearest Common Ancestor | |
| Total Spent on Products | |
| String Mapping | |
| Sort Strings | |
| Most Repetition | |
| Duplicate Rows | |
| Priority Queue Using Linked List | |
| Descending Alphanumeric Sorting | |
| Finding The Mode | |
| Concurrent LLM Serving | |
| String Palindromes | |
| Foreign Key Constraints | |
| Mouse Search | |
| Shortest Path Algorithms | |
| Above Average Product Prices | |
| Acquisition Threshold | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Pool Matching | |
| Cross-Culture Reports | |
| Generative AI Privacy | |
| Statistically Significant Test | |
| Dropbox Database |
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.
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 interview process.
Many candidates go through a Karat-conducted live coding interview that includes Java fundamentals, one or two DSA problems (often building on each other), and sometimes system design discussion questions. The format is talk-and-type simultaneously, so narrating your reasoning throughout is essential.
Typically two back-to-back technical rounds conducted via HackerRank or CoderPad, covering LeetCode-style DSA problems (trees, stacks, heaps, binary search, BFS/DFS, two pointers), OOP concepts, and occasionally web fundamentals like HTTP methods or API basics. One round may be with a senior engineer and another with an engineering manager who also covers resume and behavioral questions.
Candidates are asked to design systems such as a Dropbox-like application, a scalable notification system, or a chat application, with discussion around scaling, caching, data consistency, and security. Some roles extend this to full-stack architecture covering DNS, CDN, load balancers, WebSockets, and database schema design.
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.