Paypal

I went through the recruitment process for a Software Engineer Intern position at PayPal through my college. The process started with an online assessment containing multiple coding problems. The questions were mostly based on standard DSA concepts, but the time constraint made the assessment slightly tricky. I encountered problems involving arrays, hashing, and basic graph traversal. The main challenge was deciding quickly which approach would be efficient enough rather than spending too much time on brute-force ideas. After the assessment, I was shortlisted for the interview stage, which consisted of two technical rounds. Each round lasted around 45 minutes and was heavily tilted towards DSA and problem solving. The first round began with a short introduction, after which the interviewer immediately moved into coding. I was given an array-based problem where I first explained a simple approach and then optimized it using a more efficient data structure. The interviewer kept throwing small variations at me, especially around duplicate values and edge cases. Another question involved a linked list, where pointer manipulation became the main headache. I reached the correct approach but made a small implementation mistake initially and had to trace the pointers manually to fix it. The second round felt more intense. I was asked a binary-tree traversal problem followed by a dynamic-programming question. I was able to solve the tree problem and explain the complexity properly. The DP question was more convoluted, and although I identified the state and recurrence, I couldn't completely finish the implementation within the available time. There was also a brief conversation about my projects, mainly focusing on why I selected certain technologies and what parts I personally implemented. The interviews were predominantly DSA-oriented, with very little emphasis on traditional core-subject theory. Ultimately, I received a rejection. The experience taught me that solving familiar patterns is not enough; interview performance also depends heavily on speed, communication, debugging, and adapting when the problem takes an unexpected turn.