paypay logo
Paypay· Backend Engineer

Backend Engineer | PayPay

Experience
4 years
Posted
31 Jul 2025
661 reads

Summary

I interviewed for a Backend Engineer position at PayPay, going through three rounds that covered DSA, system design, and resume discussions. Despite my efforts, I was ultimately rejected.

How it went

Current YOE : 4 Current Organisation : PBC TC : 26 Base + 10% Var

First Round (60 mins): The interviewer seemed really nice the first 30 mins asked about the most challenging project dug deeper on the same, asked me about the different concepts like REST APIs, SQL vs NoSQL etc and some java concepts. The last 30 mins was DSA question where they asked this question : Given an input in this format : [fileID, CollectionId, fileSize] find the topK collections based on their size of files inside them. The filesystem was like this - FileSystem contains Collection which in turn contains Files. Gave the heap approach selected for the next round.

Second Round (60 mins) : Asked me about a few questions based on my resume, then gave a Graph question : https://leetcode.com/problems/min-cost-to-connect-all-points/description/ . Post this we had a discussion related to API design and LLD of a notification system (Was just asked how would I approach this not asked to code it like which design pattern would you use given a certain scenario.)

Third Round (60 mins) : System Design Round was asked to Design a PasteBin Service asked the FR and the NFR they were as follows -

- The user  should be able to paste code/file (upto 5GB) in the service and should then get a URL.
- This URL should be sharable and then should allow anyone receiving it to open the same and see the contents of the file.
- The amount of time the file should persist should be customisable but at max 6 months.
- Around 600 M monthly active users should be handled.

My Approach : I proposed a 2 step design - Storage service and then URL generation service. But was not able to answer questions like how much compute qould be required in case 100 concurrent users upload 5GB files or how would we handle the larger files should we chunk it? What compute would be required in that case. I think I was wrong from the get go itself in generating the URLs and then uploading a file or first uploading a file and then generating the URL.

Verdict : Rejected Hope it helps.

Questions asked (4)

  1. 01

    Top K Collections by File Size

    Data Structures & Algorithms

    Given an input in this format: [fileID, CollectionId, fileSize]. Find the top K collections based on their size of files inside them. The filesystem was like this - FileSystem contains Collection which in turn contains Files.

  2. 02

    Min Cost to Connect All Points

    Data Structures & Algorithms

    A graph question.

    Open the problem
  3. 03

    API Design and LLD of a Notification System

    System Design

    Discussion related to API design and low-level design (LLD) of a notification system. I was asked how I would approach this, focusing on design patterns for a given scenario, not asked to code.

  4. 04

    Design a PasteBin Service

    System Design

    Design a PasteBin Service with the following functional and non-functional requirements:

    • The user should be able to paste code/file (upto 5GB) in the service and should then get a URL.
    • This URL should be sharable and then should allow anyone receiving it to open the same and see the contents of the file.
    • The amount of time the file should persist should be customisable but at max 6 months.
    • Around 600 M monthly active users should be handled.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Paypay recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!