I applied online. The process took 3 weeks. I interviewed at Sarvaha Systems (Chennai) in Feb 2026
Interview
The interview process consisted of four rounds followed by a final discussion. The first round was an online technical test to assess fundamental knowledge. The second round was with the CEO, focusing on multithreading concepts and a machine coding exercise. The third and fourth rounds were with the client, covering Ruby on Rails from basic to advanced topics, including database optimization, application architecture, and multithreading. The final discussion was about compensation and overall expectations.
Interview questions [1]
Question 1
One key topic they focused on was multithreading in Ruby on Rails. They asked me to explain how multithreading works in Ruby, how concurrency is handled, and in which real-world scenarios it can be applied. As part of the discussion, they also gave me a machine coding problem to implement a rate limiter. I explained the approach, discussed thread safety considerations, and described how to manage shared resources efficiently to avoid race conditions while maintaining performance.
I applied online. I interviewed at Sarvaha Systems
Interview
There were 3 rounds - coding & system design Interview. First one was with the founder - where he checked the basics of multithreading. Was given a sample program to code, second one was also based on similar concepts, threads, Sidekiq, small system design questions. A problem around leaky bucket algorithm using threads. Last one was System design
Interview was conducted by the founder and focused on multithreading, but it felt unstructured and confusing. The problem statement was vague, and even after discussion, it was unclear what was actually being asked, appeared that the interviewer himself was unsure of the requirement.
The interviewer is not from a Ruby background, which made it difficult to have a meaningful technical discussion. Standard Ruby tools like Sidekiq were dismissed as “outdated” simply because the answer didn’t align with his expectations. This shows a lack of understanding that there can be multiple valid solutions to the same problem.
The process felt outdated, poorly prepared, and misaligned with real-world Ruby development. The company should have a competent Ruby interviewer instead of the founder handling technical rounds. Overall, it was a waste of time and an unnecessarily frustrating experience.
Interview questions [1]
Question 1
Lots of uncleared things asked. I got the same feedback from other known ruby devs as well.