PayPal Software Engineer Interview Guide

The short answer: PayPal's careers page describes three steps: a recruiter screen, interviews with team members, and then next steps with your recruiter, including a background check. PayPal currently interviews virtually on Microsoft Teams and prefers cameras on. Everything else comes from candidate reports, which describe an online coding assessment, a live coding screen and a loop of 4 to 5 rounds covering coding, system design, low-level design and behavioral questions. PayPal does not publish a rule on AI use in interviews. Last reviewed October 2026.

PayPal software engineer interview: quick answers

The PayPal software engineer role

What PayPal engineers work on, the skills its job postings ask for, and what a normal week looks like.

PayPal software engineer levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

PayPal's postings print titles without level codes: Software Engineer, Sr Software Engineer, Staff, Sr Staff and Principal, asking for at least 1, 3, 5, 8 and 10 years. A few postings list minimums that do not match their title, so ask your recruiter which level a role is.

Pay in PayPal's US job postings

PayPal's US postings print a base pay range for each location, and say additional pay may include an annual performance bonus, equity or other incentive compensation. The table shows San Jose, the highest-paid location.

Postings state no level, so rows use posting titles. Austin and Chicago ranges run about 9% lower than San Jose, and Scottsdale lower still. We left out a few postings whose printed range includes commission-based pay. Ranges seen October 27, 2026.

PayPal software engineer interview process

PayPal's interviewing page names the recruiter screen, the team interviews and the offer steps. The online assessment, the live coding screen and the round mix below come from candidate reports only.

Based on PayPal's own pages and candidate reports.

PayPal gives no timeline beyond saying the process takes some time. It describes no hiring committee or team-matching step, and every posting is tied to a specific team and requisition. Last reviewed October 2026.

What is different at PayPal

• Interviews run on Microsoft Teams. PayPal prefers cameras on, recommends Edge or Chrome, and asks you to test your camera, mic and connection and join a few minutes early.
• Behavioral rounds follow competencies. PayPal asks for specific, detailed examples for each competency, different examples across roles, and honesty, and points candidates to its values and Leadership Principles.
• Payments-style design. Candidate reports describe system design questions on idempotency, retries and data integrity, and more SQL than at many tech companies.
• Many open US roles sit in Venmo teams, including payments, identity, product and cloud infrastructure, so Venmo context is useful prep. Venmo Payments Engineering runs a platform serving 65 million active users.
• You cannot reapply to the same requisition after a rejection, but you can send questions or an updated resume through your recruiter.

PayPal software engineer interview questions

Coding problems from our bank tagged to PayPal, then design, fundamentals and behavioral prompts we wrote for this guide.

1from typing import List, Tuple
2
3IOU = Tuple[str, str, int]
4
5def settle(ious: List[IOU]) -> List[IOU]:
6    """Return the transfers (payer, payee, amount_cents) that settle every balance."""
7    pass

1import heapq
2from typing import Dict, List, Tuple
3
4IOU = Tuple[str, str, int]
5
6def settle(ious: List[IOU]) -> List[IOU]:
7    net: Dict[str, int] = {}
8    for debtor, creditor, amount in ious:
9        net[debtor] = net.get(debtor, 0) - amount
10        net[creditor] = net.get(creditor, 0) + amount
11    # Max-heaps keyed by amount owed or due; the name breaks ties alphabetically.
12    debtors = [(bal, name) for name, bal in net.items() if bal < 0]
13    creditors = [(-bal, name) for name, bal in net.items() if bal > 0]
14    heapq.heapify(debtors)
15    heapq.heapify(creditors)
16    transfers: List[IOU] = []
17    while debtors:
18        owe, payer = heapq.heappop(debtors)
19        due, payee = heapq.heappop(creditors)
20        amount = min(-owe, -due)
21        transfers.append((payer, payee, amount))
22        if -owe > amount:
23            heapq.heappush(debtors, (owe + amount, payer))
24        if -due > amount:
25            heapq.heappush(creditors, (due + amount, payee))
26    return transfers
27
28# Complexity: O(m + n log n) time for m IOUs and n people, since each transfer settles at least one person,
29# and O(n) space.

How to prepare

A plan for the PayPal loop, most important first:

1. Practice easy to medium data structures and algorithms problems under time, since candidate reports describe an online coding assessment and a live coding screen.
2. Practice payments system design: idempotency keys, retries with backoff, ledgers and reconciliation for flows such as Venmo payments and merchant webhooks.
3. Review object-oriented design, design patterns and multi-threaded programming for the low-level design round, since postings list them as preferred skills.
4. Prepare a distinct, specific story for each competency, tied to PayPal's values and Leadership Principles, and be honest about what you did.
5. Brush up on SQL, which candidate reports say comes up more at PayPal than at many tech companies.
6. Set up Microsoft Teams in Edge or Chrome, test your camera and mic, and ask your recruiter whether AI tools are allowed in any round.

Practice path

Courses that cover the rounds above:

• Data Structures and Algorithms
• System Design
• SQL