PayPal engineering hiring runs on an interview process, not a single written exam — a HackerRank online assessment, followed by a loop of live rounds mixing DSA, system design, role-specific technical depth, and behavioral conversations. The exact rounds vary by level (SDE-2 vs. senior SDE-3) and by whether the role leans frontend, backend, or full-stack — the outline below is the pattern that shows up most consistently across recent (2025) candidate reports.
Typical PayPal engineering interview process
| Stage | What it tests | Typical length |
|---|---|---|
| HackerRank Online Assessment | 2-3 DSA-focused problems, sometimes combined with a small coding exercise in the role's stack (e.g. a JS class or a React component) | 60–90 min |
| DSA / Coding round(s) | 1-2 rounds of LeetCode-medium style problems — dynamic programming, stacks, strings, and graphs come up often | 45–60 min each |
| System design round(s) | Often framed as a real-world scenario discussion rather than a formal whiteboard exercise — payment-gateway, shopping-cart, and real-time pricing systems have all been reported | 45–60 min |
| Role specialization round | Team-specific depth — frontend internals (React reconciliation, hooks), backend design (low-level design against given interfaces), or SQL, depending on the role | 45–60 min |
| Bar Raiser / behavioral round(s) | Past project depth, teamwork, mentorship, and situational judgment | 30–45 min |
Candidates whose background spans both frontend and backend consistently report extra, team-specific rounds bolted onto the core loop — don't assume the table above is the whole story once you clear the first system design round. See PayPal Interview Experiences for how this actually played out for real candidates.
Prepare each track on its own terms: DSA and Behavioral & Culture-Fit questions.