My Interview Experience: Keploy (Two Attempts)
Keploy holds a special place for me — it was my first-ever interview experience, and I ended up going through the process with them twice, about a year apart.
How it started
I was part of the Keploy fellowship, and applied directly through their portal. That’s what got me the shot at an interview. I got a call from HR saying I’d been shortlisted — and the interview was scheduled for the very next day. From what I gathered, that’s just how Keploy tends to operate: they move fast, and you often don’t get much lead time to prepare. Lesson learned — with a process like this, you have to stay interview-ready all the time, not just when you know one’s coming.
First attempt (R1)
The round was taken by an SDE1 who’d actually done GSoC under Keploy herself, then joined as an intern, and eventually converted to full-time.
It opened with an intro, then a quick resume discussion — about 5 minutes — before she moved straight to a DSA problem, with the plan to come back to the resume if time allowed later.
The problem was a medium-hard, DP-based problem, something related to subsequences (the exact details are fuzzy now, since this was about a year and a half before I’m writing this). We worked through it together for about half an hour, but I wasn’t able to fully solve it — my DSA fundamentals weren’t where they needed to be at that point.
After the technical part, she was generous enough to share her own experience working at Keploy and her GSoC journey with them, which was genuinely interesting to hear.
Get Divyanshu Rajput’s stories in your inbox
Join Medium for free to get updates from this writer.
I didn’t clear this round.
Verdict — Rejected
Second attempt, a year later
I got another shot at Keploy about a year after the first attempt. Same warm intro to start.
This interviewer was also GSoC and LFX qualified. We didn’t spend much time on background this time — he moved fairly quickly into a problem, an advanced graph problem pulled from the NeetCode 150 sheet.
I actually cracked the approach and started building out the solution, but ran out of time before I could finish coding it end-to-end. Close, but not quite there within the time limit.
Rejected again after R1.
Verdict — Rejected
What stuck with me
Even with two rejections, both experiences were genuinely good ones. The Keploy team is warm and easy to talk to — it never felt like a high-pressure interrogation, more like a conversation with someone who actually wanted you to do well. If anything, it’s part of why I keep coming back.
LinkedIn: https://linkedin.com/in/divyanshu-rajput8171
Portfolio: https://divyanshu-rajput.vercel.app
