My Juspay SDE Intern Interview Experience (Summer)

I recently had the opportunity to participate in the Juspay SDE Intern hiring process during the summer. It was a challenging yet insightful experience consisting of six rounds. Unfortunately, I couldn’t make it through the final round, but I learned a lot through the process. Here’s a detailed breakdown of my experience:

Round 1: Aptitude Test (Online)

• Strength: ~300 candidates
• Duration: 1 hour
• Topics: OS, CN, Math, DSA fundamentals
• Cutoff: 50% marks required to qualify for the next round

The first round focused on basic problem-solving and conceptual understanding of computer science fundamentals. The questions were straightforward but required quick thinking and accuracy.

Round 2: DSA Round

• Strength: ~180 candidates
• Duration: 3 hours
• Topics: Trees, Graphs, Strings (3 questions)
• Cutoff: 200/300 (solving at least two questions)

The DSA round was intense, with a focus on problem-solving using efficient algorithms and data structures. I managed to solve two questions, which helped me qualify for the next round.

Round 3: Hackathon (Part A)

• Strength: ~35 candidates
• Duration: 3 hours
• Topic: Tree Operations (Implement Lock, Unlock, and Upgrade functions)
• Cutoff: 200/300

This round was quite challenging. We had to implement functions on a tree structure and ensure that the solution was both efficient and logically sound.

Round 4: Elimination Round (Anti-Cheating Verification)

• Strength: ~23 candidates
• Duration: 2 hours
• Topics: Hashing, Backtracking (2 questions)

This was an integrity check to filter out any potential unfair play. We had to share our screens and keep our cameras on while solving the questions. Both questions were of moderate difficulty but required careful thought.
https://leetcode.com/discuss/post/6538620/juspay-elimination-round-interview-exper-acnu/

Round 5: Hackathon (Part B)

• Strength: ~13 candidates
• Duration: Usually 11 AM – 8 PM, but mine lasted for 2 days
• Tasks:
  1. Explain the solution of Part A
  2. Improve the time complexity of the solution
  3. Implement a thread-safe solution without using external libraries or atomic variables

This was the most difficult round. Debugging and optimizing the solution while ensuring thread safety without relying on standard libraries made it highly complex. The round tested both my problem-solving and coding skills under pressure.

Round 6: System Design + Technical Interview

• Strength: ~9 candidates
• Duration: 2 hours 15 minutes
• Topics: OS, CN, CNS, System Design
• Questions:
  1. How does YouTube differentiate between requests from:
     • Two tabs playing YouTube on the same laptop
     • Two different laptops on the same network
     • two laptops connected to different Network
  2. How are files uploaded to Google Drive and shared between two systems?
  3. Compiler vs Interpreter — I was asked to improve the runtime of the following interpreted language code:

  Function f(int c) {
      c++;
      print(c);
      return c;
  }
  main {
      int c=0;
      for(int i = 0; i < 1000; i++) c = f(c);
  }
  (Hint: The function call is redundant and can be cached to improve performance)

The system interview was highly conceptual and challenging. The questions tested deep knowledge of OS and networking concepts along with optimization techniques.

Final Verdict: ❌ Rejected

I felt the questions in the final round were a bit tougher compared to my peers, but it was a great learning experience. This process helped me identify areas for improvement, especially in system design and optimization. I'll work on strengthening these areas and come back stronger next time!

👉 If you’ve faced similar experiences or have any suggestions, feel free to share them in the comments!.