I was contacted through LinkedIn and scheduled a phone screening interview. It went well; we reviewed my resume, background, design decisions, and career goals. It was a fun chat with a very experienced engineer, and I received a "thumbs up" the next day.
Later, I was provided with a coding challenge and about a week to complete it. It was very open-ended, combining many tools I had used in the past, but I also had to learn a few new ones. I had fun with it and implemented extra features.
An onsite interview was scheduled shortly after, with five interviewers, each for 45 minutes. Four were from the team I would work with, and one was from another team.
The first few interviewers asked questions about specific language features such as scoping, terminology, and limits. I was expecting questions specific to the coding challenge, as I was told the challenge was meant to "guide the interviews."
The last two interviewers reviewed my code and were on point with their questions, allowing me to demonstrate my experience well and in an organic way.
I did not get the position, but overall, I had a good experience. I am disappointed I could not demonstrate my full value due to the way the interviews were structured.
Here is code intentionally convoluted with many layers deep of function calls. Determine variable values at different points in the program's life.
The following metrics were computed from 1 interview experience for the PayPal Software Engineer role in Mountain View, California.
PayPal's interview process for their Software Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for PayPal's Software Engineer interview process in Mountain View, California.