HR interview questions
Common Paytm HR questions, sample answer frames, and STAR tips.
Paytm Interview Experiences
How Paytm fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
For fresher tech roles, Paytm usually runs Online Assessment (90 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), HR / Culture (20-30 min). Campus and off-campus patterns differ slightly, trust the drive college placement email over older PDFs.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | Coding (DSA) + sometimes MCQs |
| Technical Round 1 | 45-60 min | Live coding on linked lists/trees, DSA fundamentals |
| Technical Round 2 | 45-60 min | Core Java, OOPs, DBMS, networking, project discussion |
| HR / Culture | 20-30 min | Motivation, integrity, relocation |
Real interview experiences
Section titled “Real interview experiences”Rewritten from public student write-ups of Paytm’s on-campus SDE and SDE-intern drives. One correction worth making up front: despite Paytm being a payments company, fresher write-ups almost never describe a payments system-design round. What they consistently describe is live coding in a shared editor on linked lists and trees, plus core Java, OOPs, DBMS, and networking. Prepare for that, not for a UPI architecture whiteboard.
Experience 1: SDE intern + FTE, on-campus (selected)
Section titled “Experience 1: SDE intern + FTE, on-campus (selected)”Source: Paytm Interview Experience for SDE Intern + FTE (On-Campus) - GeeksforGeeks
Round 1 - data structures
- Introduction and project discussion.
- Reverse a linked list, asked both iteratively with pointers and recursively.
- Print the left view of a binary tree.
- Time and space complexity had to be stated for each solution.
Round 2 - mixed technical
- Minimum number of hotel rooms needed (an interval-scheduling problem).
- Networking basics, down to “what does HTTP stand for.”
- DBMS: SQL joins, ACID properties, constraints.
- The interviewer pushed for optimisation after the first working solution.
Round 3 - OOP and problem-solving
- Behavioural opening about the college journey so far.
- Find the median in a stream of integers.
- OOP fundamentals: types of inheritance, overloading vs overriding, access specifiers.
Format note: all rounds were on Google Meet with code written in a plain shared text editor - no autocomplete, no compiler. Practise writing compilable code without an IDE.
Result: Selected as SDE.
Commonly reported pattern across other Paytm drives
Section titled “Commonly reported pattern across other Paytm drives”- Round 1 is a HackerRank coding round, typically 2 DSA questions - one easy string problem and one harder graph-level problem.
- Recurring coding questions across write-ups: zig-zag (spiral) tree traversal, right view of a binary tree, merge two sorted linked lists without extra space, reverse a linked list recursively, lowest common ancestor in a BST, median in a stream.
- Java is the expected language in many panels, and Java-specific questions follow: Java 8 features, abstraction vs encapsulation, abstract class vs interface.
- The HR round is described as light in most accounts - casual conversation about the team and future scope, with nearly everyone who reaches it clearing it. That is the opposite of the Meesho pattern, so do not generalise between fintechs.
Sources: Paytm SDE On-Campus 2021 · Paytm SDE-1 (On-Campus) · Paytm SDE (On-Campus)
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Design an LRU cache. Usually expects HashMap + doubly linked list
- Implement a rate limiter. Usually expects sliding window / token bucket
- Merge overlapping time intervals. Usually expects sort + sweep
- Discussion on wallet transactions and UPI flows, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why fintech / payments?
- A production bug or outage you helped with
- An integrity / pressure scenario
- Joining timeline
Practical tips for Paytm
Section titled “Practical tips for Paytm”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain wallet transactions in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Paytm panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Paytm usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.