After a recruiter call to talk through the role, my process moved pretty quickly and felt focused. About a week later I had two technical interviews, each one centered on classic LeetCode-style problems with medium difficulty data structures and algorithms. One of the rounds felt like a straightforward algorithmic conversation where we worked through the problem step by step, and the other round stayed similarly rooted in DSA. Toward the end of the cycle, I was also asked questions about how I used AI, which caught me off guard a little compared to the rest of the content.
The final stretch leaned a bit more toward me as a person and how I’d work day to day. There was a hiring-manager type round where I talked through my projects and resume, plus some casual conversation around hobbies and other interests the interviewer genuinely wanted to understand. The whole experience was professional and not overly adversarial, and I left feeling like I understood what they cared about: both solid fundamentals and clear communication.
3 months ago
Difficult Positive Bengaluru
My process started with an OA that immediately set the tone as tough. I was given two hard LeetCode problems to solve within a tight 1 hour 30 minute window, and they were specifically split across a hard tree problem and a hard graph problem. That time pressure made everything feel intense from the beginning, and I remember thinking that this wasn’t just about knowing patterns—it was about executing quickly and correctly.
After the OA, the rest of my journey leaned heavily into DSA and core CS fundamentals. I went through multiple rounds, with two technical interviews and an HR/hiring-manager style round that still stayed technical. The topics weren’t limited to algorithms either; I was also asked about OOP and DBMS fundamentals. One of the steps had a coding environment where I wrote SQL queries on a platform in addition to the broader DSA work, which made the assessment feel broader than I expected.
3 months ago
Average Neutral Austin, TX
I got contacted by a recruiter for the Venmo Infrastructure side, and the process started like a normal screening: an overview call about the role and…
5 months ago
Easy Positive United States
My process started with an OA, and then it quickly shifted into a recruiter conversation and technical rounds. After the OA, I had a recruiter call wi…
5 months ago
Average Neutral Israel
My interview experience was smaller and very hands-on. I ended up with an interview that mixed basic computer science questioning with a coding task. …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Assessment & Recruiter Call
The interview process typically starts with a recruiter call to discuss the role and candidate background, followed by an online assessment (OA) that often includes LeetCode-style problems. Candidates should be prepared to articulate their motivations for joining PayPal and discuss their technical experience.
Recruiter CallOnline AssessmentMotivation
Technical Interviews (DSA Focus)
Candidates can expect multiple technical interviews focused on data structures and algorithms (DSA), with questions ranging from medium to hard difficulty. It's essential to practice coding problems under time constraints and be ready to explain thought processes clearly.
DSALeetCodeCoding Problems
System Design Discussions
Later rounds often include system design interviews where candidates are asked to design applications or services, requiring a solid understanding of architecture and product-level requirements. Candidates should prepare to discuss scalability, idempotency, and other design principles.
System DesignArchitectureScalability
Behavioral & Managerial Rounds
The interview process includes behavioral rounds where candidates discuss their projects and experiences, often with a focus on communication and cultural fit. Candidates should be ready to reflect on their teamwork and problem-solving approaches.
BehavioralCultural FitProject Experience
Overall Experience & Communication
Candidates reported varying experiences with communication throughout the process, with some feeling supported while others experienced delays or lack of follow-up. It's advisable to maintain proactive communication with recruiters for updates.
CommunicationFollow-upExperience
Difficulty Level & Expectations
The overall difficulty of the interview process is considered high, with a strong emphasis on technical fundamentals and problem-solving speed. Candidates should prepare thoroughly and expect to be evaluated on both their technical skills and their ability to articulate their reasoning.