PayPal Software Engineer Interview Experience 3 YOE HLD LLD Bar Raiser
Interview Experience
I recently completed a 4-month-long interview process with PayPal, and the timeline has been quite unusual. I’m looking for some insight—am I being ghosted, or is this typical for their process? The T
Full Details
I recently completed a 4-month-long interview process with PayPal, and the timeline has been quite unusual. I’m looking for some insight—am I being ghosted, or is this typical for their process? The Timeline: Round 1 (DSA/Theory) - Mid-Dec: No actual problem-solving or coding. It was strictly theoretical questions regarding my past work and core CS concepts. Round 2 (HLD) - Late Dec: System Design for a parking system using AI for automated entry and exit detection. Round 3 (LLD) - Late Dec: Low-Level Design for a wallet service with multi-currency support, followed by project-specific questions. The Twist: In mid-January, I received a formal rejection email. However, in the first week of March, they reached out again to schedule a 4th Round (Bar Raiser/Hiring Manager). This round focused primarily on my resume and behavioral questions. The Current Situation: It has been over two weeks since the Bar Raiser round. I contacted the coordinator who scheduled the interviews, but he told me to contact the initial recruiter who started the process. I emailed that recruiter over a week ago and haven't received a response. Has anyone else experienced a rejection followed by a callback at PayPal? Does this silence usually mean a final rejection, or is their HR coordination just slow? YOE - 3
About This Question
This is a candidate experience report from a paypal interview for a swe role during the system design round reported in 2026.
It covers the following topics: System Design, Behavioral .
Topics
More Paypal Interview Questions
About Paypal Interview Reports
This question was reported by a candidate who interviewed at Paypal. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Paypal are the higher-signal extractions to take from this report.
For broader preparation context, the Paypal interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Paypal reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Paypal Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Paypal reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.