I connected with a recruiter via email, who circulated my resume among a few teams. One of the teams contacted me for a technical interview within hours, and I interviewed a few days later.
The interviewer asked me to build a basic implementation of a data structure using OOP principles in Java. Afterwards, they asked me a number manipulation question using that data structure, then presented an easy/medium LeetCode-style problem, and another data structure question. I thought I did decently, but not perfectly. We didn’t spend too much time coding the answers out, as the interviewer preferred verbal communication about my thought processes.
The recruiter informed me that I had moved to the final round, where I interviewed with my potential manager. I was asked to go into technical depth about my projects, and we had a great conversation about goals and fit. We got along very well, so I had a good feeling about landing the job. I received the offer a few days later.
I signed an NDA, so I can’t disclose specifics, but a solid understanding of underlying data structure implementations, as well as string, array, and matrix manipulation, seemed to be emphasized the most.
The following metrics were computed from 42 interview experiences for the PayPal Software Engineer role in San Jose, California.
PayPal's interview process for their Software Engineer roles in San Jose, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for PayPal's Software Engineer interview process in San Jose, California.