Paypal Interview Experiences

How PayPal fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

PayPal placement process includes: 1. Online Assessment (90 minutes) - Aptitude, Technical, and Coding sections, 2. Technical Interview (45 minutes) - Programming problems, technical concepts, project discussion, 3. HR Interview (30 minutes) - General discussion, compensation, role expectations. Total duration: Approximately 2-3 weeks from application to offer.

Eligibility (from student reports): 6.0+ CGPA in 10th, 12th, and graduation.

Fresher package ballpark (from student reports): ₹12-18 LPA. Confirm on your offer letter.

How to use this page

Read the round table first, then the experiences. Practise the coding patterns with edge cases, and keep one clear story each for ownership, conflict, and a project failure.

Round-wise process

Round	Duration	What they test
Online Assessment	90 min	Coding (DSA) + sometimes MCQs
Technical Round 1	45-60 min	DSA with added constraints (no hash map, linear time, alternate implementations)
Technical Round 2	45-60 min	SQL, DBMS keys, OOPs, project discussion
HR / Culture	20-30 min	Motivation, integrity, relocation

Real interview experiences

Rewritten from public student write-ups of PayPal’s India campus and off-campus hiring. A correction worth stating up front: fresher write-ups do not describe a payments or ledger system-design round. What they consistently describe is DSA with constraints attached (“do it without a hash map”, “now in linear time”, “now give me three different implementations”), plus SQL, DBMS keys, and OOPs. Interviewers ask for the second and third solution after the first one works.

Experience 1: SDE-1, on-campus (selected)

Source: PayPal Interview Experience (On-Campus) - GeeksforGeeks

Round 1 - coding (120 min)

• Count pairs in an array whose sum is divisible by 60.
• An optimisation problem on placing houses to minimise distance to non-house positions.
• Complexity analysis was expected alongside a working solution.

Round 2 - technical

• Started easy: ASCII values and character frequency, then escalated.
• Find elements unique to each array - but without hash structures, in linear time, given sorted input.
• Linked list cycle detection, asked for three different implementations.
• Concepts: primary keys, natural vs surrogate keys, backtracking vs dynamic programming.

Round 3 - technical (over an hour with round 2)

• Walk through the round 1 solutions live in a HackerRank workspace - so remember what you submitted.
• Infix to postfix conversion.
• A light design discussion: explain how Google search works, using abstract classes and a UML sketch.

Round 4 - HR

• Scenario-based logic problems that still required code, then behavioural questions on aspirations and leadership.

Result: Selected. The write-up reports 5 offers from that campus (4 full-time, 1 intern).

Experience 2: Software Engineer summer internship 2023, on-campus (selected)

Source: PayPal Software Engineer Summer Internship 2023 (On-Campus) - GeeksforGeeks

• OA on HackerRank: 6 easy MCQs (aptitude, applied DSA, DBMS) plus 2 medium coding problems. 20 candidates advanced.
• Technical (~40 min): abstract classes, a string-manipulation coding problem with complexity analysis, SQL injection, and a database query asked first with subqueries and then rewritten using joins. Plus an aptitude puzzle and light networking questions.
• Managerial / HR: introduction, adaptability, a proud moment and a failure, strengths and weaknesses, what you know about PayPal, and handling disagreement in a team.
• Result: Selected - 8 interns taken from that drive.

A counter-example worth reading

An off-campus Software Engineer candidate cleared a technical round (search in a rotated sorted array with an O(log n) requirement; find the unique element with an XOR approach) and an HR round covering projects, teamwork, GitHub contributions, SQL joins and OOPs - felt it went well, and was rejected by email about a month later. PayPal’s off-campus timelines are slow and positive interviewer feedback is not a signal. (source)

What recurs across all three

• SQL is asked in every account - joins especially, often twice in different forms.
• Expect follow-up constraints, not follow-up problems. Have a second approach ready before you’re asked.
• The OA is a mix of MCQs and coding, not pure coding. Do not skip DBMS and aptitude revision.

Questions that come up often

Coding / technical

1. Design an LRU cache. Usually expects HashMap + doubly linked list
2. Implement a rate limiter. Usually expects sliding window / token bucket
3. Merge overlapping time intervals. Usually expects sort + sweep
4. Discussion on cross-border payments and risk checks, bottlenecks, failure modes, simple APIs
5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

1. Why fintech / payments?
2. A production bug or outage you helped with
3. An integrity / pressure scenario
4. Joining timeline

Practical tips for Paypal

• Clear the screening round first. Timed practice beats last-minute topic hopping.
• For domain questions, explain cross-border payments in plain language, inputs, outputs, what breaks at scale.
• OOPs and SQL still open a lot of PayPal panels. Do not skip fundamentals.
• HR answers should be concrete. One story with a result beats five slogans.
• If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, PayPal usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common PayPal HR questions, sample answer frames, and STAR tips.

Similar companies

Google · Amazon · Microsoft · Meta · Capital One · Goldman Sachs