How to Crack PayPal: The Software Engineer Intern Interview, From Real Experiences
PayPal SWE intern interview guide from six real accounts: OA coin change and music player tasks, linked lists, HashMap internals, HR questions and verified practice links.
On this page
Last reviewed November 20, 2026 · 25 min read · For candidates targeting Software Engineer and SDE summer internships in India
Researched and written by the Codinzhub Editorial Team from six independent first-hand sources: five candidate write-ups and one archived discussion comment. Five internal full-time PayPal records were reviewed but excluded because they describe SDE roles, not internships. Every question below is a verbatim report or a faithful paraphrase; nothing was invented to fill a round.
The 30-second version: The reported PayPal intern loop is a resume screen, a timed online assessment of MCQs plus one or two coding questions, one technical interview and one HR or managerial round. Assessments ran 60 minutes in two accounts and used HackerRank in three. The technical rounds mix linked-list manipulation, OOP, Java HashMap internals, SQL, graphs and easy-to-medium coding, with one account requiring code on paper and a proof of correctness. HR asks about PayPal, motivation, self-reflection and how you handle unclear or contested solutions. One 2023 campus drive selected 8 interns; one 2024 off-campus candidate was rejected after a positive technical round.
Important things to know before you start
The assessment format varies, but it is always mixed. Accounts report 20 MCQs plus one coding question, 9 MCQs plus one coding question in 60 minutes, 6 MCQs plus two coding questions, and two coding questions with MCQs uncertain. There is no single universal paper.
Linked-list surgery is a recurring theme. Two accounts describe detecting a linked-list cycle, one of them asking for the cycle's start and the other asking for removal and a proof of correctness. A queue built from stacks also appeared.
OOP is examined deeply, not by definition. Candidates were asked for real-life examples of inheritance, polymorphism, abstraction and encapsulation, the types of polymorphism, virtual functions, whether an abstract class can be private, and a 30-minute discussion of Java HashMap internals.
You may have to defend your code on paper. One technical round required linked-list code on paper, edge-case testing and a proof of the solution. Another candidate solved the coding question but could not give an optimised approach.
HR can include a coding question. One account reports an easy array problem solvable with a hashmap in the HR round, alongside a resume walkthrough. Do not treat the final round as purely conversational.
What this guide covers
This guide covers PayPal Software Engineer and SDE summer internship hiring in India, with one older US account used only to show how a loop can differ by region. It is not a guide to PayPal SDE 1, SDE 2, Full Stack Developer or Data Scientist hiring. Those are different role families, and their questions are not mixed into this guide.
Scope: Software Engineer Intern / SDE Summer Intern, India, with evidence published between 2022 and 2025 plus one archived 2017 US comment. Five full-time internal records were excluded from the question counts.
Selected vs. rejected: do this, not that
These habits come from selected and rejected accounts. They are observations from six reports, not a proven formula.
| Do this | Not that | Why it matters |
|---|---|---|
| State complexity and discuss optimisation after solving a coding problem. | Stop at a working solution and wait to be asked. | One candidate solved the problem but struggled with the optimisation discussion. |
| Know data structure trade-offs, not just definitions. | Recite definitions of arrays, trees and graphs without use cases. | Two accounts asked for differences, applications and time complexities. |
| Explain code on paper and test edge cases. | Write code without stating invariants or tests. | One interviewer asked for a proof of the linked-list solution. |
| Prepare company answers: why PayPal, unique features, local reach. | Give a generic "good company" answer. | These appeared verbatim in HR rounds. |
| Prepare situation stories for unclear requirements and team disagreement. | Assume technical rounds are the only scored stage. | The managerial round asked directly about both situations. |
Round-by-round breakdown
Stage 1: Application
Three routes are attested: an on-campus drive, an application through a university placement process, and the PayPal careers portal. One 2024 account describes an off-campus internship after resume screening. One older US comment describes a phone interview followed by four Skype interviews, but gives no questions.
Stage 2: Shortlisting
Resume screening is the first filter. One campus account says eligibility was based on CGPA up to the fourth semester, with about 400 eligible students and 8 reaching the next round. A 2023 on-campus account reports 20 candidates selected for the technical round and 8 for the internship. These are single-campus funnel numbers, not company-wide rates.
Stage 3: Online assessment
How it works. The assessment combines multiple-choice questions with one or two coding tasks. HackerRank is named in three accounts and PayPal's own interface in one. Two accounts give a 60-minute duration. Coding tasks range from easy array problems to a medium-hard music-player design question.
At a glance: 60 minutes in two accounts, not reported in three; 1 to 2 coding questions plus 6 to 20 MCQs; HackerRank in three accounts, PayPal's own interface in one. Topics: arrays, strings, coin-change DP, class design, DBMS, OS, networks and aptitude.
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Practice link |
|---|---|---|---|---|
| Find the least number of coins to make an amount using pennies, nickels, dimes and quarters. | Greedy or coin-change DP | Samples: 30 -> 2, 100 -> 4 | Intern | Coin Change |
| Design a music player based on song preferences. | Object-oriented design | Not reported | SDE Summer Intern, 2024 | No verified practice match |
| A medium-to-hard coding question on arrays and strings. | Arrays and strings | Not reported | Intern | No verified practice match |
| Two medium coding questions; statements not reported. | General DSA | Not reported | Intern, 2023 | No verified practice match |
| About 20 MCQs on C/C++ input-output, maths, verbal and quantitative aptitude. | CS fundamentals and aptitude | Not reported | Intern | No verified practice match |
| MCQs on DBMS, OS, web technology and networks; another account reports aptitude and DSA application MCQs. | CS fundamentals | Not reported | Intern, 2023-2024 | No verified practice match |
Reading this table: three rows are topic-level reports because the candidate did not record the full statement. They are included so the round is not understated, but they are not exact questions.
PayPal OA questions on Codinzhub: Browse PayPal questions.
Stage 4: The technical interview
How it works. Most accounts describe one technical round after the assessment. It opens with an introduction, then moves through data structures, OOP, a coding task and projects. One account required code on paper with edge cases and a proof. Another shared a HackerRank link inside the interview. One older US account reports four Skype rounds with algorithms, behavioural and domain questions.
At a glance: about 40 minutes in one account, not reported in others; 4 to 6 named prompts per account; paper, virtual and shared-editor surfaces. Topics: linked lists, OOP, Java HashMap, graphs, SQL, strings, concurrency and CS fundamentals.
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Practice link |
|---|---|---|---|---|
| Detect and remove a loop in a linked list; write code on paper, test edge cases and prove it. | Floyd cycle detection | Prove the solution | Intern | Linked List Cycle II |
| Distinguish between a hash table and a hash map. | Hashing concepts | Not reported | Intern | No verified practice match |
| Explain how HashMap is implemented in Java. | Java collections internals | 30-minute discussion | Intern | No verified practice match |
| Explain a single-source shortest path algorithm with an example; no code. | Graph algorithms | Not reported | Intern | No verified practice match |
| What are threads? Do they share the same address space, and why? | Concurrency and OS | Not reported | Intern | No verified practice match |
| Explain arrays, linked lists, trees and graphs with time complexities and use cases. | Data structure fundamentals | Not reported | Intern | No verified practice match |
| OOP basics with real-life examples: inheritance, polymorphism, abstraction, encapsulation. | OOP fundamentals | Real-life examples | Intern | No verified practice match |
| Types of polymorphism and virtual functions / runtime polymorphism. | OOP dispatch | Not reported | Intern | No verified practice match |
| What is abstraction? Can an abstract class be private? | Java access modifiers | Not reported | Intern | No verified practice match |
| Implement a queue using stacks. | Stack and queue composition | Not reported | Intern | Implement Queue using Stacks |
| Check a linked list for a cycle, then find the start of the cycle. | Floyd cycle detection | Find the start | Intern | Linked List Cycle |
| What is SQL injection? | Web and database security | Not reported | Intern | No verified practice match |
| Rewrite a query first answered with inner queries using joins. | SQL joins | Give a different answer with joins | Intern | No verified practice match |
| Give an approach to basic string manipulation and state its time complexity. | Strings and complexity | Time complexity | Intern | No verified practice match |
Stage 5: HR and managerial round
How it works. The final conversation is usually HR or managerial. One account describes a managerial round with nine direct prompts; another asks four company and self-reflection questions. One account reports an easy array coding problem inside the HR round, so prepare for a short technical task as well as conversation.
At a glance: duration not reported; 4 to 9 prompts; conversational, with one reported coding question.
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Practice link |
|---|---|---|---|---|
| Why PayPal? / What do you know about PayPal? | Motivation and research | Not reported | Intern | No verified practice match |
| What is the most challenging thing you have come across? | Ownership | Not reported | Intern | No verified practice match |
| What are the unique features of PayPal? | Company research | Not reported | Intern | No verified practice match |
| What is the reach of PayPal in your locality? | Market awareness | Not reported | Intern | No verified practice match |
| How adaptable are you? | Adaptability | Not reported | Intern | No verified practice match |
| What is your proud moment? | Achievement | Not reported | Intern | No verified practice match |
| Tell me about a failure in your life. | Learning from setbacks | Not reported | Intern | No verified practice match |
| Strengths, weaknesses and skills still to develop. | Self-awareness | Not reported | Intern | No verified practice match |
| What are your job expectations? | Role fit | Not reported | Intern | No verified practice match |
| What do you do if you don't understand the problem statement? | Communication | Not reported | Intern | No verified practice match |
| What if your teammates don't like your solution? | Collaboration | Not reported | Intern | No verified practice match |
| Walk me through your resume in depth. | Resume defence | Not reported | Intern | No verified practice match |
| Easy array problem solvable with a hashmap. | Hashing | Not reported | Intern | Two Sum |
Stage 6: Decision
One 2023 on-campus account reports 8 internship selections including the candidate. One 2024 off-campus candidate was not selected after a positive technical interview, with the reason unknown. No account describes a hiring committee, team match, level change or compensation discussion. One 2017 US comment reports progressing through four Skype interviews, but no outcome.
Candidate experiences reviewed
| Background | Role and reported outcome | What was asked |
|---|---|---|
| India campus, CGPA shortlist | Intern · outcome not reported | Coin change OA; linked-list loop removal with proof, HashMap internals, shortest path, threads; PayPal HR questions |
| Second-year student, careers portal | Intern · outcome not reported | 9 MCQs + array/string coding; DS use cases, OOP, optimisation discussion |
| University applicant, Nov 2023 | Intern · outcome not reported | 2 coding OA; OOP, queue using stacks, linked-list cycle; HR resume and array problem |
| Off-campus 2024 | SDE Summer Intern · rejected | MCQ + music player design; DS differences, OOP, array problem; HR |
| On-campus 2023 | SWE Summer Intern · selected | 6 MCQs + 2 coding; abstract class, strings, SQL injection, joins, puzzle; nine managerial prompts |
The Codinzhub Next-Round Playbook
To get past the online assessment
- Practise one coding problem after nine MCQs in 60 minutes. Two accounts describe exactly that format.
- Revise coin-change DP and greedy counting. The pennies/nickels/dimes/quarters problem is the only fully specified OA coding task.
- Revise CS fundamentals for MCQs: DBMS, OS, computer networks, web technology, C/C++ input-output and aptitude.
- Be ready for a design-flavoured task. The music-player prompt was lengthy and required time to understand.
To get past the technical round
- Master linked-list cycle problems: detect, find the start and remove the loop. Be able to prove why the fast and slow pointers meet.
- Prepare Java HashMap internals to a depth of at least 30 minutes of discussion: hashing, buckets, collisions, resizing and treeification.
- Revise OOP with examples and know the difference between an abstract class and an interface, and whether an abstract class can be private.
- Practise SQL joins and SQL injection as short verbal answers, plus one query rewrite from a subquery to a join.
- Write code on paper and state edge cases, complexity and a short correctness argument.
To get past the HR and managerial round
- Prepare four company answers: why PayPal, unique features, local reach, and what you know about the business.
- Prepare six STAR stories for challenge, adaptability, proud moment, failure, strengths and weaknesses, and team disagreement.
- Rehearse the two situation answers: unclear problem statement, and a teammate rejecting your solution.
- Expect a short coding task in some rounds; an easy hashmap-based array problem was reported.
How the loop differs by level
| Level | Typical experience | What the accounts emphasise | Coding depth |
|---|---|---|---|
| Software Engineer Intern / SDE Summer Intern | Resume screen, timed assessment, one technical round, one HR or managerial round | DSA, OOP, DBMS, company knowledge | Easy to medium, with occasional medium-hard design |
| SDE 1 / SDE 2 (out of scope) | Longer loops with system design and hiring-manager rounds | Not covered here; five full-time records were excluded | Not combined with intern evidence |
| US SWE intern, 2017 | One phone interview plus four Skype interviews | Algorithms alongside behavioural and domain questions | One old report, no questions recorded |
Do not assume the Indian three-stage pattern applies to every region or year. The US report is eight years older and describes a longer loop.
Most-asked topics
| Topic | What it means in plain English | Evidence-backed priority | Reported examples |
|---|---|---|---|
| Linked lists | Rewiring nodes and detecting cycles with two pointers. | High - 3 of 4 technical accounts | Loop removal with proof; cycle detection and start |
| OOP | Classes, inheritance, polymorphism, abstraction and encapsulation. | Very high - 4 of 4 technical accounts | Real-life examples, virtual functions, private abstract class |
| Hashing | Mapping keys to buckets and reasoning about collisions. | Medium - 2 of 4 technical accounts | Hash table vs HashMap, Java implementation, hashmap array problem |
| Arrays and strings | Scanning, frequency maps and complexity of simple approaches. | Very high - 4 of 4 technical accounts | Array/string OA, string manipulation, array problem, Two Sum-style task |
| SQL and DBMS | Joins, subqueries and injection. | Medium - 3 of 4 technical accounts | SQL injection, join rewrite, DBMS MCQs |
| Graphs | Shortest paths and data structure use cases. | Medium - 2 of 4 technical accounts | Single-source shortest path, graph use cases |
| Concurrency and OS | Threads, address spaces and OS fundamentals. | Medium - 2 of 4 technical accounts | Shared address space, OS MCQs |
| Company and behaviour | Motivation, self-reflection and scenario answers. | Very high - 4 of 4 accounts | Why PayPal, failure, team disagreement, unclear statement |
The question patterns that keep coming back
1. Linked-list cycle reasoning
- How to recognise it: "detect a loop", "find the start", "remove the loop", "prove it".
- The invariant: a slow pointer moves one step and a fast pointer two; if they meet, a cycle exists. Resetting one pointer to the head finds the start.
- Preparation action: write the loop detection, start-finding and removal versions from memory, and explain each in two sentences.
2. Data structure comparisons
- How to recognise it: "differences between data structures", "time complexities and use cases", "hash table versus hash map".
- The invariant: compare by access pattern, memory and operation cost, not by definition alone.
- Preparation action: prepare a four-row table for array, linked list, tree and graph with one use case each.
3. OOP with justification
- How to recognise it: "real-life example", "types of polymorphism", "can an abstract class be private".
- The invariant: tie each concept to a language mechanism and a concrete example from your projects.
- Preparation action: rehearse a single example that demonstrates inheritance, polymorphism, encapsulation and abstraction together.
4. SQL alternatives
- How to recognise it: "give a different answer using joins".
- The invariant: a subquery and a join can express the same filter; know when each is clearer.
- Preparation action: rewrite three subquery problems as joins and explain the difference.
5. Situation answers in HR
- How to recognise it: "what if the statement is unclear", "what if teammates dislike your solution".
- The invariant: clarify first, state assumptions, propose a small experiment and appeal to evidence rather than authority.
- Preparation action: prepare a 60-second answer for each using one real project example.
Preparing for the HR and managerial round
The HR and managerial rounds are scored. The prompts are direct: motivation, company knowledge, adaptability, a proud moment, a failure, strengths and weaknesses, job expectations, and two situation questions. One account also reports an easy coding task.
Core themes: motivation, self-awareness, adaptability, collaboration and clarity under ambiguity.
The six STAR stories to prepare
Use STAR: Situation, Task, Action, Result.
| # | Story prompt | Focus area |
|---|---|---|
| 1 | A time you received unclear requirements and clarified them. | Communication |
| 2 | A teammate disagreed with your technical solution. | Collaboration |
| 3 | A project failure and what changed afterwards. | Learning |
| 4 | A moment you had to adapt quickly to a new tool or domain. | Adaptability |
| 5 | A piece of work you are genuinely proud of. | Achievement |
| 6 | A strength you used and a weakness you are improving. | Self-awareness |
Practice problems that match these experiences
Note on practice analogues: These problems share the technique named in the accounts. Unless marked "Exact reported problem", they are analogues, not leaked questions.
| # | Practice problem | Pattern | Seen in these experiences as | Link |
|---|---|---|---|---|
| 1 | Coin Change | Greedy / DP | Least coins with pennies, nickels, dimes, quarters | LeetCode #322 |
| 2 | Linked List Cycle II | Two pointers | Detect and remove a loop, with proof | LeetCode #142 |
| 3 | Linked List Cycle | Two pointers | Detect a cycle, then find its start | LeetCode #141 |
| 4 | Implement Queue using Stacks | Stack composition | Implement a queue using stacks | LeetCode #232 |
| 5 | Two Sum | Hashing | Easy array problem solvable with a hashmap | LeetCode #1 |
How to handle a question you have never seen
- Restate the problem and ask for constraints before coding.
- State the brute-force baseline and its complexity so the interviewer can follow your reasoning.
- Name the bottleneck: repeated lookups suggest a hash map, a sequence with a loop suggests two pointers, and independent choices with a target suggest DP or greedy.
- Write clean code with edge-case guards first, then trace a small example by hand.
- State complexity and one optimisation proactively. One candidate's gap was exactly this step.
- If asked to prove a solution, explain the invariant in words before formalising it.
Why candidates were rejected
No recruiter feedback is reported. Two self-reflections are relevant: one candidate solved a coding problem but could not give an optimised approach, and another was not selected after a positive technical round with the reason unknown. Treat these as observations, not as proven causes of rejection.
If you remember only five things
- Prepare for 60-minute MCQ-plus-coding assessments with coin-change, arrays and strings, and class design.
- Master linked-list cycle detection, including find-the-start and remove-the-loop variants.
- Revise OOP and Java HashMap internals deeply, not by definition.
- Practise SQL joins and short CS-fundamental answers for technical rounds.
- Prepare company and situation answers for HR, and expect a possible easy coding task.
Frequently asked questions (FAQ)
Is this a full-time SDE guide?
No. It covers Software Engineer and SDE summer internships. Five full-time PayPal records were excluded because they are a different role family.
How many rounds does the PayPal intern process have?
The Indian accounts describe three stages after resume screening: an assessment, one technical interview and one HR or managerial round. An older US comment describes a phone interview plus four Skype interviews.
Which platform is used for the assessment?
HackerRank is named in three accounts and PayPal's own interface in one. Two accounts do not name the platform.
Is system design asked in the intern loop?
There is no separate system-design round in these accounts. One OA task asked for a music-player design based on song preferences, and one account was asked to scale a project in a different role family's report, which is not included here.
Are the practice links exact questions?
Most are analogues. A queue using stacks, the linked-list cycle problems and Two Sum match reported prompts closely; the coin-change page is an analogue for the named coin denominations problem.
Why are some OA rows topic-level?
Because the candidates did not record the full statements. The guide says so in the table and does not invent wording.
About this guide and methodology
This guide was compiled by the Codinzhub Editorial Team from six first-hand sources: five candidate write-ups and one archived discussion comment. Full-time SDE, SDE 2, Full Stack Developer and Data Scientist accounts were excluded. No external research URLs, internal record identifiers or private ledgers appear in this article. Practice links are verified analogue or exact-problem pages.
Disclaimer: Hiring processes change over time and vary by campus, team and region. This guide reflects reported historical experiences and is not an official statement from PayPal. Confirm the current format with your recruiter.
Other company and role guides
- Intuit Software Development Engineer 1 guide
- Goldman Sachs software engineer interview guide
- Amazon software engineer intern guide
- Google software engineer intern guide
- Zomato SDE 1 interview guide
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 20 of 74 questions
Find the least number of coins to make an amount using pennies, nickels, dimes and quarters.
Level: Samples: 30 -> 2, 100 -> 4.
Design a music player based on song preferences.
Level: Not reported.
A medium-to-hard coding question on arrays and strings.
Level: Not reported.
Two medium coding questions; statements not reported.
Level: Not reported.
About 20 MCQs on C/C++ input-output, maths, verbal and quantitative aptitude.
Level: Not reported.
MCQs on DBMS, OS, web technology and networks; another account reports aptitude and DSA application MCQs.
Level: Not reported.
Detect and remove a loop in a linked list; write code on paper, test edge cases and prove it.
Level: Prove the solution.
Distinguish between a hash table and a hash map.
Level: Not reported.
Explain how HashMap is implemented in Java.
Level: 30-minute discussion.
Explain a single-source shortest path algorithm with an example; no code.
Level: Not reported.
What are threads? Do they share the same address space, and why?
Level: Not reported.
Explain arrays, linked lists, trees and graphs with time complexities and use cases.
Level: Not reported.
OOP basics with real-life examples: inheritance, polymorphism, abstraction, encapsulation.
Level: Real-life examples.
Types of polymorphism and virtual functions / runtime polymorphism.
Level: Not reported.
What is abstraction? Can an abstract class be private?
Level: Not reported.
Implement a queue using stacks.
Level: Not reported.
Check a linked list for a cycle, then find the start of the cycle.
Level: Find the start.
What is SQL injection?
Level: Not reported.
Rewrite a query first answered with inner queries using joins.
Level: Give a different answer with joins.
Give an approach to basic string manipulation and state its time complexity.
Level: Time complexity.
Keep preparing on Codinzhub
- PayPal interview questions and experiences — OA questions and interview experiences candidates shared for PayPal.
- Browse PayPal online assessment questions — filter the Codinzhub question bank by company.
- Amazon Software Engineer interview guide — the Amazon process, rounds and question patterns.
- Google Software Engineer interview guide — the Google process, rounds and question patterns.
- Adobe Software Engineer interview guide — the Adobe process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Keep track of what you’ve learned.