Juspay SDE-Intern Experience

In June 2025, I applied for the Juspay Hiring Challenge 2025 through Unstop. At that time, I didn’t expect how long and demanding this journey would turn out to be.

More than 2 lakh+ candidates registered for the challenge, making it one of the most competitive hiring processes I’ve ever been part of.

What followed was a multi-month elimination marathon spanning MCQs, multiple coding rounds, hackathons, platform switches, and interviews

---

📌 Round 1 – MCQ Assessment (July 2025)

• Platform: Unstop
• Type: Objective (MCQs)
• Timeline: July 2025

This was the initial screening round consisting of core CS fundamentals, aptitude, and logical reasoning.

Result:
Out of 2 lakh+ applicants, 9,754 candidates were shortlisted for Round 2.
Source: Unstop Round 1 Result

---

📌 Round 2 – MCQ Assessment (July 2025)

• Platform: Unstop
• Type: Advanced MCQs
• Timeline: July 2025

This round went deeper into analytical thinking and computer science concepts.

Result:
Only 4,389 candidates advanced to the next round.
Source: Unstop Round 2 Result

---

📌 Round 3 – Coding Round (August 2025)

• Platform: Unstop
• Type: Coding (DSA-based)
• Timeline: 29 August 2025

This was the first major coding elimination round.

Result:
Just 1,443 candidates were shortlisted after this stage.
Source: Unstop Round 3 Result

---

📌 Round 4 – Hackathon Part A (Tree of Space Problem)

• Platform: HackerEarth
• Type: Hackathon (Design + Problem Solving)
• Timeline: September 2025

This round introduced a design-heavy problem called Tree of Space, focused on data structures, efficiency, and scalability. Since it was not hosted on Unstop, exact shortlisting numbers were not disclosed.

I successfully implemented Lock, Unlock, Upgrade and submitted my solution.

---

📌 Round 5 – Coding Round (October 2025)

• Platform: WeCP
• Type: Coding
• Timeline: October 2025

This was another elimination coding round, conducted on a completely different platform.

Result:
I cleared this round as well.

---

📌 Round 6 – Elimination Interview (November 2025)

In early November, I received a mail stating that an Elimination Round Interview would be conducted in the first week of November. However, no interview was scheduled, and there were no updates for almost one month.

After waiting patiently, I mailed Juspay for clarification. The very next day, my elimination interview was suddenly scheduled.

Result:
I cleared the elimination interview.

---

📌 Round 7 – Hackathon Part B (Final Technical Stage)

• Platform: Slack + Google Meet
• Duration: 11:00 AM – 6:00 PM
• Timeline: December 2025

This round focused on making the Tree of Space solution thread-safe. It was a full-day, highly intensive hackathon.

---

📌 Round 8 - Final Technical Discussion

The next day, HR called me to schedule a 1-hour technical interview focused entirely on my Part B solution.

The discussion covered:

Thread safety
Concurrency control
Design trade-offs
Synchronization strategies

I explained my approach, walked through my implementation, and justified every major design decision.

---

Final Outcome – Rejection

After clearing 7+ rounds over seven months (June–December 2025), I received a rejection email.

No feedback
No justification
No explanation

Just a generic rejection message.

---

Final Thoughts

This hiring process involved:

7+ elimination rounds
Multiple platforms (Unstop, WECP, HackerRank, Slack, Google Meet)
MCQs, coding rounds, hackathons, and interviews
Full-day problem-solving sessions

While rejection is part of any hiring journey, the lack of feedback after such an extensive evaluation is disappointing.

Still, the process significantly strengthened my understanding of:

• System design
• Concurrency and thread safety
• Handling long and uncertain hiring pipelines

I’m sharing this experience so future candidates know what they are signing up for and can make informed decisions.

---

If you found this helpful and are preparing for long hiring challenges like this, stay patient, focus on learning, and try not to tie effort directly to outcomes.*