Juspay Interview Experience | SDE (6-Month Internship + FTE) | On-Campus Placement 2026

Company: Juspay
Role: Software Development Engineer (6-Month Internship + Full-Time Employment)
Notification Date: September 23, 2026
Drive Date: September 29, 2026
Final Result: Selected 🎉

Hi everyone! a final-year B.Tech CSE student. I’m sharing my Juspay interview experience to help others preparing for similar opportunities.

The entire selection process, from the Online Assessment (OA) to both technical interviews, was conducted on the same day. Since we received the notification only a few days before the drive, there wasn’t much time to prepare specifically for Juspay.

Nevertheless, I was fortunate to clear all the rounds and receive an offer. Here’s how the process unfolded.

Selection Process

The selection process consisted of three stages:

1. Online Assessment (3 hours): One coding question, conducted as a hackathon round.
2. MCQ Round (1 hour): 16 questions covering Core Computer Science, Physics, and Mathematics.
3. Technical Interviews: Two rounds, each lasting approximately 1.5 hours.

The entire process was conducted on a single day, making it quite demanding in terms of both preparation and endurance.

Round 1: Online Assessment (OA)

The OA consisted of a single, implementation-heavy coding question with a time limit of three hours.

I was able to solve the problem in approximately 1.5 hours and submit my solution.

The shortlist was released at around 2:15 PM, and shortlisted candidates were asked to report for the MCQ round at 2:30 PM.

Round 2: MCQ Round

The MCQ round consisted of 16 questions to be solved in one hour.

The questions covered:

• Core Computer Science subjects
• Physics
• Mathematics

I was able to solve 15 out of the 16 questions.

After this round, we had to wait for the interview schedule. The interviews were scheduled to begin at around 6 PM.

Round 3: Technical Interview 1

Duration: Approximately 1.5 hours
Mode: Online, conducted at the TPO

The interview began with a brief introduction. The interviewer asked me how I had started coding and what had motivated me to pursue Competitive Programming (CP).

After discussing my coding journey and profile, the interviewer was impressed with my CP background and decided to skip the DSA portion.

1. Projects and Technical Fundamentals

The interviewer asked me to walk through the projects mentioned on my resume. I briefly explained each project and the technologies I had used.

He then asked follow-up questions about the technical concepts and keywords mentioned in my project descriptions, including:

• JWT and authentication
• OAuth 2.0
• Hosting and deployment
• Forgot-password and password-recovery flows

The questions were not limited to definitions. I had to explain how these concepts worked and how they were used in my projects.

2. System Design Through Real-World Scenarios

This was one of the most interesting parts of the interview.

Instead of directly asking conventional system design questions, the interviewer introduced scenarios based on my projects and gradually added more complexity.

Some of the topics discussed were:

• DNS resolution: How does a browser discover the IP address of a website?
• Scalability: How would you handle an increasing number of users?
• Scaling strategies: Horizontal scaling vs. vertical scaling
• Availability and load balancing
• Caching and Redis
• Content Delivery Networks (CDNs)
• Rate limiting and API gateways
• Consistent hashing
• Data centres and availability zones
• Microservices architecture
• Deployment strategies and Docker

These are the major topics I remember, although there were several other questions as well.

The interviewer kept introducing new constraints and scenarios, which required me to think about how the system would behave as it grew.

3. Operating System Concepts

Towards the end, the interviewer moved to Operating Systems and again used scenario-based questions rather than simply asking for textbook definitions.

I was able to answer most of the questions throughout the round.

There were instances when I couldn't immediately understand what the interviewer was asking or what a particular scenario implied. Whenever that happened, I politely asked him to repeat or rephrase the question.

He was cooperative and happy to clarify whenever required.

Overall, the round went well. The interviewer mentioned that he was impressed with my answers.

Round 4: Technical Interview 2

Duration: Approximately 1.5 hours

This round deserves a special mention because of the long wait.

My second interview started at around 1:30 AM on September 30. Yes, the time is correct!

After waiting for several hours, the TPR informed me that my next round would begin in five minutes. I was then called into the interview room.

The interviewers were supportive and cooperative throughout the discussion.

1. Verifying My OA Submission

The interviewer opened my OA submission and asked whether the submitted solution was mine. I confirmed that it was.

He then gave me a sample test case and asked me to perform a dry run of my implementation.

After that, he asked several follow-up questions about my approach and implementation. I was able to explain my solution and answer the questions.

I believe this discussion was particularly important because the OA had only one question, with a three-hour time limit, and was highly implementation-oriented.

2. DSA: Majority Element

Next, I was given a DSA problem: Find the Majority Element in an Array, a problem commonly covered in Striver's A2Z DSA Sheet.

I explained my approach in detail, including the reasoning behind it. However, I struggled to write the code correctly.

Despite this, the interviewer was understanding, and we moved forward with the discussion.

My takeaway from this part was that explaining your reasoning clearly is valuable, even when you struggle to implement the solution perfectly. Of course, this doesn't mean coding practice can be neglected.

3. In-Depth Project Discussion

At this point, another interviewer joined the discussion, and the focus shifted heavily towards my projects.

I had mentioned features such as navigation, ETA calculation, and Google Maps integration in my resume. The interviewers asked me to explain my approach and how I would implement these features from scratch.

Some of the questions and topics included:

• How would you build a navigation system?
• How would you calculate the estimated time of arrival (ETA)?
• How would you approach implementing map-based features?
• How does Dijkstra's algorithm work?
• Can Dijkstra's algorithm be used in a navigation system?

The discussion went beyond simply explaining which APIs or libraries I had used. I needed to demonstrate that I understood the underlying concepts and could reason about implementing the functionality myself.

4. Redis Geospatial Features

One particularly interesting question involved Redis and geospatial data.

The interviewer described a scenario in which a map displays a particular geographical area. As the user zooms in or out, the application should return the number of active users within the visible area.

The question was based on Redis's geospatial capabilities.

Reference: https://redis.io/docs/latest/develop/data-types/geospatial/

I proposed an alternative approach using Redis. Although my approach differed from the feature the interviewer had in mind, the discussion gave me an opportunity to explain my reasoning and explore the problem from a system design perspective.

5. General Discussion

Towards the end, we discussed my family background and hobbies.

The interview concluded after approximately 1.5 hours.

A few minutes later, the TPR informed me that I had been selected for the role!

After such a long day and an interview extending into the early hours of the next morning, receiving that confirmation was a wonderful feeling.

Final Result: Selected!

Looking back, the process tested much more than DSA alone. It evaluated my understanding of computer science fundamentals, my ability to reason about system design, my knowledge of my own projects, and how effectively I communicated under pressure.

Here are the key lessons I took away from the experience.

Key Takeaways and Advice

1. Be confident, but stay honest.

You don't need to know the answer to every question. What matters is how you approach unfamiliar problems, explain your reasoning, and respond to feedback.

2. Take your time to think.

If you need a moment to structure your thoughts, communicate that to the interviewer. A thoughtful answer is better than a rushed one.

3. Ask clarifying questions.

This was one of the most important lessons from my interviews. Don't assume that you have understood the problem correctly. Clarify ambiguous requirements, ask the interviewer to restate a scenario if necessary, and explicitly mention any assumptions you make.

4. Know your projects inside out.

Anything mentioned on your resume can become a starting point for an in-depth discussion. Be prepared to explain not only what you built, but also why you chose a particular technology, how the implementation works, what its limitations are, and how you would build it from scratch.

5. Strengthen your Core CS fundamentals.

Prepare OS, DBMS, Computer Networks, and OOP alongside DSA. Also practise applying these concepts to real-world situations rather than memorising definitions.

6. Keep practising DSA and Competitive Programming.

A strong coding profile can help you stand out, but it doesn't replace the ability to solve problems and implement solutions during an interview. Keep practising, revising, and learning from your mistakes.

7. Be patient with the placement process.

This was my fourth interview of the placement season. Before Juspay, I had interviewed with UKG, InMobi, and TetriFox.

Placement season can be stressful and unpredictable. Sometimes, despite your preparation, things don't work out. Keep improving rather than letting individual setbacks define your progress.

Final Words

Placements can be stressful, unpredictable, and sometimes heavily dependent on timing and luck. But don't let that become a reason to stop preparing.

Keep revising your concepts, practising DSA, building meaningful projects, and learning from every interview.

There may be delays, rejections, and difficult days along the way, but consistency matters.

“Jab lagni hogi, tab lag hi jayegi. Jab tumhara din aayega, toh sab tumhare favour mein hoga.”

Keep working hard and trust the process. Your opportunity may come when you least expect it.

All the best to everyone preparing for placements!