cswork / libraryOpen practice workspace

Interview experiences · Juspay

Juspay Software Engineer hackathon coding and systems threshold process

RejectedTech screen

After a recruiter step, I went through a long sequence that felt closer to events than ordinary interviews. An early hackathon-style track included a live coding problem. A developer explained the prompt and stayed engaged while I worked, and the judging focused on how I wrote code and handled the engineering work as it unfolded. Later discussions covered DBMS, computer networks, operating system…

After a recruiter step, I went through a long sequence that felt closer to events than ordinary interviews. An early hackathon-style track included a live coding problem. A developer explained the prompt and stayed engaged while I worked, and the judging focused on how I wrote code and handled the engineering work as it unfolded.

Later discussions covered DBMS, computer networks, operating systems, and system-oriented technical questions. One part had a server-optimization angle and mixed algorithms with systems concepts. I also had to change and extend the earlier codework as new requirements were added.

The process used thresholds: there were minimum marks in DSA and hackathon-style rounds to reach the next stage. It was intense but not chaotic, and judged problem solving and execution. I did not receive an offer. My lasting impression was that it demanded performance across coding and systems depth, not one standout round.

Location: India. Overall feedback: Positive. Offer status: no offer.

Comments

Nothing here yet.

Join in on CSWork →