Paypal Software Engineer Interview Guide

PayPal's Software Engineer interviews vary by team, but the reported loops share a recognizable shape: an early screen, one or more coding rounds, a design conversation for experienced hires, and a behavioral or managerial close. One checkout-team candidate started with a Karat coding screen of two easy-to-medium JavaScript problems, followed by a recruiter call about career trajectory and interest in PayPal. An intern applicant instead submitted a recorded video application, then had a recruiter call and two technical interviews.

The coding bar is generally easy-to-medium DSA, with hashmaps showing up repeatedly. Reported problems include counting character frequencies in a string, a medium problem about platforms, and a vowel-related string question where the interviewer wanted better than brute-force complexity. Expect fundamentals checks tied to the team's stack. One candidate was pressed on Java internals such as the Singleton pattern, HashMap internals, exception handling, and immutable class design. A React-focused loop tested useState and useReducer through code-output questions. One loop included a code review of a small Python database class, and another deliberately used a very easy problem to judge how clearly the candidate explained their thinking and collaborated.

For experienced hires, a design round is common. Reported prompts include designing a reviews service, and walking through the high-level design of a past project before designing a REST API and database schema for a peer-to-peer chat app. A behavioral or managerial round covering past work and conflict with teammates usually closes the loop. Reported timelines range from about two weeks to about a month. One candidate never heard back after the final round, so a polite recruiter follow-up is reasonable if things go quiet.