Real, anonymous reports from people who interviewed for Software Engineer at PayPal, newest first and distilled into what to expect across the loop.
After a recruiter call that gave me an overview of the role, I moved into a pretty standard set of technical rounds. I had two technical interviews where the vibe was very LeetCode-style—medium difficulty data structures and algorithms questions, and a lot of focus on being able to explain my thinking while solving. At the end of the process, I got asked some follow-ups about how I use AI in practice, which caught me a little off guard because it didn’t fit the coding format.
My process felt very DSA-heavy and distinctly harder than the usual “medium LeetCode” reputation. I first hit an online assessment where I was asked two hard problems—one on trees and one on graphs—and I had only about 1 hour 30 minutes to solve both. The time pressure was real, and by the time I was switching between those topics, I could feel the difficulty compounding.
Candidates can expect multiple technical coding interviews focused on data structures and algorithms (DSA), often with a mix of medium to hard difficulty questions. The interviews typically emphasize clear communication of thought processes while solving problems.
There is usually a system design component that tests candidates on their ability to design applications and understand architectural trade-offs, often requiring a shift from algorithmic thinking to broader system-level considerations.
Candidates should prepare for behavioral interviews that assess cultural fit and leadership style, often involving discussions about past projects and personal interests, along with how they approach teamwork and problem-solving.
The interview process typically begins with an online assessment on platforms like HackerRank, where candidates solve coding problems under time constraints, which can vary in difficulty and topics such as SQL and recursion.
The overall interview process is generally structured and can be completed within a 1-2 week timeframe, with clear communication from interviewers regarding expectations and outcomes, contributing to a predictable experience.
Candidates often reflect on the high expectations for performance across various rounds, noting that missing small details can significantly impact outcomes, particularly in a short interview pipeline.