The interview process was a really long process and a large demand on candidates' time. It also felt like the evaluation was very subjective. It mainly involved describing projects you've worked on and pair programming, none of which have objective metrics. So, it seems like success really depends on how well you click with your interviewers.

The take-home test was not difficult but took a large amount of time (about 8 hours, or most of my weekend for me). Coding is done via a take-home assignment and pair programming at the onsite.

The team and interview process seem to have an identity crisis between Braintree and PayPal. My interviews were with part Braintree and part PayPal teams. I mentioned some things I liked about Braintree culture, such as pair programming and TDD, and one of the interviewers said they don't do it on their team, but the recruiter told me it is a big part of their culture and stressed its importance. One of the interviewers left a bad impression on me as they cut me short during my responses and asked about my weaknesses and how others might negatively perceive me.

The interview process consisted of:

• 45-minute recruiter phone screen.
• 1-hour Technical Experience Interview with two Engineers.
• 1 take-home assignment. Took me about 8 hours of time, but they give you a week to complete.
• 30-minute call with the recruiter discussing the onsite interview format.
• Full-day onsite interviewing, consisting of multiple rounds (10 am-5 pm): 1 pair programming, 1 system design, 1 behavioral interview, 1 project experience interview, 1 EM interview.

The interview did not have intense LeetCode-style coding questions, which is a plus if you don't like these.

Deep technical questions about projects you worked on in the past.

Typical behavioral questions: Why do you want to work at PayPal?

An Engineering Manager asked more difficult questions.

Weakness questions: What are areas you feel you need improvement? What negative feedback might your manager give you?