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.