PayPal Software Engineer candidates report assessments or recruiter screens followed by coding, system design, and behavioral discussions. Preparation should prioritize clear problem solving, engineering fundamentals, and tradeoff-driven design.
$188K
Avg. Base Comp
$244K
Avg. Total Comp
2-5 rounds
Typical Rounds
2-4 weeks
Process Length
PayPal Software Engineer interviews reported here vary by team and seniority, but the recurring preparation themes are live coding with follow-ups, practical system design, and clear communication. Candidates began with either an online assessment or a recruiter conversation. One candidate then completed two interviews, while another described five stages including the assessment. A Karat screen also appeared in one account, so treat the exact sequence as variable rather than fixed.
For coding, candidates report HackerRank, CoderPad, Karat, and live-coding questions covering arrays, linked lists, binary trees, binary search, graph scheduling, and merging sorted arrays. One assessment also included a debugging task. A useful practice routine is to solve the core problem, narrate the approach, test edge cases, and adapt when the interviewer adds constraints. Java and OOP fundamentals appeared in multiple reports, while another interview included SQL and database questions.
Reported system-design prompts included a URL shortener, Dropbox-like storage, and a scalable notification system. Prepare to clarify requirements and explain scaling, consistency, security, and tradeoffs without assuming every candidate receives the same design topic. Behavioral discussions may cover past projects, teamwork, leadership, and difficult challenges. Two candidates explicitly reported end-to-end processes lasting about two and four weeks, while other reports did not provide a complete duration.
Synthesized from 17 candidate 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 | |
|---|---|
| Rolling Bank Transactions | |
| String Shift | |
| Over-Budget Projects | |
| Find the Missing Number | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| Paired Products | |
| P-value to a Layman | |
| Third Purchase | |
| Nearest Common Ancestor | |
| Sort Strings | |
| String Mapping | |
| Most Repetition | |
| Finding The Mode | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Success Measurement | |
| Duplicate Rows | |
| Nightly Job | |
| Descending Alphanumeric Sorting | |
| Mouse Search | |
| Concurrent LLM Serving | |
| User Event Data Pipeline | |
| String Palindromes | |
| Foreign Key Constraints | |
| Shortest Path Algorithms | |
| Above Average Product Prices | |
| Cross-Culture Reports | |
| Acquisition Threshold |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either an online assessment or a recruiter/manager conversation at the start. Assessments included coding, debugging, OOP, or basic problem-solving; early conversations may cover background, projects, interest in the role, location, and fit.
Candidates report HackerRank, CoderPad, Karat, and live-editor coding sessions. Topics varied across trees, stacks, heaps, linked lists, grids, BFS, LRU cache, and Java or OOP fundamentals; follow-up constraints and explaining reasoning were common.
System design may be a dedicated discussion or part of a technical interview. Reported prompts included URL shortening, file storage, notifications, chat, ecommerce, and project architecture, with candidates discussing scale, data, security, consistency, and tradeoffs.
Candidates report behavioral or manager conversations in some processes, covering projects, teamwork, leadership, conflict, strengths and weaknesses, and motivation. The emphasis and placement of this discussion appear to vary by team.
