PayU Interview Experience | Set 4 (For Fresher)
Interview Experience
Here's my interview experience at PayU india (fresher). Round 1Firstly, a discussion of projects in resume and a detailed chat on my internship1. Search for an element in ...
Full Details
Here's my interview experience at PayU india (fresher). Round 1 Firstly, a discussion of projects in resume and a detailed chat on my internship 1. Search for an element in a pivoted array. (Only logic and pseudo code ) 2. Find middle node of a linked list. (Tested a lot by asking questions) 3. LCA in binary tree. (Complete code was required). 4. A puzzle which I can't recollect. (Was not common ) 5. Was asked to design corpus search engine. He told me the basics and I gave ideas based on what I could think of . (Came close to a good design) 6. Some OS questions like mutex and paging. This round well and I qualified for
next round. Round 2 Again, a detailed discussion on projects and internship. This round had very less DSA. 1. https://www.geeksforgeeks.org/ given-only-a-pointer-to-a- node-to-be-deleted-in-a- singly-linked-list-how-do-you- delete-it/ 2. https://www.techinterview.org/ post/526370758/100-doors-in-a- row/ (With proof) 3. Asked about semaphores, race conditions, deadlock etc. Asked me to implement a situation. 4. Databases - Gave some data in the form of tables and asked questions on inner join, normalization etc. 5. Again a very hard puzzle, can't remember it. (Was not common ) This round didn't go well as I was not good at OS and DBMS. So, prepare those sections as well apart from DSA. I was
rejected after this round. All Practice Problems for PayU !
About This Question
This is a candidate experience report from a payu interview for a swe role (intern level) during the phone screen round reported in 2025.
It covers the following topics: Linked List, Trees, Binary Tree, Sql, Os, Arrays .
Difficulty rating: Hard
Topics
About Payu Interview Reports
This question was reported by a candidate who interviewed at Payu. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Payu are the higher-signal extractions to take from this report.
For broader preparation context, the Payu interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Payu reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Payu Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Payu reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.