Scribd
Upload
44 views2 pages

Juspay Interview Experience

The document details a candidate's interview experience for Juspay, which included multiple rounds focusing on aptitude, computer science fundamentals, coding assessments, and system design discussions. The final round involved behavioral and technical questions, emphasizing the candidate's ability to communicate and think critically under pressure. Ultimately, the candidate received a job offer after successfully navigating the rigorous interview process.

Uploaded by

known61234098
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
44 views2 pages

Juspay Interview Experience

The document details a candidate's interview experience for Juspay, which included multiple rounds focusing on aptitude, computer science fundamentals, coding assessments, and system design discussions. The final round involved behavioral and technical questions, emphasizing the candidate's ability to communicate and think critically under pressure. Ultimately, the candidate received a job offer after successfully navigating the rigorous interview process.

Uploaded by

known61234098
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Juspay Interview Experience ​

I participated in the Juspay Hiring Challenge 2024 and received an offer through it.

Round 1: Aptitude MCQ


This round was purely aptitude-based. Speed and accuracy were critical. It's better to solve 10
easy/medium questions than waste time on 3 difficult ones. Choose your questions wisely as time is limited.
.​
Round 2: CS Fundamentals MCQ
This round was a bit unexpected. Though it was MCQ again, it focused on computer science fundamentals
(OS, DBMS, CN, etc.) along with basic engineering-level Maths and Physics. Stuff like solving equations
using logs, basic integrals, and simple physics concepts like mass, work, energy. Nothing too deep—more
about general awareness and logical thinking.

Round 3: Online Assessment​


This round had three coding questions with a total duration of 3 hours:
●​ 1.5 hours for Q1 and Q2: One was a medium-level binary search + math problem, and the other
was a graph problem.
●​ 1.5 hours for Q3: A challenging problem based on M-ary trees where we had to implement 3 core
functions for the problems.

Round 4: Hackathon + Deep Dive​


This was a full-day virtual hackathon via Slack and Meet. Juspay has a unique process here—it wasn’t
building a project, but instead a deep dive into the 3rd question of Round 3.
●​ 11:00 - 13:00 I started by explaining my solution and was asked to optimize it until it was solid.This
felt like absolute grilling because the solution I presented was optimal but the interviewer was not
satisfied and wanted me to do more.
●​ 14:00 - 17:30 Then after lunch came system-level discussions: threading, concurrency,
semaphores, mutexes, etc. I had to implement a thread-safe version of the same problem. Each
code block I wrote was discussed in detail. This was an extension to the previous question itself
where we had to make it thread safe. I had to give reasoning for every thing I did, and explain and
dry run test cases how threading would work, deadlocks, race conditions etc before implementing
anything. The interviewer was supportive and pointed out potential issues that might arise.
●​ 17:30-18:00 The focus shifted to my internships. We discussed the IIT Bombay AIML work in
depth—topics like the dataset pipeline, model optimization, and use cases. And he asked me open
ended questions about LLMs and since I mentioned I have worked with LLMs and studied about it I
was asked to explain the architecture to it as well and how things actually work.
●​ 18:00-19:30 The focus was again shifted to problem solving and I I was given a DSA question on
string manipulation. Solved it from brute-force to optimal solution within 20/25 minutes. After this I
got another DSA question based on dynamic programming. This took more time as the interviewer
kept pushing for optimizations and lots of dry running before writing the code.

This round wasn’t like a standard coding interview. It was a full-day stress test, assessing my depth of
understanding, ability to handle pressure, and communication over long discussions. Along with the things I
mentioned above, small things here and there from the core subjects like DBMS, OOPS, SQL etc were
asked in between (more like brain teasers).

Round 5: 1:1 with Senior Engineer (UPI Team)


The round started casually with a chat about my background, internships, and what I’ve worked on in
college. Then came a coding problem — a variation of the Rotten Oranges problem involving multi-source
BFS. I explained the logic, wrote a clean solution, and handled a few follow-up questions about edge cases
and time/space complexity. I finished it in about 20 minutes.
Since my resume was filled with ML and Backend, he switched to ML next. He asked me to explain why ML
is even needed, and then went into Gradient Descent vs. Ascent — not in code, but the math behind weight
updates and the actual derivation (very unexpected but luckily we had covered it in our syllabus so was
able to finish it off). He tested if I actually knew ML or it was just about using sklearn to fit models. Then a
small discussion on the research paper I had published.

Next, we dove into OS and DBMS concepts. The main focus was on thread safety, which makes sense
since Juspay is a payment platform. We discussed how race conditions happen, what mutexes and
semaphores are, and how to write thread-safe code. He wanted practical understanding, not just
definitions. For DBMS, he asked me a couple of SQL queries and the standard questions like ACID
properties, SQL vs NoSQL, what are transactions etc. The round wrapped up with a casual conversation
around GPA, academics, and time management. He appreciated that I maintained a good GPA while doing
internships and projects consistently. Overall, this round felt like a solid mix of DSA, systems, and
resume-based deep dive.

Round 6: Final Round (Behavior + Tech) - ​


This round lasted about 3 hours in the evening and happened right in the middle of my end-sem exams — I
had my ML-IV paper the very next day — so I was a bit nervous going in. It was taken by a very senior
engineer from the UPI team, and as I had been informed by the interviewer, this round had no fixed
structure.

The first question helped me personally break the ice because he asked “How have you managed to do so
many internships while maintaining such a good GPA?” A general tip is to prepare such generic questions
well in advance so you are able to give very well structured answers on the spot. And apart from the
technical knowledge you have - communication skills matter a lot, even when you don’t know an answer
you should know how to rightly convey your lack of knowledge in that domain to the interviewer.

Then came a completely unexpected question: “What happens when you press a key on a mechanical
keyboard?” At first, I was thrown off, but I started talking about what I knew — from keypress to scan codes,
OS interrupt handling, to rendering characters on the screen. We had a long, back-and-forth discussion
here. He wasn’t looking for a textbook answer — just wanted to see how I thought and broke things down
under pressure.

After that we discussed my OFSS internship in detail and, he asked: “Why would you prefer Juspay over
Oracle, especially since you have a PPO?” This led to a 45-minute monologue from him, where he shared
Juspay’s origin story — how they started before UPI existed, the challenges they faced, the scale they
operate at now. It honestly didn’t feel like an interview at that point — more like him telling their learning and
mistakes over the years which helped them grow as a company.

We then jumped into DBMS design questions — around sharding, indexing strategies, trade-offs in
distributed systems — followed by OS and OOPS concepts. No coding was required here, but I had to
explain everything at an architectural and design level. He then picked one of my full-stack projects and
asked me to deep dive — the DB schema, API designs, which stack and why, which DB and why, how I
handled failures, etc. He really grilled me on why I chose what I chose and is that even needed.

Before wrapping up, he asked a few offbeat, open-ended questions like: “Why is the hypotenuse the
longest side of a right-angled triangle? Can you prove it?” We had a fun discussion on the math behind it —
he just wanted to see how I think when put on the spot. There were a few more random questions as well
and I don’t think any preparation is needed on such questions as they are doable then and there itself.

To end the interview, he asked about my family background, where I come from, long-term goals, whether I
plan to pursue an MS, and what really drives me.

1 week later I got the offer.

You might also like