Cashfree Payments | SDE-2

cashfree payments logo
cashfree payments
SDE-24 yearsRejected
September 5, 20258 reads

Summary

I applied for an SDE-2 role at Cashfree Payments through LinkedIn and underwent two virtual interview rounds, focusing on Data Structures & Algorithms and Low-Level Design. Unfortunately, my application was rejected.

Full Experience

I had an interview experience with Cashfree Payments for the SDE-2 position. I applied via LinkedIn and my current experience is 4 years. The entire interview process was conducted virtually, consisting of two main rounds.

Round-1: Data Structures & Algorithms
This round focused on DSA and included two medium-level questions. The first question was about finding pairs in a list of song durations that sum up to a multiple of 120. The second question, which I don't recall perfectly, involved a flight dependency list and a list of delayed flights; I had to return all other flights affected by these delays. I solved this using a Breadth-First Search (BFS) approach.

Round-2: Low-Level Design
The second round was a low-level design challenge, where I was asked to design a system similar to Google Calendar. The expectations included designing appropriate classes and utility functions to handle several core functionalities: scheduling meetings for multiple users with specific start/end times, implementing recurring meetings with defined frequencies, setting user reminders, and presenting various calendar views (day, week, month).

After completing both rounds, I received a rejection.

Interview Questions (3)

Q1
Pair Divisible by 120
Data Structures & AlgorithmsMedium

Given a list of integers representing song durations, return a pair of durations such that their sum is divisible by 120.

Q2
Affected Delayed Flights
Data Structures & AlgorithmsMedium

Given a flight dependency list and a list of initially delayed flights, return a list of all other flights that will consequently be delayed.

Q3
Low-Level Design: Google Calendar
System Design

Design the low-level architecture for a Google Calendar-like system. I was expected to design classes and implement required utility functions to support the following features:

  • Schedule a meeting for a given list of users with specified start and end times.
  • Schedule recurring meetings with a defined frequency.
  • Set reminders for users.
  • Display day, week, and month calendar views for users.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

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